[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUV1_43d1SvMEaFzjO72-UDdyQAPds=PZitT+TvdSUbB8g@mail.gmail.com>
Date: Sat, 30 Jul 2011 18:16:39 +0200
From: Sedat Dilek <sedat.dilek@...glemail.com>
To: Arnaud Lacombe <lacombar@...il.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Randy Dunlap <rdunlap@...otime.net>
Subject: Re: linux-next: Tree for July 29
On Sat, Jul 30, 2011 at 6:08 PM, Arnaud Lacombe <lacombar@...il.com> wrote:
> Hi,
>
> On Sat, Jul 30, 2011 at 7:38 AM, Sedat Dilek <sedat.dilek@...glemail.com> wrote:
>> On Fri, Jul 29, 2011 at 9:38 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>> Hi all,
>>>
>>> Just in case anyone needs reminding: Please do not add anything destined
>>> for v3.2 into linux-next included trees until after v3.1-rc1.
>>>
>>> The powerpc allyesconfig and sparc defconfig build (at least) fail today.
>>>
>>> Changes since 20110728:
>>>
>>> New tree: moduleh
>>>
>>
>> See all those followup/fixup patches the last day, might be not such a
>> good idea to include this tree :-).
> In the opposite, that is all the point of including a tree in -next:
> give expose to code :)
>
Agreed... and I know about the risks of linux-next (even as a
Debian/sid user) :-).
- Sedat -
> - Arnaud
>
>> I wait for next Monday's linux-next.
>>
>> - Sedat -
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@...r.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists