From: Johannes Berg <johannes@sipsolutions.net>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
backports@vger.kernel.org
Subject: Re: newbie questions
Date: Mon, 31 Aug 2015 14:54:24 +0200 [thread overview]
Message-ID: <1441025664.13980.8.camel@sipsolutions.net> (raw)
In-Reply-To: <55E44DA7.3000209@linux.intel.com>
On Mon, 2015-08-31 at 07:50 -0500, Pierre-Louis Bossart wrote:
>
> > In general, this is possible. Check out the copy-list file. You can
> > edit this, and it'll copy only what's listed there.
>
> ok. I was thinking of a more automated way that doesn't require me to
> maintain a branch but that'll do for now.
maintaining a branch of the copy-list is simple though.
> > In order to add sound though, you'll also have to at least change
> > backport/Makefile.kernel and backport/Kconfig.sources to include
> > the
> > sound directory in the kconfig and build.
>
> yes that part works fine. I still have to figure out how Kconfig
> works in the backports, I didn't get the explanations.
You can submit this part upstream btw - it'll just be disabled in the
default copy-list... unless you also submit that upstream.
> humm... What I wanted is backport next-20150731 to v4.1.6. linux-next
> is checked out to next-20150731.
> which of the two does git-revision refer two? the linux-next origin
> or the destination?
The *to* version is never relevant. A given backport will compile
against many different *to* versions.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2015-08-31 12:54 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 [this message]
2015-08-31 13:21 ` Pierre-Louis Bossart
2015-08-31 13:33 ` Johannes Berg
2015-08-31 14:26 ` Pierre-Louis Bossart
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=1441025664.13980.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
/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.