All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: Andrew Jones <andrew.jones@oss.qualcomm.com>
Cc: iommu@lists.linux.dev, linux-riscv@lists.infradead.org,
	 linux-kernel@vger.kernel.org, jgg@nvidia.com,
	tomasz.jeznach@linux.dev, will@kernel.org,  robin.murphy@arm.com,
	pjw@kernel.org, palmer@dabbelt.com
Subject: Re: [PATCH] iommu/riscv: Report cache coherency capability
Date: Thu, 24 Sep 2026 13:19:45 +0200	[thread overview]
Message-ID: <arUHQrcUWgU5nbVE@8bytes.org> (raw)
In-Reply-To: <20260821112100.572037-1-andrew.jones@oss.qualcomm.com>

On Fri, Aug 21, 2026 at 01:21:00PM +0200, Andrew Jones wrote:
>  drivers/iommu/riscv/iommu.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)

Applied, thanks.


WARNING: multiple messages have this Message-ID (diff)
From: "Jörg Rödel" <joro@8bytes.org>
To: Andrew Jones <andrew.jones@oss.qualcomm.com>
Cc: iommu@lists.linux.dev, linux-riscv@lists.infradead.org,
	 linux-kernel@vger.kernel.org, jgg@nvidia.com,
	tomasz.jeznach@linux.dev, will@kernel.org,  robin.murphy@arm.com,
	pjw@kernel.org, palmer@dabbelt.com
Subject: Re: [PATCH] iommu/riscv: Report cache coherency capability
Date: Thu, 24 Sep 2026 13:19:45 +0200	[thread overview]
Message-ID: <arUHQrcUWgU5nbVE@8bytes.org> (raw)
In-Reply-To: <20260821112100.572037-1-andrew.jones@oss.qualcomm.com>

On Fri, Aug 21, 2026 at 01:21:00PM +0200, Andrew Jones wrote:
>  drivers/iommu/riscv/iommu.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)

Applied, thanks.


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

  reply	other threads:[~2026-09-24 11:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 11:21 [PATCH] iommu/riscv: Report cache coherency capability Andrew Jones
2026-08-21 11:21 ` Andrew Jones
2026-09-24 11:19 ` Jörg Rödel [this message]
2026-09-24 11:19   ` Jörg Rödel

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=arUHQrcUWgU5nbVE@8bytes.org \
    --to=joro@8bytes.org \
    --cc=andrew.jones@oss.qualcomm.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=tomasz.jeznach@linux.dev \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.