From: Greg KH <greg@kroah.com>
To: Greg KH <gregkh@suse.de>
Cc: 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.17
Date: Wed, 21 Jun 2006 12:25:19 -0700 [thread overview]
Message-ID: <20060621192519.GA22142@kroah.com> (raw)
In-Reply-To: <20060621190246.GA20912@kroah.com>
On Wed, Jun 21, 2006 at 12:02:46PM -0700, Greg KH wrote:
> Here are some PCI fixes and patches for 2.6.17. They do a bunch of work
> getting MSI to work properly on ia64, and fix some other MSI issues. We
> also added a few new sysfs attributes for PCI devices and add some more
> quirks and fix a few minor bugs.
Oh, and others have already noticed, the first patch in this series
fixes a build bug in the current tree where myri10ge.c does not build
due to PCI_CAP_ID_VNDR not being defined.
Sorry about that, it was a dependancy between the network driver tree
and mine.
thanks,
greg k-h
prev parent reply other threads:[~2006-06-21 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 19:02 [GIT PATCH] PCI patches for 2.6.17 Greg KH
2006-06-21 19:25 ` Greg KH [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=20060621192519.GA22142@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--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