From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: greg@kroah.com, khali@linux-fr.org, miltonm@bga.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, allen.m.kay@intel.com,
jun.nakajima@intel.com
Subject: Re: [PATCH 1/2] PCI: allow pci driver to support only dynids
Date: Mon, 1 Dec 2008 12:41:24 -0800 [thread overview]
Message-ID: <200812011241.24769.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20081126033610.GB19881@sequoia.sous-sol.org>
On Tuesday, November 25, 2008 7:36 pm Chris Wright wrote:
> commit b41d6cf38e27 (PCI: Check dynids driver_data value for validity)
> requires all drivers to include an id table to try and match
> driver_data. Before validating driver_data check driver has an id
> table.
>
> Cc: Jean Delvare <khali@linux-fr.org>
> Cc: Milton Miller <miltonm@bga.com>
> Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Applied these to my linux-next branch, thanks Chris.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2008-12-01 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 3:36 [PATCH 1/2] PCI: allow pci driver to support only dynids Chris Wright
2008-11-26 3:38 ` [PATCH 2/2] PCI: pci-stub module to reserve pci device Chris Wright
2008-11-26 4:19 ` Greg KH
2008-11-26 5:07 ` Chris Wright
2008-11-26 5:17 ` [PATCH 2/2 v2] " Chris Wright
2008-11-26 8:28 ` [PATCH 1/2] PCI: allow pci driver to support only dynids Jean Delvare
2008-11-26 15:19 ` Chris Wright
2008-11-26 20:34 ` Jean Delvare
2008-11-26 21:07 ` Chris Wright
2008-12-01 20:41 ` Jesse Barnes [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=200812011241.24769.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=allen.m.kay@intel.com \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=jun.nakajima@intel.com \
--cc=khali@linux-fr.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=miltonm@bga.com \
/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.