From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <nealf@xilinx.com>
Cc: "luca@lucaceresoli.net" <luca@lucaceresoli.net>,
"giulio.benetti@benettiengineering.com"
<giulio.benetti@benettiengineering.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: bump to Xilinx 2022.1
Date: Tue, 03 May 2022 16:44:38 +0200 [thread overview]
Message-ID: <871qxa4qw9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <SJ0PR02MB7758E081BE889432D144B4B6D7C09@SJ0PR02MB7758.namprd02.prod.outlook.com> (Neal Frager's message of "Tue, 3 May 2022 14:38:11 +0000")
>>>>> "Neal" == Neal Frager <nealf@xilinx.com> writes:
> Hi Peter,
>> Committed, thanks.
> Thank you!
>> Out of interest, why is there two tags (based on 5.15 and 5.15.19)?
>> Is the plan to rebase the _LTS_ one on future stable releases?
>> git tag | grep 'xlnx.*5.15'
>> xlnx_rebase_v5.15_2022.1
>> xlnx_rebase_v5.15_LTS_2022.1
> The xlnx_rebase_v5.15_2022.1 tag is continuing our older release strategy of staying with a 5.15.0 kernel for the entire year.
> Developers would then be fully responsible for rebasing the kernel.org security patches.
> The xlnx_rebase_v5.15_LTS_2022.1 is our new release strategy and the one I am promoting for everyone to use.
> This tag is using Linux kernel 5.15.19 for 2022.1 and will update to 5.15.x for 2022.2.
> Essentially, developers get two updates of security patches per year by using these tags.
> Petalinux and Yocto are also using the xlnx_rebase_v5.15_LTS_2022.1 release tag.
Ok, nice - Definately a step in the right direction!
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-03 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 7:49 [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: bump to Xilinx 2022.1 Neal Frager via buildroot
2022-05-02 7:49 ` [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2022-05-03 13:32 ` Luca Ceresoli
2022-05-03 13:33 ` Luca Ceresoli
2022-05-03 14:17 ` Peter Korsgaard
2022-05-28 6:58 ` Peter Korsgaard
2022-05-03 14:17 ` [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: " Peter Korsgaard
2022-05-03 14:38 ` Neal Frager
2022-05-03 14:44 ` Peter Korsgaard [this message]
2022-05-28 6:58 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qxa4qw9.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca@lucaceresoli.net \
--cc=neal.frager@amd.com \
--cc=nealf@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox