Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5;
Sender: Tejun Heo <htejun@gmail.com>
Date:   Tue, 21 Nov 2023 06:20:08 -1000
From:   Tejun Heo <tj@kernel.org>
To:     Waiman Long <longman@redhat.com>
Cc:     Lai Jiangshan <jiangshanlai@gmail.com>, cgroups@vger.kernel.org,
        linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH-cgroup] workqueue: Move workqueue_set_unbound_cpumask()
 and its helpers inside CONFIG_SYSFS
Message-ID: <ZVzYuHLvWfgIn5qP@slm.duckdns.org>
References: <20231121021840.10937-1-longman@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20231121021840.10937-1-longman@redhat.com>
Precedence: bulk

On Mon, Nov 20, 2023 at 09:18:40PM -0500, Waiman Long wrote:
> Commit fe28f631fa94 ("workqueue: Add workqueue_unbound_exclude_cpumask()
> to exclude CPUs from wq_unbound_cpumask") makes
> workqueue_set_unbound_cpumask() static as it is not used elsewhere in
> the kernel. However, this triggers a kernel test robot warning about
> 'workqueue_set_unbound_cpumask' defined but not used when CONFIG_SYS
> isn't defined. It happens that workqueue_set_unbound_cpumask() is only
> called when CONFIG_SYS is defined.
> 
> Move workqueue_set_unbound_cpumask() and its helpers inside the
> CONFIG_SYSFS compilation block to avoid the warning. There is no
> functional change.
> 
> Fixes: fe28f631fa94 ("workqueue: Add workqueue_unbound_exclude_cpumask() to exclude CPUs from wq_unbound_cpumask")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202311130831.uh0AoCd1-lkp@intel.com/
> Signed-off-by: Waiman Long <longman@redhat.com>

Applied to cgroup/for-6.8.

Thanks.

-- 
tejun