From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: thomas.lendacky@amd.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, iommu@lists.linux-foundation.org,
rientjes@google.com, hch@lst.de
Subject: Re: [PATCH] dma-direct: Don't over-decrypt memory
Date: Sun, 22 May 2022 15:07:52 +0200 [thread overview]
Message-ID: <20220522130752.GA25785@lst.de> (raw)
In-Reply-To: <796ddc256b8a3054cb0b2f43363613463fcf0d61.1653066613.git.robin.murphy@arm.com>
Thanks,
applied to the dma-mapping for-next branch.
_______________________________________________
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, m.szyprowski@samsung.com,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
thomas.lendacky@amd.com, rientjes@google.com,
stable@vger.kernel.org
Subject: Re: [PATCH] dma-direct: Don't over-decrypt memory
Date: Sun, 22 May 2022 15:07:52 +0200 [thread overview]
Message-ID: <20220522130752.GA25785@lst.de> (raw)
In-Reply-To: <796ddc256b8a3054cb0b2f43363613463fcf0d61.1653066613.git.robin.murphy@arm.com>
Thanks,
applied to the dma-mapping for-next branch.
next prev parent reply other threads:[~2022-05-22 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 17:10 [PATCH] dma-direct: Don't over-decrypt memory Robin Murphy
2022-05-20 17:10 ` Robin Murphy
2022-05-22 13:07 ` Christoph Hellwig [this message]
2022-05-22 13:07 ` Christoph Hellwig
2022-05-23 1:04 ` David Rientjes via iommu
2022-05-23 1:04 ` David Rientjes
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=20220522130752.GA25785@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.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 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.