From: kbuild test robot <lkp@intel.com>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
urezki@gmail.com
Subject: Re: [PATCH 2/2] rcuperf: Measure memory footprint during kfree_rcu() test (v4)
Date: Mon, 27 Jan 2020 16:51:10 +0800 [thread overview]
Message-ID: <202001271653.IxODFuYS%lkp@intel.com> (raw)
In-Reply-To: <20200115224225.246061-2-joel@joelfernandes.org>
Hi "Joel,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20200116]
[cannot apply to rcu/dev linux/master linus/master v5.5-rc6 v5.5-rc5 v5.5-rc4 v5.5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Joel-Fernandes-Google/rcuperf-Add-support-to-vary-the-slab-object-sizes/20200117-101205
base: 2747d5fdab78f43210256cd52fb2718e0b3cce74
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-153-g47b6dfef-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kernel/rcu/rcuperf.c:620:11: sparse: sparse: symbol 'mem_begin' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/2] rcuperf: Measure memory footprint during kfree_rcu() test (v4)
Date: Mon, 27 Jan 2020 16:51:10 +0800 [thread overview]
Message-ID: <202001271653.IxODFuYS%lkp@intel.com> (raw)
In-Reply-To: <20200115224225.246061-2-joel@joelfernandes.org>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Hi "Joel,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20200116]
[cannot apply to rcu/dev linux/master linus/master v5.5-rc6 v5.5-rc5 v5.5-rc4 v5.5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Joel-Fernandes-Google/rcuperf-Add-support-to-vary-the-slab-object-sizes/20200117-101205
base: 2747d5fdab78f43210256cd52fb2718e0b3cce74
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-153-g47b6dfef-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kernel/rcu/rcuperf.c:620:11: sparse: sparse: symbol 'mem_begin' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
next prev parent reply other threads:[~2020-01-27 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 22:42 [PATCH 1/2] rcuperf: Add support to vary the slab object sizes Joel Fernandes (Google)
2020-01-15 22:42 ` [PATCH 2/2] rcuperf: Measure memory footprint during kfree_rcu() test (v4) Joel Fernandes (Google)
2020-01-18 10:51 ` kbuild test robot
2020-01-18 10:51 ` kbuild test robot
2020-01-18 11:56 ` kbuild test robot
2020-01-18 11:56 ` kbuild test robot
2020-01-27 8:51 ` kbuild test robot [this message]
2020-01-27 8:51 ` kbuild test robot
2020-01-27 8:51 ` [RFC PATCH] rcuperf: mem_begin can be static kbuild test robot
2020-01-27 8:51 ` kbuild test robot
2020-01-18 12:00 ` [PATCH 1/2] rcuperf: Add support to vary the slab object sizes Uladzislau Rezki
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 22:40 Joel Fernandes (Google)
2020-01-15 22:40 ` [PATCH 2/2] rcuperf: Measure memory footprint during kfree_rcu() test (v4) Joel Fernandes (Google)
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=202001271653.IxODFuYS%lkp@intel.com \
--to=lkp@intel.com \
--cc=dave@stgolabs.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.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 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.