From: Christoph Hellwig <hch@lst.de>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Christoph Hellwig <hch@lst.de>,
jgross@suse.com, xen-devel@lists.xenproject.org,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org,
Rahul Singh <Rahul.Singh@arm.com>
Subject: Re: [PATCH] swiotlb-xen: fix DMA_ATTR_NO_KERNEL_MAPPING on arm
Date: Mon, 9 May 2022 08:18:00 +0200 [thread overview]
Message-ID: <20220509061800.GC17190@lst.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2204281548320.915916@ubuntu-linux-20-04-desktop>
On Thu, Apr 28, 2022 at 03:49:53PM -0700, Stefano Stabellini wrote:
> On one hand, Linux doesn't boot on a platform without this fix. On the
> other hand, I totally see that this patch could introduce regressions on
> x86 so I think it is fair that we are careful with it.
>
> >From my point of view, it might be better to wait for 5.19 and mark it
> as backport.
Sounds good to me. Based on the other mails I assume you want me to
take it through the dma-mapping tree, so I will do that tomorrow unless
I hear otherwise.
_______________________________________________
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-05-09 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 17:14 [PATCH] swiotlb-xen: fix DMA_ATTR_NO_KERNEL_MAPPING on arm Christoph Hellwig
2022-04-26 12:42 ` Rahul Singh
2022-04-26 23:07 ` Stefano Stabellini
2022-04-28 13:27 ` Christoph Hellwig
2022-04-28 21:49 ` Stefano Stabellini
2022-04-28 22:47 ` Boris Ostrovsky
2022-04-28 22:49 ` Stefano Stabellini
2022-04-29 23:12 ` Boris Ostrovsky
2022-04-29 23:15 ` Stefano Stabellini
2022-05-11 14:13 ` Christoph Hellwig
2022-05-11 20:28 ` Stefano Stabellini
2022-05-09 6:18 ` Christoph Hellwig [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=20220509061800.GC17190@lst.de \
--to=hch@lst.de \
--cc=Rahul.Singh@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgross@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).