public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, joro@8bytes.org
Cc: Robin Murphy <robin.murphy@arm.com>,
	catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	iommu@lists.linux.dev
Subject: Re: [PATCH] arm64: Properly clean up iommu-dma remnants
Date: Tue, 7 May 2024 10:50:38 +0100	[thread overview]
Message-ID: <20240507095037.GA22185@willie-the-truck> (raw)
In-Reply-To: <CAA8EJpqcCpiuqeU9Bktev9vSa6Gdw1jTn+VAk+xbu9kKPTrjEg@mail.gmail.com>

On Sat, May 04, 2024 at 05:21:12PM +0300, Dmitry Baryshkov wrote:
> On Tue, 30 Apr 2024 at 13:23, Robin Murphy <robin.murphy@arm.com> wrote:
> >
> > Thanks to the somewhat asymmetrical nature, while removing
> > iommu_setup_dma_ops() from the arch_setup_dma_ops() flow, I managed to
> > forget that arm64's teardown path was also specific to iommu-dma. Clean
> > that up to match, otherwise probe deferral will lead to the arch code
> > erroneously removing DMA ops set elsewhere.
> >
> > Reported-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > Link: https://lore.kernel.org/linux-iommu/Zi_LV28TR-P-PzXi@eriador.lumag.spb.ru/
> > Fixes: b67483b3c44e ("iommu/dma: Centralise iommu_setup_dma_ops()")
> > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> > ---
> >  arch/arm64/Kconfig          | 1 -
> >  arch/arm64/mm/dma-mapping.c | 8 --------
> >  2 files changed, 9 deletions(-)
> 
> 
> Just wanted to ping regarding the patch. It's still not a part of
> linux-next, Is it going to be picked up for 6.10?

Oops, thanks Dmitry!

Joerg -- please can you pick this one up for iommu next? It fixes a
commit you already have there, so I think it's best to keep everything
together.

FWIW:

Acked-by: Will Deacon <will@kernel.org>

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-05-07  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 10:22 [PATCH] arm64: Properly clean up iommu-dma remnants Robin Murphy
2024-04-30 10:32 ` Dmitry Baryshkov
2024-04-30 11:00   ` Robin Murphy
2024-04-30 11:22 ` Catalin Marinas
2024-04-30 12:51 ` Konrad Dybcio
2024-05-04 14:21 ` Dmitry Baryshkov
2024-05-07  9:50   ` Will Deacon [this message]
2024-05-09  9:04 ` Nicolin Chen
2024-05-10  7:04 ` Joerg Roedel

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=20240507095037.GA22185@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.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