Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Araneda <luaraneda@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] linux: Fix URL for release candidate versions
Date: Tue, 25 Jul 2017 22:13:52 -0400	[thread overview]
Message-ID: <20170726021352.31148-1-luaraneda@gmail.com> (raw)

Starting with 4.12-rc1, tarballs are generated by cgit
directly from Linus's tree.
Also, set LINUX_SOURCE only on non-rc kernels,
and use <PKG>_SOURCE otherwise.

This method also applies to older release candidates.

Signed-off-by: Luis Araneda <luaraneda@gmail.com>

---
Changes v1 -> v2:
  - Set LINUX_SOURCE only on non-rc kernels (suggested by Arnout)

 linux/linux.mk | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/linux/linux.mk b/linux/linux.mk
index 032d64fc2..f02734102 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -16,7 +16,9 @@ define LINUX_HELP_CMDS
 endef
 
 # Compute LINUX_SOURCE and LINUX_SITE from the configuration
-ifeq ($(BR2_LINUX_KERNEL_CUSTOM_TARBALL),y)
+ifneq ($(findstring -rc,$(LINUX_VERSION)),)
+LINUX_SITE := https://git.kernel.org/torvalds/t
+else ifeq ($(BR2_LINUX_KERNEL_CUSTOM_TARBALL),y)
 LINUX_TARBALL = $(call qstrip,$(BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION))
 LINUX_SITE = $(patsubst %/,%,$(dir $(LINUX_TARBALL)))
 LINUX_SOURCE = $(notdir $(LINUX_TARBALL))
@@ -43,10 +45,6 @@ LINUX_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/v3.x
 else ifeq ($(findstring x4.,x$(LINUX_VERSION)),x4.)
 LINUX_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/v4.x
 endif
-# release candidates are in testing/ subdir
-ifneq ($(findstring -rc,$(LINUX_VERSION)),)
-LINUX_SITE := $(LINUX_SITE)/testing
-endif # -rc
 endif
 
 ifeq ($(BR2_LINUX_KERNEL)$(BR2_LINUX_KERNEL_LATEST_VERSION),y)
-- 
2.13.3

             reply	other threads:[~2017-07-26  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26  2:13 Luis Araneda [this message]
2017-08-01 21:44 ` [Buildroot] [PATCH v2] linux: Fix URL for release candidate versions Thomas Petazzoni
2017-08-02  4:18   ` Luis Araneda

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=20170726021352.31148-1-luaraneda@gmail.com \
    --to=luaraneda@gmail.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