From: Andreas Larsson <andreas@gaisler.com>
To: kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: sparclinux@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:pending-fixes] BUILD REGRESSION 37b3c1c31342cdb8ee57f80a3a78cfe651a3f2ae
Date: Tue, 4 Oct 2022 15:57:36 +0200 [thread overview]
Message-ID: <c96920b5-2d49-1946-4a4e-6a67fd8e5772@gaisler.com> (raw)
In-Reply-To: <633c0193.srGRSlP3TyZ9yamz%lkp@intel.com>
On 2022-10-04 11:49, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
> branch HEAD: 37b3c1c31342cdb8ee57f80a3a78cfe651a3f2ae Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git
>
> Error/Warning reports:
>
> https://lore.kernel.org/linux-mm/202210041036.f84z3tBl-lkp@intel.com
>
> Error/Warning: (recently discovered and may have been fixed)
>
> arch/sparc/mm/srmmu.c:1662:25: error: too few arguments to function 'xc1'
> arch/sparc/mm/srmmu.c:1662:30: error: 'smpfunc_t' undeclared (first use in this function); did you mean 'cmp_func_t'?
> arch/sparc/mm/srmmu.c:1662:40: error: expected ')' before 'local_ops'
> arch/sparc/mm/srmmu.c:1694:25: error: too few arguments to function 'xc3'
> arch/sparc/mm/srmmu.c:1726:25: error: too few arguments to function 'xc2'
>
Commit 2d2b17d08bfc ("sparc: Unbreak the build") in
linux-next/pending-fixes is missing a number of changes to
arch/sparc/mm/srmmu.c that was done in commit 17006e86a764 ("sparc:
Unbreak the build") in the master branch.
--
Andreas Larsson
prev parent reply other threads:[~2022-10-04 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 9:49 kernel test robot
2022-10-04 13:57 ` Andreas Larsson [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=c96920b5-2d49-1946-4a4e-6a67fd8e5772@gaisler.com \
--to=andreas@gaisler.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=sparclinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox