From: Greg KH <gregkh@linuxfoundation.org>
To: cgel.zte@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
ye xingchen <ye.xingchen@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] eeprom: at24:using the pm_runtime_resume_and_get to simplify the code
Date: Wed, 3 Aug 2022 08:22:16 +0200 [thread overview]
Message-ID: <YuoUGD2M0sDV2KCy@kroah.com> (raw)
In-Reply-To: <20220803061618.1650538-1-ye.xingchen@zte.com.cn>
On Wed, Aug 03, 2022 at 06:16:18AM +0000, cgel.zte@gmail.com wrote:
> From: ye xingchen <ye.xingchen@zte.com.cn>
>
> Using pm_runtime_resume_and_get() to instade of pm_runtime_get_sync
> and pm_runtime_put_noidle.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
> ---
> drivers/misc/eeprom/at24.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
> index 633e1cf08d6e..f354b79619d8 100644
> --- a/drivers/misc/eeprom/at24.c
> +++ b/drivers/misc/eeprom/at24.c
> @@ -431,9 +431,8 @@ static int at24_read(void *priv, unsigned int off, void *val, size_t count)
> if (off + count > at24->byte_len)
> return -EINVAL;
>
> - ret = pm_runtime_get_sync(dev);
> + ret = pm_runtime_resume_and_get(dev);
> if (ret < 0) {
> - pm_runtime_put_noidle(dev);
> return ret;
> }
>
> @@ -478,9 +477,8 @@ static int at24_write(void *priv, unsigned int off, void *val, size_t count)
> if (off + count > at24->byte_len)
> return -EINVAL;
>
> - ret = pm_runtime_get_sync(dev);
> + ret = pm_runtime_resume_and_get(dev);
> if (ret < 0) {
> - pm_runtime_put_noidle(dev);
> return ret;
> }
>
> --
> 2.25.1
Again, please read:
https://lore.kernel.org/r/YujeLEMsIrVD2tGn@kroah.com
prev parent reply other threads:[~2022-08-03 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 6:16 [PATCH linux-next] eeprom: at24:using the pm_runtime_resume_and_get to simplify the code cgel.zte
2022-08-03 6:22 ` Greg KH [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=YuoUGD2M0sDV2KCy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cgel.zte@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ye.xingchen@zte.com.cn \
--cc=zealci@zte.com.cn \
/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