From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
"brandon.maier@collins.com" <brandon.maier@collins.com>,
Neal Frager via buildroot <buildroot@buildroot.org>,
"romain.naour@smile.fr" <romain.naour@smile.fr>,
"Simek, Michal" <michal.simek@amd.com>,
"yann.morin.1998@free.fr" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v1 1/5] board/xilinx/patches/linux: add linux 6.6.40 hash
Date: Wed, 7 Aug 2024 16:28:41 +0200 [thread overview]
Message-ID: <20240807162841.52d0481d@windsurf> (raw)
In-Reply-To: <CH2PR12MB5004D0D6722981F95A9C6D17F0B82@CH2PR12MB5004.namprd12.prod.outlook.com>
On Wed, 7 Aug 2024 14:26:24 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> From my view, it is best to keep the shared hash files since there are now 12
> xilinx defconfigs using this and soon to be 13.
>
> Since it only requires a single line change in the defconfig files, I will
> squash this into a single patch that updates all 12 defconfigs to Linux 6.6.40.
But are you able to test that those 12 (soon 13) defconfigs all build
and boot fine when doing such updates to all defconfigs at the same time?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-07 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 10:58 [Buildroot] [PATCH v1 1/5] board/xilinx/patches/linux: add linux 6.6.40 hash Neal Frager via buildroot
2024-08-07 10:58 ` [Buildroot] [PATCH v1 2/5] configs/zynq_zc702_defconfig: bump to 6.6.40 Neal Frager via buildroot
2024-08-07 10:58 ` [Buildroot] [PATCH v1 3/5] configs/zynq_zc706_defconfig: " Neal Frager via buildroot
2024-08-07 10:58 ` [Buildroot] [PATCH v1 4/5] configs/zynq_microzed_defconfig: " Neal Frager via buildroot
2024-08-07 10:58 ` [Buildroot] [PATCH v1 5/5] configs/zynq_zed_defconfig: " Neal Frager via buildroot
2024-08-07 12:25 ` [Buildroot] [PATCH v1 1/5] board/xilinx/patches/linux: add linux 6.6.40 hash Thomas Petazzoni via buildroot
2024-08-07 14:26 ` Frager, Neal via buildroot
2024-08-07 14:28 ` Thomas Petazzoni via buildroot [this message]
2024-08-07 14:39 ` Frager, Neal via buildroot
2024-08-07 14:47 ` Frager, Neal via buildroot
2024-08-08 9:10 ` Frager, Neal via buildroot
2024-08-08 9:35 ` Thomas Petazzoni via buildroot
2024-08-08 9:46 ` Frager, Neal via buildroot
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=20240807162841.52d0481d@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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