From: Tianyu Lan <ltykernel@gmail.com>
To: "hch@infradead.org" <hch@infradead.org>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"paulmck@kernel.org" <paulmck@kernel.org>,
"bp@suse.de" <bp@suse.de>,
"keescook@chromium.org" <keescook@chromium.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"pmladek@suse.com" <pmladek@suse.com>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"damien.lemoal@opensource.wdc.com"
<damien.lemoal@opensource.wdc.com>,
KY Srinivasan <kys@microsoft.com>,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
vkuznets <vkuznets@redhat.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
"parri.andrea@gmail.com" <parri.andrea@gmail.com>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"kirill.shutemov@intel.com" <kirill.shutemov@intel.com>,
"andi.kleen@intel.com" <andi.kleen@intel.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH V4] swiotlb: Split up single swiotlb lock
Date: Wed, 20 Jul 2022 14:23:57 +0800 [thread overview]
Message-ID: <020db88c-981f-01fb-9689-3e54824f260a@gmail.com> (raw)
In-Reply-To: <YtefA9mZJo5+YzBG@infradead.org>
On 7/20/2022 2:21 PM, hch@infradead.org wrote:
> Tianyu or Michael, can someone please send me a fixup patch for this?
>
Sure. I will do this soon.
prev parent reply other threads:[~2022-07-20 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 16:15 [PATCH V4] swiotlb: Split up single swiotlb lock Tianyu Lan
2022-07-12 6:44 ` Christoph Hellwig
2022-07-18 17:41 ` Michael Kelley (LINUX)
2022-07-20 6:21 ` hch
2022-07-20 6:23 ` Tianyu Lan [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=020db88c-981f-01fb-9689-3e54824f260a@gmail.com \
--to=ltykernel@gmail.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@intel.com \
--cc=kys@microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mikelley@microsoft.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=thomas.lendacky@amd.com \
--cc=vkuznets@redhat.com \
--cc=wei.liu@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).