From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Mirsad Todorovac" <mtodorovac69@gmail.com>
Cc: "John Hubbard" <jhubbard@nvidia.com>,
<linux-kselftest@vger.kernel.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Shuah Khan" <shuah@kernel.org>, <linux-sgx@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, "Edward Liaw" <edliaw@google.com>
Subject: Re: [PATCH v1 1/1] selftests/sgx: Fix the implicit declaration of asprintf() compiler error
Date: Mon, 13 May 2024 14:20:52 +0300 [thread overview]
Message-ID: <D18H6GHC4VSW.3C39QY6XUDOQR@kernel.org> (raw)
In-Reply-To: <CAJ3WTWRQcZN5JSNAhUKXfpH8Q5sW_-EorMpgCE24G3NpczpqZQ@mail.gmail.com>
On Mon May 13, 2024 at 12:43 PM EEST, Mirsad Todorovac wrote:
> Thanks for your explanation.
>
> I did not realise that __USE_GNU is evil. :-/
It's not "evil" IMHO. It is not just part of defined API :-)
Thus the official man pages are your friend.
>
> FWIW, there is a sound explanation of the difference between
> _GNU_SOURCE and __USE_GNU
> here: https://stackoverflow.com/questions/7296963/gnu-source-and-use-gnu
>
> Thanks,
> Mirsad
BR, Jarkko
next prev parent reply other threads:[~2024-05-13 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 20:37 [PATCH v1 1/1] selftests/sgx: Fix the implicit declaration of asprintf() compiler error Mirsad Todorovac
2024-05-10 20:52 ` John Hubbard
2024-05-10 21:02 ` Mirsad Todorovac
2024-05-12 23:02 ` Jarkko Sakkinen
2024-05-13 9:43 ` Mirsad Todorovac
2024-05-13 11:20 ` Jarkko Sakkinen [this message]
2024-05-12 22:58 ` Jarkko Sakkinen
2024-05-12 22:48 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2024-05-10 20:46 Mirsad Todorovac
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=D18H6GHC4VSW.3C39QY6XUDOQR@kernel.org \
--to=jarkko@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=edliaw@google.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mtodorovac69@gmail.com \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).