From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: kevin.tian@intel.com, nicolinc@nvidia.com,
baolu.lu@linux.intel.com, iommu@lists.linux.dev
Subject: Re: [PATCH 0/2] Two fixes to vevent path
Date: Tue, 25 Mar 2025 10:35:43 -0300 [thread overview]
Message-ID: <Z+KxLzIFFNp9A67E@nvidia.com> (raw)
In-Reply-To: <20250324120034.5940-1-yi.l.liu@intel.com>
On Mon, Mar 24, 2025 at 05:00:32AM -0700, Yi Liu wrote:
> Yi Liu (2):
> iommufd: Initialize the flags of vevent in
> iommufd_viommu_report_event()
> iommufd: Balance veventq->num_events inc/dec
Applied, thanks
Jason
prev parent reply other threads:[~2025-03-25 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 12:00 [PATCH 0/2] Two fixes to vevent path Yi Liu
2025-03-24 12:00 ` [PATCH 1/2] iommufd: Initialize the flags of vevent in iommufd_viommu_report_event() Yi Liu
2025-03-24 14:04 ` Nicolin Chen
2025-03-24 12:00 ` [PATCH 2/2] iommufd: Balance veventq->num_events inc/dec Yi Liu
2025-03-24 14:07 ` Nicolin Chen
2025-03-25 13:35 ` Jason Gunthorpe [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=Z+KxLzIFFNp9A67E@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=nicolinc@nvidia.com \
--cc=yi.l.liu@intel.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