From: Zhu Yanjun <yanjun.zhu@linux•dev>
To: kernel test robot <lkp@intel•com>,
Xuan Zhuo <xuanzhuo@linux•alibaba.com>,
netdev@vger•kernel.org
Cc: llvm@lists•linux.dev, oe-kbuild-all@lists•linux.dev,
"Michael S. Tsirkin" <mst@redhat•com>,
Jason Wang <jasowang@redhat•com>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
virtualization@lists•linux.dev
Subject: Re: [PATCH net-next 1/6] virtio_net: introduce device stats feature and structures
Date: Sun, 24 Dec 2023 16:40:42 +0800 [thread overview]
Message-ID: <2f475009-709a-4e0b-8711-51fd4a938763@linux.dev> (raw)
In-Reply-To: <202312240125.00z3nxGY-lkp@intel.com>
在 2023/12/24 1:55, kernel test robot 写道:
> Hi Xuan,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on mst-vhost/linux-next]
> [also build test ERROR on linus/master v6.7-rc6 next-20231222]
> [cannot apply to net-next/main horms-ipvs/master]
> [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/Xuan-Zhuo/virtio_net-introduce-device-stats-feature-and-structures/20231222-175505
> base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
> patch link: https://lore.kernel.org/r/20231222033021.20649-2-xuanzhuo%40linux.alibaba.com
> patch subject: [PATCH net-next 1/6] virtio_net: introduce device stats feature and structures
> config: x86_64-buildonly-randconfig-002-20231223 (https://download.01.org/0day-ci/archive/20231224/202312240125.00z3nxGY-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231224/202312240125.00z3nxGY-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/202312240125.00z3nxGY-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> In file included from <built-in>:1:
>>> ./usr/include/linux/virtio_net.h:454:2: error: unknown type name 'u8'
> u8 type;
> ^
> ./usr/include/linux/virtio_net.h:455:2: error: unknown type name 'u8'
> u8 reserved;
I can reproduce this problem.
Replacing u8 as __u8 can fix this problem.
Not sure whether __u8 is correct to the whole patches.
Zhu Yanjun
> ^
> 2 errors generated.
>
next prev parent reply other threads:[~2023-12-24 8:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 3:30 [PATCH net-next 0/6] virtio-net: support device stats Xuan Zhuo
2023-12-22 3:30 ` [PATCH net-next 1/6] virtio_net: introduce device stats feature and structures Xuan Zhuo
2023-12-23 17:55 ` kernel test robot
2023-12-24 8:40 ` Zhu Yanjun [this message]
2023-12-25 8:01 ` Zhu Yanjun
2023-12-26 6:17 ` Xuan Zhuo
2023-12-26 8:58 ` Michael S. Tsirkin
2023-12-26 9:00 ` Xuan Zhuo
2023-12-26 9:08 ` Michael S. Tsirkin
2023-12-26 9:09 ` Xuan Zhuo
2023-12-26 9:19 ` Michael S. Tsirkin
2023-12-26 9:24 ` Xuan Zhuo
2023-12-22 3:30 ` [PATCH net-next 2/6] virtio_net: virtnet_send_command supports command-specific-result Xuan Zhuo
2023-12-22 3:30 ` [PATCH net-next 3/6] virtio_net: support device stats Xuan Zhuo
2023-12-23 17:03 ` kernel test robot
2023-12-23 17:23 ` kernel test robot
2023-12-24 8:55 ` Zhu Yanjun
2024-01-03 21:03 ` Simon Horman
2023-12-22 3:30 ` [PATCH net-next 4/6] virtio_net: stats map include driver stats Xuan Zhuo
2023-12-22 3:30 ` [PATCH net-next 5/6] virtio_net: add the total stats field Xuan Zhuo
2023-12-22 3:30 ` [PATCH net-next 6/6] virtio_net: rename stat tx_timeout to timeout Xuan Zhuo
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=2f475009-709a-4e0b-8711-51fd4a938763@linux.dev \
--to=yanjun.zhu@linux$(echo .)dev \
--cc=edumazet@google$(echo .)com \
--cc=jasowang@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=lkp@intel$(echo .)com \
--cc=llvm@lists$(echo .)linux.dev \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=oe-kbuild-all@lists$(echo .)linux.dev \
--cc=pabeni@redhat$(echo .)com \
--cc=virtualization@lists$(echo .)linux.dev \
--cc=xuanzhuo@linux$(echo .)alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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