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 09:43:08 +0200 [thread overview]
Message-ID: <1441006988.13980.3.camel@sipsolutions.net> (raw)
In-Reply-To: <55E3A03D.6050607@linux.intel.com> (sfid-20150831_023101_616135_D37C8DBB)
Hi,
> question1: is there a way the list of packages can be selected? I'd
> like to use the backports infrastructure only for what I care about
> (media, usb, audio). It'd be really nice if I could limit the updates
> to the parts I care about (media, usb, sound) and remove all the
> networking part I don't really have a use for. It's fine if the
> releases include everything, I only want to limit the changes in my
> own workspace.
In general, this is possible. Check out the copy-list file. You can
edit this, and it'll copy only what's listed there.
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.
The existing semantic patches will be applied to it automatically, but
it seems fairly unlikely that it'll all compile cleanly without more
effort.
> question2: I am not sure I understand how the code is generated.
> Nothing seems to work/compile even without my changes... If I use
> linux-next with the next-20150731 tag and the latest backport code, I
> get:
>
> ~/backports$ ./gentree.py --clean --verbose --gitdebug --git-revision
> v4.1.6 ../linux-next ../linux-next-backport
You're not using next-20150731 tag? You're using v4.1.6 tag. If you
checked out linux-next in ../linux-next, then you can simply remove the
"--git-revision ..." argument and make the script a bit faster even.
> Exception: Patch failed
This is because you're not using the right tag.
> Now if I use branch origin/linux-4.1.y, the tree is generated but
> usually doesn't compile (random options selected)
>
> Can anyone help with a known config that works?
>
>
> question 3: how exactly does ckmake work and what am I missing?
> :~/backports$ ./devel/ckmake
> [snip] backports/Makefile does not exist
>
Don't worry about it for now. It's just a test tool to compile against
a lot of trees - you need to run it on the result of backport.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2015-08-31 7:43 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 [this message]
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
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=1441006988.13980.3.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