On Fri, Aug 28, 2020 at 05:27:45PM +0200, SeongJae Park wrote: > From: SeongJae Park <sjpark@xxxxxxxxx> > > Hello, > > > We found below 27 commits in the 'v5.5..linus/master (upstream)' seems fixing or mentioning > commits in the 'v5.4..stable/linux-5.4.y (downstream)' but are not merged in the 'downstream' yet. > Could you please review if those need to be merged in? > > A commit is considered as fix of another if the complete 'Fixed:' tag is in the > commit message. If the tag is not found but the commit message contains the > title or the hash id of the other commit, it is considered mentioning it. So, > the 'mentions' might have many false positives, but it could cover the typos (I > found such cases before). > > The commits are grouped as 'fixes cleanly applicable', 'fixes not cleanly > applicable (need manual backporting to be applied)', 'mentions cleanly > applicable', and 'mentions not cleanly applicable'. Also, the commits in each > group are sorted by the commit dates (oldest first). > > Both the finding of the commits and the writeup of this report is automatically > done by a little script[1]. I'm going to run the tool and post this kind of > report every couple of weeks or every month. Any comment (e.g., regarding > posting period, new features request, bug report, ...) is welcome. > > Especially, if you find some commits that don't need to be merged in the > downstream, please let me know so that I can mark those as unnecessary and > don't bother you again. > > [1] https://github.com/sjp38/stream-track > > > Thanks, > SeongJae > > > # v5.5: 4e3112a240ba9986cc3f67a6880da6529a955006 > # linus/master: 15bc20c6af4ceee97a1f90b43c0e386643c071b4 > # v5.4: 6e815efe19a99a33b16cc720c3d3a727565a4fa1 > # stable/linux-5.4.y: 6576d69aac94cd8409636dfa86e0df39facdf0d2 > > > Fixes cleanly applicable > ------------------------ > > 2fb75ceaf71a ("remoteproc: Add missing '\n' in log messages") > # commit date: 2020-04-22, author: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx> > # fixes 'remoteproc: Fix NULL pointer dereference in rproc_virtio_notify' Not a real fix, right? > 1b9ae0c92925 ("wireless: Use linux/stddef.h instead of stddef.h") > # commit date: 2020-05-27, author: Hauke Mehrtens <hauke@xxxxxxxxxx> > # fixes 'wireless: Use offsetof instead of custom macro.' Is this really needed? > e4b0e41fee94 ("ALSA: usb-audio: Use the new macro for HP Dock rename quirks") > # commit date: 2020-06-08, author: Takashi Iwai <tiwai@xxxxxxx> > # fixes 'ALSA: usb-audio: Add vendor, product and profile name for HP Thunderbolt Dock' Alsa stuff has been covered already... > efb94790852a ("drm/panel-simple: fix connector type for LogicPD Type28 Display") > # commit date: 2020-06-21, author: Adam Ford <aford173@xxxxxxxxx> > # fixes 'drm/panel: simple: Add Logic PD Type 28 display support' Why is this applicable to 5.4.y? It says "5.6+" in the commit itself, right? > > 2f57b8d57673 ("dmaengine: imx-sdma: Fix: Remove 'always true' comparison") > # commit date: 2020-06-24, author: Fabio Estevam <festevam@xxxxxxxxx> > # fixes 'dmaengine: imx-sdma: Fix the event id check to include RX event for UART6' Does not change any logic > > 10de795a5add ("kprobes: Fix compiler warning for !CONFIG_KPROBES_ON_FTRACE") > # commit date: 2020-08-06, author: Muchun Song <songmuchun@xxxxxxxxxxxxx> > # fixes 'kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler' Not needed, as mentioned. > Fixes not cleanly applicable <snip> Stopping right here, if you have fixes that will not cleanly apply, and you think they should be applied, please fix them and send the proper backport. I don't have the cycles to do these on my own. Same for anything else here that you think should be applied but does not cleanly build/apply. > ---------------------------- > > 3907ccfaec5d ("crypto: atmel-aes - Fix CTR counter overflow when multiple fragments") > # commit date: 2019-12-20, author: Tudor Ambarus <tudor.ambarus@xxxxxxxxxxxxx> > # fixes 'crypto: atmel-aes - Fix counter overflow in CTR mode' > > 9210c075cef2 ("nvme-pci: avoid race between nvme_reap_pending_cqes() and nvme_poll()") > # commit date: 2020-05-27, author: Dongli Zhang <dongli.zhang@xxxxxxxxxx> > # fixes 'nvme/pci: move cqe check after device shutdown' > > 6e2f83884c09 ("bnxt_en: Fix AER reset logic on 57500 chips.") > # commit date: 2020-06-15, author: Michael Chan <michael.chan@xxxxxxxxxxxx> > # fixes 'bnxt_en: Improve AER slot reset.' > > 695cf5ab401c ("ALSA: usb-audio: Fix packet size calculation") > # commit date: 2020-06-30, author: Alexander Tsoy <alexander@xxxxxxx> > # fixes 'ALSA: usb-audio: Improve frames size computation' > > 2fb2799a2abb ("net: rmnet: do not allow to add multiple bridge interfaces") > # commit date: 2020-07-04, author: Taehee Yoo <ap420073@xxxxxxxxx> > # fixes 'net: rmnet: use upper/lower device infrastructure' > > > > Mentions cleanly applicable > --------------------------- > > 32ada3b9e04c ("x86/resctrl: Clean up unused function parameter in mkdir path") > # commit date: 2020-01-20, author: Xiaochen Shen <xiaochen.shen@xxxxxxxxx> > # mentions 'x86/resctrl: Fix a deadlock due to inaccurate reference' > > 20f513091caf ("crypto: ccree - remove set but not used variable 'du_size'") > # commit date: 2020-02-13, author: YueHaibing <yuehaibing@xxxxxxxxxx> > # mentions 'crypto: ccree - fix FDE descriptor sequence' Oh come on, why is this tripping anything? Please read the patches and see if you think they make sense for a stable kernel, please tell me how the above one does? stopping here... greg k-h
