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: 8+ 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
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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox