linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Petr Tesarik <petrtesarik@huaweicloud.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jianxiong Gao <jxgao@google.com>,
	David Stevens <stevensd@chromium.org>,
	Joerg Roedel <jroedel@suse.de>,
	"open list:DMA MAPPING HELPERS" <iommu@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>,
	Roberto Sassu <roberto.sassu@huawei.com>,
	petr@tesarici.cz
Subject: Re: [PATCH v1 0/2] swiotlb: Cleanup and alignment fix
Date: Wed, 22 Mar 2023 09:05:11 +0100	[thread overview]
Message-ID: <20230322080511.GA21440@lst.de> (raw)
In-Reply-To: <cover.1679382779.git.petr.tesarik.ext@huawei.com>

Thanks,

I've applied this to the for-linus branch with minor cosmetic tweaks.

      parent reply	other threads:[~2023-03-22  8:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21  8:31 [PATCH v1 0/2] swiotlb: Cleanup and alignment fix Petr Tesarik
2023-03-21  8:31 ` [PATCH v1 1/2] swiotlb: Use wrap_area_index() instead of open-coding it Petr Tesarik
2023-03-21  8:31 ` [PATCH v1 2/2] swiotlb: Fix slot alignment checks Petr Tesarik
2023-04-04 19:55   ` Dexuan-Linux Cui
2023-04-04 20:11     ` Dexuan Cui
2023-04-05  4:40       ` Petr Tesařík
2023-04-05  5:11         ` Dexuan Cui
2023-04-05  5:32           ` Petr Tesařík
2023-04-05  5:50             ` Petr Tesařík
2023-04-05  6:00               ` Dexuan Cui
2023-04-05  6:07                 ` Petr Tesařík
2023-04-05  6:34                   ` Dexuan Cui
2023-04-06  4:52               ` Kelsey Steele
2023-04-06 14:42                 ` Petr Tesarik
2023-04-07  4:13                   ` Kelsey Steele
2023-04-11 15:46                     ` Petr Tesarik
2023-04-05 12:24     ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-03-22  8:05 ` Christoph Hellwig [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=20230322080511.GA21440@lst.de \
    --to=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=jroedel@suse.de \
    --cc=jxgao@google.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=petr@tesarici.cz \
    --cc=petrtesarik@huaweicloud.com \
    --cc=roberto.sassu@huawei.com \
    --cc=robin.murphy@arm.com \
    --cc=stevensd@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 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).