Linux IOMMU Development
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@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 11:27:54 -0700	[thread overview]
Message-ID: <ah3PKufmQ7wZEX0U@Asurada-Nvidia> (raw)
In-Reply-To: <20260601120754.GF3195266@nvidia.com>

Hi Jason,

On Mon, Jun 01, 2026 at 09:07:54AM -0300, Jason Gunthorpe wrote:
> 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

Would you please update your remote for-next branch also?

I have a followup series to send. There would be some dependencies
for git-apply and Sashiko review.

Thanks
Nicolin

      reply	other threads:[~2026-06-01 18:28 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 ` [PATCH rc v3 0/4] iommufd: Fix veventq_depth boundary Jason Gunthorpe
2026-06-01 18:27   ` Nicolin Chen [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=ah3PKufmQ7wZEX0U@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.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