From: Sasha Levin <sashal@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>, Imran Khan <imran.f.khan@oracle.com>,
Xuewen Yan <xuewen.yan@unisoc.com>
Subject: Re: stable-rc: 5.4: cgroup.c:2404:2: error: implicit declaration of function 'cpus_read_lock' [-Werror,-Wimplicit-function-declaration]
Date: Tue, 13 Sep 2022 12:16:05 -0400 [thread overview]
Message-ID: <YyCsxQsGYdDAlFiy@sashalap> (raw)
In-Reply-To: <CA+G9fYvnc4q4kFGWEYHounj1a7PdQ8f4AefgjUFqNVn9d6h8kA@mail.gmail.com>
On Tue, Sep 13, 2022 at 07:52:38PM +0530, Naresh Kamboju wrote:
>On Tue, 13 Sept 2022 at 19:29, Sasha Levin <sashal@kernel.org> wrote:
>>
>> On Tue, Sep 13, 2022 at 04:48:44PM +0530, Naresh Kamboju wrote:
>> >On stable-rc 5.4 arm and arm64 builds failed due to following errors / warnings.
>> >
>> >kernel/cgroup/cgroup.c:2404:2: error: implicit declaration of function
>> >'cpus_read_lock' [-Werror,-Wimplicit-function-declaration]
>> > cpus_read_lock();
>> > ^
>> >kernel/cgroup/cgroup.c:2404:2: note: did you mean 'cpuset_read_lock'?
>> >include/linux/cpuset.h:58:13: note: 'cpuset_read_lock' declared here
>> >extern void cpuset_read_lock(void);
>> > ^
>> >kernel/cgroup/cgroup.c:2417:2: error: implicit declaration of function
>> >'cpus_read_unlock' [-Werror,-Wimplicit-function-declaration]
>> > cpus_read_unlock();
>> > ^
>> >kernel/cgroup/cgroup.c:2417:2: note: did you mean 'cpuset_read_unlock'?
>> >include/linux/cpuset.h:59:13: note: 'cpuset_read_unlock' declared here
>> >extern void cpuset_read_unlock(void);
>> > ^
>> >2 errors generated.
>> >
>> >drivers/gpu/drm/drm_lock.c:363:6: warning: misleading indentation;
>> >statement is not part of the previous 'if' [-Wmisleading-indentation]
>> > */ mutex_lock(&dev->struct_mutex);
>> > ^
>> >drivers/gpu/drm/drm_lock.c:357:2: note: previous statement is here
>> > if (!drm_core_check_feature(dev, DRIVER_LEGACY))
>> > ^
>> >1 warning generated.
>> >
>> >Build link:
>> > - https://builds.tuxbuild.com/2EfrNYbejRQczhhqndawRkHARHZ/
>> >
>> >
>> >Steps to reproduce:
>> >-------------------
>> ># To install tuxmake on your system globally:
>> ># sudo pip3 install -U tuxmake
>> >#
>> >
>> >tuxmake --runtime podman --target-arch arm64 --toolchain clang-nightly
>> >--kconfig defconfig LLVM=1 LLVM_IAS=1
>>
>> Hm, I can't reproduce this one, (and can't install tuxmake on the work
>> machine). What's the actual config that you end up using here?
>
>The "defconfig" for arm64 with clang nightly.
Greg actually ended up fixing it up and I haven't noticed, thanks both
:)
--
Thanks,
Sasha
prev parent reply other threads:[~2022-09-13 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 11:18 stable-rc: 5.4: cgroup.c:2404:2: error: implicit declaration of function 'cpus_read_lock' [-Werror,-Wimplicit-function-declaration] Naresh Kamboju
2022-09-13 13:58 ` Greg Kroah-Hartman
2022-09-13 13:59 ` Sasha Levin
2022-09-13 14:22 ` Naresh Kamboju
2022-09-13 16:16 ` Sasha Levin [this message]
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=YyCsxQsGYdDAlFiy@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imran.f.khan@oracle.com \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=xuewen.yan@unisoc.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