From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
len.brown@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thinkpad_acpi: convert to seq_file
Date: Sat, 5 Dec 2009 12:39:57 -0200 [thread overview]
Message-ID: <20091205143957.GA4901@khazad-dum.debian.net> (raw)
In-Reply-To: <20091203150001.b017c2f1.akpm@linux-foundation.org>
On Thu, 03 Dec 2009, Andrew Morton wrote:
> On Thu, 3 Dec 2009 15:26:09 -0200
> Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> > Alexey, I like your patch, but it pretty much clashes with lots of stuff in
> > my patch queue.
> >
> > I think the easiest way is for me to take in your patch, place it at the end
> > of the queue, and update it when I get to it.
> >
> > I won't promise I will be able to merge it for 2.6.33, but I can promise I
> > will do it for 2.6.34. Depends how fast I can get the higher priority stuff
> > out of the door.
>
> Your patch queue isn't in linux-next :(
It gets there through acpi-test, usually. I have not been able to submit my
stack of patch well before the merge window lately, though :-(
> Can we fix that?
Well, getting my queue directly in linux-next would be possible, and I would
feel less bad about publishing more often as I'd not have to waste anyone's
time asking them to drop patches if I find out I need to fix something on a
patch that is not in mainline yet (because linux-next regenerates from
scratch automatically).
Note: there _is_ some shuffle in my queue, plus fixing of earlier patches,
so if I sent stuff to Len more often, I'd also end up pestering him often as
well. I do all I can to preserve perfect bissectability, allowing at most
for some "defined but not used" warnings. I want as few bugs in the driver
as possible at every point in time. This does mean I go back and fix
patches if I find out they're subtly incorrect before they are in mainline.
Anyway, if I feed my tree directly to linux-next, it could cause problems
for Len since acpi-test is also in linux-next, and thinkpad-acpi is merged
through the acpi trees. For that to work out without causing problems for
Len, we'd have to arrange for the stuff I submit to him to not make it to
linux-next.
Len, what do you think?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2009-12-05 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 7:16 Alexey Dobriyan
2009-12-03 17:26 ` Henrique de Moraes Holschuh
2009-12-03 23:00 ` Andrew Morton
2009-12-05 14:39 ` Henrique de Moraes Holschuh [this message]
2009-12-11 1:04 ` Henrique de Moraes Holschuh
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=20091205143957.GA4901@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®