From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, lists@binarus.de
Subject: Re: [PATCH] PCI: Add Marvell 9128 to DMA alias quirks
Date: Tue, 16 Jan 2018 11:43:04 -0600 [thread overview]
Message-ID: <20180116174304.GA10860@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20180116170457.22911.89578.stgit@gimli.home>
On Tue, Jan 16, 2018 at 10:05:26AM -0700, Alex Williamson wrote:
> This is the original device generating bug 42679, from which many
> other Marvell DMA alias quirks have been sourced, but we didn't have
> positive confirmation of the fix on 9128 until now.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=42679
> Link: https://www.spinics.net/lists/kvm/msg161459.html
> Reported-by: Binarus <lists@binarus.de>
> Tested-by: Binarus <lists@binarus.de>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Applied to pci/virtualization for v4.16, thanks!
> ---
> drivers/pci/quirks.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 10684b17d0bd..db0c652c01cb 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -3879,6 +3879,8 @@ static void quirk_dma_func1_alias(struct pci_dev *dev)
> quirk_dma_func1_alias);
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9123,
> quirk_dma_func1_alias);
> +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9128,
> + quirk_dma_func1_alias);
> /* https://bugzilla.kernel.org/show_bug.cgi?id=42679#c14 */
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_MARVELL_EXT, 0x9130,
> quirk_dma_func1_alias);
>
prev parent reply other threads:[~2018-01-16 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 17:05 Alex Williamson
2018-01-16 17:43 ` Bjorn Helgaas [this message]
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=20180116174304.GA10860@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lists@binarus.de \
/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
all inboxes | Powered by JetHome®