linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Darren Hart <dvhart@infradead.org>
Subject: Re: linux-next: Tree for May 14
Date: Mon, 14 May 2018 22:40:06 +1000	[thread overview]
Message-ID: <20180514224006.06827f71@canb.auug.org.au> (raw)
In-Reply-To: <CAHp75Vfs_Za5d8YLJ5FNJDmytRJE-P+q_Kds9V+ivBGy3v+p8g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

Hi Andy,

On Mon, 14 May 2018 10:26:07 +0300 Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>
> Hmm... It seems my message was buried in the pile of the thread WRT
> fixes branches.

No, I just didn't read enough email early enough this morning.

> Please, add our PDx86 fixes branch as well:
> git://git.infradead.org/linux-platform-drivers-x86.git fixes

Added from tomorrow (called drivers-x86-fixes).

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.

BTW, the drivers-x86 tree I have is

https://github.com/dvhart/linux-pdx86.git#for-next

and the contact is Darren Hart.  Is that expected?
-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-05-14 12:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14  7:20 Stephen Rothwell
2018-05-14  7:26 ` Andy Shevchenko
2018-05-14 12:40   ` Stephen Rothwell [this message]
2018-05-14 17:14     ` Andy Shevchenko
2018-05-14 21:54       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2021-05-14  5:40 Stephen Rothwell
2020-05-14 11:07 Stephen Rothwell
2019-05-14  4:35 Stephen Rothwell
2015-05-14  8:25 Stephen Rothwell
2014-05-14  8:26 Stephen Rothwell
2013-05-14  4:17 Stephen Rothwell
2012-05-14 10:03 Stephen Rothwell
2010-05-14  6:14 Stephen Rothwell
2009-05-14  6:41 Stephen Rothwell
2009-05-14 13:17 ` Nico -telmich- Schottelius
2008-05-14  7:01 Stephen Rothwell
2008-05-14 20:38 ` Geert Uytterhoeven
2008-05-14 20:50   ` Randy Dunlap
2008-05-14 21:04     ` Tony Breeds
2008-05-15  1:05       ` Tony Breeds
2008-05-15  7:17         ` Geert Uytterhoeven
2008-05-15  7:23           ` Stephen Rothwell
2008-05-16  2:10           ` Tony Breeds
2008-05-16  7:12             ` Geert Uytterhoeven

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=20180514224006.06827f71@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andy.shevchenko@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --subject='Re: linux-next: Tree for May 14' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).