Messages in this thread |  | | | Date | Sat, 6 Jun 2009 12:17:25 +0200 | | Subject | Re: [PATCH] eeepc-laptop: enable camera by default | | From | Corentin Chary <> |
| |
On Sat, Jun 6, 2009 at 11:17 AM, Pekka Enberg<penberg@cs.helsinki.fi> wrote: > Hi Corentin, > > On Sat, 6 Jun 2009 09:25:34 +0200 Corentin Chary > <corentin.chary@gmail.com> wrote: >>>> fixed patch pushed into acpi4asus. > > On Sat, Jun 6, 2009 at 9:31 AM, Andrew Morton<akpm@linux-foundation.org> wrote: >>> What's that? >>> >>> Should it be added to linux-next? > > On Sat, Jun 6, 2009 at 10:52 AM, Corentin Chary > <corentin.chary@gmail.com> wrote: >> http://acpi4asus.sourceforge.net/ - >> http://git.iksaif.net/?p=acpi4asus.git;a=summary >> The tree is based on >> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 >> >> 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 http://xf.iksaif.net - http://uffs.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |