From: Andrew Morton <akpm@linux-foundation.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: 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: Mon, 23 Jul 2007 15:49:09 -0700 [thread overview]
Message-ID: <20070723154909.55862883.akpm@linux-foundation.org> (raw)
In-Reply-To: <200707231639.57796.bjorn.helgaas@hp.com>
On Mon, 23 Jul 2007 16:39:57 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Monday 23 July 2007 04:08:52 pm Andrew Morton wrote:
> > On Mon, 23 Jul 2007 15:27:57 -0600
> > helgaas@ldl.fc.hp.com wrote:
> >
> > > Run PNP files through Lindent. These patches are all completely
> > > independent and contain no functional changes. Object files before
> > > and after are identical.
> > >
> > > These are against current upstream. If you prefer a different base
> > > or drop some of these due to conflicts with things already in -mm,
> > > let me know and I can regenerate them.
> > >
> >
> > eep, this is the worst time for me to merge this stuff: I get to carry
> > large diffs against lots of files for two months.
> >
> > 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.
next prev parent reply other threads:[~2007-07-23 22:50 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 [this message]
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
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=20070723154909.55862883.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=linux-acpi@vger.kernel.org \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.