From: Andrew Morton <akpm@linux-foundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
lkft-triage@lists.linaro.org,
linux-parisc <linux-parisc@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
Rik van Riel <riel@surriel.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: sh4: parisc: asm/cmpxchg.h:60:24: error: implicit declaration of function 'cmpxchg_emu_u8' [-Werror=implicit-function-declaration]
Date: Wed, 3 Apr 2024 13:52:05 -0700 [thread overview]
Message-ID: <20240403135205.7673001add2216e63db02d1e@linux-foundation.org> (raw)
In-Reply-To: <CA+G9fYvUwyf-5yB=xZVAPXrF3C9z==7bbhDYBnX9jdJ1PxzPnQ@mail.gmail.com>
On Wed, 3 Apr 2024 13:23:23 +0530 Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> The parisc and sh defconfig builds failed due to following build warnings
> and errors on Linux next-20240402.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> parisc:
> build:
> * gcc-11-tinyconfig - Failed
> * gcc-11-allnoconfig - Failed
> * gcc-11-defconfig - Failed
>
> sh:
> build:
> * gcc-11-defconfig - Failed
> * gcc-11-dreamcast_defconfig - Failed
> * gcc-11-tinyconfig - Failed
> * gcc-11-shx3_defconfig - Failed
> * gcc-11-allnoconfig - Failed
Is this a new failure? If so, can we please identify a suitable Fixes: target?
next prev parent reply other threads:[~2024-04-03 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 7:53 Naresh Kamboju
2024-04-03 20:52 ` Andrew Morton [this message]
2024-04-03 21:02 ` Paul E. McKenney
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=20240403135205.7673001add2216e63db02d1e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mgorman@techsingularity.net \
--cc=naresh.kamboju@linaro.org \
--cc=paulmck@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=riel@surriel.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®