From: Jiang Liu <liuj97@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Unable to mount NFSROOT: pcie change breaks e1000?
Date: Thu, 23 Aug 2012 23:03:29 +0800 [thread overview]
Message-ID: <50364641.8010000@gmail.com> (raw)
In-Reply-To: <503587F4.3090907@huawei.com>
Hi Bjorn,
Could you please help to fold this small patch into
"[5/40] PCI/core: Use PCI Express Capability accessors"?
It fixes a bug reported by Fengguang.
Thanks!
Gerry
On 08/23/2012 09:31 AM, Jiang Liu wrote:
> Hi Fengguang,
> Could you please help to verify whether following patch
> fixes the issue?
> Thanks!
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index f6b491b..fac08f5 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -842,6 +842,9 @@ static int pci_save_pcie_state(struct pci_dev *dev)
> struct pci_cap_saved_state *save_state;
> u16 *cap;
>
> + if (!pci_is_pcie(dev))
> + return 0;
> +
> save_state = pci_find_saved_cap(dev, PCI_CAP_ID_EXP);
> if (!save_state) {
> dev_err(&dev->dev, "buffer not found in %s\n", __func__);
>
> On 2012-8-23 8:46, Fengguang Wu wrote:
>> buffer not found
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2012-08-23 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 0:46 Unable to mount NFSROOT: pcie change breaks e1000? Fengguang Wu
2012-08-23 1:31 ` Jiang Liu
2012-08-23 2:33 ` Fengguang Wu
2012-08-23 15:03 ` Jiang Liu [this message]
2012-08-23 16:12 ` Bjorn Helgaas
2012-08-24 14:42 ` Jiang Liu
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=50364641.8010000@gmail.com \
--to=liuj97@gmail.com \
--cc=bhelgaas@google.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.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