From: Heiner Kallweit <hkallweit1@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>, David Miller <davem@davemloft.net>
Cc: linux-pci@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] PCI: add help pci_dev_id
Date: Tue, 23 Apr 2019 08:05:58 +0200 [thread overview]
Message-ID: <14c5ed05-da19-db71-c811-e6457925a069@gmail.com> (raw)
In-Reply-To: <20190422132020.GK173520@google.com>
On 22.04.2019 15:20, Bjorn Helgaas wrote:
> On Fri, Apr 19, 2019 at 03:13:38PM -0700, David Miller wrote:
>> From: Heiner Kallweit <hkallweit1@gmail.com>
>> Date: Fri, 19 Apr 2019 20:27:45 +0200
>>
>>> In several places in the kernel we find PCI_DEVID used like this:
>>> PCI_DEVID(dev->bus->number, dev->devfn) Therefore create a helper
>>> for it.
>>
>> I'll wait for an ACK from the PCI folks on patch #1.
>
> #1 and #2 touch PCI, #3 is a trivial r8169 patch. There are a few
> other places where this helper could be used (powernv/npu-dma.c,
> amdkfd/kfd_topology.c, amd_iommu.c, intel-iommu.c,
> intel_irq_remapping.c, stmmac_pci.c, chromeos_laptop.c).
>
> I think it would be easier for me to collect acks for the trivial
> changes to those places and merge the whole shebang via PCI.
>
> Heiner, do you want to update those other places, too?
>
Yes, will do so.
> Bjorn
>
Heiner
next prev parent reply other threads:[~2019-04-23 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 18:27 [PATCH 0/3] PCI: add help pci_dev_id Heiner Kallweit
2019-04-19 18:28 ` [PATCH 1/3] PCI: add helper pci_dev_id Heiner Kallweit
2019-04-19 18:29 ` [PATCH 2/3] PCI: use " Heiner Kallweit
2019-04-19 18:29 ` [PATCH 3/3] r8169: use new " Heiner Kallweit
2019-04-19 22:13 ` [PATCH 0/3] PCI: add help pci_dev_id David Miller
2019-04-22 13:20 ` Bjorn Helgaas
2019-04-23 4:09 ` David Miller
2019-04-23 6:05 ` Heiner Kallweit [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-19 11:08 Heiner Kallweit
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=14c5ed05-da19-db71-c811-e6457925a069@gmail.com \
--to=hkallweit1@gmail.com \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).