From: Rajesh Shah <rajesh.shah@intel.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Greg KH <gregkh@suse.de>, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [GIT PATCH] PCI patches for 2.6.14
Date: Fri, 28 Oct 2005 16:17:45 -0700 [thread overview]
Message-ID: <20051028161745.A27003@unix-os.sc.intel.com> (raw)
In-Reply-To: <20051028225335.GB21871@parisc-linux.org>; from matthew@wil.cx on Fri, Oct 28, 2005 at 04:53:35PM -0600
On Fri, Oct 28, 2005 at 04:53:35PM -0600, Matthew Wilcox wrote:
> On Fri, Oct 28, 2005 at 03:50:55PM -0700, Greg KH wrote:
> > Here are some PCI patches against your latest git tree. They have all
> > been in the -mm tree for a while with no problems.
> >
> > Main things here are:
> > - pci-ids.h cleanup
> > - shpchp driver cleanup (very good job done here.)
> > - more quirks added.
>
> Does this just about clear you out of pending PCI patches? I want to do
> the s/hotplug_slot/pci_slot/ changes soon and it'll cause massive
> conflicts with anyone else's pending work.
>
> (I suppose I could do a gradual transition with a #define if preferred,
> but a big bang seems like much less effort)
I just got done doing to pciehp what I did to shpchp (major
revamp). The code is working on one machine and I'm testing
on another. I hope to send it out early next week. If you can
wait till then, it'd be great. If I can't send it out by next
week, I can merge my changes on top of yours.
Thanks,
Rajesh
prev parent reply other threads:[~2005-10-28 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 22:50 Greg KH
2005-10-28 22:53 ` Matthew Wilcox
2005-10-28 23:04 ` Greg KH
2005-10-28 23:17 ` Rajesh Shah [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=20051028161745.A27003@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=matthew@wil.cx \
--cc=torvalds@osdl.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
Powered by JetHome