{"push_id":2929857221,"size":526,"distinct_size":520,"ref":"refs/heads/linux-next","head":"8f84a21675f06c8aea55148ce37a618c6fe52a0b","before":"62f3d25900c9a597db7bf3808de4bc8451d04306","commits":[{"sha":"9d831528a6567da92d1ce2a77c575af29068d063","author":{"name":"Angelo Dureghello","email":"d489b904fec03b850597df49e1e32fcdb1a7a7f4@sysam.it"},"message":"dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)\n\nThis patch adds a new fsl-edma-common module to allow new\nmcf-edma module code to use most of the fsl-edma code.\n\nSigned-off-by: Angelo Dureghello <angelo@sysam.it>\nTested-by: Krzysztof Kozlowski <krzk@kernel.org>\nSigned-off-by: Vinod Koul <vkoul@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/9d831528a6567da92d1ce2a77c575af29068d063"},{"sha":"377eaf3b3c4ad74efed77e846320188fc312a0e2","author":{"name":"Angelo Dureghello","email":"d489b904fec03b850597df49e1e32fcdb1a7a7f4@sysam.it"},"message":"dmaengine: fsl-edma: add edma version and configurable registers\n\nThis patch adds configurable registers (using __iomem addresses)\nto allow the use of fsl-edma-common code with slightly different\nedma module versions, as Vybrid (v1) and ColdFire (v2) are.\n\nSigned-off-by: Angelo Dureghello <angelo@sysam.it>\nTested-by: Krzysztof Kozlowski <krzk@kernel.org>\nSigned-off-by: Vinod Koul <vkoul@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/377eaf3b3c4ad74efed77e846320188fc312a0e2"},{"sha":"4d6d3a90e4acfdcf6134a854da20a061cb9da2a6","author":{"name":"Angelo Dureghello","email":"d489b904fec03b850597df49e1e32fcdb1a7a7f4@sysam.it"},"message":"dmaengine: fsl-edma: fix macros\n\nThis patch fixes macros to use BIT() and GENMASK(), removing\nalso some unneeded.\n\nSigned-off-by: Angelo Dureghello <angelo@sysam.it>\nTested-by: Krzysztof Kozlowski <krzk@kernel.org>\nSigned-off-by: Vinod Koul <vkoul@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/4d6d3a90e4acfdcf6134a854da20a061cb9da2a6"},{"sha":"e7a3ff92eaf19eab14e8149758428e680c61706b","author":{"name":"Angelo Dureghello","email":"d489b904fec03b850597df49e1e32fcdb1a7a7f4@sysam.it"},"message":"dmaengine: fsl-edma: add ColdFire mcf5441x edma support\n\nThis patch adds support for ColdFire mcf5441x-family edma\nmodule.\n\nThe ColdFire edma module is slightly different from fsl-edma,\nso a new driver is added. But most of the code is common\nbetween fsl-edma and mcf-edma so it has been collected into a\nseparate common module fsl-edma-common (patch 1/3).\n\nSigned-off-by: Angelo Dureghello <angelo@sysam.it>\nTested-by: Krzysztof Kozlowski <krzk@kernel.org>\nSigned-off-by: Vinod Koul <vkoul@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/e7a3ff92eaf19eab14e8149758428e680c61706b"},{"sha":"5b7d0c9474bc3798b38c393974747336a2cf8497","author":{"name":"Angelo Dureghello","email":"d489b904fec03b850597df49e1e32fcdb1a7a7f4@sysam.it"},"message":"dmaengine: mcf-edma: avoid warning for wrong pointer cast\n\nThis patch fixes the following compilation warning\nreported during x86_64 allmodconfig build:\n\n  drivers/dma/mcf-edma.c: In function 'mcf_edma_filter_fn':\n  drivers/dma/mcf-edma.c:296:33: warning: cast from pointer to\ninteger of different size [-Wpointer-to-int-cast]\n        return (mcf_chan->slave_id == (u32)param);\n\nReported-by: Stephen Rothwell <sfr@canb.auug.org.au>\nSigned-off-by: Angelo Dureghello <angelo@sysam.it>\nSigned-off-by: Vinod Koul <vkoul@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/5b7d0c9474bc3798b38c393974747336a2cf8497"},{"sha":"cfb03be6c7e8a1591285849c361d67b09f5149f7","author":{"name":"Waiman Long","email":"38805f3311ec64b8a137036eb65c6135c09e144d@redhat.com"},"message":"driver/dma/ioat: Call del_timer_sync() without holding prep_lock\n\nThe following lockdep splat was observed:\n\n[ 1222.241750] ======================================================\n[ 1222.271301] WARNING: possible circular locking dependency detected\n[ 1222.301060] 4.16.0-10.el8+5.x86_64+debug #1 Not tainted\n[ 1222.326659] ------------------------------------------------------\n[ 1222.356565] systemd-shutdow/1 is trying to acquire lock:\n[ 1222.382660]  ((&ioat_chan->timer)){+.-.}, at: [<00000000f71e1a28>] del_timer_sync+0x5/0xf0\n[ 1222.422928]\n[ 1222.422928] but task is already holding lock:\n[ 1222.451743]  (&(&ioat_chan->prep_lock)->rlock){+.-.}, at: [<000000008ea98b12>] ioat_shutdown+0x86/0x100 [ioatdma]\n   :\n[ 1223.524987] Chain exists of:\n[ 1223.524987]   (&ioat_chan->timer) --> &(&ioat_chan->cleanup_lock)->rlock --> &(&ioat_chan->prep_lock)->rlock\n[ 1223.524987]\n[ 1223.594082]  Possible unsafe locking scenario:\n[ 1223.594082]\n[ 1223.622630]        CPU0                    CPU1\n[ 1223.645080]        ----                    ----\n[ 1223.667404]   lock(&(&ioat_chan->prep_lock)->rlock);\n[ 1223.691535]                                lock(&(&ioat_chan->cleanup_lock)->rlock);\n[ 1223.728657]                                lock(&(&ioat_chan->prep_lock)->rlock);\n[ 1223.765122]   lock((&ioat_chan->timer));\n[ 1223.784095]\n[ 1223.784095]  *** DEADLOCK ***\n[ 1223.784095]\n[ 1223.813492] 4 locks held by systemd-shutdow/1:\n[ 1223.834677]  #0:  (reboot_mutex){+.+.}, at: [<0000000056d33456>] SYSC_reboot+0x10f/0x300\n[ 1223.873310]  #1:  (&dev->mutex){....}, at: [<00000000258dfdd7>] device_shutdown+0x1c8/0x660\n[ 1223.913604]  #2:  (&dev->mutex){....}, at: [<0000000068331147>] device_shutdown+0x1d6/0x660\n[ 1223.954000]  #3:  (&(&ioat_chan->prep_lock)->rlock){+.-.}, at: [<000000008ea98b12>] ioat_shutdown+0x86/0x100 [ioatdma]\n\nIn the ioat_shutdown() function:\n\n\tspin_lock_bh(&ioat_chan->prep_lock);\n\tset_bit(IOAT_CHAN_DOWN, &ioat_chan->state);\n\tdel_timer_sync(&ioat_chan->timer);\n\tspin_unlock_bh(&ioat_chan->prep_lock);\n\nAccording to the synchronization rule for the del_timer_sync() function,\nthe caller must not hold locks which would prevent completion of the\ntimer's handler.\n\nThe timer structure has its own lock that manages its synchronization.\nSetting the IOAT_CHAN_DOWN bit should prevent other CPUs from\ntrying to use that device anyway, there is probably no need to call\ndel_timer_sync() while holding the prep_lock. So the del_timer_sync()\ncall is now moved outside of the prep_lock critical section to prevent\nthe circular lock dependency.\n\nSigned-off-by: Waiman Long <longman@redhat.com>\nReviewed-by: Dave Jiang <dave.jiang@intel.com>\nSigned-off-by: Vinod Koul <vkoul@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/cfb03be6c7e8a1591285849c361d67b09f5149f7"},{"sha":"082dc55e3c5e559b0e6855c0de23ebd674bcc91e","author":{"name":"Amelie Delaunay","email":"703d6e8a2227152edc0ad38da46c3db0e6880a7c@st.com"},"message":"ARM: dts: stm32: update SPI6 dmas property on stm32mp157c\n\nRemove unused parameter from SPI6 dmas property on stm32mp157c SoC.\n\nFixes: dc3f8c86c10d (\"ARM: dts: stm32: add SPI support on stm32mp157c\")\nSigned-off-by: Amelie Delaunay <amelie.delaunay@st.com>\nSigned-off-by: Alexandre Torgue <alexandre.torgue@st.com>\n[olof: Without this patch, SPI6 will fall back to interrupt mode with\nlower perfmance]\nSigned-off-by: Olof Johansson <olof@lixom.net>","distinct":false,"url":"https://api.github.com/repos/jessfraz/linux/commits/082dc55e3c5e559b0e6855c0de23ebd674bcc91e"},{"sha":"cb28c306b93b71f2741ce1a5a66289db26715f4d","author":{"name":"Matias Karhumaa","email":"1d05ebe002ba1487354d9448127f4a3db2b6229a@gmail.com"},"message":"Bluetooth: SMP: fix crash in unpairing\n\nIn case unpair_device() was called through mgmt interface at the same time\nwhen pairing was in progress, Bluetooth kernel module crash was seen.\n\n[  600.351225] general protection fault: 0000 [#1] SMP PTI\n[  600.351235] CPU: 1 PID: 11096 Comm: btmgmt Tainted: G           OE     4.19.0-rc1+ #1\n[  600.351238] Hardware name: Dell Inc. Latitude E5440/08RCYC, BIOS A18 05/14/2017\n[  600.351272] RIP: 0010:smp_chan_destroy.isra.10+0xce/0x2c0 [bluetooth]\n[  600.351276] Code: c0 0f 84 b4 01 00 00 80 78 28 04 0f 84 53 01 00 00 4d 85 ed 0f 85 ab 00 00 00 48 8b 08 48 8b 50 08 be 10 00 00 00 48 89 51 08 <48> 89 0a 48 b9 00 02 00 00 00 00 ad de 48 89 48 08 48 8b 83 00 01\n[  600.351279] RSP: 0018:ffffa9be839b3b50 EFLAGS: 00010246\n[  600.351282] RAX: ffff9c999ac565a0 RBX: ffff9c9996e98c00 RCX: ffff9c999aa28b60\n[  600.351285] RDX: dead000000000200 RSI: 0000000000000010 RDI: ffff9c999e403500\n[  600.351287] RBP: ffffa9be839b3b70 R08: 0000000000000000 R09: ffffffff92a25c00\n[  600.351290] R10: ffffa9be839b3ae8 R11: 0000000000000001 R12: ffff9c995375b800\n[  600.351292] R13: 0000000000000000 R14: ffff9c99619a5000 R15: ffff9c9962a01c00\n[  600.351295] FS:  00007fb2be27c700(0000) GS:ffff9c999e880000(0000) knlGS:0000000000000000\n[  600.351298] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  600.351300] CR2: 00007fb2bdadbad0 CR3: 000000041c328001 CR4: 00000000001606e0\n[  600.351302] Call Trace:\n[  600.351325]  smp_failure+0x4f/0x70 [bluetooth]\n[  600.351345]  smp_cancel_pairing+0x74/0x80 [bluetooth]\n[  600.351370]  unpair_device+0x1c1/0x330 [bluetooth]\n[  600.351399]  hci_sock_sendmsg+0x960/0x9f0 [bluetooth]\n[  600.351409]  ? apparmor_socket_sendmsg+0x1e/0x20\n[  600.351417]  sock_sendmsg+0x3e/0x50\n[  600.351422]  sock_write_iter+0x85/0xf0\n[  600.351429]  do_iter_readv_writev+0x12b/0x1b0\n[  600.351434]  do_iter_write+0x87/0x1a0\n[  600.351439]  vfs_writev+0x98/0x110\n[  600.351443]  ? ep_poll+0x16d/0x3d0\n[  600.351447]  ? ep_modify+0x73/0x170\n[  600.351451]  do_writev+0x61/0xf0\n[  600.351455]  ? do_writev+0x61/0xf0\n[  600.351460]  __x64_sys_writev+0x1c/0x20\n[  600.351465]  do_syscall_64+0x5a/0x110\n[  600.351471]  entry_SYSCALL_64_after_hwframe+0x44/0xa9\n[  600.351474] RIP: 0033:0x7fb2bdb62fe0\n[  600.351477] Code: 73 01 c3 48 8b 0d b8 6e 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d 69 c7 2c 00 00 75 10 b8 14 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 de 80 01 00 48 89 04 24\n[  600.351479] RSP: 002b:00007ffe062cb8f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014\n[  600.351484] RAX: ffffffffffffffda RBX: 000000000255b3d0 RCX: 00007fb2bdb62fe0\n[  600.351487] RDX: 0000000000000001 RSI: 00007ffe062cb920 RDI: 0000000000000004\n[  600.351490] RBP: 00007ffe062cb920 R08: 000000000255bd80 R09: 0000000000000000\n[  600.351494] R10: 0000000000000353 R11: 0000000000000246 R12: 0000000000000001\n[  600.351497] R13: 00007ffe062cbbe0 R14: 0000000000000000 R15: 0000000000000000\n[  600.351501] Modules linked in: algif_hash algif_skcipher af_alg cmac ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc overlay arc4 nls_iso8859_1 dm_crypt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp dell_laptop kvm_intel crct10dif_pclmul dell_smm_hwmon crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media hid_multitouch input_leds joydev serio_raw dell_wmi snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic dell_smbios dcdbas sparse_keymap\n[  600.351569]  snd_hda_intel btusb snd_hda_codec btrtl btbcm btintel snd_hda_core bluetooth(OE) snd_hwdep snd_pcm iwlmvm ecdh_generic wmi_bmof dell_wmi_descriptor snd_seq_midi mac80211 snd_seq_midi_event lpc_ich iwlwifi snd_rawmidi snd_seq snd_seq_device snd_timer cfg80211 snd soundcore mei_me mei dell_rbtn dell_smo8800 mac_hid parport_pc ppdev lp parport autofs4 hid_generic usbhid hid i915 nouveau kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt mxm_wmi psmouse ahci sdhci_pci cqhci libahci fb_sys_fops sdhci drm e1000e video wmi\n[  600.351637] ---[ end trace e49e9f1df09c94fb ]---\n[  600.351664] RIP: 0010:smp_chan_destroy.isra.10+0xce/0x2c0 [bluetooth]\n[  600.351666] Code: c0 0f 84 b4 01 00 00 80 78 28 04 0f 84 53 01 00 00 4d 85 ed 0f 85 ab 00 00 00 48 8b 08 48 8b 50 08 be 10 00 00 00 48 89 51 08 <48> 89 0a 48 b9 00 02 00 00 00 00 ad de 48 89 48 08 48 8b 83 00 01\n[  600.351669] RSP: 0018:ffffa9be839b3b50 EFLAGS: 00010246\n[  600.351672] RAX: ffff9c999ac565a0 RBX: ffff9c9996e98c00 RCX: ffff9c999aa28b60\n[  600.351674] RDX: dead000000000200 RSI: 0000000000000010 RDI: ffff9c999e403500\n[  600.351676] RBP: ffffa9be839b3b70 R08: 0000000000000000 R09: ffffffff92a25c00\n[  600.351679] R10: ffffa9be839b3ae8 R11: 0000000000000001 R12: ffff9c995375b800\n[  600.351681] R13: 0000000000000000 R14: ffff9c99619a5000 R15: ffff9c9962a01c00\n[  600.351684] FS:  00007fb2be27c700(0000) GS:ffff9c999e880000(0000) knlGS:0000000000000000\n[  600.351686] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  600.351689] CR2: 00007fb2bdadbad0 CR3: 000000041c328001 CR4: 00000000001606e0\n\nCrash happened because list_del_rcu() was called twice for smp->ltk. This\nwas possible if unpair_device was called right after ltk was generated\nbut before keys were distributed.\n\nIn this commit smp_cancel_pairing was refactored to cancel pairing if it\nis in progress and otherwise just removes keys. Once keys are removed from\nrcu list, pointers to smp context's keys are set to NULL to make sure\nremoved list items are not accessed later.\n\nThis commit also adjusts the functionality of mgmt unpair_device() little\nbit. Previously pairing was canceled only if pairing was in state that\nkeys were already generated. With this commit unpair_device() cancels\npairing already in earlier states.\n\nBug was found by fuzzing kernel SMP implementation using Synopsys\nDefensics.\n\nReported-by: Pekka Oikarainen <pekka.oikarainen@synopsys.com>\nSigned-off-by: Matias Karhumaa <matias.karhumaa@gmail.com>\nSigned-off-by: Johan Hedberg <johan.hedberg@intel.com>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/cb28c306b93b71f2741ce1a5a66289db26715f4d"},{"sha":"bfcb79fca19d267712e425af1dd48812c40dec0c","author":{"name":"Keith Busch","email":"695e2a2c1e39535baaa147c5eb4e5da14054d59f@intel.com"},"message":"PCI/ERR: Run error recovery callbacks for all affected devices\n\nIf an Endpoint reported an error with ERR_FATAL, we previously ran driver\nerror recovery callbacks only for the Endpoint's driver.  But if we reset a\nLink to recover from the error, all downstream components are affected,\nincluding the Endpoint, any multi-function peers, and children of those\npeers.\n\nInitiate the Link reset from the deepest Downstream Port that is\nreliable, and call the error recovery callbacks for all its children.\n\nIf a Downstream Port (including a Root Port) reports an error, we assume\nthe Port itself is reliable and we need to reset its downstream Link.  In\nall other cases (Switch Upstream Ports, Endpoints, Bridges, etc), we assume\nthe Link leading to the component needs to be reset, so we initiate the\nreset at the parent Downstream Port.\n\nThis allows two other clean-ups.  First, we currently only use a Link\nreset, which can only be initiated using a Downstream Port, so we can\nremove checks for Endpoints.  Second, the Downstream Port where we initiate\nthe Link reset is reliable (unlike components downstream from it), so the\nspecial cases for error detect and resume are no longer necessary.\n\nSigned-off-by: Keith Busch <keith.busch@intel.com>\n[bhelgaas: changelog]\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nReviewed-by: Sinan Kaya <okaya@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/bfcb79fca19d267712e425af1dd48812c40dec0c"},{"sha":"89d13c38501df730cbb2e02c4499da1b5187119d","author":{"name":"Jaegeuk Kim","email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org"},"message":"f2fs: fix missing up_read\n\nThis patch fixes missing up_read call.\n\nFixes: c9b60788fc76 (\"f2fs: fix to do sanity check with block address in main area\")\nCc: <stable@vger.kernel.org> # 4.19+\nReviewed-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/89d13c38501df730cbb2e02c4499da1b5187119d"},{"sha":"ea2698597e13e2d812929d3ba33946e78a8db4d1","author":{"name":"Emmanuel Vadot","email":"158873d90a7ef40f3637a222b7329c09d0222554@freebsd.org"},"message":"nvmem: sunxi-sid: add support for H5's SID controller\n\nThe H5 SoC have a SID controller that looks like the one in A64, the\ncells are in the same offset but doesn't contain the same data (thermal\nsensor calibration for example).\nAdd a binding for it.\n\nSigned-off-by: Emmanuel Vadot <manu@freebsd.org>\nSigned-off-by: Maxime Ripard <maxime.ripard@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/ea2698597e13e2d812929d3ba33946e78a8db4d1"},{"sha":"cd3f03df13d4eb1e727fab4a8a20d43eb392c34f","author":{"name":"Diego Rondini","email":"f48a046fa74db96735a4084e98d9bb18d62ce377@kynetics.com"},"message":"ARM: dts: sun8i: Add initial Orangepi Zero Plus 2 H3 support\n\nOrangepi Zero Plus 2 is an open-source single-board computer, available in two\nAllwinner SOC variants, H3 and H5. We add support for H3 variant here, as the\nH5 is already supported by sun50i-h5-orangepi-zero-plus2.dts.\n\nH3 Orangepi Zero Plus 2 has:\n- Quad-core Cortex-A7\n- 512MB DDR3\n- microSD slot and 8GB eMMC\n- Debug TTL UART\n- HDMI\n- Wifi + BT\n- OTG + power supply\n\nSigned-off-by: Diego Rondini <diego.rondini@kynetics.com>\nSigned-off-by: Maxime Ripard <maxime.ripard@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/cd3f03df13d4eb1e727fab4a8a20d43eb392c34f"},{"sha":"bb39ed07e55bd56e16993e7d454f649e99c9b7f2","author":{"name":"Chen-Yu Tsai","email":"11e8bbde1bc9e0af703df23be02afe58864a4a18@csie.org"},"message":"arm64: dts: allwinner: h5: Add device node for Mali-450 GPU\n\nThe H5 has a Mali-450 GPU with 4 Pixel Processor cores.\n\nInterestingly, while the datasheet lists an interrupt line for the GPU's\nPMU, the hardware block itself doesn't seem to have it. Reads from the\nPMU address range all return zero, and writes are ignored.\n\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>\nSigned-off-by: Maxime Ripard <maxime.ripard@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/bb39ed07e55bd56e16993e7d454f649e99c9b7f2"},{"sha":"6c700289a3e84d5d3f2a95cf27732a7f7fce105b","author":{"name":"Philipp Rossak","email":"9debf08d67e902e033c751e2729cdd486182a297@gmail.com"},"message":"ARM: dts: sun8i: h3-h5: ir register size should be the whole memory block\n\nThe size of the register should be the size of the whole memory block,\nnot just the registers, that are needed.\n\nSigned-off-by: Philipp Rossak <embed3d@gmail.com>\nAcked-by: Maxime Ripard <maxime.ripard@bootlin.com>\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/6c700289a3e84d5d3f2a95cf27732a7f7fce105b"},{"sha":"db9fd9d13e30fc67737ac9893a82e6b095e85a64","author":{"name":"Chen-Yu Tsai","email":"11e8bbde1bc9e0af703df23be02afe58864a4a18@csie.org"},"message":"ARM: dts: sun8i: h3: bpi-m2-plus: Fix address for external RGMII Ethernet PHY\n\nThe external RTL8211E RGMII Ethernet PHY is configured via external\nresistors to use the address 0x1. The 0x0 address is a broadcast address\nfor this family of PHYs, and should not be used explicitly.\n\nFixes: 8c7ba536e709 (\"ARM: sun8i: bananapi-m2-plus: Enable dwmac-sun8i\")\nFixes: 4904337fe34f (\"ARM: dts: sunxi: Restore EMAC changes (boards)\")\nAcked-by: Maxime Ripard <maxime.ripard@bootlin.com>\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/db9fd9d13e30fc67737ac9893a82e6b095e85a64"},{"sha":"aa8fee415f46a33a867e0d9da0a73ccdcdbce97a","author":{"name":"Chen-Yu Tsai","email":"11e8bbde1bc9e0af703df23be02afe58864a4a18@csie.org"},"message":"ARM: dts: sun8i: h3: Split out non-SoC-specific parts of Bananapi M2 Plus\n\nThree more variants of the Bananapi M2 Plus have been introduced. One\nwith the H5 instead of the H3, another with the H2+ instead, and the\nlast with the H3 but with WiFi and eMMC removed.\n\nAll these variants use the same board. This patch splits out the\nnon-SoC-specific parts of the device tree, so that they can be shared\namong all the variants. The original Bananapi M2 Plus has been renamed\nto Bananapi M2 Plus H3.\n\nAcked-by: Maxime Ripard <maxime.ripard@bootlin.com>\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/aa8fee415f46a33a867e0d9da0a73ccdcdbce97a"},{"sha":"80c21c8c8b8d0f80fe5e06e3d4c631f0ab42b693","author":{"name":"Chen-Yu Tsai","email":"11e8bbde1bc9e0af703df23be02afe58864a4a18@csie.org"},"message":"arm64: dts: allwinner: h5: Add device tree for Bananapi M2 Plus H5\n\nThe Bananapi M2 Plus H5 is a variant of the original Bananapi M2 Plus,\nwith the H3 SoC replaced with an H5. Everything else is the same.\n\nAdd a stub device tree incorporating the shared bananapi-m2-plus dtsi\nfile.\n\nAcked-by: Maxime Ripard <maxime.ripard@bootlin.com>\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/80c21c8c8b8d0f80fe5e06e3d4c631f0ab42b693"},{"sha":"36c4bef372a114222266858b1f342f7c03fabdd7","author":{"name":"Paul Kocialkowski","email":"9016e9b42ab7c99df1a95addd0a70ded9a86418d@bootlin.com"},"message":"ARM: dts: sun8i-h3: Add Video Engine and reserved memory nodes\n\nThis adds nodes for the Video Engine and the associated reserved memory\nfor the H3. Up to 96 MiB of memory are dedicated to the CMA pool.\n\nSigned-off-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>\nAcked-by: Maxime Ripard <maxime.ripard@bootlin.com>\nSigned-off-by: Maxime Ripard <maxime.ripard@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/36c4bef372a114222266858b1f342f7c03fabdd7"},{"sha":"6eeb4180d4b9887b6bc8bbe0a22c1ce3634417f0","author":{"name":"Chen-Yu Tsai","email":"11e8bbde1bc9e0af703df23be02afe58864a4a18@csie.org"},"message":"ARM: dts: sunxi: h3-h5: Add Bananapi M2+ v1.2 device trees\n\nBananapi released an updated revision of the H3/H5 based Bananapi M2+.\nVersion 1.2 enables voltage control for the CPU's regulator by using\na GPIO line to toggle a MOSFET that can change the effective resistance\nvalue in the regulator's feedback network.\n\nThis patch adds a common .dtsi file for this new revision, which\nincludes the original common sunxi-bananapi-m2-plus.dtsi file, and\nadds the GPIO-controlled regulator and a cpu-supply reference. H3\nand H5 variant dts files are added as well.\n\nAcked-by: Maxime Ripard <maxime.ripard@bootlin.com>\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/6eeb4180d4b9887b6bc8bbe0a22c1ce3634417f0"},{"sha":"095680f24f2673d860fd1d3d2f54f40f330b4c63","author":{"name":"Jaegeuk Kim","email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org"},"message":"f2fs: keep lazytime on remount\n\nThis patch fixes losing lazytime when remounting f2fs.\n\nReviewed-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/jessfraz/linux/commits/095680f24f2673d860fd1d3d2f54f40f330b4c63"}]}
{"actor":{"display_login":"jessfraz"}}