From: Christoph Hellwig <hch@infradead.org>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Christoph Hellwig <hch@infradead.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [patchV2 1/2] pci: introduce an extra method for matching in pci_driver
Date: Tue, 12 Jun 2018 23:37:10 -0700 [thread overview]
Message-ID: <20180613063710.GA30350@infradead.org> (raw)
In-Reply-To: <1528871397-17917-2-git-send-email-kernelfans@gmail.com>
If we successfull call ->probe twice on a device we have a much
deeper problem than we can fix in the PCI layer or shpchp.
Please explain the actual race or other condition that can lead to
this and report it to the driver core maintainer.
next prev parent reply other threads:[~2018-06-13 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 6:29 [patchV2 0/2] shpchp: no claim on pcie port device Pingfan Liu
2018-06-13 6:29 ` [patchV2 1/2] pci: introduce an extra method for matching in pci_driver Pingfan Liu
2018-06-13 6:37 ` Christoph Hellwig [this message]
2018-06-13 7:28 ` Pingfan Liu
2018-06-13 6:29 ` [patchV2 2/2] pci/shpchp: no claim on pcie port device Pingfan Liu
2018-06-13 13:13 ` Bjorn Helgaas
2018-06-25 2:59 ` Pingfan 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=20180613063710.GA30350@infradead.org \
--to=hch@infradead.org \
--cc=bhelgaas@google.com \
--cc=kernelfans@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).