{"push_id":3370316105,"size":181,"distinct_size":181,"ref":"refs/heads/master","head":"3717f613f48df0222311f974cf8a06c8a6c97bae","before":"d9862cfbe2099deb83f0e9c1932c91f2d9c50464","commits":[{"sha":"44133f7eaebec227d1381868d642e3c64023520f","author":{"name":"Mathieu Malaterre","email":"4c3884f3d1d87411d98f0c382fe7d7c73faff4d0@debian.org"},"message":"genirq: Annotate implicit fall through\n\nThere is a plan to build the kernel with -Wimplicit-fallthrough. The\nfallthrough in __irq_set_trigger() lacks an annotation. Add it.\n\nSigned-off-by: Mathieu Malaterre <malat@debian.org>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nLink: https://lkml.kernel.org/r/20190114203154.17125-1-malat@debian.org","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/44133f7eaebec227d1381868d642e3c64023520f"},{"sha":"01cdfa912f1004c463586f52f1dfcbec1274b1f2","author":{"name":"Mathieu Malaterre","email":"4c3884f3d1d87411d98f0c382fe7d7c73faff4d0@debian.org"},"message":"genirq: Correctly annotate implicit fall through\n\nThere is a plan to build the kernel with -Wimplicit-fallthrough. The\nfallthrough in __handle_irq_event_percpu() has a fallthrough annotation\nwhich is followed by an additional comment and is not recognized by GCC.\n\nSeparate the 'fall through' and the rest of the comment with a dash so the\nregular expression used by GCC matches.\n\nSigned-off-by: Mathieu Malaterre <malat@debian.org>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nLink: https://lkml.kernel.org/r/20190114203633.18557-1-malat@debian.org","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/01cdfa912f1004c463586f52f1dfcbec1274b1f2"},{"sha":"a4cffdad731447217701d3bc6da4587bbb4d2cbd","author":{"name":"Paul E. McKenney","email":"1e0ce936bb9b355d257bf5790d2513c3f28be22b@linux.ibm.com"},"message":"time: Move CONTEXT_TRACKING to kernel/time/Kconfig\n\nBoth CONTEXT_TRACKING and CONTEXT_TRACKING_FORCE are currently defined\nin kernel/rcu/kconfig, which might have made sense at some point, but\nno longer does given that RCU refers to neither of these Kconfig options.\n\nTherefore move them to kernel/time/Kconfig, where the rest of the\nNO_HZ_FULL Kconfig options live.\n\nSigned-off-by: Paul E. McKenney <paulmck@linux.ibm.com>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nLink: https://lkml.kernel.org/r/20181220170525.GA12579@linux.ibm.com","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/a4cffdad731447217701d3bc6da4587bbb4d2cbd"},{"sha":"b17d1ce7efe21e075dace85658d26d354766b443","author":{"name":"Thomas Gleixner","email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de"},"message":"Merge branch 'timers/urgent' into timers/core\n\nMerge urgent fix so depending cleanup patch can be applied.","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/b17d1ce7efe21e075dace85658d26d354766b443"},{"sha":"16118794ede91aac1a73abe15de22d3de9d2b775","author":{"name":"Thomas Gleixner","email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de"},"message":"posix-cpu-timers: Remove private interval storage\n\nPosix CPU timers store the interval in private storage for historical\nreasons (it_interval used to be a non scalar representation on 32bit\nsystems). This is gone and there is no reason for duplicated storage\nanymore.\n\nUse it_interval everywhere.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: John Stultz <john.stultz@linaro.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: \"H.J. Lu\" <hjl.tools@gmail.com>\nLink: https://lkml.kernel.org/r/20190111133500.945255655@linutronix.de","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/16118794ede91aac1a73abe15de22d3de9d2b775"},{"sha":"5b735eb1ce481b2f1674a47c0995944b1cb6f5d5","author":{"name":"Andrea Parri","email":"f5020f480e2657f08122c617b5b289837e6f1f62@amarulasolutions.com"},"message":"tools/memory-model: Model smp_mb__after_unlock_lock()\n\nThe kernel documents smp_mb__after_unlock_lock() the following way:\n\n  \"Place this after a lock-acquisition primitive to guarantee that\n   an UNLOCK+LOCK pair acts as a full barrier.  This guarantee applies\n   if the UNLOCK and LOCK are executed by the same CPU or if the\n   UNLOCK and LOCK operate on the same lock variable.\"\n\nFormalize in LKMM the above guarantee by defining (new) mb-links according\nto the law:\n\n  ([M] ; po ; [UL] ; (co | po) ; [LKW] ;\n\tfencerel(After-unlock-lock) ; [M])\n\nwhere the component ([UL] ; co ; [LKW]) identifies \"UNLOCK+LOCK pairs on\nthe same lock variable\" and the component ([UL] ; po ; [LKW]) identifies\n\"UNLOCK+LOCK pairs executed by the same CPU\".\n\nIn particular, the LKMM forbids the following two behaviors (the second\nlitmus test below is based on:\n\n  Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.html\n\nc.f., Section \"Tree RCU Grace Period Memory Ordering Building Blocks\"):\n\nC after-unlock-lock-same-cpu\n\n(*\n * Result: Never\n *)\n\n{}\n\nP0(spinlock_t *s, spinlock_t *t, int *x, int *y)\n{\n\tint r0;\n\n\tspin_lock(s);\n\tWRITE_ONCE(*x, 1);\n\tspin_unlock(s);\n\tspin_lock(t);\n\tsmp_mb__after_unlock_lock();\n\tr0 = READ_ONCE(*y);\n\tspin_unlock(t);\n}\n\nP1(int *x, int *y)\n{\n\tint r0;\n\n\tWRITE_ONCE(*y, 1);\n\tsmp_mb();\n\tr0 = READ_ONCE(*x);\n}\n\nexists (0:r0=0 /\\ 1:r0=0)\n\nC after-unlock-lock-same-lock-variable\n\n(*\n * Result: Never\n *)\n\n{}\n\nP0(spinlock_t *s, int *x, int *y)\n{\n\tint r0;\n\n\tspin_lock(s);\n\tWRITE_ONCE(*x, 1);\n\tr0 = READ_ONCE(*y);\n\tspin_unlock(s);\n}\n\nP1(spinlock_t *s, int *y, int *z)\n{\n\tint r0;\n\n\tspin_lock(s);\n\tsmp_mb__after_unlock_lock();\n\tWRITE_ONCE(*y, 1);\n\tr0 = READ_ONCE(*z);\n\tspin_unlock(s);\n}\n\nP2(int *z, int *x)\n{\n\tint r0;\n\n\tWRITE_ONCE(*z, 1);\n\tsmp_mb();\n\tr0 = READ_ONCE(*x);\n}\n\nexists (0:r0=0 /\\ 1:r0=0 /\\ 2:r0=0)\n\nSigned-off-by: Andrea Parri <andrea.parri@amarulasolutions.com>\nSigned-off-by: Paul E. McKenney <paulmck@linux.ibm.com>\nCc: Akira Yokosawa <akiyks@gmail.com>\nCc: Alan Stern <stern@rowland.harvard.edu>\nCc: Boqun Feng <boqun.feng@gmail.com>\nCc: Daniel Lustig <dlustig@nvidia.com>\nCc: David Howells <dhowells@redhat.com>\nCc: Jade Alglave <j.alglave@ucl.ac.uk>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Luc Maranget <luc.maranget@inria.fr>\nCc: Nicholas Piggin <npiggin@gmail.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Will Deacon <will.deacon@arm.com>\nCc: linux-arch@vger.kernel.org\nCc: parri.andrea@gmail.com\nLink: http://lkml.kernel.org/r/20181203230451.28921-1-paulmck@linux.ibm.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/5b735eb1ce481b2f1674a47c0995944b1cb6f5d5"},{"sha":"b02eb5b0961a06561b89f5b7f0dd171b750e5789","author":{"name":"Paul E. McKenney","email":"1e0ce936bb9b355d257bf5790d2513c3f28be22b@linux.vnet.ibm.com"},"message":"tools/memory-model: Add scripts to check github litmus tests\n\nThe https://github.com/paulmckrcu/litmus repository contains a large\nnumber of C-language litmus tests that include \"Result:\" comments\npredicting the verification result.  This commit adds a number of scripts\nthat run tests on these litmus tests:\n\ncheckghlitmus.sh:\n\tRuns all litmus tests in the https://github.com/paulmckrcu/litmus\n        archive that are C-language and that have \"Result:\" comment lines\n\tdocumenting expected results, comparing the actual results to\n\tthose expected.  Clones the repository if it has not already\n\tbeen cloned into the \"tools/memory-model/litmus\" directory.\n\ninitlitmushist.sh\n\tRun all litmus tests having no more than the specified number\n\tof processes given a specified timeout, recording the results in\n\t.litmus.out files.  Clones the repository if it has not already\n\tbeen cloned into the \"tools/memory-model/litmus\" directory.\n\nnewlitmushist.sh\n\tFor all new or updated litmus tests having no more than the\n\tspecified number of processes given a specified timeout, run\n\tand record the results in .litmus.out files.\n\nchecklitmushist.sh\n\tRun all litmus tests having .litmus.out files from previous\n\tinitlitmushist.sh or newlitmushist.sh runs, comparing the\n\therd output to that of the original runs.\n\nThe above scripts will run litmus tests concurrently, by default with\none job per available CPU.  Giving any of these scripts the --help\nargument will cause them to print usage information.\n\nThis commit also adds a number of helper scripts that are not intended\nto be invoked from the command line:\n\ncmplitmushist.sh: Compare the output of two different runs of the same\n\tlitmus test.\n\njudgelitmus.sh: Compare the output of a litmus test to its \"Result:\"\n\tcomment line.\n\nparseargs.sh: Parse command-line arguments.\n\nrunlitmushist.sh: Run the litmus tests whose pathnames are provided one\n\tper line on standard input.\n\nWhile in the area, this commit also makes the existing checklitmus.sh\nand checkalllitmus.sh scripts use parseargs.sh in order to provide a\nbit of uniformity.  In addition, per-litmus-test status output is directed\nto stdout, while end-of-test summary information is directed to stderr.\nFinally, the error flag standardizes on \"!!!\" to assist those familiar\nwith rcutorture output.\n\nThe defaults for the parseargs.sh arguments may be overridden by using\nenvironment variables: LKMM_DESTDIR for --destdir, LKMM_HERD_OPTIONS\nfor --herdoptions, LKMM_JOBS for --jobs, LKMM_PROCS for --procs, and\nLKMM_TIMEOUT for --timeout.\n\n[ paulmck: History-check summary-line changes per Alan Stern feedback. ]\nSigned-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: akiyks@gmail.com\nCc: boqun.feng@gmail.com\nCc: dhowells@redhat.com\nCc: j.alglave@ucl.ac.uk\nCc: linux-arch@vger.kernel.org\nCc: luc.maranget@inria.fr\nCc: npiggin@gmail.com\nCc: parri.andrea@gmail.com\nCc: stern@rowland.harvard.edu\nCc: will.deacon@arm.com\nLink: http://lkml.kernel.org/r/20181203230451.28921-2-paulmck@linux.ibm.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/b02eb5b0961a06561b89f5b7f0dd171b750e5789"},{"sha":"910cc9591d1433c2e26bd1c210844b09c699dd89","author":{"name":"Paul E. McKenney","email":"1e0ce936bb9b355d257bf5790d2513c3f28be22b@linux.vnet.ibm.com"},"message":"tools/memory-model: Make scripts take \"-j\" abbreviation for \"--jobs\"\n\nThe \"--jobs\" argument to the litmus-test scripts is similar to the \"-jN\"\nargument to \"make\", so this commit allows the \"-jN\" form as well.  While\nin the area, it also prohibits the various forms of \"-j0\".\n\nSuggested-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: akiyks@gmail.com\nCc: boqun.feng@gmail.com\nCc: dhowells@redhat.com\nCc: j.alglave@ucl.ac.uk\nCc: linux-arch@vger.kernel.org\nCc: luc.maranget@inria.fr\nCc: npiggin@gmail.com\nCc: parri.andrea@gmail.com\nCc: will.deacon@arm.com\nLink: http://lkml.kernel.org/r/20181203230451.28921-3-paulmck@linux.ibm.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/910cc9591d1433c2e26bd1c210844b09c699dd89"},{"sha":"74cd2184833f8346a3e7f99b24097b3e25d41e11","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"ia64: add __NR_umount2 definition\n\nOther architectures commonly use __NR_umount2 for sys_umount,\nonly ia64 and alpha use __NR_umount here. In order to synchronize\nthe generated tables, use umount2 like everyone else, and add back\nthe old name from asm/unistd.h for compatibility.\n\nThe __IGNORE_* lines are now all obsolete and can be removed as\na side-effect.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/74cd2184833f8346a3e7f99b24097b3e25d41e11"},{"sha":"7349ee3a97edbec60ada97e81b26b9c20e96156b","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"ia64: add statx and io_pgetevents syscalls\n\nAll architectures should implement these two, so assign numbers\nand hook them up on ia64.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/7349ee3a97edbec60ada97e81b26b9c20e96156b"},{"sha":"acce2f71779c54086962fefce3833d886c655f62","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"ia64: assign syscall numbers for perf and seccomp\n\nMost architectures have assigned numbers for both seccomp and\nperf_event_open, even when they do not implement either.\n\nia64 is an exception here, so for consistency lets add numbers for both\nof them. Unless CONFIG_PERF_EVENTS and CONFIG_SECCOMP are implemented,\nthe system calls just return -ENOSYS.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/acce2f71779c54086962fefce3833d886c655f62"},{"sha":"d012d1325ba523b8ef3e55ba79c943e220154fdc","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"alpha: wire up io_pgetevents system call\n\nThe io_pgetevents system call was added in linux-4.18 but has\nno entry for alpha:\n\nwarning: #warning syscall io_pgetevents not implemented [-Wcpp]\n\nAssign a the next system call number here.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/d012d1325ba523b8ef3e55ba79c943e220154fdc"},{"sha":"12b57c5c70f397a9410411d4e348096edada20f9","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"alpha: update syscall macro definitions\n\nOther architectures commonly use __NR_umount2 for sys_umount,\nonly ia64 and alpha use __NR_umount here. In order to synchronize\nthe generated tables, use umount2 like everyone else, and add back\nthe old name from asm/unistd.h for compatibility.\n\nFor shmat, alpha uses the osf_shmat name, we can do the same thing\nhere, which means we don't have to add an entry in the __IGNORE\nlist now that shmat is mandatory everywhere\n\nalarm, creat, pause, time, and utime are optional everywhere\nthese days, no need to list them here any more.\n\nI considered also adding the regular versions of the get*id system\ncalls that have different names and calling conventions on alpha,\nwhich would further help unify the syscall ABI, but for now\nI decided against that.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/12b57c5c70f397a9410411d4e348096edada20f9"},{"sha":"78594b95998f1496e25411c6b7c7041bcb9bf7d1","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"ARM: add migrate_pages() system call\n\nThe migrate_pages system call has an assigned number on all architectures\nexcept ARM. When it got added initially in commit d80ade7b3231 (\"ARM:\nFix warning: #warning syscall migrate_pages not implemented\"), it was\nintentionally left out based on the observation that there are no 32-bit\nARM NUMA systems.\n\nHowever, there are now arm64 NUMA machines that can in theory run 32-bit\nkernels (actually enabling NUMA there would require additional work)\nas well as 32-bit user space on 64-bit kernels, so that argument is no\nlonger very strong.\n\nAssigning the number lets us use the system call on 64-bit kernels as well\nas providing a more consistent set of syscalls across architectures.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nAcked-by: Catalin Marinas <catalin.marinas@arm.com>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/78594b95998f1496e25411c6b7c7041bcb9bf7d1"},{"sha":"4ab65ba7a5cbad47520274d88d066bf8eb83f161","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"ARM: add kexec_file_load system call number\n\nA couple of architectures including arm64 already implement the\nkexec_file_load system call, on many others we have assigned a system\ncall number for it, but not implemented it yet.\n\nAdding the number in arch/arm/ lets us use the system call on arm64\nsystems in compat mode, and also reduces the number of differences\nbetween architectures. If we want to implement kexec_file_load on ARM\nin the future, the number assignment means that kexec tools can already\nbe built with the now current set of kernel headers.\n\nAcked-by: Catalin Marinas <catalin.marinas@arm.com>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/4ab65ba7a5cbad47520274d88d066bf8eb83f161"},{"sha":"09ac12603bf007eb5475c5847e78905e05d4c729","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"m68k: assign syscall number for seccomp\n\nMost architectures have assigned a numbers for the seccomp syscall\neven when they do not implement it.\n\nm68k is an exception here, so for consistency lets add the number.\nUnless CONFIG_SECCOMP is implemented, the system call just\nreturns -ENOSYS.\n\nAcked-by: Geert Uytterhoeven <geert@linux-m68k.org>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/09ac12603bf007eb5475c5847e78905e05d4c729"},{"sha":"83f609135a51d3a4811c4e32d430cac184d0477f","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"sh: remove duplicate unistd_32.h file\n\nWhen I merged this patch, the file was accidentally left intact\ninstead of being removed, which means any changes to syscall.tbl\nhave no effect.\n\nFixes: 2b3c5a99d5f3 (\"sh: generate uapi header and syscall table header files\")\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/83f609135a51d3a4811c4e32d430cac184d0477f"},{"sha":"d25a122afd4374071bb8489a980051da37136ee1","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"sh: add statx system call\n\nstatx is available on almost all other architectures but\ngot missed on sh, so add it now.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/d25a122afd4374071bb8489a980051da37136ee1"},{"sha":"73a66023c937ef258f2aa340cdb53ae7d8b1d47c","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"sparc64: fix sparc_ipc type conversion\n\n__kernel_timespec and timespec are currently the same type, but once\nthey are different, the type cast has to be changed here.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/73a66023c937ef258f2aa340cdb53ae7d8b1d47c"},{"sha":"275f22148e8720e84b180d9e0cdf8abfd69bac5b","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"ipc: rename old-style shmctl/semctl/msgctl syscalls\n\nThe behavior of these system calls is slightly different between\narchitectures, as determined by the CONFIG_ARCH_WANT_IPC_PARSE_VERSION\nsymbol. Most architectures that implement the split IPC syscalls don't set\nthat symbol and only get the modern version, but alpha, arm, microblaze,\nmips-n32, mips-n64 and xtensa expect the caller to pass the IPC_64 flag.\n\nFor the architectures that so far only implement sys_ipc(), i.e. m68k,\nmips-o32, powerpc, s390, sh, sparc, and x86-32, we want the new behavior\nwhen adding the split syscalls, so we need to distinguish between the\ntwo groups of architectures.\n\nThe method I picked for this distinction is to have a separate system call\nentry point: sys_old_*ctl() now uses ipc_parse_version, while sys_*ctl()\ndoes not. The system call tables of the five architectures are changed\naccordingly.\n\nAs an additional benefit, we no longer need the configuration specific\ndefinition for ipc_parse_version(), it always does the same thing now,\nbut simply won't get called on architectures with the modern interface.\n\nA small downside is that on architectures that do set\nARCH_WANT_IPC_PARSE_VERSION, we now have an extra set of entry points\nthat are never called. They only add a few bytes of bloat, so it seems\nbetter to keep them compared to adding yet another Kconfig symbol.\nI considered adding new syscall numbers for the IPC_64 variants for\nconsistency, but decided against that for now.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/kraj/linux/commits/275f22148e8720e84b180d9e0cdf8abfd69bac5b"}]}
{"actor":{"display_login":"kraj"}}