From: Alejandro Colomar <alx@kernel.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Alexander Ofitserov <oficerovas@altlinux.org>,
linux-man@vger.kernel.org, dutyrok@altlinux.org,
kovalev@altlinux.org
Subject: Re: [PATCH] delete_module.2: Update man to actual syscall behaviour
Date: Tue, 20 Feb 2024 19:42:02 +0100 [thread overview]
Message-ID: <ZdTyelsM_Wuid98m@debian> (raw)
In-Reply-To: <20240220181830.GA12635@altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
Hi Dmitry, Alexander,
On Tue, Feb 20, 2024 at 08:18:30PM +0200, Dmitry V. Levin wrote:
> On Tue, Feb 20, 2024 at 12:21:44PM +0300, Alexander Ofitserov wrote:
> > Parameter O_NONBLOCK described in man doesn't exist anymore
> > in kernel versions 3.13+, which is quite old,
>
> I suggest mentioning the Linux kernel commit id that removed O_NONBLOCK
> support, which seems to be 3f2b9c9cdf389e303b2273679af08aab5f153517
> aka v3.13-rc1~83^2~5.
>
> > only O_TRUNC parameter present for actual kernel version,
> > O_NONBLOCK does nothing.
>
> While it's vital to document the current kernel behavior,
> I wish a description of the historical behavior is also retained.
Thanks! You could describe the old behavior in the HISTORY section.
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-20 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 9:21 [PATCH] delete_module.2: Update man to actual syscall behaviour Alexander Ofitserov
2024-02-20 13:20 ` G. Branden Robinson
2024-02-20 15:24 ` Alejandro Colomar
2024-02-20 16:36 ` G. Branden Robinson
2024-02-20 17:48 ` Alejandro Colomar
2024-02-20 18:18 ` Dmitry V. Levin
2024-02-20 18:42 ` 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=ZdTyelsM_Wuid98m@debian \
--to=alx@kernel.org \
--cc=dutyrok@altlinux.org \
--cc=kovalev@altlinux.org \
--cc=ldv@altlinux.org \
--cc=linux-man@vger.kernel.org \
--cc=oficerovas@altlinux.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.