From: Kent Overstreet <kent.overstreet@linux.dev>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
Suren Baghdasaryan <surenb@google.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: include/asm-generic/percpu.h:31:40: error: implicit declaration of function 'raw_smp_processor_id'
Date: Sat, 25 May 2024 04:32:03 -0400 [thread overview]
Message-ID: <2b5jetp5exc7jwjqhdvwnrttp3b7gge4pqq6jjvjc7aj6zzqtk@5aghxx2x4u6q> (raw)
In-Reply-To: <ZlGcfHD3ZCNKWDdr@rli9-mobl>
On Sat, May 25, 2024 at 04:08:28PM +0800, Philip Li wrote:
> On Fri, May 24, 2024 at 11:58:30AM -0400, Kent Overstreet wrote:
> > On Tue, May 21, 2024 at 12:31:18AM +0800, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > > head: eb6a9339efeb6f3d2b5c86fdf2382cdc293eca2c
> > > commit: 24e44cc22aa3112082f2ee23137d048c73ca96d5 mm: percpu: enable per-cpu allocation tagging
> > > date: 4 weeks ago
> > > config: mips-randconfig-r133-20240520 (https://download.01.org/0day-ci/archive/20240521/202405210052.DIrMXJNz-lkp@intel.com/config)
> > > compiler: mips-linux-gcc (GCC) 13.2.0
> > > reproduce: (https://download.01.org/0day-ci/archive/20240521/202405210052.DIrMXJNz-lkp@intel.com/reproduce)
> > >
> > > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > > the same patch/commit), kindly add following tags
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202405210052.DIrMXJNz-lkp@intel.com/
> >
> > I have a fix I'm testing for this but it's going to need a lot of
> > randconfig build testing on all archs.
> >
> > Philip, could 0day help out with that? I don't know how you schedule
>
> Got it, we will cover this branch with randconfig build tests.
>
> > which branches for which testing, and previously the memory allocation
> > profiling didn't get enough build testing before Andrew merged it.
>
> Sorry about this, we really need extend the test number to generate
> more randconfigs.
It was getting caught by 0day in Andrew's tree, I think it may have just
been a timing thing. This is (one of the reasons) why I'm hoping to get
you a dashboard (and maybe get some test infrastructure consolidation
going, too) - right now I just have no way of knowing how long the
randconfig tests take or when they're finished.
prev parent reply other threads:[~2024-05-25 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 16:31 kernel test robot
2024-05-24 15:58 ` Kent Overstreet
2024-05-25 8:08 ` Philip Li
2024-05-25 8:32 ` Kent Overstreet [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=2b5jetp5exc7jwjqhdvwnrttp3b7gge4pqq6jjvjc7aj6zzqtk@5aghxx2x4u6q \
--to=kent.overstreet@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=philip.li@intel.com \
--cc=surenb@google.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