Linux clock framework development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Wiebe, Wladislav (Nokia - DE/Ulm)" <wladislav.wiebe@nokia.com>
Cc: "mturquette@baylibre.com" <mturquette@baylibre.com>,
	"sboyd@kernel.org" <sboyd@kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] clk: move orphan_list back to DEBUG_FS section
Date: Wed, 18 Nov 2020 11:46:43 +0100	[thread overview]
Message-ID: <X7T7kxuY1fuAtlqX@kroah.com> (raw)
In-Reply-To: <AM7PR07MB67076EAED784F061D17AC015FAE10@AM7PR07MB6707.eurprd07.prod.outlook.com>

On Wed, Nov 18, 2020 at 10:23:02AM +0000, Wiebe, Wladislav (Nokia - DE/Ulm) wrote:
> commit 903c6bd937ca ("clk: Evict unregistered clks from parent caches")
> in v4.19.142 moves orphan_list to global section which is not used when
> CONFIG_DEBUG_FS is disabled.
> 
> Fixes:
> drivers/clk/clk.c:49:27: error: 'orphan_list' defined but not used
> [-Werror=unused-variable]
>  static struct hlist_head *orphan_list[] = {
>                            ^~~~~~~~~~~
> 
> Fixes: 903c6bd937ca ("clk: Evict unregistered clks from parent caches")
> 
> Signed-off-by: Wladislav Wiebe <wladislav.wiebe@nokia.com>
> 
> ---
>  drivers/clk/clk.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  reply	other threads:[~2020-11-18 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 10:23 [PATCH] clk: move orphan_list back to DEBUG_FS section Wiebe, Wladislav (Nokia - DE/Ulm)
2020-11-18 10:46 ` Greg KH [this message]
2020-11-18 11:12   ` Wiebe, Wladislav (Nokia - DE/Ulm)

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=X7T7kxuY1fuAtlqX@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wladislav.wiebe@nokia.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