From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@amd.com>
Cc: michal.simek@amd.com, luca.ceresoli@bootlin.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/3] configs/zynq_zed_defconfig: bump to xilinx-v2023.2
Date: Wed, 18 Oct 2023 11:41:20 +0200 [thread overview]
Message-ID: <87h6motghr.fsf@48ers.dk> (raw)
In-Reply-To: <20231018091002.2162735-2-neal.frager@amd.com> (Neal Frager's message of "Wed, 18 Oct 2023 10:10:01 +0100")
>>>>> "Neal" == Neal Frager <neal.frager@amd.com> writes:
> This patch bumps the zynq_zed_defconfig to xilinx-v2023.2 which includes
> the following updates:
> - Linux v6.1.30
Out of interest, how come this was "only" based on 6.1.30, when there
were already rebases of 2023.1 based on 6.1.40 and 6.1.50?
commit ae6daa717cb4cd4d8234e6f91b99af68ef438252 (tag: xlnx_rebase_v6.1_LTS_2023.1_merge_6.1.40)
Merge: 9299ac26ca51 75389113731b
Author: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Date: Wed Aug 2 13:28:10 2023 +0530
Merge tag 'v6.1.40' into xlnx_rebase_v6.1_LTS_2023.1_update
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
Committed, thanks.
--
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 9:41 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 [this message]
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
[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=87h6motghr.fsf@48ers.dk \
--to=peter@korsgaard.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