All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Didin <Evgeniy.Didin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] Re: [PATCH] configs/snps_arc*_defconfig: update linux version
Date: Thu, 19 Apr 2018 15:16:51 +0000	[thread overview]
Message-ID: <1524151010.7288.3.camel@synopsys.com> (raw)
In-Reply-To: <20180419161502.6414c2e8@windsurf.numericable.fr>

Hello,

> Hello,
> 
> On Thu, 19 Apr 2018 16:55:24 +0300, Evgeniy Didin wrote:
> > With this commit we update Linux kernel version to 4.16.3
> > and Linux headers version to 4.16.
> > For some configs we switch headers version to be independent from
> > Linux kernel version.
> 
> Why ? The change doesn't make you independent at all from the Linux
> kernel version, and causes two kernel tarballs to be downloaded instead
> of one, which isn't nice.
> 
> Could you justify this change ?

With option BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1*=y
BR2_KERNEL_HEADERS_AS_KERNEL parameter is set.
Defconfig is meant as a starting point for work with the board.
In these case if user wants to change version of Linux kernel,
such error appears:
---------------------------->8---------------------------------
Incorrect selection of kernel headers: expected 4.16.x, got 4.15.x,
----------------------------8<---------------------------------
Also in case of choosing new kernel rc's, error 404 occurs.
For inexperienced users, these errors may not be obvious.

> (side note: could you use my @bootlin.com address instead of
> @free-electrons.com. The DEVELOPERS file has been updated since quite
> some time about this already. Thanks a lot!)

Sure

Best regards,
Evgeniy Didin

  reply	other threads:[~2018-04-19 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 13:55 [Buildroot] [PATCH] configs/snps_arc*_defconfig: update linux version Evgeniy Didin
2018-04-19 14:15 ` Thomas Petazzoni
2018-04-19 15:16   ` Evgeniy Didin [this message]
2018-04-20  6:56     ` [Buildroot] [arc-buildroot] " Thomas Petazzoni

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=1524151010.7288.3.camel@synopsys.com \
    --to=evgeniy.didin@synopsys.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.