linux-kernel - Re: [PATCH] thinkpad_acpi: convert to seq

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, 5 Dec 2009 12:39:57 -0200
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Alexey Dobriyan <adobriyan@...il.com>, len.brown@...el.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] thinkpad_acpi: convert to seq_file

On Thu, 03 Dec 2009, Andrew Morton wrote:
> On Thu, 3 Dec 2009 15:26:09 -0200
> Henrique de Moraes Holschuh <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
--
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/