From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: iommu@lists.linux.dev, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Chen-Yu Tsai <wenst@chromium.org>
Subject: Re: [PATCH 1/3] iommu: Provide iommu_probe_device_locked()
Date: Wed, 9 Aug 2023 11:14:36 +0200 [thread overview]
Message-ID: <ZNNY_NP-dCvSoVa7@8bytes.org> (raw)
In-Reply-To: <1-v1-8612b9ef48da+333-iommu_group_locking2_jgg@nvidia.com>
Hi Jason,
On Tue, Aug 08, 2023 at 02:27:05PM -0300, Jason Gunthorpe wrote:
> Fixes: a2dde836050f ("iommu: Complete the locking for dev->iommu_group")
The right commit-id here is: a16b5d1681ab
Please update the fixes tags and re-send after addressing Kevin's
concerns.
Regards,
Joerg
next prev parent reply other threads:[~2023-08-09 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 17:27 [PATCH 0/3] Fix device_lock deadlock on two probe() paths Jason Gunthorpe
2023-08-08 17:27 ` [PATCH 1/3] iommu: Provide iommu_probe_device_locked() Jason Gunthorpe
2023-08-09 3:55 ` Tian, Kevin
2023-08-09 9:14 ` Joerg Roedel [this message]
2023-08-08 17:27 ` [PATCH 2/3] iommu: Pass in the iommu_device to probe for in bus_iommu_probe() Jason Gunthorpe
2023-08-09 3:57 ` Tian, Kevin
2023-08-08 17:27 ` [PATCH 3/3] iommu: Do not attempt to re-lock the iommu device when probing Jason Gunthorpe
2023-08-09 4:01 ` Tian, Kevin
2023-08-09 12:15 ` Jason Gunthorpe
2023-08-09 13:38 ` Marek Szyprowski
2023-08-09 14:33 ` Jason Gunthorpe
2023-08-08 20:18 ` [PATCH 0/3] Fix device_lock deadlock on two probe() paths Mark Brown
2023-08-08 22:26 ` Jason Gunthorpe
2023-08-09 6:37 ` Chen-Yu Tsai
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=ZNNY_NP-dCvSoVa7@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=wenst@chromium.org \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.