From: Alain Volmat <avolmat@me.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Patrice Chotard <patrice.chotard@foss.st.com>,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: st: fix comments compilation warnings
Date: Mon, 20 Dec 2021 07:29:55 +0100 [thread overview]
Message-ID: <20211220062955.GA198368@gnbcxl0045.gnb.st.com> (raw)
In-Reply-To: <CACRpkdaAefLm_SxtbryDdGopr8WfVZkJmg4y8-w-WJuJqE-u1w@mail.gmail.com>
Hi Linus,
apologies. Indeed those two warnings are already fixed in your
devel branch. This patch is thus no more necessary.
Regards,
Alain
On Mon, Dec 20, 2021 at 03:17:46AM +0100, Linus Walleij wrote:
> On Sat, Dec 18, 2021 at 10:25 PM Alain Volmat <avolmat@me.com> wrote:
>
> > This commit fixes 2 compilation warnings due to comment starting with
> > /** while not being kernel-doc comments.
> >
> > drivers/pinctrl/pinctrl-st.c:59: warning: This comment starts with '/**',
> > but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> > * Packed style retime configuration.
> > drivers/pinctrl/pinctrl-st.c:73: warning: This comment starts with '/**',
> > but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> > * Dedicated style retime Configuration register
> >
> > Signed-off-by: Alain Volmat <avolmat@me.com>
>
> This does not apply on my "devel" branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=devel
>
> Please rebase and resend.
>
> Yours,
> Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-12-20 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 21:25 [PATCH] pinctrl: st: fix comments compilation warnings Alain Volmat
2021-12-20 2:17 ` Linus Walleij
2021-12-20 6:29 ` Alain Volmat [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=20211220062955.GA198368@gnbcxl0045.gnb.st.com \
--to=avolmat@me.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@foss.st.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