All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Konstantin Taranov <kotaranov@microsoft.com>,
	 "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"leon@kernel.org" <leon@kernel.org>,
	 Long Li <longli@microsoft.com>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: Re: [PATCH rdma-next] RDMA/mana_ib: Retain create CQ flags field name
Date: Sun, 9 Aug 2026 17:55:27 +0200	[thread overview]
Message-ID: <aniik0sdK04Ie4HH@FV6GYCPJ69> (raw)
In-Reply-To: <20260807231356.GM200537@ziepe.ca>

Sat, Aug 08, 2026 at 01:13:56AM +0200, jgg@ziepe.ca wrote:
>On Mon, Aug 03, 2026 at 01:59:07PM +0200, Jiri Pirko wrote:
>
>> That is not doable in UAPI. Some userspace app, like rdma-core in
>> this case, might use it and rename breaks the compilation. Some other
>> app you don't know about may use it.
>
>Linus actualy had some comments on this once (which I will never be
>able to find I guess), but we broadly follow what he outlined. The
>userspace has copies of the kernel headers embedded in it. When the
>kernel headers change the user space updates it's copy and fixes any
>build breaks.
>
>So long as the build breaks are fixable, and don't change the ABI, it
>is fine.
>
>Many parts of the kernel work like this because userspace is not
>supposed to directly use the kernel headers themselves, they are
>supposed to be sanitized by glibc or some other helper library.
>
>There are a few places that don't work like this of course..

Yeah, me being mainly netdev-guy, that was never allowed there. Not sure
about now. But makes sense. Would be nice to have it explicitly
documented in kernel docs though.

Thanks!


      reply	other threads:[~2026-08-09 15:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  9:10 [PATCH rdma-next] RDMA/mana_ib: Retain create CQ flags field name Jiri Pirko
2026-07-31 12:54 ` Konstantin Taranov
2026-08-03 11:59   ` Jiri Pirko
2026-08-03 13:28     ` Leon Romanovsky
2026-08-04 11:08       ` Jiri Pirko
2026-08-06 11:07         ` Leon Romanovsky
2026-08-07 23:13     ` Jason Gunthorpe
2026-08-09 15:55       ` Jiri Pirko [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=aniik0sdK04Ie4HH@FV6GYCPJ69 \
    --to=jiri@resnulli.us \
    --cc=jgg@ziepe.ca \
    --cc=kotaranov@microsoft.com \
    --cc=leon@kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=longli@microsoft.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 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.