All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
	lkft-triage@lists.linaro.org, petr@tesarici.cz,
	Sasha Levin <sashal@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>,
	Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: stable-rc: 5.10: arm: u64_stats_sync.h:136:2: error: implicit declaration of function 'preempt_disable_nested'
Date: Tue, 23 Apr 2024 09:22:32 -0700	[thread overview]
Message-ID: <2024042307-detract-flammable-d542@gregkh> (raw)
In-Reply-To: <CA+G9fYsyacpJG1NwpbyJ_68B=cz5DvpRpGCD_jw598H3FXgUdQ@mail.gmail.com>

On Tue, Apr 23, 2024 at 01:35:28PM +0530, Naresh Kamboju wrote:
> The arm and i386 builds failed with clang-17 and gcc-12 on stable-rc
> linux.5.10.y
> branch with linked config [1].
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> In file included from init/do_mounts.c:7:
> In file included from include/linux/suspend.h:5:
> In file included from include/linux/swap.h:9:
> In file included from include/linux/memcontrol.h:13:
> In file included from include/linux/cgroup.h:28:
> In file included from include/linux/cgroup-defs.h:20:
> include/linux/u64_stats_sync.h:136:2: error: implicit declaration of
> function 'preempt_disable_nested'
> [-Werror,-Wimplicit-function-declaration]
>   136 |         preempt_disable_nested();
>       |         ^

That function is not in the queue at all, are you sure you are up to
date?

thanks,

greg k-h

  reply	other threads:[~2024-04-23 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  8:05 stable-rc: 5.10: arm: u64_stats_sync.h:136:2: error: implicit declaration of function 'preempt_disable_nested' Naresh Kamboju
2024-04-23 16:22 ` Greg Kroah-Hartman [this message]
2024-04-23 16:53   ` Shreeya Patel
2024-04-23 16:59     ` Greg Kroah-Hartman
2024-04-24 14:41       ` Dan Carpenter

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=2024042307-detract-flammable-d542@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=petr@tesarici.cz \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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.