From: Greg KH <greg@kroah.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: dsaxena@plexity.net, linux-kernel@vger.kernel.org,
ralf@linux-mips.org, akpm@osdl.org
Subject: Re: [PATCH][5/3][ARM] PCI quirks update for ARM
Date: Wed, 4 Aug 2004 15:38:36 -0700 [thread overview]
Message-ID: <20040804223835.GA10284@kroah.com> (raw)
In-Reply-To: <1091625077.4383.2728.camel@hades.cambridge.redhat.com>
On Wed, Aug 04, 2004 at 02:11:18PM +0100, David Woodhouse wrote:
> On Tue, 2004-08-03 at 12:37 -0700, Deepak Saxena wrote:
> > On Aug 03 2004, at 18:33, David Woodhouse was caught saying:
> > > It's a pain in the arse to set up platform-specific PCI quirks -- you
> > > have to put your platform-specific quirk into the generic (or at least
> > > the architecture) array. This patch fixes that, allowing you to
> > > DECLARE_PCI_FIXUP_HEADER() or DECLARE_PCI_FIXUP_FINAL() anywhere you
> > > like.
> >
> > Good idea. Following is ARM patch.
>
> Thanks. I did the rest of the architectures too -- it's all at
> bk://linux-mtd.bkbits.net/quirks-2.6
>
> It probably doesn't want to go to Linus until after 2.6.8 is released,
> but perhaps we could put it in the -mm tree until then?
Thanks, I've pulled all of these into my pci bk tree, and will send them
off to Linus after 2.6.8 is out.
greg k-h
next prev parent reply other threads:[~2004-08-04 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 17:33 [PATCH] [1/3] Split pci quirks array to allow separate declarations David Woodhouse
2004-08-03 17:36 ` [PATCH] [2/3] PCI quirks -- PPC David Woodhouse
2004-08-03 17:38 ` [PATCH] [3/3] PCI quirks -- i386 David Woodhouse
2004-08-03 20:28 ` [PATCH] [2/3] PCI quirks -- PPC Benjamin Herrenschmidt
2004-08-03 23:40 ` David Woodhouse
2004-08-04 0:49 ` Benjamin Herrenschmidt
2004-08-03 19:37 ` [PATCH][5/3][ARM] PCI quirks update for ARM Deepak Saxena
2004-08-04 13:11 ` David Woodhouse
2004-08-04 19:07 ` Andrew Morton
2004-08-04 22:38 ` Greg KH [this message]
2004-08-03 21:47 ` [PATCH] [4/3] PCI quirks -- MIPS Ralf Baechle
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=20040804223835.GA10284@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=dsaxena@plexity.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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 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.