From: Li Wang via ltp <ltp@lists.linux.it>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] openat2: Move includes to lapi, remove _GNU_SOURCE
Date: Thu, 5 Feb 2026 18:17:11 +0800 [thread overview]
Message-ID: <aYRuJ9BuS_MutfOD@redhat.com> (raw)
In-Reply-To: <20260205094458.GA294817@pevik>
On Thu, Feb 05, 2026 at 10:44:58AM +0100, Petr Vorel wrote:
> > On Wed, Feb 04, 2026 at 01:43:23PM +0100, Petr Vorel wrote:
> > > Improve 767b3e519e. struct open_how is also used in lapi/openat2.h,
> > > which is used by all openat2*.c tests. Therefore move <fcntl.h> to the
> > > lapi header (and use lapi/fcntl.h instead).
>
> > > Also remove _GNU_SOURCE which should not be needed.
>
> > > While at it, move include "config.h" to the top.
>
> > > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > > ---
> > > Hi Li,
>
> > > my points from the original patchset why not use _GNU_SOURCE:
>
> > > glibc test tst-openat2.c [1] which includes <fcntl.h>, uses struct
>
> > Interesting, I haven't figure out why it can be built within glibc itself.
>
> I also checked Makefile, but haven't found that. Never mind, I was wrong, it's
> obviously needed.
It's becuase of -D_GNU_SOURCE cflag in Makerules(which included in Makefile):
https://sourceware.org/git/?p=glibc.git;a=blob;f=Makerules;h=30c3559a285e5bc0571358ab785bf9b5d5a8f449;hb=HEAD#l1182
In case of you miss my last reply thread:
https://lists.linux.it/pipermail/ltp/2026-February/046438.html
--
Regards,
Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-02-05 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 12:43 [LTP] [PATCH] openat2: Move includes to lapi, remove _GNU_SOURCE Petr Vorel
2026-02-05 6:08 ` Li Wang via ltp
2026-02-05 9:41 ` Li Wang via ltp
2026-02-05 10:25 ` Petr Vorel
2026-02-05 9:44 ` Petr Vorel
2026-02-05 10:17 ` Li Wang via ltp [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=aYRuJ9BuS_MutfOD@redhat.com \
--to=ltp@lists.linux.it \
--cc=liwang@redhat.com \
--cc=pvorel@suse.cz \
/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