From: Linus Walleij <linus.walleij@linaro.org>
To: kernel test robot <lkp@intel.com>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
kbuild-all@lists.01.org, linux-gpio@vger.kernel.org,
Chen-Yu Tsai <wenst@chromium.org>,
Sean Wang <sean.wang@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: mediatek: common-v1: fix semicolon.cocci warnings
Date: Sun, 27 Mar 2022 14:01:07 +0200 [thread overview]
Message-ID: <CACRpkdbiUDREqOe6C_AAnG7vpeMCgMvaOKknEXT2B0yUWKbyzQ@mail.gmail.com> (raw)
In-Reply-To: <20220322130308.GA21877@65fc916127a5>
On Tue, Mar 22, 2022 at 2:03 PM kernel test robot <lkp@intel.com> wrote:
> From: kernel test robot <lkp@intel.com>
>
> drivers/pinctrl/mediatek/pinctrl-mtk-common.c:171:2-3: Unneeded semicolon
>
>
> Remove unneeded semicolon.
>
> Generated by: scripts/coccinelle/misc/semicolon.cocci
>
> Fixes: 156f721704b5 ("pinctrl: mediatek: common-v1: Commonize spec_ies_smt_set callback")
> CC: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: kernel test robot <lkp@intel.com>
Patch applied.
Yours,
Linus Walleij
prev parent reply other threads:[~2022-03-27 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:13 [linusw-pinctrl:for-next 76/78] drivers/pinctrl/mediatek/pinctrl-mtk-common.c:171:2-3: Unneeded semicolon kernel test robot
2022-03-22 13:03 ` [PATCH] pinctrl: mediatek: common-v1: fix semicolon.cocci warnings kernel test robot
2022-03-27 12:01 ` Linus Walleij [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=CACRpkdbiUDREqOe6C_AAnG7vpeMCgMvaOKknEXT2B0yUWKbyzQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lkp@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@kernel.org \
--cc=wenst@chromium.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).