linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-next@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hai Li <hali@codeaurora.org>, Dave Airlie <airlied@linux.ie>,
	Bjorn Andersson <bjorn.andersson@sonymobile.com>
Subject: drm-msm tree (Was: Re: linux-next: build failure after merge of the regulator tree)
Date: Fri, 10 Apr 2015 09:49:14 +1000	[thread overview]
Message-ID: <20150410094914.4c855142@canb.auug.org.au> (raw)
In-Reply-To: <CAF6AEGtgyHYqmJPgzqSpDgFy1t447V1+0hfaYe1MFJCp-729Lw@mail.gmail.com>

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

Hi Rob,

On Thu, 9 Apr 2015 11:00:44 -0400 Rob Clark <robdclark@gmail.com> wrote:
>
> Thanks.. btw, would it be possible to get my msm-next branch picked up
> by linux-next?  That seems like it would help to catch these earlier..
> 
>  git://people.freedesktop.org/~robclark/linux msm-next

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment 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 
sfr@canb.auug.org.au

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

      reply	other threads:[~2015-04-09 23:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09  4:33 linux-next: build failure after merge of the regulator tree Stephen Rothwell
2015-04-09  9:35 ` Mark Brown
2015-04-13 23:44   ` Stephen Rothwell
2015-04-14  1:07     ` Bjorn Andersson
2015-04-14  1:22       ` Stephen Rothwell
2015-04-14  9:40         ` Mark Brown
2015-04-15  3:03           ` Dave Airlie
2015-04-09 15:00 ` Rob Clark
2015-04-09 23:49   ` Stephen Rothwell [this message]

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=20150410094914.4c855142@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=broonie@kernel.org \
    --cc=hali@codeaurora.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robdclark@gmail.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;
as well as URLs for NNTP newsgroup(s).