public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Another tree in Linux -next
Date: Wed, 23 Jul 2014 08:34:03 +0100	[thread overview]
Message-ID: <20140723073403.GF23210@lee--X1> (raw)
In-Reply-To: <20140723084314.34870f0e@canb.auug.org.au>

On Wed, 23 Jul 2014, Stephen Rothwell wrote:
> On Tue, 22 Jul 2014 10:22:08 +0100 Lee Jones <lee.jones@linaro.org> wrote:
> >
> > Can I have another branch in -next please?
> > 
> > > Sure, if you think you meet the criteria, then send me a URL:
> > > 
> > > 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.
> > 
> > The new branch also matches the critera.
> > 
> > Repo:   git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
> > Branch: for-backlight-next
> 
> Added from today.

Thanks Stephen, much obliged.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2014-07-23  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130731101119.GC13298@lee--X1>
     [not found] ` <20130801094146.2266f4ff61ddac67cd449f53@canb.auug.org.au>
     [not found]   ` <20140722092208.GG28529@lee--X1>
2014-07-22 22:43     ` Another tree in Linux -next Stephen Rothwell
2014-07-23  7:34       ` Lee Jones [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=20140723073403.GF23210@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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