public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: vursc <vursc@vursc.org>
Cc: Mark Harris <mark.hsj@gmail.com>,
	linux-man@vger.kernel.org,  libc-help@sourceware.org
Subject: Re: [PATCH] man/man2/getdents.2: Fix incorrect argument type
Date: Mon, 6 Apr 2026 10:28:00 +0200	[thread overview]
Message-ID: <adNtfcGsNW9bsZyH@debian> (raw)
In-Reply-To: <DHLTV0BGLRPZ.3LJZ9TGV7U7YF@vursc.org>

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

Hi vursc,

On Mon, Apr 06, 2026 at 05:37:24AM +0000, vursc wrote:
> Should I document the dirent64 structure in glibc?


Given that it's different from the kernel one, I think we should
document both, yes.

> versions of struct dirent64 in glibc, in
> glibc/sysdeps/unix/sysv/linux/bits/dirent.h and glibc/bits/dirent.h,
> and the latter seems irrelevant on linux systems.

Yes, I seem to have the former in the installed headers.  I don't know
why the latter exists.  I've CCed libc-help@ in case they can help.

> 
> And I'm not sure about the wording. Feel free to reword it as you see
> fit.

The current patch seems reasonable.  If you add the glibc struct, I'll
add it, and later maybe I'll tweak that page to look more like other
pages.


Have a lovely day!
Alex

> 
> -vursc
> 

-- 
<https://www.alejandro-colomar.es>
Use port 80 (that is, <...:80/>).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-04-06  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04  7:49 [PATCH] man/man2/getdents.2: Fix incorrect argument type vursc
2026-04-04 21:53 ` Mark Harris
2026-04-05 22:04   ` Alejandro Colomar
2026-04-06  5:37   ` vursc
2026-04-06  8:28     ` Alejandro Colomar [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=adNtfcGsNW9bsZyH@debian \
    --to=alx@kernel.org \
    --cc=libc-help@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mark.hsj@gmail.com \
    --cc=vursc@vursc.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