linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: iommu@lists.linux.dev, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Rob Clark <robdclark@gmail.com>,
	Gaurav Kohli <quic_gkohli@quicinc.com>,
	Steven Price <steven.price@arm.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	kernel@collabora.com
Subject: Re: [PATCH v3 0/2] iommu: Allow passing custom allocators to pgtable drivers
Date: Mon, 27 Nov 2023 11:10:54 +0100	[thread overview]
Message-ID: <ZWRrLhxEHxzNz41r@8bytes.org> (raw)
In-Reply-To: <20231124142434.1577550-1-boris.brezillon@collabora.com>

On Fri, Nov 24, 2023 at 03:24:32PM +0100, Boris Brezillon wrote:
> Boris Brezillon (2):
>   iommu: Allow passing custom allocators to pgtable drivers
>   iommu: Extend LPAE page table format to support custom allocators
> 
>  drivers/iommu/io-pgtable-arm.c | 55 ++++++++++++++++++++++++----------
>  drivers/iommu/io-pgtable.c     | 23 ++++++++++++++
>  include/linux/io-pgtable.h     | 34 +++++++++++++++++++++
>  3 files changed, 96 insertions(+), 16 deletions(-)

Applied, thanks.

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

  parent reply	other threads:[~2023-11-27 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 14:24 [PATCH v3 0/2] iommu: Allow passing custom allocators to pgtable drivers Boris Brezillon
2023-11-24 14:24 ` [PATCH v3 1/2] " Boris Brezillon
2023-11-24 14:24 ` [PATCH v3 2/2] iommu: Extend LPAE page table format to support custom allocators Boris Brezillon
2023-11-27 10:10 ` Joerg Roedel [this message]
2023-11-27 13:35   ` [PATCH v3 0/2] iommu: Allow passing custom allocators to pgtable drivers Gaurav Kohli

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=ZWRrLhxEHxzNz41r@8bytes.org \
    --to=joro@8bytes.org \
    --cc=boris.brezillon@collabora.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=quic_gkohli@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=steven.price@arm.com \
    --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 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).