From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 14849/15097] drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:201:3: error: expected expression
Date: Thu, 11 Aug 2022 04:22:00 -0400 [thread overview]
Message-ID: <20220811042124-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220811081217.ugn7vslc2nlqv6l3@sgarzare-redhat>
On Thu, Aug 11, 2022 at 10:12:17AM +0200, Stefano Garzarella wrote:
> Hi Michael,
>
> On Thu, Aug 11, 2022 at 03:46:35PM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 40d43a7507e1547dd45cb02af2e40d897c591870
> > commit: d79b32c2e4a4e66d5678410cd45815c1c2375196 [14849/15097] vdpa_sim_blk: add support for discard and write-zeroes
> > config: i386-randconfig-a015 (https://download.01.org/0day-ci/archive/20220811/202208111501.5PSP1WaM-lkp@intel.com/config)
> > compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 5f1c7e2cc5a3c07cbc2412e851a7283c1841f520)
> > 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/next/linux-next.git/commit/?id=d79b32c2e4a4e66d5678410cd45815c1c2375196
> > git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > git fetch --no-tags linux-next master
> > git checkout d79b32c2e4a4e66d5678410cd45815c1c2375196
> > # 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=i386 SHELL=/bin/bash drivers/vdpa/vdpa_sim/
> >
> > If you fix the issue, kindly add following tag where applicable
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> > All error/warnings (new ones prefixed by >>):
> >
> > > > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:201:3: error: expected expression
> > struct virtio_blk_discard_write_zeroes range;
> > ^
> > > > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:204:25: error: use of undeclared identifier 'range'
> > if (to_pull != sizeof(range)) {
> > ^
> > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:207:21: error: use of undeclared identifier 'range'
> > to_pull, sizeof(range));
> > ^
> > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:212:60: error: use of undeclared identifier 'range'
> > bytes = vringh_iov_pull_iotlb(&vq->vring, &vq->out_iov, &range,
> > ^
> > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:222:38: error: use of undeclared identifier 'range'
> > sector = vdpasim64_to_cpu(vdpasim, range.sector);
> > ^
> > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:224:43: error: use of undeclared identifier 'range'
> > num_sectors = vdpasim32_to_cpu(vdpasim, range.num_sectors);
> > ^
> > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:225:37: error: use of undeclared identifier 'range'
> > flags = vdpasim32_to_cpu(vdpasim, range.flags);
> > ^
> > > > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:202:7: warning: mixing declarations and code is incompatible with standards before C99 [-Wdeclaration-after-statement]
> > u32 num_sectors, flags;
> > ^
> > 1 warning and 7 errors generated.
>
> I'll send followup patches to fix this issue and another that I found
> building with C=2 (virtio_blk_discard_write_zeroes fields are __leX not
> __virtioX, so I should use leX_to_cpu).
>
> Is that okay or should I re-send the original series fixed?
>
> Thanks,
Resend, I dropped them for now. Unlikely to be included in this window, at this point.
--
MST
next prev parent reply other threads:[~2022-08-11 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 7:46 kernel test robot
2022-08-11 8:12 ` Stefano Garzarella
2022-08-11 8:22 ` Michael S. Tsirkin [this message]
2022-08-11 8:29 ` Stefano Garzarella
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=20220811042124-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=sgarzare@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