From: Joerg Roedel <joro@8bytes.org>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, baolu.lu@linux.intel.com,
suravee.suthikulpanit@amd.com, robin.murphy@arm.com,
will@kernel.org, "Felix Kuehling" <Felix.Kuehling@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
"Christian König" <christian.koenig@amd.com>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Matt Fagnani" <matt.fagnani@bell.net>
Subject: Re: [PATCH v3 1/3] iommu: Attach device group to old domain in error path
Date: Sat, 18 Feb 2023 15:42:04 +0100 [thread overview]
Message-ID: <Y/DilsJ9ItuWXhGU@8bytes.org> (raw)
In-Reply-To: <0f6e2838-9d7f-dc2c-6e5b-0d02e239f032@amd.com>
On Fri, Feb 17, 2023 at 11:23:36AM +0530, Vasant Hegde wrote:
> Can you consider this patch for 6.2?
Queued to core branch for 6.2.
next prev parent reply other threads:[~2023-02-18 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 5:26 [PATCH v3 1/3] iommu: Attach device group to old domain in error path Vasant Hegde
2023-02-15 5:26 ` [PATCH v3 2/3] iommu/amd: Skip attach device domain is same as new domain Vasant Hegde
2023-02-15 5:26 ` [PATCH v3 3/3] iommu/amd: Improve page fault error reporting Vasant Hegde
2023-02-16 9:41 ` Thorsten Leemhuis
2023-02-17 5:56 ` Vasant Hegde
2023-02-17 6:11 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-16 10:18 ` Joerg Roedel
2023-02-17 5:53 ` [PATCH v3 1/3] iommu: Attach device group to old domain in error path Vasant Hegde
2023-02-18 14:42 ` Joerg Roedel [this message]
2023-02-19 10:17 ` Vasant Hegde
2023-03-12 14:42 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-13 4:29 ` Vasant Hegde
2023-03-13 6:29 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-17 13:44 ` Jason Gunthorpe
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=Y/DilsJ9ItuWXhGU@8bytes.org \
--to=joro@8bytes.org \
--cc=Felix.Kuehling@amd.com \
--cc=alexander.deucher@amd.com \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=matt.fagnani@bell.net \
--cc=regressions@leemhuis.info \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--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.