From: Peter Korsgaard <peter@korsgaard.com>
To: Michal Simek <michal.simek@amd.com>
Cc: "luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
"Frager, Neal" <neal.frager@amd.com>,
"Chaplin, Kris" <Kris.Chaplin@amd.com>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 2/3] configs/zynq_zed_defconfig: bump to xilinx-v2023.2
Date: Wed, 18 Oct 2023 12:40:08 +0200 [thread overview]
Message-ID: <878r80tdrr.fsf@48ers.dk> (raw)
In-Reply-To: <f88a31b0-b6dd-4bfa-921b-1f37b737847f@amd.com> (Michal Simek's message of "Wed, 18 Oct 2023 12:27:39 +0200")
>>>>> "Michal" == Michal Simek <michal.simek@amd.com> writes:
Hi,
>>> commit 496752408d031f93159fcf1aba2831c807a389a3 (tag:
>>> xlnx_rebase_v6.1_LTS_2023.1_merge_6.1.50,
>>> xlnx/xlnx_rebase_v6.1_LTS_2023.1_update)
>>> Merge: 0f7f048016e0 a2943d2d9a00
>>> Author: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
>>> Date: Wed Sep 20 17:50:18 2023 +0530
>>
>>> Merge tag 'v6.1.50' into xlnx_rebase_v6.1_LTS_2023.1_update
>>
>>> - U-Boot v2023.01 with additional bug fixes
>> I noticed that and I actually have the same question.
>> @Simek, Michal, perhaps you can shed some light on this?
>> In addition to Peter's question, should we be bumping the Linux
>> kernel release tag we use with buildroot each time we merge with
>> another set of 10 upstream patches?
> It is because our internal deadlines and associated work in connection
> to our releases.
> When .1 version is tagged we are merging every 10th LTS version on the
> top of xilinx 2023.1 tag.
> On .2 version we continue to do new development and we reached the
> time where there shouldn't be major changes merged to that
> branch. That's why .2 version stopped at .30 for running all
> regressions and .1 can move on .40/.50(coming soon).
Coming soon? .1.50 was tagged 4 weeks ago (see above).
> I see that xlnx_rebase_v6.1_LTS_2023.2 has been created. That means
> that next step is going to be that we will do merges for both branches
> to 6.1.60.
> At that time both branches will be using the same LTS release.
> And we should be doing merges to both branches till ~ April 2024.
Ok, thanks! So +/- until the (presumably 6.6 based?) 2024.1 release?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-18 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 9:10 [Buildroot] [PATCH v1 1/3] configs/zynq_zc706_defconfig: bump to xilinx-v2023.2 Neal Frager via buildroot
2023-10-18 9:10 ` [Buildroot] [PATCH v1 2/3] configs/zynq_zed_defconfig: " Neal Frager via buildroot
2023-10-18 9:41 ` Peter Korsgaard
2023-10-18 10:08 ` Frager, Neal via buildroot
[not found] ` <f88a31b0-b6dd-4bfa-921b-1f37b737847f@amd.com>
2023-10-18 10:36 ` Frager, Neal via buildroot
2023-10-18 11:55 ` Peter Korsgaard
2023-10-18 10:40 ` Peter Korsgaard [this message]
[not found] ` <fa1501e0-b4ce-4d8d-9596-60b39c5f4fa1@amd.com>
2023-10-18 11:27 ` Peter Korsgaard
[not found] ` <9d57c3bb-7193-4ffb-962f-30aec4b53cf5@amd.com>
2023-10-18 11:56 ` Peter Korsgaard
2023-10-18 9:10 ` [Buildroot] [PATCH v1 3/3] configs/zynq_microzed_defconfig: " Neal Frager via buildroot
2023-10-18 9:41 ` 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=878r80tdrr.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=Kris.Chaplin@amd.com \
--cc=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=thomas.petazzoni@bootlin.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