All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Tejun Heo <tj@kernel.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the cgroup tree
Date: Tue, 11 Jul 2023 10:06:52 +0800	[thread overview]
Message-ID: <9031f42f-6ff3-3e60-049b-fc1917915da9@huawei.com> (raw)
In-Reply-To: <ZKyuwkDWB85Zs9R0@slm.duckdns.org>

On 2023/7/11 9:22, Tejun Heo wrote:
> On Tue, Jul 11, 2023 at 11:15:09AM +1000, Stephen Rothwell wrote:
>> 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()")
> 
> Miaohe, can you send a patch to either add __maybe_unused to
> cgroup_tryget_css() or also put it inside CONFIG_CGROUP_SCHED?

Will do. Sorry for my mistake.

Thanks.


  reply	other threads:[~2023-07-11  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  1:15 linux-next: build warning after merge of the cgroup tree Stephen Rothwell
2023-07-11  1:22 ` Tejun Heo
2023-07-11  2:06   ` Miaohe Lin [this message]
  -- 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=9031f42f-6ff3-3e60-049b-fc1917915da9@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.