From: Krzysztof Kozlowski <krzk@kernel.org>
To: Charles Han <hanchunchao@inspur.com>,
sre@kernel.org, akpm@linux-foundation.org, lee@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] charger: max14577: Handle NULL pdata when CONFIG_OF is not set
Date: Mon, 19 May 2025 18:20:11 +0200 [thread overview]
Message-ID: <aa9eeea9-c97e-4938-b736-e730ca056a2e@kernel.org> (raw)
In-Reply-To: <20250519061601.8755-1-hanchunchao@inspur.com>
On 19/05/2025 08:16, Charles Han wrote:
> When the kernel is not configured CONFIG_OF, the max14577_charger_dt_init
> function returns NULL. Fix the max14577_charger_probe functionby returning
Typo, "function by"
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
(there is no subsystem "charger").
> -ENODATA instead of potentially passing a NULL pointer to PTR_ERR.
>
> Fix below smatch warning.
> smatch warnings:
> drivers/power/supply/max14577_charger.c:576 max14577_charger_probe() warn: passing zero to 'PTR_ERR'
>
Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets.
With that:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-19 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 9:53 [PATCH] charger: max14577: Handle NULL pdata when CONFIG_OF is not set Charles Han
2025-05-16 12:32 ` Krzysztof Kozlowski
2025-05-19 1:48 ` [PATCH V2] " Charles Han
2025-05-19 5:51 ` Krzysztof Kozlowski
2025-05-19 5:58 ` kernel test robot
2025-05-19 6:16 ` [PATCH V3] " Charles Han
2025-05-19 16:20 ` Krzysztof Kozlowski [this message]
2025-06-22 19:13 ` 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=aa9eeea9-c97e-4938-b736-e730ca056a2e@kernel.org \
--to=krzk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hanchunchao@inspur.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.