From: kernel test robot <lkp@intel.com>
To: "Yuxue Liu yuxue.liu@jaguarmicro.com" <yuxue.liu@jaguarmicro.com>,
jasowang@redhat.com, mst@redhat.com
Cc: oe-kbuild-all@lists.linux.dev, xuanzhuo@linux.alibaba.com,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
yuxue.liu@jaguarmicro.com, angus.chen@jaguarmicro.com
Subject: Re: [PATCH] vdpa/vp_vdpa: implement kick_vq_with_data callback
Date: Mon, 2 Dec 2024 20:20:43 +0800 [thread overview]
Message-ID: <202412021926.Sg38msHn-lkp@intel.com> (raw)
In-Reply-To: <20241202033611.1374-1-yuxue.liu@jaguarmicro.com>
Hi Yuxue,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.13-rc1 next-20241128]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Yuxue-Liu-yuxue-liu-jaguarmicro-com/vdpa-vp_vdpa-implement-kick_vq_with_data-callback/20241202-114053
base: linus/master
patch link: https://lore.kernel.org/r/20241202033611.1374-1-yuxue.liu%40jaguarmicro.com
patch subject: [PATCH] vdpa/vp_vdpa: implement kick_vq_with_data callback
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20241202/202412021926.Sg38msHn-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241202/202412021926.Sg38msHn-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202412021926.Sg38msHn-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/vdpa/virtio_pci/vp_vdpa.c: In function 'vp_vdpa_kick_vq_with_data':
>> drivers/vdpa/virtio_pci/vp_vdpa.c:372:46: error: 'vdpa' undeclared (first use in this function)
372 | struct vp_vdpa *vp_vdpa = vdpa_to_vp(vdpa);
| ^~~~
drivers/vdpa/virtio_pci/vp_vdpa.c:372:46: note: each undeclared identifier is reported only once for each function it appears in
vim +/vdpa +372 drivers/vdpa/virtio_pci/vp_vdpa.c
369
370 static void vp_vdpa_kick_vq_with_data(struct vdpa_device *vdpa_dev, u32 data)
371 {
> 372 struct vp_vdpa *vp_vdpa = vdpa_to_vp(vdpa);
373 u16 qid = data & 0xFFFF;
374
375 vp_iowrite32(data, vp_vdpa->vring[qid].notify);
376 }
377
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-02 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 3:36 [PATCH] vdpa/vp_vdpa: implement kick_vq_with_data callback Yuxue Liu yuxue.liu@jaguarmicro.com
2024-12-02 4:21 ` Jason Wang
2024-12-03 2:37 ` [PATCH v2] " Yuxue Liu yuxue.liu@jaguarmicro.com
2024-12-04 3:09 ` Jason Wang
2025-01-08 12:02 ` Michael S. Tsirkin
2024-12-02 12:20 ` kernel test robot [this message]
2024-12-02 12:41 ` [PATCH] " kernel test robot
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=202412021926.Sg38msHn-lkp@intel.com \
--to=lkp@intel.com \
--cc=angus.chen@jaguarmicro.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yuxue.liu@jaguarmicro.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