From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: "Robin Murphy" <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
"Marek Behún" <kabel@kernel.org>
Subject: Re: mvebu DMA fix
Date: Thu, 6 Oct 2022 12:52:04 +0100 [thread overview]
Message-ID: <Yz7BZOkUkQhJUgKf@shell.armlinux.org.uk> (raw)
In-Reply-To: <20221006074824.521457-1-hch@lst.de>
On Thu, Oct 06, 2022 at 09:48:22AM +0200, Christoph Hellwig wrote:
> Hi Russell,
>
> the first patch fixes the regression that overwrites ->dma_coherent after
> the mvebu notifier set it, and the second one removes a now unused field
> in the arm arch_devdata.
>
> Let me know if you want to take these, or if I should route them through
> the dma-mapping tree that introduced this problem.
I think it would make sense to send them through the dma-mapping tree,
so for the series:
Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Thanks for fixing this!
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-10-06 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 7:48 mvebu DMA fix Christoph Hellwig
2022-10-06 7:48 ` [PATCH 1/2] ARM/dma-mappіng: don't override ->dma_coherent when set from a bus notifier Christoph Hellwig
2022-10-06 7:48 ` [PATCH 2/2] ARM/dma-mapping: remove the dma_coherent member of struct dev_archdata Christoph Hellwig
2022-10-06 11:52 ` Russell King (Oracle) [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=Yz7BZOkUkQhJUgKf@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.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).