All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schier <nsc@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Arnd Bergmann" <arnd@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Dodji Seketeli <dodji@seketeli.org>,
	John Moon <john@jmoon.dev>, Nathan Chancellor <nathan@kernel.org>,
	libabigail@sourceware.org
Subject: Re: [PATCH 3/3] check-uapi: use dummy libc includes
Date: Fri, 20 Mar 2026 21:12:53 +0100	[thread overview]
Message-ID: <ab2qRWp2asMzQuWK@derry.ads.avm.de> (raw)
In-Reply-To: <0a2464d4-37b9-4b73-b29b-3802f096d343@t-8ch.de>

Hi Arnd and Thomas,

On Sat, Mar 07, 2026 at 09:51:05AM +0100, Thomas Weißschuh wrote:
> On 2026-03-06 17:45:36+0100, Arnd Bergmann wrote:
> > On Fri, Mar 6, 2026, at 17:39, Thomas Weißschuh wrote:
> > > On 2026-03-06 17:33:09+0100, Arnd Bergmann wrote:
> > >>  		  -g \
> > >>  		  "-I${inc_dir}" \
> > >> +		  "-Iusr/dummy-include" \
> > >
> > > What about also using -nostdinc?
> > 
> > I just removed it from my version after I found it made no difference,
> > and I wanted to keep the changes shorter. I agree it's slightly cleaner.
> 
> Ack, your choice.
> 
> > > I have a similar (unfinished) patch flying around which also
> > > uses usr/dummy-include from the different kernel versions
> > > to avoid mismatches in case something gets removed there.
> > > Not sure if it is worth it.
> > 
> > Agreed, I certainly don't mind having your version either if
> > anyone cares enough. I suppose it would add a very small build time
> > overhead for the extra copy, but if it does help catch bugs it
> > would be worth the time.
> 
> It is less about catching bugs, those will already have been caught by
> the header tests before. But if something is removed from the dummy
> headers because it became unused, the old UAPI headers won't build
> anymore against the new dummy-headers.
> 
> 
> Thomas

Shall I wait some more days for a possible modified patch 3/3?
Otherwise I'd like to apply the series to kbuild-next-unstable.  

Thanks and kind regards,
Nicolas

  reply	other threads:[~2026-03-20 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 16:33 [PATCH 0/3] check-uapi: improve portability for testing headers Arnd Bergmann
2026-03-06 16:33 ` [PATCH 1/3] check-uapi: link into shared objects Arnd Bergmann
2026-03-06 16:33 ` [PATCH 2/3] check-uapi: honor ${CROSS_COMPILE} setting Arnd Bergmann
2026-03-06 16:33 ` [PATCH 3/3] check-uapi: use dummy libc includes Arnd Bergmann
2026-03-06 16:39   ` Thomas Weißschuh
2026-03-06 16:45     ` Arnd Bergmann
2026-03-07  8:51       ` Thomas Weißschuh
2026-03-20 20:12         ` Nicolas Schier [this message]
2026-03-20 20:31           ` Thomas Weißschuh
2026-03-20 20:39             ` Nicolas Schier
2026-03-10  1:12 ` [PATCH 0/3] check-uapi: improve portability for testing headers Nathan Chancellor
2026-03-20 20:51 ` Nicolas Schier

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=ab2qRWp2asMzQuWK@derry.ads.avm.de \
    --to=nsc@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=dodji@seketeli.org \
    --cc=john@jmoon.dev \
    --cc=libabigail@sourceware.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=nathan@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.