From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: buildroot@buildroot.org, ibai.erkiaga-elorza@amd.com,
luca.ceresoli@bootlin.com, yann.morin@orange.com,
brandon.maier@collins.com, thomas.petazzoni@bootlin.com,
romain.naour@smile.fr, michal.simek@amd.com,
romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v1 1/6] board/xilinx: add Linux 6.12.70 hash
Date: Mon, 20 Apr 2026 22:50:00 +0200 [thread overview]
Message-ID: <1680095fb1bc4aadf9082cbb51c22151@free.fr> (raw)
In-Reply-To: <20260420173858.1655069-1-neal.frager@amd.com>
On 20/04/2026 19:38, Neal Frager via buildroot wrote:
> Add the hash for the Xilinx Linux 6.12.70 release tag.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-20 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 17:38 [Buildroot] [PATCH v1 1/6] board/xilinx: add Linux 6.12.70 hash Neal Frager via buildroot
2026-04-20 17:38 ` [Buildroot] [PATCH v1 2/6] configs/zynq_*: bump to Linux 6.12.70 Neal Frager via buildroot
2026-04-20 17:38 ` [Buildroot] [PATCH v1 3/6] configs/zynqmp_*: " Neal Frager via buildroot
2026-04-20 17:38 ` [Buildroot] [PATCH v1 4/6] configs/versal_*: " Neal Frager via buildroot
2026-04-20 17:38 ` [Buildroot] [PATCH v1 5/6] configs/versal2_*: " Neal Frager via buildroot
2026-04-20 17:38 ` [Buildroot] [PATCH v1 6/6] board/xilinx: remove Linux 6.12.60 hash Neal Frager via buildroot
2026-04-20 20:50 ` Julien Olivain via buildroot [this message]
2026-04-21 19:39 ` [Buildroot] [PATCH v1 1/6] board/xilinx: add Linux 6.12.70 hash Peter Korsgaard
2026-04-22 7:05 ` 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=1680095fb1bc4aadf9082cbb51c22151@free.fr \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.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