All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: guozhengkui@vivo.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org, tientzu@chromium.org,
	hch@lst.de
Subject: Re: [PATCH 0/3] Some minor SWIOTLB cleanups
Date: Wed, 26 Jan 2022 17:21:57 +0100	[thread overview]
Message-ID: <20220126162157.GA31431@lst.de> (raw)
In-Reply-To: <cover.1643028164.git.robin.murphy@arm.com>

Thanks,

applied to the dma-mapping for-next tree.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: hch@lst.de, konrad@kernel.org, iommu@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, tientzu@chromium.org,
	guozhengkui@vivo.com
Subject: Re: [PATCH 0/3] Some minor SWIOTLB cleanups
Date: Wed, 26 Jan 2022 17:21:57 +0100	[thread overview]
Message-ID: <20220126162157.GA31431@lst.de> (raw)
In-Reply-To: <cover.1643028164.git.robin.murphy@arm.com>

Thanks,

applied to the dma-mapping for-next tree.

  parent reply	other threads:[~2022-01-26 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 16:40 [PATCH 0/3] Some minor SWIOTLB cleanups Robin Murphy
2022-01-24 16:40 ` Robin Murphy
2022-01-24 16:40 ` [PATCH 1/3] swiotlb: Simplify debugfs setup Robin Murphy
2022-01-24 16:40   ` Robin Murphy
2022-01-24 16:40 ` [PATCH 2/3] swiotlb: Tidy up includes Robin Murphy
2022-01-24 16:40   ` Robin Murphy
2022-01-24 16:40 ` [PATCH 3/3] swiotlb: Simplify array allocation Robin Murphy
2022-01-24 16:40   ` Robin Murphy
2022-01-26 16:21 ` Christoph Hellwig [this message]
2022-01-26 16:21   ` [PATCH 0/3] Some minor SWIOTLB cleanups Christoph Hellwig

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=20220126162157.GA31431@lst.de \
    --to=hch@lst.de \
    --cc=guozhengkui@vivo.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=tientzu@chromium.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.