From: Dan Carpenter <dan.carpenter@oracle.com>
To: FelixCuioc <FelixCui-oc@zhaoxin.com>
Cc: kbuild-all@lists.01.org, CobeChen-oc@zhaoxin.com,
kbuild@lists.01.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, TonyWWang-oc@zhaoxin.com,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 3/3] iommu/vt-d:Add mutex_unlock() before returning
Date: Wed, 26 Aug 2020 13:59:59 +0300 [thread overview]
Message-ID: <20200826105959.GB5493@kadam> (raw)
In-Reply-To: <20200826102752.3776-4-FelixCui-oc@zhaoxin.com>
On Wed, Aug 26, 2020 at 06:27:52AM -0400, FelixCuioc wrote:
> In the probe_acpi_namespace_devices function,when the physical
> node of the acpi device is NULL,the unlock function is missing.
> Add mutex_unlock(&adev->physical_node_lock).
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: FelixCuioc <FelixCui-oc@zhaoxin.com>
Oh... Crap. I wondered why I was being CC'd on this patchset. Just
fold this into the ealier patch. Don't worry about the Reported-by.
regards,
dan carpenter
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-08-26 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 10:27 [PATCH v2 0/3] Add support for ACPI device in RMRR to access reserved memory FelixCuioc
2020-08-26 10:27 ` [PATCH 1/3] iommu/vt-d:Add support for detecting ACPI device in RMRR FelixCuioc
2020-08-26 10:54 ` Dan Carpenter
2020-08-26 10:27 ` [PATCH 2/3] iommu/vt-d:Add support for probing " FelixCuioc
2020-08-26 10:58 ` Dan Carpenter
2020-08-26 10:27 ` [PATCH 3/3] iommu/vt-d:Add mutex_unlock() before returning FelixCuioc
2020-08-26 10:59 ` Dan Carpenter [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=20200826105959.GB5493@kadam \
--to=dan.carpenter@oracle.com \
--cc=CobeChen-oc@zhaoxin.com \
--cc=FelixCui-oc@zhaoxin.com \
--cc=TonyWWang-oc@zhaoxin.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).