mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bo Liu <liubo03@inspur.com>, mst@redhat.com, jasowang@redhat.com
Cc: kbuild-all@lists.01.org,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, Bo Liu <liubo03@inspur.com>
Subject: Re: [PATCH] virtio_ring: remove unused variable in virtqueue_add()
Date: Fri, 20 May 2022 22:12:21 +0800	[thread overview]
Message-ID: <202205202236.ztzLWFZ4-lkp@intel.com> (raw)
In-Reply-To: <20220520070740.7151-1-liubo03@inspur.com>

Hi Bo,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.18-rc7 next-20220519]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/intel-lab-lkp/linux/commits/Bo-Liu/virtio_ring-remove-unused-variable-in-virtqueue_add/20220520-161845
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 3d7285a335edaf23b699e87c528cf0b0070e3293
config: x86_64-rhel-8.3-func (https://download.01.org/0day-ci/archive/20220520/202205202236.ztzLWFZ4-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce (this is a W=1 build):
        # https://github.com/intel-lab-lkp/linux/commit/8344061823a47f3245d81db45f5898d940ac488e
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Bo-Liu/virtio_ring-remove-unused-variable-in-virtqueue_add/20220520-161845
        git checkout 8344061823a47f3245d81db45f5898d940ac488e
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/virtio/virtio_ring.c: In function 'virtqueue_add':
>> drivers/virtio/virtio_ring.c:1785:16: error: 'vq' undeclared (first use in this function); did you mean '_vq'?
    1785 |         return vq->packed_ring ? virtqueue_add_packed(_vq, sgs, total_sg,
         |                ^~
         |                _vq
   drivers/virtio/virtio_ring.c:1785:16: note: each undeclared identifier is reported only once for each function it appears in
   drivers/virtio/virtio_ring.c:1789:1: error: control reaches end of non-void function [-Werror=return-type]
    1789 | }
         | ^
   cc1: some warnings being treated as errors


vim +1785 drivers/virtio/virtio_ring.c

1ce9e6055fa0a9 Tiwei Bie 2018-11-21  1770  
1ce9e6055fa0a9 Tiwei Bie 2018-11-21  1771  
e6f633e5beab65 Tiwei Bie 2018-11-21  1772  /*
e6f633e5beab65 Tiwei Bie 2018-11-21  1773   * Generic functions and exported symbols.
e6f633e5beab65 Tiwei Bie 2018-11-21  1774   */
e6f633e5beab65 Tiwei Bie 2018-11-21  1775  
e6f633e5beab65 Tiwei Bie 2018-11-21  1776  static inline int virtqueue_add(struct virtqueue *_vq,
e6f633e5beab65 Tiwei Bie 2018-11-21  1777  				struct scatterlist *sgs[],
e6f633e5beab65 Tiwei Bie 2018-11-21  1778  				unsigned int total_sg,
e6f633e5beab65 Tiwei Bie 2018-11-21  1779  				unsigned int out_sgs,
e6f633e5beab65 Tiwei Bie 2018-11-21  1780  				unsigned int in_sgs,
e6f633e5beab65 Tiwei Bie 2018-11-21  1781  				void *data,
e6f633e5beab65 Tiwei Bie 2018-11-21  1782  				void *ctx,
e6f633e5beab65 Tiwei Bie 2018-11-21  1783  				gfp_t gfp)
e6f633e5beab65 Tiwei Bie 2018-11-21  1784  {
1ce9e6055fa0a9 Tiwei Bie 2018-11-21 @1785  	return vq->packed_ring ? virtqueue_add_packed(_vq, sgs, total_sg,
1ce9e6055fa0a9 Tiwei Bie 2018-11-21  1786  					out_sgs, in_sgs, data, ctx, gfp) :
1ce9e6055fa0a9 Tiwei Bie 2018-11-21  1787  				 virtqueue_add_split(_vq, sgs, total_sg,
e6f633e5beab65 Tiwei Bie 2018-11-21  1788  					out_sgs, in_sgs, data, ctx, gfp);
e6f633e5beab65 Tiwei Bie 2018-11-21  1789  }
e6f633e5beab65 Tiwei Bie 2018-11-21  1790  

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

      reply	other threads:[~2022-05-20 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  7:07 Bo Liu
2022-05-20 14:12 ` kernel test robot [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=202205202236.ztzLWFZ4-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jasowang@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubo03@inspur.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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®