Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/linux-headers: fix support for -rc kernels
Date: Thu, 14 Mar 2019 22:14:02 +0100	[thread overview]
Message-ID: <20190314221402.5a28354a@windsurf> (raw)
In-Reply-To: <20190306212815.19759-1-arnout@mind.be>

On Wed,  6 Mar 2019 22:28:14 +0100
"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be> wrote:

> -rc kernels after v3.x are no longer available in the testing
> subdirectory. Instead they should be fetched from cgit.
> 
> Commit ff4cccbdcf5417a5a8c251ff302791a306023cc1 did this for linux
> itself, now we also do it for linux-headers.
> 
> When fetched from cgit, .tar.xz can't be used. Adding this to the
> existing condition is not so simple, so refactor how _SOURCE is set:
> simply set it explicitly in each branch of the condition. While more
> verbose (it is repeated 4 times), it's easier to understand and to
> maintain.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
>  package/linux-headers/linux-headers.mk | 23 ++++++++++-------------
>  1 file changed, 10 insertions(+), 13 deletions(-)

Both applied. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2019-03-14 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 21:28 [Buildroot] [PATCH 1/2] package/linux-headers: fix support for -rc kernels Arnout Vandecappelle
2019-03-06 21:28 ` [Buildroot] [PATCH 2/2] linux{, -headers}: support downloads of v5+ Arnout Vandecappelle
2019-03-07 11:23   ` Jan Kundrát
2019-03-13 22:24     ` Adam Duskett
2019-03-25 20:46   ` Peter Korsgaard
2019-03-14 21:14 ` Thomas Petazzoni [this message]
2019-03-25 20:45 ` [Buildroot] [PATCH 1/2] package/linux-headers: fix support for -rc kernels 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=20190314221402.5a28354a@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