public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	acpi4asus-user@lists.sourceforge.net, len.brown@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eeepc-laptop: enable camera by default
Date: Sat, 6 Jun 2009 12:17:14 +0300	[thread overview]
Message-ID: <84144f020906060217r2ac950dcp74f4c66d64a292a3@mail.gmail.com> (raw)
In-Reply-To: <71cd59b00906060052n153835e8p37e0ccb7c73ba5c5@mail.gmail.com>

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

  reply	other threads:[~2009-06-06  9:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05  8:59 [PATCH] eeepc-laptop: enable camera by default Pekka J Enberg
2009-06-05 11:46 ` Corentin Chary
2009-06-05 12:44   ` Pekka Enberg
2009-06-05 13:02     ` Corentin Chary
2009-06-05 13:39       ` Alan Jenkins
2009-06-05 13:51       ` Pekka Enberg
2009-06-05 13:54         ` Pekka Enberg
2009-06-05 13:58         ` Corentin Chary
2009-06-05 14:38         ` Alan Jenkins
2009-06-05 14:50           ` Pekka Enberg
2009-06-05 14:55             ` Alan Jenkins
2009-06-05 15:08               ` Alan Jenkins
2009-06-05 15:14                 ` Pekka Enberg
2009-06-07 14:54                 ` Darren Salt
2009-06-07 15:41                   ` Alan Jenkins
2009-06-07 23:28                     ` Matthew Garrett
2009-06-08  3:03                       ` Alan Stern
2009-06-08  3:07                         ` Matthew Garrett
2009-06-08  3:10                           ` Alan Stern
2009-06-08 15:00                             ` Matthew Garrett
2009-06-08 20:44                               ` Alan Stern
2009-06-05 15:13               ` Alan Stern
2009-06-05 15:22                 ` Pekka Enberg
2009-06-05 21:01   ` Woody Suwalski
2009-06-06  7:12     ` Corentin Chary
2009-06-06  8:04       ` Alan Jenkins
2009-06-05 20:08 ` Andrew Morton
2009-06-06  7:25   ` Corentin Chary
2009-06-06  7:31     ` Andrew Morton
2009-06-06  7:52       ` Corentin Chary
2009-06-06  9:17         ` Pekka Enberg [this message]
2009-06-06 10:17           ` Corentin Chary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84144f020906060217r2ac950dcp74f4c66d64a292a3@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=akpm@linux-foundation.org \
    --cc=corentin.chary@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox