From: Bart Van Assche <bvanassche@acm.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:pending-fixes 787/854] arch/sparc/mm/srmmu.c:1662:30: error: 'smpfunc_t' undeclared; did you mean 'cmp_func_t'?
Date: Tue, 4 Oct 2022 06:56:38 -0700 [thread overview]
Message-ID: <13613249-90bb-99d1-8b9a-eb09ed3c200b@acm.org> (raw)
In-Reply-To: <202210041036.f84z3tBl-lkp@intel.com>
On 10/3/22 20:02, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
> head: 37b3c1c31342cdb8ee57f80a3a78cfe651a3f2ae
> commit: 2d2b17d08bfc3d98cf93622e8c6543eaaf02dabe [787/854] sparc: Unbreak the build
> config: sparc-randconfig-r005-20221002
> compiler: sparc-linux-gcc (GCC) 12.1.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2d2b17d08bfc3d98cf93622e8c6543eaaf02dabe
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next pending-fixes
> git checkout 2d2b17d08bfc3d98cf93622e8c6543eaaf02dabe
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sparc SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> arch/sparc/mm/srmmu.c: In function 'poke_hypersparc':
> arch/sparc/mm/srmmu.c:1081:32: error: variable 'clear' set but not used [-Werror=unused-but-set-variable]
> 1081 | volatile unsigned long clear;
> | ^~~~~
It seems like the pending-fixes branch is missing the following commit
from the master branch: 17006e86a764 ("sparc: Unbreak the build").
Thanks,
Bart.
next prev parent reply other threads:[~2022-10-04 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 3:02 kernel test robot
2022-10-04 13:56 ` Bart Van Assche [this message]
2022-10-04 21:39 ` Stephen Rothwell
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=13613249-90bb-99d1-8b9a-eb09ed3c200b@acm.org \
--to=bvanassche@acm.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=sfr@canb.auug.org.au \
/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