lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 6 Jun 2009 12:17:14 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Corentin Chary <corentin.chary@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	acpi4asus-user@...ts.sourceforge.net, len.brown@...el.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] eeepc-laptop: enable camera by default

Hi Corentin,

On Sat, 6 Jun 2009 09:25:34 +0200 Corentin Chary
<corentin.chary@...il.com> wrote:
>>> fixed patch pushed into acpi4asus.

On Sat, Jun 6, 2009 at 9:31 AM, Andrew Morton<akpm@...ux-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@...il.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
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ