All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Alex Williamson <alex@shazbot.org>,
	Kevin Tian <kevin.tian@intel.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the vfio tree
Date: Mon, 9 Feb 2026 08:30:12 +0200	[thread overview]
Message-ID: <20260209063012.GB12887@unreal> (raw)
In-Reply-To: <aYlBU4l2YoT8iaBK@sirena.co.uk>

On Mon, Feb 09, 2026 at 02:07:15AM +0000, Mark Brown wrote:
> Hi all,
> 
> After merging the vfio tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> In file included from /tmp/next/build/include/rdma/ib_addr.h:21,
>                  from /tmp/next/build/include/rdma/rdma_cm.h:12,
>                  from /tmp/next/build/drivers/block/rnbd/rnbd-clt-sysfs.c:22:
> /tmp/next/build/include/rdma/ib_verbs.h:2509:37: error: 'struct dma_buf_phys_vec' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
>  2509 |                              struct dma_buf_phys_vec *phys_vec,
>       |                                     ^~~~~~~~~~~~~~~~

<...>

> Caused by commit
> 
>   b703b31ea8cd22 (types: reuse common phys_vec type instead of DMABUF open‑coded variant)
> 
> interacting with commit:
> 
>   e6738fe6cad448 (RDMA/uverbs: Add DMABUF object type and operations)
> 
> from the rdma tree.  I have reverted the latter commit (it being the new
> one), really a semantic fixup should be applied - I will try to revisit
> tomorrow.

Thanks for the report. I had forgotten to merge Alex's
common_phys_vec_via_vfio tag. This is corrected now.

Thanks




  parent reply	other threads:[~2026-02-09  6:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09  2:07 linux-next: build failure after merge of the vfio tree Mark Brown
2026-02-09  2:42 ` Mark Brown
2026-02-09  9:46   ` Edward Srouji
2026-02-09  6:30 ` Leon Romanovsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-13  3:07 Stephen Rothwell
2020-10-13 15:56 ` Diana Craciun OSS
2020-10-13 19:20   ` Alex Williamson
2020-10-15  0:59     ` Stephen Rothwell
2020-10-15  2:21       ` Alex Williamson
2020-10-13 22:16   ` Stephen Rothwell
2020-10-14 13:43     ` Diana Craciun OSS

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=20260209063012.GB12887@unreal \
    --to=leonro@nvidia.com \
    --cc=alex@shazbot.org \
    --cc=broonie@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.