From: David Woodhouse <dwmw2@infradead.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Lawrynowicz, Jacek" <jacek.lawrynowicz@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"jroedel@suse.de" <jroedel@suse.de>
Subject: Re: [PATCH] pci: Add support for multiple DMA aliases
Date: Thu, 21 Jan 2016 15:32:37 +0000 [thread overview]
Message-ID: <1453390357.4639.101.camel@infradead.org> (raw)
In-Reply-To: <20160121152236.GA6629@localhost>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Thu, 2016-01-21 at 09:22 -0600, Bjorn Helgaas wrote:
>
> This definitely isn't part of the driver code; I didn't mean to
> suggest that. I'd like to see this as a separate patch, but as part
> of a series that adds a user of the multiple-alias functionality.
>
> All I'm saying is that as-is, this patch makes the quirks easier to
> read but doesn't actually change any behavior: we set up at most one
> alias, and we do it as a header quirk at enumeration-time, so there
> are no new lifetime issues. Normally we merge things when they're
> needed, and multiple alias support is a bit of infrastructure that
> isn't used yet.
Ah, right. I see your point.
I don't actually see why pci_add_dma_alias() should be exported at all.
I suspect the best approach is for Jacek to add a second patch in this
series, adding the required quirk to drivers/pci/quirks.c for the
device in question, and then resubmit them to you when Linus releases
4.5-rc1.
This is completely independent of any native driver for the device, of
course.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2016-01-21 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 11:59 [PATCH] pci: Add support for multiple DMA aliases Jacek Lawrynowicz
2016-01-18 16:07 ` Jacek Lawrynowicz
2016-01-19 3:33 ` Bjorn Helgaas
2016-01-19 9:21 ` Lawrynowicz, Jacek
2016-01-19 20:12 ` Bjorn Helgaas
2016-01-19 21:04 ` Alex Williamson
2016-01-19 21:39 ` Bjorn Helgaas
2016-01-20 15:02 ` Lawrynowicz, Jacek
2016-01-20 17:46 ` Bjorn Helgaas
2016-01-21 9:39 ` David Woodhouse
2016-01-21 15:22 ` Bjorn Helgaas
2016-01-21 15:32 ` David Woodhouse [this message]
2016-01-26 10:15 ` Lawrynowicz, Jacek
2016-01-21 12:43 ` Lawrynowicz, Jacek
-- strict thread matches above, loose matches on Subject: below --
2016-02-29 22:44 [PATCH v4 3/6] PCI: " Bjorn Helgaas
2016-03-03 14:22 ` [PATCH] " Jacek Lawrynowicz
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=1453390357.4639.101.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jacek.lawrynowicz@intel.com \
--cc=jroedel@suse.de \
--cc=linux-pci@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).