From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] {linux, linux-headers}: add version 5.9
Date: Mon, 12 Oct 2020 22:42:03 +0200 [thread overview]
Message-ID: <20201012224203.0de3ce19@windsurf.home> (raw)
In-Reply-To: <20201012083317.11732-1-michael@walle.cc>
Hello Michael,
On Mon, 12 Oct 2020 10:33:16 +0200
Michael Walle <michael@walle.cc> wrote:
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> linux/Config.in | 4 ++--
> linux/linux.hash | 1 +
> package/linux-headers/Config.in.host | 13 +++++++++++--
> toolchain/Config.in | 5 +++++
> .../toolchain-external-custom/Config.in.options | 6 +++++-
> 5 files changed, 24 insertions(+), 5 deletions(-)
Applied to master, thanks. However, it is not normal that your
defconfig uses just the "latest kernel version". We normally want all
our defconfigs to use a fixed and well-defined kernel versions so that
we are sure that what our users build is a kernel version that was
tested by the person who contributed the defconfig.
Could you send another patch to adjust your defconfig accordingly ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-10-12 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 8:33 [Buildroot] [PATCH 1/2] {linux, linux-headers}: add version 5.9 Michael Walle
2020-10-12 8:33 ` [Buildroot] [PATCH 2/2] configs/kontron_smarc_sal28: remove kernel config fragment Michael Walle
2020-10-12 15:35 ` [Buildroot] [PATCH 1/2] {linux, linux-headers}: add version 5.9 Bilal Wasim
2020-10-12 20:42 ` Thomas Petazzoni [this message]
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=20201012224203.0de3ce19@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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