All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: writable limits to -next [was: Adding to linux-next?]
Date: Fri, 23 Oct 2009 10:36:26 +0200	[thread overview]
Message-ID: <4AE16B0A.7020400@gmail.com> (raw)
In-Reply-To: <20091006225751.7d5f3eec.sfr@canb.auug.org.au>

On 10/06/2009 01:57 PM, Stephen Rothwell wrote:
> Here is my boilerplate:
> 
> 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. 

Hi, could you please add git://decibel.fi.muni.cz/~xslaby/linux#limits
into the -next tree?

> 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,

I posted the patches twice, nobody seems to want to pick them up.
The last repost is at:
http://lkml.org/lkml/2009/10/17/126

>      * reviewed by you (or another maintainer of your subsystem tree),
>      * successfully unit tested, and 
>      * destined for the current or next Linux merge window.

I'll try to merge it to 2.6.33.

Thanks.

  reply	other threads:[~2009-10-23  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 17:08 Adding to linux-next? Gregory Haskins
2009-10-06 11:57 ` Stephen Rothwell
2009-10-23  8:36   ` Jiri Slaby [this message]
2009-10-25 22:47     ` writable limits to -next [was: Adding to linux-next?] Stephen Rothwell
2009-10-25 22:55       ` Stephen Rothwell
2009-10-25 23:37         ` Jiri Slaby
2009-10-26  0:35       ` writable limits to -next Krzysztof Halasa
2009-10-26  0:35         ` Krzysztof Halasa
2009-10-26  1:04         ` Stephen Rothwell
2009-10-26  1:04           ` Stephen Rothwell
2009-10-26 13:04           ` Krzysztof Halasa
2009-10-26 13:04             ` Krzysztof Halasa

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=4AE16B0A.7020400@gmail.com \
    --to=jirislaby@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.