{"push_id":704562351,"size":184,"distinct_size":184,"ref":"refs/heads/ntb-abh","head":"40bc62ea44c7521a64e0ac6d11328cfe1b97c95d","before":"e1b22d2a04c67ee450889c66f1b3552e3dfddbd9","commits":[{"sha":"4ed6a540fab8ea4388c1703b73ecfed68a2009d1","author":{"email":"b460d66aaf00c296a3db1c1d9eeafc081d5f7d70@intel.com","name":"David Woodhouse"},"message":"iommu/vt-d: Fix passthrough mode with translation-disabled devices\n\nWhen we use 'intel_iommu=igfx_off' to disable translation for the\ngraphics, and when we discover that the BIOS has misconfigured the DMAR\nsetup for I/OAT, we use a special DUMMY_DEVICE_DOMAIN_INFO value in\ndev->archdata.iommu to indicate that translation is disabled.\n\nWith passthrough mode, we were attempting to dereference that as a\nnormal pointer to a struct device_domain_info when setting up an\nidentity mapping for the affected device.\n\nThis fixes the problem by making device_to_iommu() explicitly check for\nthe special value and indicate that no IOMMU was found to handle the\ndevices in question.\n\nSigned-off-by: David Woodhouse <David.Woodhouse@intel.com>\nCc: stable@vger.kernel.org (which means you can pick up 18436afdc now too)","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/4ed6a540fab8ea4388c1703b73ecfed68a2009d1"},{"sha":"e96998fc200867f005dd14c7d1dd35e1107d4914","author":{"email":"597b950a11648b2814571a5c9aa3212afe97b3f8@marvell.com","name":"Nadav Haklai"},"message":"ata: ahci_mvebu: Fix wrongly set base address for the MBus window setting\n\nAccording to the Armada 38x datasheet, the window base address\nregisters value is set in bits [31:4] of the register and corresponds\nto the transaction address bits [47:20].\n\nTherefore, the 32bit base address value should be shifted right by\n20bits and left by 4bits, resulting in 16 bit shift right.\n\nThe bug as not been noticed yet because if the memory available on\nthe platform is less than 2GB, then the base address is zero.\n\n[gregory.clement@free-electrons.com: add extra-explanation]\n\nFixes: a3464ed2f14 (ata: ahci_mvebu: new driver for Marvell Armada 380\nAHCI interfaces)\nSigned-off-by: Nadav Haklai <nadavh@marvell.com>\nReviewed-by: Omri Itach <omrii@marvell.com>\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/e96998fc200867f005dd14c7d1dd35e1107d4914"},{"sha":"d71c11f3bd2bb0c09e3f08169f5b75dba4b800ea","author":{"email":"c00cbc2b736c26791a3822db86f8796fe9efff67@pengutronix.de","name":"Sascha Hauer"},"message":"soc: mediatek: PMIC wrap: Fix clock rate handling\n\nreplace chipselect extension values based on SPI clock with hardcoded SoC\nspecific values.\n\nThe PMIC wrapper has the ability of extending the chipselects by configurable\namounts of time. We configured the values based on the rate of SPI clock, but\nthis is wrong. The delays should be configured based on the internal PMIC clock\nthat latches the values from the SPI bus to the internal PMIC registers. By\ndefault this clock is 24MHz. Other clock frequencies are for debugging only\nand can be removed from the driver.\n\nSigned-off-by: Sascha Hauer <s.hauer@pengutronix.de>\nSigned-off-by: Matthias Brugger <matthias.bgg@gmail.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/d71c11f3bd2bb0c09e3f08169f5b75dba4b800ea"},{"sha":"d956b80ac7a6ba6ee45ac46e969f68dd15b4b729","author":{"email":"c00cbc2b736c26791a3822db86f8796fe9efff67@pengutronix.de","name":"Sascha Hauer"},"message":"soc: mediatek: PMIC wrap: Fix register state machine handling\n\nWhen the PMIC wrapper state machine has read a register it goes into the\n\"wait for valid clear\" (vldclr) state. The state machine stays in this\nstate until the VLDCLR bit is written to. We should write this bit after\nreading a register because the SCPSYS won't let the system go into\nsuspend as long as the state machine waits for valid clear.\n\nSince now we never leave the state machine in vldclr state we no longer\nhave to check for this state on pwrap_read/pwrap_write entry and can\nremove the corresponding code.\n\nSigned-off-by: Sascha Hauer <s.hauer@pengutronix.de>\nSigned-off-by: Matthias Brugger <matthias.bgg@gmail.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/d956b80ac7a6ba6ee45ac46e969f68dd15b4b729"},{"sha":"2a910d139e405f1038c0f2ea7f9ac45acc84cce9","author":{"email":"28c780319e2c7f6db09304375fbd148f9c25d13f@gmail.com","name":"Matthias Brugger"},"message":"soc: mediatek: Add compile dependency to pmic-wrapper\n\nThe pmic-wrapper calls the reset controller. If CONFIG_RESET_CONTROLLER\nis not set, compilation fails with:\ndrivers/soc/mediatek/mtk-pmic-wrap.c: In function ‘pwrap_probe’:\ndrivers/soc/mediatek/mtk-pmic-wrap.c:836:2: error: implicit declaration of function ‘devm_reset_control_get’ [-Werror=implicit-function-declaration]\n\nThis patch sets the dependency in the Kconfig file.\n\nSigned-off-by: Matthias Brugger <matthias.bgg@gmail.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/2a910d139e405f1038c0f2ea7f9ac45acc84cce9"},{"sha":"2ff9ab4c7b6d17c82a01e3449173465cf742e897","author":{"email":"9fa18aedd982da975b2d97e5cdaef39466bfd1fa@openwrt.org","name":"Imre Kaloz"},"message":"ARM: mvebu: armada-xp-linksys-mamba: Disable internal RTC\n\nThe Mamba (like the OpenBlocks AX3) doesn't have a crystal\nconnected to the internal RTC - let's prevent the kernel from\nprobing it.\n\nSigned-off-by: Imre Kaloz <kaloz@openwrt.org>\nCc: <stable@vger.kernel.org> # v4.0 +\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/2ff9ab4c7b6d17c82a01e3449173465cf742e897"},{"sha":"8c9e06e64768665503e778088a39ecff3a6f2e0c","author":{"email":"c54e4189a7955dc43220bb9a8c71cc47ff418750@freebox.fr","name":"Nicolas Schichan"},"message":"bus: mvebu-mbus: do not set WIN_CTRL_SYNCBARRIER on non io-coherent platforms.\n\nCommit a0b5cd4ac2d6 (\"bus: mvebu-mbus: use automatic I/O\nsynchronization barriers\") enabled the usage of automatic I/O\nsynchronization barriers by enabling bit WIN_CTRL_SYNCBARRIER in the\ncontrol registers of MBus windows, but on non io-coherent platforms\n(orion5x, kirkwood and dove) the WIN_CTRL_SYNCBARRIER bit in\nthe window control register is either reserved (all windows except 6\nand 7) or enables read-only protection (windows 6 and 7).\n\nSigned-off-by: Nicolas Schichan <nschichan@freebox.fr>\nReviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCc: <stable@vger.kernel.org> # v4.0+\nFixes: a0b5cd4ac2d6 (\"bus: mvebu-mbus: use automatic I/O synchronization barriers\")\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/8c9e06e64768665503e778088a39ecff3a6f2e0c"},{"sha":"885dbd154b2f2ee305cec6fd0a162e1a77ae2b06","author":{"email":"a5d87d2bd7c424ee5cbdb4e978635bf653d5a005@free-electrons.com","name":"Thomas Petazzoni"},"message":"Revert \"bus: mvebu-mbus: make sure SDRAM CS for DMA don't overlap the MBus bridge window\"\n\nThis reverts commit 1737cac69369 (\"bus: mvebu-mbus: make sure SDRAM CS\nfor DMA don't overlap the MBus bridge window\"), because it breaks DMA\non platforms having more than 2 GB of RAM.\n\nThis commit changed the information reported to DMA masters device\ndrivers through the mv_mbus_dram_info() function so that the returned\nDRAM ranges do not overlap with I/O windows.\n\nThis was necessary as a preparation to support the new CESA Crypto\nEngine driver, which will use DMA for cryptographic operations. But\nsince it does DMA with the SRAM which is mapped as an I/O window,\nhaving DRAM ranges overlapping with I/O windows was problematic.\n\nTo solve this, the above mentioned commit changed the mvebu-mbus to\nadjust the DRAM ranges so that they don't overlap with the I/O\nwindows. However, by doing this, we re-adjust the DRAM ranges in a way\nthat makes them have a size that is no longer a power of two. While\nthis is perfectly fine for the Crypto Engine, which supports DRAM\nranges with a granularity of 64 KB, it breaks basically all other DMA\nmasters, which expect power of two sizes for the DRAM ranges.\n\nDue to this, if the installed system memory is 4 GB, in two\nchip-selects of 2 GB, the second DRAM range will be reduced from 2 GB\nto a little bit less than 2 GB to not overlap with the I/O windows, in\na way that results in a DRAM range that doesn't have a power of two\nsize. This means that whenever you do a DMA transfer with an address\nlocated in the [ 2 GB ; 4 GB ] area, it will freeze the system. Any\nserious DMA activity like simply running:\n\n  for i in $(seq 1 64) ; do dd if=/dev/urandom of=file$i bs=1M count=16 ; done\n\nin an ext3 partition mounted over a SATA drive will freeze the system.\n\nSince the new CESA crypto driver that uses DMA has not been merged\nyet, the easiest fix is to simply revert this commit. A follow-up\ncommit will introduce a different solution for the CESA crypto driver.\n\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nFixes: 1737cac69369 (\"bus: mvebu-mbus: make sure SDRAM CS for DMA don't overlap the MBus bridge window\")\nCc: <stable@vger.kernel.org> # v4.0+\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/885dbd154b2f2ee305cec6fd0a162e1a77ae2b06"},{"sha":"d8a50941c91a68da202aaa96a3dacd471ea9c693","author":{"email":"1001e8702733cced254345e193c88aaa47a4f5de@atomide.com","name":"Tony Lindgren"},"message":"ARM: OMAP3: Fix booting with thumb2 kernel\n\nWe get a NULL pointer dereference on omap3 for thumb2 compiled kernels:\n\nInternal error: Oops: 80000005 [#1] SMP THUMB2\n...\n[<c046497b>] (_raw_spin_unlock_irqrestore) from [<c0024375>]\n(omap3_enter_idle_bm+0xc5/0x178)\n[<c0024375>] (omap3_enter_idle_bm) from [<c0374e63>]\n(cpuidle_enter_state+0x77/0x27c)\n[<c0374e63>] (cpuidle_enter_state) from [<c00627f1>]\n(cpu_startup_entry+0x155/0x23c)\n[<c00627f1>] (cpu_startup_entry) from [<c06b9a47>]\n(start_kernel+0x32f/0x338)\n[<c06b9a47>] (start_kernel) from [<8000807f>] (0x8000807f)\n\nThe power management related assembly on omaps needs to interact with\nARM mode bootrom code, so we need to keep most of the related assembly\nin ARM mode.\n\nTurns out this error is because of missing ENDPROC for assembly code\nas suggested by Stephen Boyd <sboyd@codeaurora.org>. Let's fix the\nproblem by adding ENDPROC in two places to sleep34xx.S.\n\nLet's also remove the now duplicate custom code for mode switching.\nThis has been unnecessary since commit 6ebbf2ce437b (\"ARM: convert\nall \"mov.* pc, reg\" to \"bx reg\" for ARMv6+\").\n\nAnd let's also remove the comments about local variables, they are\nnow just confusing after the ENDPROC.\n\nThe reason why ENDPROC makes a difference is it sets .type and then\nthe compiler knows what to do with the thumb bit as explained at:\n\nhttps://wiki.ubuntu.com/ARM/Thumb2PortingHowto\n\nReported-by: Kevin Hilman <khilman@kernel.org>\nTested-by: Kevin Hilman <khilman@linaro.org>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/d8a50941c91a68da202aaa96a3dacd471ea9c693"},{"sha":"1b205c535b573fe95b7f6f6577a43671d312556f","author":{"email":"1001e8702733cced254345e193c88aaa47a4f5de@atomide.com","name":"Tony Lindgren"},"message":"ARM: dts: Fix dm816x to use right compatible flag for MUSB\n\nWith commit 3e457371f436 (\"usb: musb: Fix fifo reads for dm816x with\nmusb_dsps\") we need to use the right compatible flag to avoid issues\nwith FIFO reads.\n\nCc: Bin Liu <binmlist@gmail.com>\nCc: Brian Hutchinson <b.hutchman@gmail.com>\nCc: George Cherian <george.cherian@ti.com>\nFixes: 3e457371f436 (\"usb: musb: Fix fifo reads for dm816x with musb_dsps\")\nAcked-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/1b205c535b573fe95b7f6f6577a43671d312556f"},{"sha":"8770d0898af7f0f0a8e88ce702b02a9ca326254f","author":{"email":"2375fa63e2908bb2df59f606483a3aa92321db7a@ucw.cz","name":"Pavel Machek"},"message":"ARM: dts: Fix n900 dts file to work around 4.1 touchscreen regression on n900\n\nFix dts to match what the Linux kernel expects. This works around\ntouchscreen problems in 4.1 linux on Nokia n900.\n\nSigned-off-by: Pavel Machek <pavel@ucw.cz>\nReviewed-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/8770d0898af7f0f0a8e88ce702b02a9ca326254f"},{"sha":"fe931229c61c04e0a7906c4ebef9623a4538a5ab","author":{"email":"a16cc0c82647c52d401177f8e50567df5499e36c@arm.com","name":"Marc Zyngier"},"message":"ARM: exynos: Fix wake-up interrupts for Exynos3250\n\nCommit 8b283c025443 (ARM: exynos4/5: convert pmu wakeup to\nstacked domains) changed the Exynos PMU code to use stacked\ndomains. This has led to a number of interrupt numbers to be\nfixed.\n\nIn the meantime, support for Exynos 3250 was added, missing\nthe required change to this platform. This amounts to revert\nace283a04a4a (ARM: EXYNOS: Fix wrong hwirq of RTC interrupt\nfor Exynos3250 SoC), as the initial patch was right, just a\nbit early...\n\nCc: Chanwoo Choi <cw00.choi@samsung.com>\nCc: Kyungmin Park <kyungmin.park@samsung.com>\nCc: Krzysztof Kozlowski <k.kozlowski@samsung.com>\nCc: Kukjin Kim <kgene@kernel.org>\nSigned-off-by: Marc Zyngier <marc.zyngier@arm.com>\nReviewed-by: Chanwoo Choi <cw00.choi@samsung.com>\nSigned-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/fe931229c61c04e0a7906c4ebef9623a4538a5ab"},{"sha":"692ef3ee36833b6098a352c079d3cea8fc6ed3ef","author":{"email":"0fa4ef9e7c72646732a82dcdd6eaba77c29231b5@mediatek.com","name":"Yingjoe Chen"},"message":"arm64: dts: mt8173-evb: fix model name\n\nModel name in mt8173-evb.dts doesn't follow dts convention (it should\nbe human readable model name). Fix it.\n\nFixes: b3a372484157 (\"arm64: dts: Add mediatek MT8173 SoC and evaluation board dts and Makefile\")\nCc: <stable@vger.kernel.org> # v4.0+\nSigned-off-by: Yingjoe Chen <yingjoe.chen@mediatek.com>\nSigned-off-by: Matthias Brugger <matthias.bgg@gmail.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/692ef3ee36833b6098a352c079d3cea8fc6ed3ef"},{"sha":"e9d57102ba7d8576f28970075f6df04650d72355","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"Merge tag 'v4.1-next-soc' of https://github.com/mbgg/linux-mediatek into fixes\n\nThese are bug fixes for mediatek, fixing code that was recently introduced.\n\n- pmic wrapper: fix clock handling\n- pmic wrapper: fix state machine\n- pmic wrapper: fix compile dependency\n\n* tag 'v4.1-next-soc' of https://github.com/mbgg/linux-mediatek:\n  soc: mediatek: Add compile dependency to pmic-wrapper\n  soc: mediatek: PMIC wrap: Fix register state machine handling\n  soc: mediatek: PMIC wrap: Fix clock rate handling","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/e9d57102ba7d8576f28970075f6df04650d72355"},{"sha":"8f1ab524b1b97e91356e1b34322b27c304e39e7f","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"Merge tag 'mvebu-fixes-4.1-3' of git://git.infradead.org/linux-mvebu into fixes\n\nMerge \"mvebu fixes for 4.1 (part 3)\" from Gregory CLEMENT:\n\nDisable unused internal RTC for Mamba from linksys (Armada XP)\nAnd 2 commits fixing regressions on mvebu-mbus:\n- the first one for Kirkwood or Orion SoC\n- the second one for DMA when the platform have more than 4GB (only\n  possible on Armada XP as far as I know)\n\n* tag 'mvebu-fixes-4.1-3' of git://git.infradead.org/linux-mvebu:\n  Revert \"bus: mvebu-mbus: make sure SDRAM CS for DMA don't overlap the MBus bridge window\"\n  bus: mvebu-mbus: do not set WIN_CTRL_SYNCBARRIER on non io-coherent platforms.\n  ARM: mvebu: armada-xp-linksys-mamba: Disable internal RTC","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/8f1ab524b1b97e91356e1b34322b27c304e39e7f"},{"sha":"1a02b6627bb9e7cefc8f7faf884172e8e8d87ac8","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"Merge tag 'samsung-fixes-4.1-4' of https://github.com/krzk/linux into fixes\n\nMerge \"ARM: EXYNOS: Fix for 4.1, 4th\" from Krzysztof Kozlowski:\n\nFix for Exynos3250 RTC wake-up interrupts after converting PMU\nwakeup to stacked domains. This allows waking up the device from\nsuspend to RAM using S3C RTC driver (the RTC on SoC).\n\nThe patch should be applied some time ago, unfortunately\nit seems it slipped through fingers.\n\n* tag 'samsung-fixes-4.1-4' of https://github.com/krzk/linux:\n  ARM: exynos: Fix wake-up interrupts for Exynos3250","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/1a02b6627bb9e7cefc8f7faf884172e8e8d87ac8"},{"sha":"9947c34cf7921722b82440a7917ce219eefa5241","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"Merge tag 'v4.1-next-arm64-fixes' of https://github.com/mbgg/linux-mediatek into fixes\n\n- dts: mt8173: fix compatible string\n\n* tag 'v4.1-next-arm64-fixes' of https://github.com/mbgg/linux-mediatek:\n  arm64: dts: mt8173-evb: fix model name","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/9947c34cf7921722b82440a7917ce219eefa5241"},{"sha":"b33558c906bf330336b16dc4598fecee66e48a57","author":{"email":"060a12f1fbc7e2e5d830b72f402ff04fdae8d312@ti.com","name":"Tero Kristo"},"message":"ARM: dts: AM35xx: fix system control module clocks\n\nNew system control module layout for omap3 overlooked parts of the am35xx\nconfiguration. Basically the am35xx clocks were not converted to use the\nchanged offsets, which caused weird boot warnings. The errors were not\nfatal so far, so they were not caught earlier. Fixed by applying the\nproper offsets for the AM35xx scm clocks.\n\nFixes: b8845074cf (\"ARM: dts: omap3: add minimal l4 bus layout with...\")\n\nSigned-off-by: Tero Kristo <t-kristo@ti.com>\nReported-by: Jeroen Hofstee <linux-arm@myspectrum.nl>\nCc: Paul Walmsley <paul@pwsan.com>\nTested-by: Jeroen Hofstee <jeroen@myspectrum.nl>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/b33558c906bf330336b16dc4598fecee66e48a57"},{"sha":"7a6cb0abe1aa63334f3ded6d2b6c8eca80e72302","author":{"email":"2d9a0dd874e183d835d94043b79464ae3de04e0a@gmail.com","name":"Matthijs van Duin"},"message":"ARM: dts: am335x-boneblack: disable RTC-only sleep to avoid hardware damage\n\nAvoid entering \"RTC-only mode\" at poweroff. It is unsupported by most\nversions of BeagleBone, and risks hardware damage.\n\nThe damaging configuration is having system-power-controller\nwithout ti,pmic-shutdown-controller.\n\nReported-by: Matthijs van Duin <matthijsvanduin@gmail.com>\nTested-by: Matthijs van Duin <matthijsvanduin@gmail.com>\nSigned-off-by: Robert Nelson <robertcnelson@gmail.com>\nCc: Tony Lindgren <tony@atomide.com>\nCc: Felipe Balbi <balbi@ti.com>\nCc: Johan Hovold <johan@kernel.org>\n[Matthijs van Duin: added explanatory comments]\nSigned-off-by: Matthijs van Duin <matthijsvanduin@gmail.com>\nFixes: http://bugs.elinux.org/issues/143\nCc: stable@vger.kernel.org # v3.12+\n[tony@atomide.com: updated comments with the hardware breaking info]\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/7a6cb0abe1aa63334f3ded6d2b6c8eca80e72302"},{"sha":"bbac1c94880cb8c7e093718897f4822f3933dd3c","author":{"email":"db4757c56f54651f568cc7cda79cd93c781b1605@linux.vnet.ibm.com","name":"Michael Holzheu"},"message":"s390/bpf: fix stack allocation\n\nOn s390x we have to provide 160 bytes stack space before we can call\nthe next function. From the 160 bytes that we got from the previous\nfunction we only use 11 * 8 bytes and have 160 - 11 * 8 bytes left.\nCurrently for BPF we allocate additional 160 - 11 * 8 bytes for the\nnext function. This is wrong because then the next function only gets:\n\n (160 - 11 * 8) + (160 - 11 * 8) = 2 * 72 = 144 bytes\n\nFix this and allocate enough memory for the next function.\n\nFixes: 054623105728 (\"s390/bpf: Add s390x eBPF JIT compiler backend\")\nSigned-off-by: Michael Holzheu <holzheu@linux.vnet.ibm.com>\nAcked-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Alexei Starovoitov <ast@plumgrid.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/allenbh/linux/commits/bbac1c94880cb8c7e093718897f4822f3933dd3c"}]}