All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] {linux, linux-headers}: bump 5.{4, 10, 11}.x 4.{4, 9, 14, 19} series
Date: Fri, 26 Mar 2021 23:52:22 +0100	[thread overview]
Message-ID: <87lfa9il3t.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210323180811.24938-1-petr.vorel@gmail.com> (Petr Vorel's message of "Tue, 23 Mar 2021 19:08:10 +0100")

>>>>> "Petr" == Petr Vorel <petr.vorel@gmail.com> writes:

 > Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
 > ---
 >  linux/Config.in                      |  4 ++--
 >  linux/linux.hash                     | 14 +++++++-------
 >  package/linux-headers/Config.in.host | 14 +++++++-------
 >  3 files changed, 16 insertions(+), 16 deletions(-)

 > diff --git a/linux/Config.in b/linux/Config.in
 > index 3370162faa..1f60fbc801 100644
 > --- a/linux/Config.in
 > +++ b/linux/Config.in
 > @@ -28,7 +28,7 @@ choice
 >  	prompt "Kernel version"
 
 >  config BR2_LINUX_KERNEL_LATEST_VERSION
 > -	bool "Latest version (5.11)"
 > +	bool "Latest version (5.11.8)"

While correct, we normally don't update the prompt for every minor
version number (which also makes backporting a bit more annoying), so
I've dropped that and committed, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2021-03-26 22:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 18:08 [Buildroot] [PATCH 1/2] {linux, linux-headers}: bump 5.{4, 10, 11}.x 4.{4, 9, 14, 19} series Petr Vorel
2021-03-23 18:08 ` [Buildroot] [PATCH 2/2] linux: bump CIP kernel 4.19 series Petr Vorel
2021-03-26 22:52   ` Peter Korsgaard
2021-03-28 20:45   ` Peter Korsgaard
2021-03-26 22:52 ` Peter Korsgaard [this message]
2021-03-28 20:45 ` [Buildroot] [PATCH 1/2] {linux, linux-headers}: bump 5.{4, 10, 11}.x 4.{4, 9, 14, 19} series 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=87lfa9il3t.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.