{"push_id":665253759,"size":29,"distinct_size":29,"ref":"refs/heads/master","head":"d6c65764a6eb893da95cbf861d81fb9c448340c8","before":"6986a13100ad557e420142b1534c5d87a75e7f7c","commits":[{"sha":"b9a95e85bbc56f168f078885f414f305b4589c4b","author":{"email":"b913f13ef92ac157955c954ccaaff7be065faba4@arm.com","name":"Will Deacon"},"message":"Revert \"arm64: alternative: Allow immediate branch as alternative instruction\"\n\nThis reverts most of commit fef7f2b2010381c795ae43743ad31931cc58f5ad.\n\nIt turns out that there are a couple of problems with the way we're\nfixing up branch instructions used as part of alternative instruction\nsequences:\n\n  (1) If the branch target is also in the alternative sequence, we'll\n      generate a branch into the .altinstructions section which actually\n      gets freed.\n\n  (2) The calls to aarch64_insn_{read,write} bring an awful lot more\n      code into the patching path (e.g. taking locks, poking the fixmap,\n      invalidating the TLB) which isn't actually needed for the early\n      patching run under stop_machine, but makes the use of alternative\n      sequences extremely fragile (as we can't patch code that could be\n      used by the patching code).\n\nGiven that no code actually requires alternative patching of immediate\nbranches, let's remove this support for now and revisit it when we've\ngot a user. We leave the updated size check, since we really do require\nthe sequences to be the same length.\n\nAcked-by: Marc Zyngier <marc.zyngier@arm.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/b9a95e85bbc56f168f078885f414f305b4589c4b"},{"sha":"326a780317d572711f70d53054502e86a1ff5317","author":{"email":"f439b29a58b762d53bfe0721c899ebd460d3253b@gmail.com","name":"Jungseung Lee"},"message":"arm64: mm: Fix build error with CONFIG_SPARSEMEM_VMEMMAP disabled\n\nThis fix the below build error:\n\narch/arm64/mm/dump.c: In function ‘ptdump_init’:\narch/arm64/mm/dump.c:331:18: error: ‘VMEMMAP_START_NR’ undeclared (first use in this function)\n  address_markers[VMEMMAP_START_NR].start_address =\n                  ^\narch/arm64/mm/dump.c:331:18: note: each undeclared identifier is reported only once for each\nfunction it appears in\narch/arm64/mm/dump.c:333:18: error: ‘VMEMMAP_END_NR’ undeclared (first use in this function)\n  address_markers[VMEMMAP_END_NR].start_address =\n                  ^\nAcked-by: Laura Abbott <labbott@redhat.com>\nSigned-off-by: Jungseung Lee <js07.lee@gmail.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/326a780317d572711f70d53054502e86a1ff5317"},{"sha":"b9a5e5e18fbf223502c0b2264c15024e393da928","author":{"email":"27ffc44a8ec6a212fba98cfc3246c6ce8ab131e0@intel.com","name":"Rafael J. Wysocki"},"message":"ACPI / init: Fix the ordering of acpi_reserve_resources()\n\nSince acpi_reserve_resources() is defined as a device_initcall(),\nthere's no guarantee that it will be executed in the right order\nwith respect to the rest of the ACPI initialization code.  On some\nsystems this leads to breakage if, for example, the address range\nthat should be reserved for the ACPI fixed registers is given to\nthe PCI host bridge instead if the race is won by the wrong code\npath.\n\nFix this by turning acpi_reserve_resources() into a void function\nand calling it directly from within the ACPI initialization sequence.\n\nReported-and-tested-by: George McCollister <george.mccollister@gmail.com>\nLink: http://marc.info/?t=143092384600002&r=1&w=2\nCc: All applicable <stable@vger.kernel.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/b9a5e5e18fbf223502c0b2264c15024e393da928"},{"sha":"1e4df6b7208140f3c49f316d33a409d3a161f350","author":{"email":"91e0ff19c25a4c90f9bdc24b1ac8e48e9177c077@gmail.com","name":"Xi Wang"},"message":"arm64: bpf: fix signedness bug in loading 64-bit immediate\n\nConsider \"(u64)insn1.imm << 32 | imm\" in the arm64 JIT.  Since imm is\nsigned 32-bit, it is sign-extended to 64-bit, losing the high 32 bits.\nThe fix is to convert imm to u32 first, which will be zero-extended to\nu64 implicitly.\n\nCc: Zi Shen Lim <zlim.lnx@gmail.com>\nCc: Alexei Starovoitov <ast@plumgrid.com>\nCc: Catalin Marinas <catalin.marinas@arm.com>\nCc: <stable@vger.kernel.org>\nFixes: 30d3d94cc3d5 (\"arm64: bpf: add 'load 64-bit immediate' instruction\")\nSigned-off-by: Xi Wang <xi.wang@gmail.com>\n[will: removed non-arm64 bits and redundant casting]\nSigned-off-by: Will Deacon <will.deacon@arm.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/1e4df6b7208140f3c49f316d33a409d3a161f350"},{"sha":"364aece01a2dd748fc36a1e8bf52ef639b0857bd","author":{"email":"1a085457c23ff0b9dc0948eaffafeb6266467720@intel.com","name":"Peter Antoine"},"message":"drm/i915: Avoid GPU hang when coming out of s3 or s4\n\nThis patch fixes a timing issue that causes a GPU hang when the system\ncomes out of power saving.\n\nDuring pm_resume, We are submitting batchbuffers before enabling\nInterrupts this is causing us to miss the context switch interrupt,\nand in consequence intel_execlists_handle_ctx_events is not triggered.\n\nThis patch is based on a patch from Deepak S <deepak.s@intel.com>\nfrom another platform.\n\nThe patch fixes an issue introduced by:\n  commit e7778be1eab918274f79603d7c17b3ec8be77386\n  drm/i915: Fix startup failure in LRC mode after recent init changes\n\nThe above patch added a call to init_context() to fix an issue introduced\nby a previous patch. But, it then opened up a small timing window for the\nbatches being added by the init_context (basically setting up the context)\nto complete before the interrupts have been turned on, thus hanging the\nGPU.\n\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89600\nCc: stable@vger.kernel.org # 4.0+\nSigned-off-by: Peter Antoine <peter.antoine@intel.com>\nReviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>\n[Jani: fixed typo in subject, massaged the comments a bit]\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/364aece01a2dd748fc36a1e8bf52ef639b0857bd"},{"sha":"607d48063512707a414e346972e2210dc71ab491","author":{"email":"c7ea837d7a46effe4232b086213468b8b31643bf@amd.com","name":"Christian König"},"message":"drm/radeon: fix VM_CONTEXT*_PAGE_TABLE_END_ADDR handling\n\nThe mapping range is inclusive between starting and ending addresses.\n\nSigned-off-by: Christian König <christian.koenig@amd.com>\nCC: stable@vger.kernel.org\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/607d48063512707a414e346972e2210dc71ab491"},{"sha":"4801ba338acad2e69e905e0c537e8ba2682c4e65","author":{"email":"b913f13ef92ac157955c954ccaaff7be065faba4@arm.com","name":"Will Deacon"},"message":"arm64: perf: fix memory leak when probing PMU PPIs\n\nCommit d795ef9aa831 (\"arm64: perf: don't warn about missing\ninterrupt-affinity property for PPIs\") added a check for PPIs so that\nwe avoid parsing the interrupt-affinity property for these naturally\naffine interrupts.\n\nUnfortunately, this check can trigger an early (successful) return and\nwe will leak the irqs array. This patch fixes the issue by reordering\nthe code so that the check is performed before any independent\nallocation.\n\nReported-by: David Binderman <dcb314@hotmail.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/4801ba338acad2e69e905e0c537e8ba2682c4e65"},{"sha":"fcf3b54282e4c5a95a1f45f67558bc105acdbc6a","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"message":"drm/radeon: add new bonaire pci id\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/fcf3b54282e4c5a95a1f45f67558bc105acdbc6a"},{"sha":"ff284f37fc0e6f3b51ede85c5944d571b640ac0f","author":{"email":"27ffc44a8ec6a212fba98cfc3246c6ce8ab131e0@intel.com","name":"Rafael J. Wysocki"},"message":"Revert \"ACPICA: Permanently set _REV to the value '2'.\"\n\nRevert commit b1ef29725865 (ACPICA: Permanently set _REV to the value\n'2'.) as it causes a sound regression to happen on Dell XPS 13 (2015).\n\nReported-by: Dominik Brodowski <linux@dominikbrodowski.net>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/ff284f37fc0e6f3b51ede85c5944d571b640ac0f"},{"sha":"c24930457d4b06903aa5dada50e04a83513e3b6b","author":{"email":"efca98801f3398ebd7eeff805a2c18e6c49e84d4@suse.de","name":"Jean Delvare"},"message":"firmware: dmi_scan: Simplified displayed version\n\nThe trailing .x adds no information for the reader, and if anyone\ntries to parse that line, this is more work as they have 3 different\nformats to handle instead of 2. Plus, this makes backporting fixes\nharder.\n\nSigned-off-by: Jean Delvare <jdelvare@suse.de>\nFixes: 95be58df74a5 (\"firmware: dmi_scan: Use full dmi version for SMBIOS3\")\nCc: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/c24930457d4b06903aa5dada50e04a83513e3b6b"},{"sha":"5c1ac56b51b9d222ab202dec1ac2f4215346129d","author":{"email":"efca98801f3398ebd7eeff805a2c18e6c49e84d4@suse.de","name":"Jean Delvare"},"message":"firmware: dmi_scan: Fix ordering of product_uuid\n\nIn function dmi_present(), dmi_walk_early() calls dmi_table(), which\ncalls dmi_decode(), which ultimately calls dmi_save_uuid(). This last\nfunction makes a decision based on the value of global variable\ndmi_ver. The problem is that this variable is set right _after_\ndmi_walk_early() returns. So dmi_save_uuid() always sees dmi_ver == 0\nregardless of the actual version implemented.\n\nThis causes /sys/class/dmi/id/product_uuid to always use the old\nordering even on systems implementing DMI/SMBIOS 2.6 or later, which\nshould use the new ordering.\n\nThis is broken since kernel v3.8 for legacy DMI implementations and\nsince kernel v3.10 for SMBIOS 2 implementations. SMBIOS 3\nimplementations with the 64-bit entry point are not affected.\n\nThe first breakage does not matter much as in practice legacy DMI\nimplementations are always for versions older than 2.6, which is when\nthe UUID ordering changed. The second breakage is more problematic as\nit affects the vast majority of x86 systems manufactured since 2009.\n\nSigned-off-by: Jean Delvare <jdelvare@suse.de>\nFixes: 9f9c9cbb6057 (\"drivers/firmware/dmi_scan.c: fetch dmi version from SMBIOS if it exists\")\nFixes: 79bae42d51a5 (\"dmi_scan: refactor dmi_scan_machine(), {smbios,dmi}_present()\")\nAcked-by: Zhenzhong Duan <zhenzhong.duan@oracle.com>\nCc: Ben Hutchings <ben@decadent.org.uk>\nCc: Artem Savkov <artem.savkov@gmail.com>\nCc: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>\nCc: Matt Fleming <matt.fleming@intel.com>\nCc: stable@vger.kernel.org [v3.10+]","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/5c1ac56b51b9d222ab202dec1ac2f4215346129d"},{"sha":"bed447e7d1bd2d32d3fb09b4de0d0d5a23d3f82b","author":{"email":"f2295d84e358395675bc8031be58672073ae065e@redhat.com","name":"Dave Airlie"},"message":"drm/radeon: don't do mst probing if MST isn't enabled.\n\nThis causes an oops as we haven't initialised the mst\nlayer.\n\nReported-by: Dave Jones <<davej@codemonkey.org.uk>\nSigned-off-by: Dave Airlie <airlied@redhat.com>\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/bed447e7d1bd2d32d3fb09b4de0d0d5a23d3f82b"},{"sha":"4de5167ee07f7a9b66d999e40f2c3193d1a08add","author":{"email":"27ffc44a8ec6a212fba98cfc3246c6ce8ab131e0@intel.com","name":"Rafael J. Wysocki"},"message":"Merge branches 'acpi-init' and 'acpica'\n\n* acpi-init:\n  ACPI / init: Fix the ordering of acpi_reserve_resources()\n\n* acpica:\n  Revert \"ACPICA: Permanently set _REV to the value '2'.\"","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/4de5167ee07f7a9b66d999e40f2c3193d1a08add"},{"sha":"f98b733e93e00365b4df78fbb33c2cad3080f6bb","author":{"email":"5c1e68b099950c134891f0b6e179498a8ebe9cf9@linux-foundation.org","name":"Andrew Morton"},"message":"drivers/rtc/rtc-armada38x.c: remove unused local `flags'\n\nReported-by: Fengguang Wu <fengguang.wu@gmail.com>\nCc: Gregory CLEMENT <gregory.clement@free-electrons.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/f98b733e93e00365b4df78fbb33c2cad3080f6bb"},{"sha":"4933f55fe72c86e57efc454dd6e673c7f17af5a3","author":{"email":"0474aee45985f5ae829f53849df476200e876990@linux.intel.com","name":"Andi Kleen"},"message":"tools/vm: fix page-flags build\n\nlibabikfs.a doesn't exist anymore, so we now need to link with libapi.a.\n\nSigned-off-by: Andi Kleen <ak@linux.intel.com>\nCc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/4933f55fe72c86e57efc454dd6e673c7f17af5a3"},{"sha":"8f4fc071b1926d0b20336e2b3f8ab85c94c734c5","author":{"email":"0d62248ee021b6e01c0ee596a62a5b145b996974@parallels.com","name":"Vladimir Davydov"},"message":"gfp: add __GFP_NOACCOUNT\n\nNot all kmem allocations should be accounted to memcg.  The following\npatch gives an example when accounting of a certain type of allocations to\nmemcg can effectively result in a memory leak.  This patch adds the\n__GFP_NOACCOUNT flag which if passed to kmalloc and friends will force the\nallocation to go through the root cgroup.  It will be used by the next\npatch.\n\nNote, since in case of kmemleak enabled each kmalloc implies yet another\nallocation from the kmemleak_object cache, we add __GFP_NOACCOUNT to\ngfp_kmemleak_mask.\n\nAlternatively, we could introduce a per kmem cache flag disabling\naccounting for all allocations of a particular kind, but (a) we would not\nbe able to bypass accounting for kmalloc then and (b) a kmem cache with\nthis flag set could not be merged with a kmem cache without this flag,\nwhich would increase the number of global caches and therefore\nfragmentation even if the memory cgroup controller is not used.\n\nDespite its generic name, currently __GFP_NOACCOUNT disables accounting\nonly for kmem allocations while user page allocations are always charged.\nTo catch abusing of this flag, a warning is issued on an attempt of\npassing it to mem_cgroup_try_charge.\n\nSigned-off-by: Vladimir Davydov <vdavydov@parallels.com>\nCc: Tejun Heo <tj@kernel.org>\nCc: Johannes Weiner <hannes@cmpxchg.org>\nCc: Michal Hocko <mhocko@suse.cz>\nCc: Christoph Lameter <cl@linux.com>\nCc: Pekka Enberg <penberg@kernel.org>\nCc: David Rientjes <rientjes@google.com>\nCc: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nCc: Greg Thelen <gthelen@google.com>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nCc: <stable@vger.kernel.org>\t[4.0.x]\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/8f4fc071b1926d0b20336e2b3f8ab85c94c734c5"},{"sha":"499611ed451508a42d1d7d1faff10177827755d5","author":{"email":"0d62248ee021b6e01c0ee596a62a5b145b996974@parallels.com","name":"Vladimir Davydov"},"message":"kernfs: do not account ino_ida allocations to memcg\n\nroot->ino_ida is used for kernfs inode number allocations. Since IDA has\na layered structure, different IDs can reside on the same layer, which\nis currently accounted to some memory cgroup. The problem is that each\nkmem cache of a memory cgroup has its own directory on sysfs (under\n/sys/fs/kernel/<cache-name>/cgroup). If the inode number of such a\ndirectory or any file in it gets allocated from a layer accounted to the\ncgroup which the cache is created for, the cgroup will get pinned for\ngood, because one has to free all kmem allocations accounted to a cgroup\nin order to release it and destroy all its kmem caches. That said we\nmust not account layers of ino_ida to any memory cgroup.\n\nSince per net init operations may create new sysfs entries directly\n(e.g. lo device) or indirectly (nf_conntrack creates a new kmem cache\nper each namespace, which, in turn, creates new sysfs entries), an easy\nway to reproduce this issue is by creating network namespace(s) from\ninside a kmem-active memory cgroup.\n\nSigned-off-by: Vladimir Davydov <vdavydov@parallels.com>\nAcked-by: Tejun Heo <tj@kernel.org>\nCc: Johannes Weiner <hannes@cmpxchg.org>\nCc: Michal Hocko <mhocko@suse.cz>\nCc: Christoph Lameter <cl@linux.com>\nCc: Pekka Enberg <penberg@kernel.org>\nCc: David Rientjes <rientjes@google.com>\nCc: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nCc: Greg Thelen <gthelen@google.com>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nCc: <stable@vger.kernel.org>\t[4.0.x]\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/499611ed451508a42d1d7d1faff10177827755d5"},{"sha":"929aa5b250bfc59aca492d3213c7f3a53e2a5247","author":{"email":"c028c213ed5efcf30c3f4fc7361dbde0c893c5b7@joshtriplett.org","name":"Josh Triplett"},"message":"uidgid: make uid_valid and gid_valid work with !CONFIG_MULTIUSER\n\n{u,g}id_valid call {u,g}id_eq, which calls __k{u,g}id_val on both\narguments and compares.  With !CONFIG_MULTIUSER, __k{u,g}id_val return a\nconstant 0, which makes {u,g}id_valid always return false.  Change\n{u,g}id_valid to compare their argument against -1 instead.  That produces\nidentical results in the normal CONFIG_MULTIUSER=y case, but with\n!CONFIG_MULTIUSER will make {u,g}id_valid constant-fold into \"return\ntrue;\" rather than \"return false;\".\n\nThis fixes uses of devpts without CONFIG_MULTIUSER.\n\nSigned-off-by: Josh Triplett <josh@joshtriplett.org>\nReported-by: Fengguang Wu <fengguang.wu@intel.com>,\nCc: Peter Hurley <peter@hurleysoftware.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/929aa5b250bfc59aca492d3213c7f3a53e2a5247"},{"sha":"1ae7013dfa4281644a9a9591105c24d639216b22","author":{"email":"5cfda7752f2f29ca7a13bd8f5c17b69f4411517f@xiaomi.com","name":"Hui Zhu"},"message":"CMA: page_isolation: check buddy before accessing it\n\nI had an issue:\n\n    Unable to handle kernel NULL pointer dereference at virtual address 0000082a\n    pgd = cc970000\n    [0000082a] *pgd=00000000\n    Internal error: Oops: 5 [#1] PREEMPT SMP ARM\n    PC is at get_pageblock_flags_group+0x5c/0xb0\n    LR is at unset_migratetype_isolate+0x148/0x1b0\n    pc : [<c00cc9a0>]    lr : [<c0109874>]    psr: 80000093\n    sp : c7029d00  ip : 00000105  fp : c7029d1c\n    r10: 00000001  r9 : 0000000a  r8 : 00000004\n    r7 : 60000013  r6 : 000000a4  r5 : c0a357e4  r4 : 00000000\n    r3 : 00000826  r2 : 00000002  r1 : 00000000  r0 : 0000003f\n    Flags: Nzcv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user\n    Control: 10c5387d  Table: 2cb7006a  DAC: 00000015\n    Backtrace:\n        get_pageblock_flags_group+0x0/0xb0\n        unset_migratetype_isolate+0x0/0x1b0\n        undo_isolate_page_range+0x0/0xdc\n        __alloc_contig_range+0x0/0x34c\n        alloc_contig_range+0x0/0x18\n\nThis issue is because when calling unset_migratetype_isolate() to unset\na part of CMA memory, it try to access the buddy page to get its status:\n\n\t\tif (order >= pageblock_order) {\n\t\t\tpage_idx = page_to_pfn(page) & ((1 << MAX_ORDER) - 1);\n\t\t\tbuddy_idx = __find_buddy_index(page_idx, order);\n\t\t\tbuddy = page + (buddy_idx - page_idx);\n\n\t\t\tif (!is_migrate_isolate_page(buddy)) {\n\nBut the begin addr of this part of CMA memory is very close to a part of\nmemory that is reserved at boot time (not in buddy system).  So add a\ncheck before accessing it.\n\n[akpm@linux-foundation.org: use conventional code layout]\nSigned-off-by: Hui Zhu <zhuhui@xiaomi.com>\nSuggested-by: Laura Abbott <labbott@redhat.com>\nSuggested-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nCc: Vlastimil Babka <vbabka@suse.cz>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/1ae7013dfa4281644a9a9591105c24d639216b22"},{"sha":"b77017555ce514262abcb28a0ff3cc065d4acfb8","author":{"email":"ef4fc1703356c7317681ccb0f7a24ace05d8f6b6@gmail.com","name":"Jingoo Han"},"message":"MAINTAINERS: update Jingoo Han's email address\n\nChange my private email address.\n\nSigned-off-by: Jingoo Han <jingoohan1@gmail.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/dabrace/linux/commits/b77017555ce514262abcb28a0ff3cc065d4acfb8"}]}