From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, Ralf Jung <ralfjung-e@gmx.de>,
Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH] PCI hotplug: shpchp: don't blindly claim non-AMD 0x7450 device IDs
Date: Mon, 14 Nov 2011 09:43:55 -0800 [thread overview]
Message-ID: <20111114094355.4f1c7f19@jbarnes-desktop> (raw)
In-Reply-To: <CAErSpo6KSYqyj_oOVLo=rQFPZhE=CawZrhcF3TJT4sjnev9G+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On Mon, 14 Nov 2011 10:37:14 -0700
Bjorn Helgaas <bhelgaas@google.com> wrote:
> On Fri, Aug 26, 2011 at 3:24 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > On Tue, 23 Aug 2011 10:16:43 -0600
> > Bjorn Helgaas <bhelgaas@google.com> wrote:
> >
> >> Previously we claimed device ID 0x7450, regardless of the vendor, which is
> >> clearly wrong. Now we'll claim that device ID only for AMD.
> >>
> >> I suspect this was just a typo in the original code, but it's possible this
> >> change will break shpchp on non-7450 AMD bridges. If so, we'll have to fix
> >> them as we find them.
> >
> > Applied to my for-linus branch, thanks.
>
> Jesse, I think this one got lost (at least, I don't see it in the
> current upstream tree).
Thanks for checking; looks like it got lost in my kernel.org transition
somehow. Queued to for-linus now.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-11-14 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110823161643.27268.89203.stgit@bhelgaas.mtv.corp.google.com>
[not found] ` <20110826142424.4757cfe9@jbarnes-desktop>
2011-11-14 17:37 ` [PATCH] PCI hotplug: shpchp: don't blindly claim non-AMD 0x7450 device IDs Bjorn Helgaas
2011-11-14 17:43 ` 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=20111114094355.4f1c7f19@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=joerg.roedel@amd.com \
--cc=linux-pci@vger.kernel.org \
--cc=ralfjung-e@gmx.de \
/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