[Re: v5.2.x - stable updates comprising v5.2.33] On 27/02/2020 (Thu 14:40) Bruce Ashfield wrote:
> In message: v5.2.x - stable updates comprising v5.2.33 > on 25/02/2020 Paul Gortmaker wrote: > > > Bruce, Yocto kernel folks: > > > > Here is the next 5.2.x stable update "extension" primarily created for > > the Yocto project, as the 12th v5.2.x post-EOL release. > > > > This release is the 2nd in monitoring the v5.4.x content since the v5.3.18 > > kernel was the last in the v5.3.x series. As mentioned in the previous > > release notes, the v5.4.7 release had a hefty 433 commits to consider! > > > > But since we are now using 5.4.x content as possible candidates for this > > 5.2.x extension, there will be (as I mentioned before?) more than 2x the > > 5.3+ and 5.4+ content not appropriate for this v5.2 -- and this release > > bears that out -- as I'm left with about 335 appropriate commits for our > > v5.2 after I do backporting, and Fixes: revision lookups and multi-arch > > build testing -- so, a larger "not appropriate" percentage than before... > > > > Anyway, I don't think that should concern anybody, but just a passing > > note on the numbers, in case anyone out there is interested in that. > > > > As always, there is the repo below with all the details of what was > > rejected and what was used - starting from the raw import point. > > > > I've put this 5.2.33 queue through the usual testing; build testing on > > x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis and > > finally some sanity runtime tests on x86-64. > > > > I did the signed tag just as per the previously released versions. > > Please find a signed v5.2.33 tag using this key: > > > > http://pgp.mit.edu/pks/lookup?op=vindex&search=0xEBCE84042C07D1D6 > > > > in the repo in the kernel.org directory here: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git/?h=linux-5.2.y > > git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git > > As usual, I had a conflict in -rt: > > both modified: arch/x86/kernel/apic/io_apic.c The above was just a case of upstream df4393424af changing irq --> IRQ in a comment. Nothing to worry about there. > both modified: lib/ubsan.c This one is from the backport of 9a50dcaf0416 (adding a classic "goto out" unwind) that is running into the local yocto-rt commit ID: commit 7adf9cbf1caa216652dfe7058477bb4fe420ea16 Author: Julien Grall <[email protected]> Date: Fri Sep 20 11:08:35 2019 +0100 lib/ubsan: Don't seralize UBSAN report ...which removes "flags" from ubsan_prologue() args. Knowing that, and looking at your merge resolution in 876c748613 -- I think we are good. > I resolved it locally, but if you can have a look at it, I'd appreciate > any fixups that are required. > > I did build and boot -rt, so it is minimally sane :D Yep, I think things are good as-is; no fixups needed. Thanks, Paul. -- > > Bruce > > > > > > for merge to standard/base in linux-yocto-5.2 and then out from there > > into the other base and BSP branches. > > > > For those who are interested, the evolution of the commits is here: > > > > https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-5.2.git/ > > > > This repo isn't needed for anything; it just exists for transparency and > > so people can see the evolution of the raw commits that were originally > > selected to create this 5.2.x release. > > > > Paul.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8419): https://lists.yoctoproject.org/g/linux-yocto/message/8419 Mute This Topic: https://lists.yoctoproject.org/mt/71528711/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
