From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>,
Abel Vesa <abel.vesa@nxp.com>, Anson Huang <Anson.Huang@nxp.com>,
linux-clk <linux-clk@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 7/8] clk: renesas: renesas-cpg-mssr: fix kerneldoc of cpg_mssr_priv
Date: Wed, 4 Nov 2020 11:52:23 +0100 [thread overview]
Message-ID: <CAMuHMdVx_oYFpe8G7iKcQ0FFwpPTTiWZLps3WsLSphqJ0pweyQ@mail.gmail.com> (raw)
In-Reply-To: <20201103162435.13689-7-krzk@kernel.org>
On Tue, Nov 3, 2020 at 5:25 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> The struct cpg_mssr_priv missed proper formatting:
>
> drivers/clk/renesas/renesas-cpg-mssr.c:142: warning:
> cannot understand function prototype: 'struct cpg_mssr_priv '
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-clk-for-v5.11.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-11-04 10:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 16:24 [PATCH 1/8] clk: pwm: drop of_match_ptr from of_device_id table Krzysztof Kozlowski
2020-11-03 16:24 ` [PATCH 2/8] clk: imx8mm: " Krzysztof Kozlowski
2020-11-05 1:11 ` Stephen Boyd
2020-11-10 1:54 ` Shawn Guo
2020-11-03 16:24 ` [PATCH 3/8] clk: imx8mn: " Krzysztof Kozlowski
2020-11-05 1:11 ` Stephen Boyd
2020-11-10 1:54 ` Shawn Guo
2020-11-03 16:24 ` [PATCH 4/8] clk: imx8mp: " Krzysztof Kozlowski
2020-11-05 1:11 ` Stephen Boyd
2020-11-10 1:54 ` Shawn Guo
2020-11-03 16:24 ` [PATCH 5/8] clk: imx8mq: " Krzysztof Kozlowski
2020-11-05 1:11 ` Stephen Boyd
2020-11-10 1:54 ` Shawn Guo
2020-11-03 16:24 ` [PATCH 6/8] clk: renesas: r8a779a0-cpg-mssr: add static to local function Krzysztof Kozlowski
2020-11-04 10:53 ` Geert Uytterhoeven
2020-11-03 16:24 ` [PATCH 7/8] clk: renesas: renesas-cpg-mssr: fix kerneldoc of cpg_mssr_priv Krzysztof Kozlowski
2020-11-04 10:52 ` Geert Uytterhoeven [this message]
2020-11-03 16:24 ` [PATCH 8/8] clk: scpi: mark scpi_clk_match as maybe unused Krzysztof Kozlowski
2020-11-04 9:00 ` Sudeep Holla
2020-12-10 20:24 ` Stephen Boyd
2020-12-10 20:24 ` [PATCH 1/8] clk: pwm: drop of_match_ptr from of_device_id table Stephen Boyd
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=CAMuHMdVx_oYFpe8G7iKcQ0FFwpPTTiWZLps3WsLSphqJ0pweyQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Anson.Huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).