mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Mike Snitzer <snitzer@redhat.com>, kernel test robot <lkp@intel.com>
Cc: Mike Snitzer <snitzer@kernel.org>,
	kbuild-all@lists.01.org, dm-devel@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: [device-mapper-dm:dm-5.19 132/132] drivers/md/dm.c:1542:18: error: 'result' undeclared
Date: Thu, 24 Mar 2022 08:31:12 +0800	[thread overview]
Message-ID: <2c10ed96-4558-3438-e889-f5b9ff4cea84@intel.com> (raw)
In-Reply-To: <YjuoF88MzBALI+l8@redhat.com>



On 3/24/2022 7:07 AM, Mike Snitzer wrote:
> On Wed, Mar 23 2022 at  6:57P -0400,
> kernel test robot <lkp@intel.com> wrote:
> 
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git dm-5.19
>> head:   7f8ac95a6464b895e3d2b6175f7ee64a4c10fcfe
>> commit: 7f8ac95a6464b895e3d2b6175f7ee64a4c10fcfe [132/132] dm: push error handling down to __split_and_process_bio
>> config: s390-buildonly-randconfig-r005-20220323 (https://download.01.org/0day-ci/archive/20220324/202203240638.crXQjFY5-lkp@intel.com/config)
>> compiler: s390-linux-gcc (GCC) 11.2.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/device-mapper/linux-dm.git/commit/?id=7f8ac95a6464b895e3d2b6175f7ee64a4c10fcfe
>>          git remote add device-mapper-dm https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
>>          git fetch --no-tags device-mapper-dm dm-5.19
>>          git checkout 7f8ac95a6464b895e3d2b6175f7ee64a4c10fcfe
>>          # save the config file to linux build tree
>>          mkdir build_dir
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=s390 SHELL=/bin/bash drivers/md/
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>     drivers/md/dm.c: In function '__process_abnormal_io':
>>>> drivers/md/dm.c:1542:18: error: 'result' undeclared (first use in this function)
>>      1542 |                 *result = BLK_STS_NOTSUPP;
>>           |                  ^~~~~~
>>     drivers/md/dm.c:1542:18: note: each undeclared identifier is reported only once for each function it appears in
>>
> 
> Yeah, I pushed this too soon, fixed now.
> 
> But why are you even testing this branch? I didn't include dm-5.19 in
> linux-next yet.

Hi Mike,

The bot picks up all branches to test, do you want it to only test few 
branches?


> 
> Given that it seems strange for the bot to just pick up some branch,
> and then spam LKML, dm-devel, etc like it found a meaningful problem.

we also support sending reports privately, do you want this way?

Best Regards,
Rong Chen

> 
> Mike
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
> 

      reply	other threads:[~2022-03-24  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 22:57 kernel test robot
2022-03-23 23:07 ` Mike Snitzer
2022-03-24  0:31   ` Chen, Rong A [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=2c10ed96-4558-3438-e889-f5b9ff4cea84@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=dm-devel@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=snitzer@kernel.org \
    --cc=snitzer@redhat.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

all inboxes | Powered by JetHome®