[lkml]   [2009]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] eeepc-laptop: enable camera by default
On Sat, Jun 6, 2009 at 11:17 AM, Pekka Enberg<> wrote:
> Hi Corentin,
> On Sat, 6 Jun 2009 09:25:34 +0200 Corentin Chary
> <> wrote:
>>>> fixed patch pushed into acpi4asus.
> On Sat, Jun 6, 2009 at 9:31 AM, Andrew Morton<> wrote:
>>> What's that?
>>> Should it be added to linux-next?
> On Sat, Jun 6, 2009 at 10:52 AM, Corentin Chary
> <> wrote:
>> -
>> The tree is based on
>> git://
>> It's where I regroup eeepc/asus patchs before sending them to Len.
>> I don't think it should be added to linux-next, because the patchs
>> will first go into the acpi tree, wich is in linux-next.
> I guess the main question is how often does Len pull from your tree?
> If the delay is longer than few days, it might make sense to put your
> tree directly into linux-next for early integration. And as long as
> you don't rebase the "for-next" branch and keep it append-only, there
> isn't going to be any conflicts either when Len pulls your tree and
> publishes the result in linux-next.
>                                Pekka

Len does not pull my tree, I send series to him and cc linux-acpi.
But if it could help early integration, maybe linux-next is the right way to go.
I'm not very familiar with it, the only thing I have to do is create a
"for-next" branch (no rebase, only finalized patchs) and them ask
Andrew (or someone else ?) to add it to linux-next ?

Corentin Chary -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-06-06 12:23    [W:0.039 / U:0.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site