From: Xianwei Zhao <xianwei.zhao@amlogic.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, linux-gpio@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] pinctrl: amlogic-a4: Drop surplus semicolon
Date: Tue, 25 Mar 2025 13:59:00 +0800 [thread overview]
Message-ID: <965df044-50f6-46a2-9471-0ab355378e16@amlogic.com> (raw)
In-Reply-To: <20250322-fix-amlogic-a4-v1-1-bd5ccf9ca1bb@linaro.org>
Reviewed-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
On 2025/3/23 04:41, Linus Walleij wrote:
> [ EXTERNAL EMAIL ]
>
> The kernel bots complain about untidy code found using
> coccinelle, fix it up.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202503212354.Hx2qaDRe-lkp@intel.com/
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> drivers/pinctrl/meson/pinctrl-amlogic-a4.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/meson/pinctrl-amlogic-a4.c b/drivers/pinctrl/meson/pinctrl-amlogic-a4.c
> index 35d5540b8eaa2378197d7791ef2470ca6591f693..ee7bbc72f9b36c0c6d5bec76780711f9db3c155d 100644
> --- a/drivers/pinctrl/meson/pinctrl-amlogic-a4.c
> +++ b/drivers/pinctrl/meson/pinctrl-amlogic-a4.c
> @@ -856,7 +856,7 @@ static void init_bank_register_bit(struct aml_pinctrl *info,
> break;
> }
> }
> - };
> + }
>
> if (def_offs) {
> for (i = 0; i < AML_NUM_REG; i++) {
>
> ---
> base-commit: 693c9ecd832669c55e8d8067eba064440d9a4709
> change-id: 20250322-fix-amlogic-a4-55a05e1402d5
>
> Best regards,
> --
> Linus Walleij <linus.walleij@linaro.org>
>
prev parent reply other threads:[~2025-03-25 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 20:41 [PATCH] pinctrl: amlogic-a4: Drop surplus semicolon Linus Walleij
2025-03-25 5:59 ` Xianwei Zhao [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=965df044-50f6-46a2-9471-0ab355378e16@amlogic.com \
--to=xianwei.zhao@amlogic.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.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;
as well as URLs for NNTP newsgroup(s).