Re: kill-the-bkl/reiserfs: request for linux-next inclusion

[Frédéric Weisbecker]

Le 22 mai 2009 02:50, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> a écrit :
> Hi Frédéric,
>
> On Thu, 21 May 2009 01:40:57 +0200 Frédéric Weisbecker <fweisbec@xxxxxxxxx> wrote:
>>
>> I guess Al is traveling or something.
>>
>> Until it finds its way to the VFS tree, it would be nice if this
>> reiserfs bkl removal tree could be included in linux-next
>> for testing.
>> Could you please include it ?
>>
>> You can pull from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
>> reiserfs/kill-bkl-rc6
>
> I have included this tree from today.
>
> What I tell everyone: all patches/commits in the tree/series must
> have been:
>
>        posted to a relevant mailing list
>        reviewed
>        unit tested
>        destined for the next merge window (or the current release)



Thanks,

I remember there was a checklist like that for linux-next but couldn't
retrieve it.
They meet all these requirements except the reviewed part.
Some of them have been reviewed by several people but not the last batches,
(or at least the last batches haven't received any comments).



> *before* they are included.  The linux-next tree is for integration
> testing and to lower the impact of conflicts between subsystems in the
> next 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.


Ok thanks.


> --
> Cheers,
> Stephen Rothwell                    sfr@xxxxxxxxxxxxxxxx
> http://www.canb.auug.org.au/~sfr/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/