From: Thierry Reding <thierry.reding@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] PCI: Use device_match_always()
Date: Fri, 10 Jun 2016 18:33:52 +0200 [thread overview]
Message-ID: <20160610163352.GS27142@ulmo.ba.sec> (raw)
In-Reply-To: <20160610161343.GH19309@localhost>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On Fri, Jun 10, 2016 at 11:13:43AM -0500, Bjorn Helgaas wrote:
> On Mon, Jun 06, 2016 at 09:32:37AM +0200, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > There is now a common implementation for a match function that will
> > always match, so the PCI-specific implementation can be removed.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>
> I'm sort of OK with this. It's clearly not going to break anything.
>
> But I would far rather figure out a way to remove no_pci_devices()
> completely. There's only one in-tree caller, and it's sort of
> dubious, although the idea was added by Linus (2bff5e94f1bf).
This is sort of a spin-off from another series that I sent out, which
introduced a common function that was used in far more places and has
a more clearly legitimate use. While working on that other series the
duplication here occurred to me, so I thought I'd remove it while at
it, even if there are only two occurrences.
> I suppose nowadays we would use ACPI or DMI to do this. But I guess
> this is OK as-is. It'd be pretty hard to find a PC110 to test any
> real driver changes.
>
> I assume all three of these patches would get merged together by
> somebody else.
I was thinking Greg could take them through the driver core tree.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-10 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 7:32 [PATCH 1/3] driver-core: Implement device_match_always() Thierry Reding
2016-06-06 7:32 ` [PATCH 2/3] PCI: Use device_match_always() Thierry Reding
2016-06-10 16:13 ` Bjorn Helgaas
2016-06-10 16:33 ` Thierry Reding [this message]
2016-06-06 7:32 ` [PATCH 3/3] scsi: " Thierry Reding
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=20160610163352.GS27142@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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).