From: Harris Song <songkai01@inspur.com>
To: "rafael@kernel.org" <rafael@kernel.org>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [gmail.com代发]Re: [PATCH] ACPI: CPPC: fix return value in register_pcc_channel()
Date: Mon, 25 Oct 2021 00:55:24 +0000 [thread overview]
Message-ID: <7f64a9b4910343fbb8c4377ddbf4cfd7@inspur.com> (raw)
In-Reply-To: <CAJZ5v0ixPr8WN9hdTtqj1S4XakhH9hJSWJSf9EthdyMEScaOhQ@mail.gmail.com>
> On Fri, Oct 22, 2021 at 9:39 AM Kai Song <songkai01@inspur.com> wrote:
> >
> > It uses IS_ERR to judge the return value of
> > pcc_mbox_request_channel().If it is invalid, maybe we should use
> > PTR_ERR to get the correct return value.
>
> Either there is a reason to make this change or there isn't.
>
> If there is a reason, then what is it?
Thank you for your reminding, pcc_mbox_request_channel() has other return values like -EBUSY.
But I checked through the context , it seems -ENODEV is ok.
So this patch seems harmless but not needed.
Thank you for your time.
Kai
> > Signed-off-by: Kai Song <songkai01@inspur.com>
> > ---
> > drivers/acpi/cppc_acpi.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/acpi/cppc_acpi.c b/drivers/acpi/cppc_acpi.c index
> > bd482108310c..0bbb5fa27ce7 100644
> > --- a/drivers/acpi/cppc_acpi.c
> > +++ b/drivers/acpi/cppc_acpi.c
> > @@ -503,7 +503,7 @@ static int register_pcc_channel(int pcc_ss_idx)
> > if (IS_ERR(pcc_data[pcc_ss_idx]->pcc_channel)) {
> > pr_err("Failed to find PCC channel for subspace %d\n",
> > pcc_ss_idx);
> > - return -ENODEV;
> > + return
> > + PTR_ERR(pcc_data[pcc_ss_idx]->pcc_channel);
> > }
> >
> > /*
> > --
> > 2.27.0
> >
prev parent reply other threads:[~2021-10-25 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 7:39 Kai Song
2021-10-22 12:36 ` Rafael J. Wysocki
2021-10-25 0:55 ` Harris Song [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=7f64a9b4910343fbb8c4377ddbf4cfd7@inspur.com \
--to=songkai01@inspur.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®