All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>, backports@vger.kernel.org
Subject: Re: newbie questions
Date: Mon, 31 Aug 2015 09:26:29 -0500	[thread overview]
Message-ID: <55E46415.9040003@linux.intel.com> (raw)
In-Reply-To: <1441028012.13980.10.camel@sipsolutions.net>

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]

On 08/31/2015 08:33 AM, Johannes Berg wrote:
> On Mon, 2015-08-31 at 08:21 -0500, Pierre-Louis Bossart wrote:
>>>
>>> The *to* version is never relevant. A given backport will compile
>>> against many different *to* versions.
>>
>> I guess I completely missed the concept. I was thinking that the 
>> gentree.py command would only port and adjust the delta between linux
>> -next and the version I wanted. Looks like the backport is really an 
>> add-on that will apply to multiple versions. Not sure I understand 
>> how successive changes in the tree are handled if there is a single 
>> backport.
> 
> Well, there's a single *from* version, as you say that was currently
> "next-20150731" (or that was the one you used). The backport git
> repository is maintained in lockstep with the *from* version (although
> there's usually quite a bit of wiggle room)
> 
> The result, the output of backports, will/should compile against any
> kernel starting from the earliest supported, all the way up to the
> *from* version, right now I think that's 3.0 until 4.1 or so. 

What I was really looking for is the --integrate option that does merge the backport into an existing tree.
This option is broken btw on newer kernels due to a change in the kernel Makefile in October 2014, the attached patch provides a correction (not sure how to use the right patch for the right kernel though).
-Pierre


[-- Attachment #2: 0001-enable-backports-built-in.patch --]
[-- Type: text/x-patch, Size: 1628 bytes --]

Allow backports to be integrated into vmlinux with newer Makefiles

diff --git a/Makefile b/Makefile
index f5c8983..31c7cbf 100644
--- a/Makefile
+++ b/Makefile
@@ -555,6 +555,7 @@ scripts: scripts_basic include/config/auto.conf include/config/tristate.conf \
 	$(Q)$(MAKE) $(build)=$(@)
 
 # Objects we will link into vmlinux / subdirs we need to visit
+backports-y 	:= backports/
 init-y		:= init/
 drivers-y	:= drivers/ sound/ firmware/
 net-y		:= net/
@@ -887,11 +888,13 @@ core-y		+= kernel/ mm/ fs/ ipc/ security/ crypto/ block/
 
 vmlinux-dirs	:= $(patsubst %/,%,$(filter %/, $(init-y) $(init-m) \
 		     $(core-y) $(core-m) $(drivers-y) $(drivers-m) \
+		     $(backports-y) $(backports-m) \
 		     $(net-y) $(net-m) $(libs-y) $(libs-m)))
 
 vmlinux-alldirs	:= $(sort $(vmlinux-dirs) $(patsubst %/,%,$(filter %/, \
-		     $(init-) $(core-) $(drivers-) $(net-) $(libs-))))
+		     $(init-) $(core-) $(drivers-) $(backports-) $(net-) $(libs-))))
 
+backports-y	:= $(patsubst %/, %/built-in.o, $(backports-y))
 init-y		:= $(patsubst %/, %/built-in.o, $(init-y))
 core-y		:= $(patsubst %/, %/built-in.o, $(core-y))
 drivers-y	:= $(patsubst %/, %/built-in.o, $(drivers-y))
@@ -902,7 +905,7 @@ libs-y		:= $(libs-y1) $(libs-y2)
 
 # Externally visible symbols (used by link-vmlinux.sh)
 export KBUILD_VMLINUX_INIT := $(head-y) $(init-y)
-export KBUILD_VMLINUX_MAIN := $(core-y) $(libs-y) $(drivers-y) $(net-y)
+export KBUILD_VMLINUX_MAIN := $(core-y) $(libs-y) $(drivers-y) $(net-y) $(backports-y)
 export KBUILD_LDS          := arch/$(SRCARCH)/kernel/vmlinux.lds
 export LDFLAGS_vmlinux
 # used by scripts/pacmage/Makefile

  reply	other threads:[~2015-08-31 14:26 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  0:30 newbie questions Pierre-Louis Bossart
2015-08-31  7:43 ` Johannes Berg
2015-08-31 12:50   ` Pierre-Louis Bossart
2015-08-31 12:54     ` Johannes Berg
2015-08-31 13:21       ` Pierre-Louis Bossart
2015-08-31 13:33         ` Johannes Berg
2015-08-31 14:26           ` Pierre-Louis Bossart [this message]
2015-08-31 14:38             ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2021-06-18 16:31 Newbie questions Ethy H. Brito
2021-06-18 17:40 ` Jesper Dangaard Brouer
2021-06-18 20:37   ` Ethy H. Brito
2021-06-22  1:28     ` Ethy H. Brito
2021-06-22  9:18       ` Jesper Dangaard Brouer
2012-10-06 15:31 Mark Kampe
2012-10-07  0:08 ` Adam Nielsen
2012-10-07  0:34   ` Mark Kampe
2012-10-01 12:30 Adam Nielsen
2012-10-01 13:20 ` Joao Eduardo Luis
2012-10-01 16:13 ` Sage Weil
2012-10-06 15:05   ` Adam Nielsen
2005-11-01 17:33 Larry Alkoff
2005-11-02  5:41 ` Justin Zygmont
2005-11-03  0:55 ` Ralph Alvy
2005-11-03  4:12   ` Larry Alkoff
2005-11-03  6:17     ` Ralph Alvy
2005-11-03  7:32     ` John R. Sowden
2005-11-03 19:02       ` Larry Alkoff
2005-11-03 21:26         ` John R. Sowden
2005-11-04  3:45           ` Justin Zygmont
2005-11-05 17:06         ` Ralph Alvy
2005-11-05 19:25           ` Larry Alkoff
2005-11-06  0:42             ` Ralph Alvy
     [not found]           ` <436F5554.2030304@pobox.com>
     [not found]             ` <200511070723.31259.ralvy@warpmail.net>
2005-11-07 16:36               ` Alain
2005-11-09  7:46                 ` Ralph Alvy
2005-10-06 18:17 Gaurav Poothia
2005-10-06 21:04 ` Ivan Gyurdiev
2005-10-06 22:05   ` Luke Kenneth Casson Leighton
2005-10-06 18:12 Gaurav Poothia
2005-01-19 15:07 Scott Miller
2005-01-19 15:10 ` Geert Uytterhoeven
2005-01-19 20:53   ` Scott Miller
2004-12-15 19:49 Newbie Questions Joseph Swaminathan
2004-12-15 20:23 ` Marco Gerards
2004-12-15 20:51   ` Joseph Swaminathan
2004-12-15 20:56     ` Marco Gerards
2004-03-25 21:32 Newbie questions Jan Rychter
2004-03-26  2:26 ` Steven Hand
2004-04-07 21:08   ` Jan Rychter
2004-03-26  2:35 ` Ian Pratt
2002-08-03  4:10 Gustavo Sverzut Barbieri
     [not found] ` <20020803041040.10310.qmail-L8+/D2FWflyA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2002-08-03 12:49   ` Axel Siebenwirth
     [not found] <200204070157.g371vDs24544@superglide.netfx-2000.net>
2002-04-25  8:10 ` Newbie Questions Daniel
2002-04-09 21:39 Gyzmobro
2002-04-09 22:14 ` Glynn Clements
2001-12-11 23:44 Slightly confuzed Charles Steinkuehler
2001-12-12 14:59 ` Newbie questions Charles Steinkuehler

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=55E46415.9040003@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=backports@vger.kernel.org \
    --cc=johannes@sipsolutions.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.