Hi all, Just cc'ing a more recent address for Greg ...
On Mon, 2 Jul 2018 09:34:04 +1000 Stephen Rothwell <s...@canb.auug.org.au> wrote: > > Hi Uwe, > > On Fri, 29 Jun 2018 09:38:58 +0200 Uwe Kleine-König > <u.kleine-koe...@pengutronix.de> wrote: > > > > On Thu, Jun 28, 2018 at 09:57:42AM +0200, Uwe Kleine-König wrote: > > > Greg, you applied the initial patches creating drivers/siox. I assume > > > you will continue to apply siox patches and tell if I should search a > > > different path for these. > > > > I put the two patches that I'd like to get in during the next merge > > window into a branch in my repository: > > > > https://git.pengutronix.de/git/ukl/linux siox/next > > > > I assume you wouldn't object to add this branch to linux-next? > > Added from today. Is this a continuing effort, or should I just remove > the tree once Greg has merged it? > > Thanks for adding your subsystem tree as a participant of linux-next. As > you may know, this is not a judgement of your code. The purpose of > linux-next is for integration testing and to lower the impact of > conflicts between subsystems in the next merge window. > > You will need to ensure that the patches/commits in your tree/series have > been: > * submitted under GPL v2 (or later) and include the Contributor's > Signed-off-by, > * posted to the relevant mailing list, > * reviewed by you (or another maintainer of your subsystem tree), > * successfully unit tested, and > * destined for the current or next Linux merge window. > > Basically, this should be just what you would send to Linus (or ask him > to fetch). It is allowed to be rebased if you deem it necessary. -- Cheers, Stephen Rothwell
pgpJhXfTGDopA.pgp
Description: OpenPGP digital signature
