linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: Miaohe Lin <linmiaohe@huawei.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the cgroup tree
Date: Tue, 11 Jul 2023 11:15:09 +1000	[thread overview]
Message-ID: <20230711111509.1045f32e@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 497 bytes --]

Hi all,

After merging the cgroup tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

kernel/cgroup/cgroup.c:503:36: warning: 'cgroup_tryget_css' defined but not used [-Wunused-function]
  503 | static struct cgroup_subsys_state *cgroup_tryget_css(struct cgroup *cgrp,
      |                                    ^~~~~~~~~~~~~~~~~

Introduced by commit

  1299eb2b0ad5 ("cgroup: minor cleanup for cgroup_extra_stat_show()")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-07-11  1:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  1:15 Stephen Rothwell [this message]
2023-07-11  1:22 ` linux-next: build warning after merge of the cgroup tree Tejun Heo
2023-07-11  2:06   ` Miaohe Lin
  -- strict thread matches above, loose matches on Subject: below --
2017-12-13  3:56 Stephen Rothwell
2017-12-15  9:58 ` Arnd Bergmann
2017-12-15 13:10   ` Tejun Heo
2017-05-01  4:53 Stephen Rothwell
2013-08-27 10:17 Stephen Rothwell
2013-08-27 18:33 ` Tejun Heo

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=20230711111509.1045f32e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tj@kernel.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).