public inbox for [email protected]
 help / color / mirror / Atom feed
From: Joel Fernandes <[email protected]>
To: "Paul E. McKenney" <[email protected]>
Cc: kernel test robot <[email protected]>,
	[email protected], [email protected],
	 "GNU/Weeb Mailing List" <[email protected]>,
	LKML <[email protected]>,
	 "Uladzislau Rezki (Sony)" <[email protected]>,
	Kalesh Singh <[email protected]>
Subject: Re: [ammarfaizi2-block:paulmck/linux-rcu/dev 28/28] kernel/rcu/tree_nocb.h:1213:3: warning: misleading indentation; statement is not part of the previous 'if'
Date: Wed, 20 Apr 2022 12:39:33 -0400	[thread overview]
Message-ID: <CAEXW_YSieVAKUushETvppRAsbKrt0rkFrfYo8qgTK96tXwkqYg@mail.gmail.com> (raw)
In-Reply-To: <20220420134918.GZ4285@paulmck-ThinkPad-P17-Gen-1>

On Wed, Apr 20, 2022 at 9:49 AM Paul E. McKenney <[email protected]> wrote:
>
> On Wed, Apr 20, 2022 at 05:57:46PM +0800, kernel test robot wrote:
> > tree:   https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/dev
> > head:   ad68d8bf085421e4f22731c8b64c0b774a154e06
> > commit: ad68d8bf085421e4f22731c8b64c0b774a154e06 [28/28] rcu/nocb: Add an option to offload all CPUs on boot
> > config: riscv-randconfig-r024-20220420 (https://download.01.org/0day-ci/archive/20220420/[email protected]/config)
> > compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project bac6cd5bf85669e3376610cfc4c4f9ca015e7b9b)
> > 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 riscv cross compiling tool for clang build
> >         # apt-get install binutils-riscv64-linux-gnu
> >         # https://github.com/ammarfaizi2/linux-block/commit/ad68d8bf085421e4f22731c8b64c0b774a154e06
> >         git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
> >         git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/dev
> >         git checkout ad68d8bf085421e4f22731c8b64c0b774a154e06
> >         # save the config file
> >         mkdir build_dir && cp config build_dir/.config
> >         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash kernel/
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <[email protected]>
> >
> > All warnings (new ones prefixed by >>):
>
> I am dropping this commit, and thank you for your testing efforts!

I discussed privately with Paul and things are a bit late for -next as
other testing efforts are underway. So we'll revisit this patch in the
future. Just wanted to clarify to the onlooker that Paul isn't
dropping it because of a NAK or anything ;-)

 Thanks,

 - Joel

      reply	other threads:[~2022-04-20 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  9:57 [ammarfaizi2-block:paulmck/linux-rcu/dev 28/28] kernel/rcu/tree_nocb.h:1213:3: warning: misleading indentation; statement is not part of the previous 'if' kernel test robot
2022-04-20 13:49 ` Paul E. McKenney
2022-04-20 16:39   ` Joel Fernandes [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=CAEXW_YSieVAKUushETvppRAsbKrt0rkFrfYo8qgTK96tXwkqYg@mail.gmail.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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