From: Christoph Hellwig <hch@lst.de>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Mike Snitzer <snitzer@kernel.org>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org, iommu@lists.linux.dev,
Marek Marczykowski-G'orecki <marmarek@invisiblethingslab.com>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
Jan Kara <jack@suse.cz>, Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
stable@vger.kernel.org, regressions@lists.linux.dev,
Alasdair Kergon <agk@redhat.com>,
dm-devel@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH v2] swiotlb-xen: provide the "max_mapping_size" method
Date: Wed, 8 Nov 2023 08:31:57 +0100 [thread overview]
Message-ID: <20231108073157.GB5277@lst.de> (raw)
In-Reply-To: <151bef41-e817-aea9-675-a35fdac4ed@redhat.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2023-11-08 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZULvkPhcpgAVyI8w@mail-itl>
[not found] ` <ac5b5ac0-9e8-c1b0-a26-62f832f845f0@redhat.com>
[not found] ` <ZUOL8kXVTF1OngeN@mail-itl>
[not found] ` <3cb4133c-b6db-9187-a678-11ed8c9456e@redhat.com>
[not found] ` <ZUUctamEFtAlSnSV@mail-itl>
[not found] ` <ZUUlqJoS6_1IznzT@kbusch-mbp.dhcp.thefacebook.com>
[not found] ` <ZUVYT1Xp4+hFT27W@mail-itl>
[not found] ` <ZUV3TApYYoh_oiRR@kbusch-mbp.dhcp.thefacebook.com>
[not found] ` <11a9886d-316c-edcd-d6da-24ad0b9a2b4@redhat.com>
[not found] ` <ZUZOKitOAqqKiJ4n@kbusch-mbp.dhcp.thefacebook.com>
[not found] ` <20231106071008.GB17022@lst.de>
2023-11-06 14:59 ` [PATCH] swiotlb-xen: provide the "max_mapping_size" method Mikulas Patocka
2023-11-06 15:16 ` Keith Busch
2023-11-06 15:30 ` Mike Snitzer
2023-11-06 17:12 ` [PATCH v2] " Mikulas Patocka
2023-11-07 4:18 ` Stefano Stabellini
2023-11-08 7:31 ` 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=20231108073157.GB5277@lst.de \
--to=hch@lst.de \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=dm-devel@lists.linux.dev \
--cc=iommu@lists.linux.dev \
--cc=jack@suse.cz \
--cc=jgross@suse.com \
--cc=kbusch@kernel.org \
--cc=linux-mm@kvack.org \
--cc=marmarek@invisiblethingslab.com \
--cc=mhocko@suse.com \
--cc=mpatocka@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=sagi@grimberg.me \
--cc=snitzer@kernel.org \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=xen-devel@lists.xenproject.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