From: Koba Ko <kobak@nvidia.com>
To: "Zhang, Rui" <rui.zhang@intel.com>,
"mochs@nvidia.com" <mochs@nvidia.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"erik.kaneda@intel.com" <erik.kaneda@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] acpi/prmt: find block with specific type
Date: Wed, 21 Aug 2024 15:03:34 +0800 [thread overview]
Message-ID: <a5580488-afd1-4c2f-92e6-e42430d61ea2@nvidia.com> (raw)
In-Reply-To: <13f458859adcb75d0930f1a76d7c0e2f74f5e7d5.camel@intel.com>
On 8/21/24 14:48, Zhang, Rui wrote:
> External email: Use caution opening links or attachments
>
>
> On Wed, 2024-08-21 at 14:36 +0800, Koba Ko wrote:
>> On 8/21/24 14:33, Zhang, Rui wrote:
>>> Yeah, but I mean pr_err() may be overkill if the driver is still
>>> functional.
>> how about replace with pr_warn?
> when it fails,
> 1. the address space handler still returns AE_OK (is it right?)
> 2. I don't see how PRM_HANDLER_GUID_NOT_FOUND prm_status is handled
>
> So, if it is a critical error, we should fail the prmt probe
> immediately.
> If it is not, we can let space handler returns AE_OK like you do in
> this patch, and in this case, even a pr_info() is sufficient IMV.
>
> thanks,
> rui
Agree with you. it's worse to determine the failure on another place.
better way like yours, when get failure,
just complain and block the procedure in the scene.
also will modify in the v2.
thanks
next prev parent reply other threads:[~2024-08-21 7:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 1:48 [PATCH] acpi/prmt: find block with specific type KobaK
2024-08-21 3:20 ` Zhang, Rui
2024-08-21 4:01 ` Koba Ko
2024-08-21 4:55 ` Zhang, Rui
2024-08-21 5:48 ` Koba Ko
2024-08-21 6:33 ` Zhang, Rui
2024-08-21 6:36 ` Koba Ko
2024-08-21 6:48 ` Zhang, Rui
2024-08-21 7:03 ` Koba Ko [this message]
2024-08-21 7:55 ` Koba Ko
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=a5580488-afd1-4c2f-92e6-e42430d61ea2@nvidia.com \
--to=kobak@nvidia.com \
--cc=erik.kaneda@intel.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochs@nvidia.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@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