From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: kevin.tian@intel.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH rc v3 0/4] iommufd: Fix veventq_depth boundary
Date: Mon, 1 Jun 2026 09:07:54 -0300 [thread overview]
Message-ID: <20260601120754.GF3195266@nvidia.com> (raw)
In-Reply-To: <cover.1779734952.git.nicolinc@nvidia.com>
On Mon, May 25, 2026 at 11:51:20AM -0700, Nicolin Chen wrote:
> Nicolin Chen (4):
> iommufd: Fix data_len byte-count vs element-count mismatch
> iommufd: Move vevent memory allocation outside spinlock
> iommufd: Set veventq_depth upper bound
> iommufd/selftest: Add boundary tests for veventq_depth
Applied to for-next
Thanks
Jason
next prev parent reply other threads:[~2026-06-01 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 18:51 [PATCH rc v3 0/4] iommufd: Fix veventq_depth boundary Nicolin Chen
2026-05-25 18:51 ` [PATCH rc v3 1/4] iommufd: Fix data_len byte-count vs element-count mismatch Nicolin Chen
2026-05-25 18:51 ` [PATCH rc v3 2/4] iommufd: Move vevent memory allocation outside spinlock Nicolin Chen
2026-05-25 18:51 ` [PATCH rc v3 3/4] iommufd: Set veventq_depth upper bound Nicolin Chen
2026-05-25 18:51 ` [PATCH rc v3 4/4] iommufd/selftest: Add boundary tests for veventq_depth Nicolin Chen
2026-06-01 12:07 ` Jason Gunthorpe [this message]
2026-06-01 18:27 ` [PATCH rc v3 0/4] iommufd: Fix veventq_depth boundary Nicolin Chen
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=20260601120754.GF3195266@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=nicolinc@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox