Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zhu Yanjun <yanjun.zhu@linux.dev>,
	zyjzyj2000@gmail.com, jgg@ziepe.ca, leon@kernel.org,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Zhu Yanjun <yanjun.zhu@linux.dev>
Subject: Re: [PATCH v2 2/2] RDMA/rxe: Replace struct rxe_sge with struct ib_sge
Date: Tue, 23 Dec 2025 04:49:38 +0800	[thread overview]
Message-ID: <202512230416.lX0ue12Z-lkp@intel.com> (raw)
In-Reply-To: <20251221233404.332108-2-yanjun.zhu@linux.dev>

Hi Zhu,

kernel test robot noticed the following build errors:

[auto build test ERROR on rdma/for-next]
[also build test ERROR on linus/master v6.19-rc2 next-20251219]
[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/Zhu-Yanjun/RDMA-rxe-Replace-struct-rxe_sge-with-struct-ib_sge/20251222-074206
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-next
patch link:    https://lore.kernel.org/r/20251221233404.332108-2-yanjun.zhu%40linux.dev
patch subject: [PATCH v2 2/2] RDMA/rxe: Replace struct rxe_sge with struct ib_sge
config: x86_64-buildonly-randconfig-006-20251222 (https://download.01.org/0day-ci/archive/20251223/202512230416.lX0ue12Z-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251223/202512230416.lX0ue12Z-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/202512230416.lX0ue12Z-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from <built-in>:1:
>> ./usr/include/rdma/rdma_user_rxe.h:141:3: error: array has incomplete element type 'struct ib_sge'
     141 |                 __DECLARE_FLEX_ARRAY(struct ib_sge, sge);
         |                 ^
   usr/include/linux/stddef.h:56:12: note: expanded from macro '__DECLARE_FLEX_ARRAY'
      56 |                 TYPE NAME[]; \
         |                          ^
   ./usr/include/rdma/rdma_user_rxe.h:141:31: note: forward declaration of 'struct ib_sge'
     141 |                 __DECLARE_FLEX_ARRAY(struct ib_sge, sge);
         |                                             ^
   1 error generated.

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-12-22 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-21 23:34 [PATCH v2 1/2] RDMA/rxe: Avoid -Wflex-array-member-not-at-end warnings Zhu Yanjun
2025-12-21 23:34 ` [PATCH v2 2/2] RDMA/rxe: Replace struct rxe_sge with struct ib_sge Zhu Yanjun
2025-12-22 16:36   ` kernel test robot
2025-12-22 20:49   ` kernel test robot [this message]
2025-12-22 22:49   ` 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=202512230416.lX0ue12Z-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yanjun.zhu@linux.dev \
    --cc=zyjzyj2000@gmail.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