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
