From: Peter Korsgaard <peter@korsgaard.com>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
"Chaplin, Kris" <Kris.Chaplin@amd.com>,
"Simek, Michal" <michal.simek@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 13:55:12 +0200 [thread overview]
Message-ID: <87zg0grvq7.fsf@48ers.dk> (raw)
In-Reply-To: <CH2PR12MB5004328281E2B7ACDE8B5A2EF0D5A@CH2PR12MB5004.namprd12.prod.outlook.com> (Neal Frager's message of "Wed, 18 Oct 2023 10:36:59 +0000")
>>>>> "Frager," == Frager, Neal <neal.frager@amd.com> writes:
Hello,
> Thank you for the very clear explanation.
> @Peter Korsgaard, if you would like, I could start bumping the Linux
> kernel release tag used by the buildroot zynq/zynqmp/versal example
> defconfigs every time we release a merge of .10 patches.
Sure, makes sense.
> Since there are bug fixes in 2023.2 that are specific to AMD devices,
> I would think that 2023.2 with Linux kernel 6.1.30 is still a better
> choice than 2023.1 with Linux kernel 6.1.50. However, I am happy to
> bump to 2023.2 with Linux kernel 6.1.60 as soon as this is released.
> What do you think?
Sounds good to me, please go ahead.
--
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 11:55 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 [this message]
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=87zg0grvq7.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