From: Stephen Boyd <sboyd@kernel.org>
To: lee.jones@linaro.org
Cc: linux-kernel@vger.kernel.org, Tero Kristo <kristo@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-omap@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 16/20] clk: ti: gate: Fix possible doc-rot in 'omap36xx_gate_clk_enable_with_hsdiv_restore'
Date: Thu, 11 Feb 2021 11:53:03 -0800 [thread overview]
Message-ID: <161307318365.1254594.12506451130252161384@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210120093040.1719407-17-lee.jones@linaro.org>
Quoting Lee Jones (2021-01-20 01:30:36)
> Fixes the following W=1 kernel build warning(s):
>
> drivers/clk/ti/gate.c:67: warning: Function parameter or member 'hw' not described in 'omap36xx_gate_clk_enable_with_hsdiv_restore'
> drivers/clk/ti/gate.c:67: warning: Excess function parameter 'clk' description in 'omap36xx_gate_clk_enable_with_hsdiv_restore'
>
> Cc: Tero Kristo <kristo@kernel.org>
> Cc: Michael Turquette <mturquette@baylibre.com>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Cc: linux-omap@vger.kernel.org
> Cc: linux-clk@vger.kernel.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> ---
Applied to clk-next
next prev parent reply other threads:[~2021-02-11 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 9:30 [PATCH 00/20] Rid W=1 warnings from Clock Lee Jones
2021-01-20 9:30 ` [PATCH 13/20] clk: ti: clockdomain: Fix description for 'omap2_init_clk_clkdm's hw param Lee Jones
2021-01-20 11:27 ` Tero Kristo
2021-02-11 19:52 ` Stephen Boyd
2021-01-20 9:30 ` [PATCH 15/20] clk: ti: dpll: Fix misnaming of '_register_dpll()'s 'user' parameter Lee Jones
2021-01-20 11:27 ` Tero Kristo
2021-02-11 19:52 ` Stephen Boyd
2021-01-20 9:30 ` [PATCH 16/20] clk: ti: gate: Fix possible doc-rot in 'omap36xx_gate_clk_enable_with_hsdiv_restore' Lee Jones
2021-01-20 11:28 ` Tero Kristo
2021-02-11 19:53 ` Stephen Boyd [this message]
2021-01-25 23:56 ` (subset) [PATCH 00/20] Rid W=1 warnings from Clock Heiko Stuebner
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=161307318365.1254594.12506451130252161384@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=kristo@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.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).