From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] linux: bump default to version 4.18.14
Date: Mon, 15 Oct 2018 21:24:31 +0200 [thread overview]
Message-ID: <20181015212431.286a320a@windsurf> (raw)
In-Reply-To: <20181015211918.57a23a32@windsurf>
Hello,
On Mon, 15 Oct 2018 21:19:18 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 15 Oct 2018 19:25:40 +0200, Bernd Kuhls wrote:
> > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> > ---
> > linux/Config.in | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/linux/Config.in b/linux/Config.in
> > index 235018ca0b..d372c2c1f8 100644
> > --- a/linux/Config.in
> > +++ b/linux/Config.in
> > @@ -120,7 +120,7 @@ endif
> >
> > config BR2_LINUX_KERNEL_VERSION
> > string
> > - default "4.18.10" if BR2_LINUX_KERNEL_LATEST_VERSION
> > + default "4.18.14" if BR2_LINUX_KERNEL_LATEST_VERSION
>
> You cannot change this without changing linux.hash at the same time.
Sorry: you did such a hash update in PATCH 1/2, which I missed, so
sorry about my previous comment.
However, the two patches need to be folded into one, because with only
PATCH 1/2 applied, the hash of linux-4.18.10 is no longer present,
which would break the build of the linux package in its default
version, until PATCH 2/2 is applied.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-10-15 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 17:25 [Buildroot] [PATCH 1/2] linux-headers: bump 4.{4, 9, 14, 18}.x series Bernd Kuhls
2018-10-15 17:25 ` [Buildroot] [PATCH 2/2] linux: bump default to version 4.18.14 Bernd Kuhls
2018-10-15 19:19 ` Thomas Petazzoni
2018-10-15 19:24 ` 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=20181015212431.286a320a@windsurf \
--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