From: Florian Weimer <fweimer@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Dorjoy Chowdhury <dorjoychy111@gmail.com>,
linux-man@vger.kernel.org, brauner@kernel.org,
jlayton@kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH v2 1/2] man/man3/errno.3: Document EFTYPE error code
Date: Mon, 27 Apr 2026 12:34:30 +0200 [thread overview]
Message-ID: <lhu5x5c4rpl.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <ae4K_5f1g3zgSNkC@devuan> (Alejandro Colomar's message of "Sun, 26 Apr 2026 14:59:12 +0200")
* Alejandro Colomar:
> [CC += libc-alpha]
>
> Hi Dorjoy,
>
> On 2026-04-26T17:14:25+0600, Dorjoy Chowdhury wrote:
>> Signed-off-by: Dorjoy Chowdhury <dorjoychy111@gmail.com>
>
> Thanks!
>
> Reviewed-by: Alejandro Colomar <alx@kernel.org>
>
> I will wait until glibc adds this error code to their <errno.h> before
> applying the patch. This means either you should write and send a patch
> to glibc (if so, please CC me), or you should ask them to add it
> themselves (if you're not comfortable writing glibc code).
I'm not sure where this is coming from. POSIX says EFTYPE was rejected
in favor of ENOTTY.
Thanks,
Florian
next prev parent reply other threads:[~2026-04-27 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 11:14 [PATCH v2 0/2] Document EFTYPE error code and OPENAT2_REGULAR flag Dorjoy Chowdhury
2026-04-26 11:14 ` [PATCH v2 1/2] man/man3/errno.3: Document EFTYPE error code Dorjoy Chowdhury
2026-04-26 12:59 ` Alejandro Colomar
2026-04-27 10:34 ` Florian Weimer [this message]
2026-04-27 13:13 ` Alejandro Colomar
2026-04-27 13:29 ` Florian Weimer
2026-04-27 13:33 ` Alejandro Colomar
2026-04-26 11:14 ` [PATCH v2 2/2] man/man2/openat2.2: Document OPENAT2_REGULAR flag Dorjoy Chowdhury
2026-04-26 13:03 ` Alejandro Colomar
2026-04-26 17:39 ` Dorjoy Chowdhury
2026-04-26 19:15 ` Alejandro Colomar
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=lhu5x5c4rpl.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=dorjoychy111@gmail.com \
--cc=jlayton@kernel.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox