From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] linux: fix hash for kernel 4.14.290
Date: Sat, 12 Aug 2023 14:36:34 +0200 [thread overview]
Message-ID: <20230812143634.5f88c712@windsurf> (raw)
In-Reply-To: <20230810203222.3072070-1-bernd@kuhls.net>
On Thu, 10 Aug 2023 22:32:22 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Buildroot commit e0a786a46733cc473f0e4c35064a3b09ccf548e6 added a hash
> for the wrong file.
>
> Fixes:
> http://autobuild.buildroot.net/results/fc0/fc0e253e3535bbc1413d150554e836d3da9e2042/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> linux/linux.hash | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-12 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 20:32 [Buildroot] [PATCH 1/1] linux: fix hash for kernel 4.14.290 Bernd Kuhls
2023-08-12 12:36 ` Thomas Petazzoni via buildroot [this message]
2023-09-12 6:09 ` 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=20230812143634.5f88c712@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--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