From: Hans de Goede <hdegoede@redhat.com>
To: Tang Bin <tangbin@cmss.chinamobile.com>, sre@kernel.org, wens@csie.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhang Shengju <zhangshengju@cmss.chinamobile.com>
Subject: Re: [PATCH] power: supply: axp288_charger: Use the defined variable to clean code
Date: Thu, 12 Aug 2021 17:20:25 +0200 [thread overview]
Message-ID: <60b7038f-2c68-4559-6a97-a5f2bc97647f@redhat.com> (raw)
In-Reply-To: <20210811104929.24608-1-tangbin@cmss.chinamobile.com>
Hi,
On 8/11/21 12:49 PM, Tang Bin wrote:
> Use the defined variable "dev" to make the code cleaner.
>
> Co-developed-by: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
> Signed-off-by: Zhang Shengju <zhangshengju@cmss.chinamobile.com>
> Signed-off-by: Tang Bin <tangbin@cmss.chinamobile.com>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> drivers/power/supply/axp288_charger.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/power/supply/axp288_charger.c b/drivers/power/supply/axp288_charger.c
> index a4df1ea92..b9553be9b 100644
> --- a/drivers/power/supply/axp288_charger.c
> +++ b/drivers/power/supply/axp288_charger.c
> @@ -813,7 +813,7 @@ static int axp288_charger_probe(struct platform_device *pdev)
> if (val == 0)
> return -ENODEV;
>
> - info = devm_kzalloc(&pdev->dev, sizeof(*info), GFP_KERNEL);
> + info = devm_kzalloc(dev, sizeof(*info), GFP_KERNEL);
> if (!info)
> return -ENOMEM;
>
> @@ -823,7 +823,7 @@ static int axp288_charger_probe(struct platform_device *pdev)
>
> info->cable.edev = extcon_get_extcon_dev(AXP288_EXTCON_DEV_NAME);
> if (info->cable.edev == NULL) {
> - dev_dbg(&pdev->dev, "%s is not ready, probe deferred\n",
> + dev_dbg(dev, "%s is not ready, probe deferred\n",
> AXP288_EXTCON_DEV_NAME);
> return -EPROBE_DEFER;
> }
> @@ -834,8 +834,7 @@ static int axp288_charger_probe(struct platform_device *pdev)
> dev_dbg(dev, "EXTCON_USB_HOST is not ready, probe deferred\n");
> return -EPROBE_DEFER;
> }
> - dev_info(&pdev->dev,
> - "Using " USB_HOST_EXTCON_HID " extcon for usb-id\n");
> + dev_info(dev, "Using " USB_HOST_EXTCON_HID " extcon for usb-id\n");
> }
>
> platform_set_drvdata(pdev, info);
> @@ -874,7 +873,7 @@ static int axp288_charger_probe(struct platform_device *pdev)
> INIT_WORK(&info->otg.work, axp288_charger_otg_evt_worker);
> info->otg.id_nb.notifier_call = axp288_charger_handle_otg_evt;
> if (info->otg.cable) {
> - ret = devm_extcon_register_notifier(&pdev->dev, info->otg.cable,
> + ret = devm_extcon_register_notifier(dev, info->otg.cable,
> EXTCON_USB_HOST, &info->otg.id_nb);
> if (ret) {
> dev_err(dev, "failed to register EXTCON_USB_HOST notifier\n");
> @@ -899,7 +898,7 @@ static int axp288_charger_probe(struct platform_device *pdev)
> NULL, axp288_charger_irq_thread_handler,
> IRQF_ONESHOT, info->pdev->name, info);
> if (ret) {
> - dev_err(&pdev->dev, "failed to request interrupt=%d\n",
> + dev_err(dev, "failed to request interrupt=%d\n",
> info->irq[i]);
> return ret;
> }
>
next prev parent reply other threads:[~2021-08-12 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 10:49 Tang Bin
2021-08-12 15:20 ` Hans de Goede [this message]
2021-08-13 14:32 ` Sebastian Reichel
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=60b7038f-2c68-4559-6a97-a5f2bc97647f@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tangbin@cmss.chinamobile.com \
--cc=wens@csie.org \
--cc=zhangshengju@cmss.chinamobile.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
all inboxes | Powered by JetHome®