From: Andrew Morton <akpm@linux-foundation.org>
To: Len Brown <lenb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
helgaas@ldl.fc.hp.com, Jaroslav Kysela <perex@suse.cz>,
Adam Belay <ambx1@neo.rr.com>,
linux-acpi@vger.kernel.org
Subject: Re: [patch 00/17] PNP Lindent
Date: Wed, 25 Jul 2007 14:53:22 -0700 [thread overview]
Message-ID: <20070725145322.3ad5bd41.akpm@linux-foundation.org> (raw)
In-Reply-To: <200707251224.44567.lenb@kernel.org>
On Wed, 25 Jul 2007 12:24:44 -0400
Len Brown <lenb@kernel.org> wrote:
>
> > > > > > The best time to do this would be late(ish) in the 2.6.24 merge window.
> > > > > >
> > > > > > Can we do it then?
> > > > >
> > > > > Sure. I never know what the right time is. Would that be after 2.6.23
> > > > > has come out, your big bunch-o-patches has gone to Linus, and shortly
> > > > > before 2.6.24-rc1?
> > > > >
> > > >
> > > > Yes, that works. I was carrying a Lindent-UFS patch for a month and it
> > > > broke regularly. But it was trivial to fix: I'd just rerun `Lindent
> > > > fs/ufs/*.c' to regenerate it. Then reapply the manual-post-lindent-fixups
> > > > patch on top of that, and fix any remaining rejects.
> > >
> > > It sounds like it'd be more convenient for you if I made a single
> > > Lindent-PNP patch plus a post-lindent-fixups patch, rather than
> > > separating things by files.
> >
> > yup
> >
> > > I'll try to remember to do that after
> > > 2.6.23 comes out.
> >
> > thanks.
> >
> > We could do it now if it's more convenient for you - there's not usually
> > much happening in that area.
>
> I agree it would be make-work to carry Lindent patches in -mm.
>
> I think it is also a PITA to push them to Linus before RC1
> because that is when a huge torrent of functional patches go in.
>
> I think that between RC1 and RC2 (now) is as good a time as any
> to push a Lindent cleanup to Linus. If you guys agree, I'll
> be happy to Lindent pnp and push it right now. Heck, I try
> to keep acpi Lindent-clean, so I could do that at the same time.
>
> Bjorn, did you have to do any manual fix-ups to Lindent, or
> did it actually get it right automatically?
> Over time, I've actually changed some of the syntax of the ACPI code
> so that it wouldn't confuse subsequent Lindent passes:-)
> In particular, it didn't like macros that included their own ';'s.
>
Yes, the best time for large code-motion patches and large
whitespace-wrangling patches is shortly before or shortly after -rc1.
Pleae ensure that the PNP whitespace-wrangling makes no change in code
generation. Let's get it done?
prev parent reply other threads:[~2007-07-25 21:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 21:27 [patch 00/17] PNP Lindent helgaas
2007-07-23 21:27 ` [patch 01/17] PNP: Lindent card.c helgaas
2007-07-23 21:27 ` [patch 02/17] PNP: Lindent core.c helgaas
2007-07-23 21:28 ` [patch 03/17] PNP: Lindent driver.c helgaas
2007-07-23 21:28 ` [patch 04/17] PNP: Lindent interface.c helgaas
2007-07-23 21:28 ` [patch 05/17] PNP: Lindent manager.c helgaas
2007-07-23 21:28 ` [patch 06/17] PNP: Lindent quirks.c helgaas
2007-07-23 21:28 ` [patch 07/17] PNP: Lindent resource.c helgaas
2007-07-23 21:28 ` [patch 08/17] PNP: Lindent support.c helgaas
2007-07-23 21:28 ` [patch 09/17] ISAPNP: Lindent core.c helgaas
2007-07-23 21:28 ` [patch 10/17] ISAPNP: Lindent proc.c helgaas
2007-07-23 21:28 ` [patch 11/17] PNPBIOS: remove unused bioscalls code helgaas
2007-07-23 21:28 ` [patch 12/17] PNPBIOS: Lindent bioscalls.c helgaas
2007-07-23 21:28 ` [patch 13/17] PNPBIOS: Lindent core.c helgaas
2007-07-23 21:28 ` [patch 14/17] PNPBIOS: Lindent proc.c helgaas
2007-07-23 21:28 ` [patch 15/17] PNPBIOS: Lindent rsparser.c helgaas
2007-07-23 21:28 ` [patch 16/17] PNPACPI: Lindent core.c helgaas
2007-07-23 21:28 ` [patch 17/17] PNPACPI: Lindent rsparser.c helgaas
2007-07-23 22:08 ` [patch 00/17] PNP Lindent Andrew Morton
2007-07-23 22:39 ` Bjorn Helgaas
2007-07-23 22:49 ` Andrew Morton
2007-07-23 22:53 ` Bjorn Helgaas
2007-07-23 23:00 ` Andrew Morton
2007-07-25 16:24 ` Len Brown
2007-07-25 16:57 ` Bjorn Helgaas
2007-07-25 21:53 ` Andrew Morton [this message]
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=20070725145322.3ad5bd41.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=helgaas@ldl.fc.hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=perex@suse.cz \
--cc=torvalds@linux-foundation.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