On Sun, Jun 07, 2020 at 08:26:32PM -0700, Nathan Chancellor wrote:
> On Mon, Jun 08, 2020 at 09:56:16AM +0800, Kefeng Wang wrote:
> >
> > On 2020/6/8 3:00, Paul E. McKenney wrote:
> > > On Fri, Jun 05, 2020 at 05:19:14PM -0700, Paul E. McKenney wrote:
> > > > On Sat, Jun 06, 2020 at 07:07:10AM +0800, kernel test robot wrote:
> > > > > tree:
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> > > > > dev.2020.06.02a
> > > > > head: 5216948905dd07a84cef8a7dc72c2ec076802efd
> > > > > commit: 7d16add62717136b1839f0b3d7ea4cbb98f38c2a [67/90] rcuperf: Fix
> > > > > kfree_mult to match printk() format
> > > > > config: arm-randconfig-r004-20200605 (attached as .config)
> > > > > compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project
> > > > > 6dd738e2f0609f7d3313b574a1d471263d2d3ba1)
> > > > > 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
> > > > > # install arm cross compiling tool for clang build
> > > > > # apt-get install binutils-arm-linux-gnueabi
> > > > > git checkout 7d16add62717136b1839f0b3d7ea4cbb98f38c2a
> > > > > # save the attached .config to linux build tree
> > > > > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross
> > > > > ARCH=arm
> > > > >
> > > > > If you fix the issue, kindly add following tag as appropriate
> > > > > Reported-by: kernel test robot <l...@intel.com>
> > > > Adding Kefeng on CC. Kefeng, thoughts?
> > > Like this, perhaps?
> >
> > Hi Paul，I check https://lkml.org/lkml/2020/6/2/286 and
> > <https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/log/?h=dev.2020.06.02a>
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/log/?h=dev.2020.06.02a
> >
> > There are two different ways to fix the same issue
> >
> > patch 1: rcuperf: Fix printk format warning urgent-for-mingo
> >
> > patch 2: 'rcuperf: Fix kfree_mult to match printk() format' from Ingo
> > after my patch
> >
> > since patch1 already merged, patch2 is not needed, so skip patch2?
Good point, done, and thank you both!
Thanx, Paul
