From: "Li,Rongqing" <lirongqing@baidu.com>
To: Vasant Hegde <vasant.hegde@amd.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"will@kernel.org" <will@kernel.org>,
"joro@8bytes.org" <joro@8bytes.org>
Subject: 答复: [外部邮件] Re: [PATCH] iommu: move the adding group info to proper place
Date: Mon, 6 Jan 2025 12:15:36 +0000 [thread overview]
Message-ID: <e67792513f494bb385d9ca86d82d10f5@baidu.com> (raw)
In-Reply-To: <ac420b8a-cd5b-41dc-8a4d-247f560a9043@amd.com>
>
> On 1/3/2025 10:58 AM, Li RongQing wrote:
> > After commit fa0828036488 ("iommu: Split iommu_group_add_device()"),
> > the adding group information is left in iommu_group_alloc_device, but
> >
> > @@ -1230,6 +1229,10 @@ int iommu_group_add_device(struct
> iommu_group
> > *group, struct device *dev)
>
> Add error message if iommu_group_alloc_device() fails here?
>
Ok, I will add a error message here
Thanks
-Li
> -Vasant
prev parent reply other threads:[~2025-01-06 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 5:28 [PATCH] iommu: move the adding group info to proper place Li RongQing
2025-01-06 1:06 ` Baolu Lu
2025-01-06 10:55 ` Vasant Hegde
2025-01-06 12:15 ` Li,Rongqing [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=e67792513f494bb385d9ca86d82d10f5@baidu.com \
--to=lirongqing@baidu.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox