All of lore.kernel.org
 help / color / mirror / Atom feed
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, "G. Branden Robinson" <branden@debian.org>,
	Stefan Puiu <stefan.puiu@gmail.com>
Subject: Re: [PATCH v3] delete_module.2: Update man to current syscall behaviour
Date: Mon, 4 Mar 2024 17:09:47 +0100	[thread overview]
Message-ID: <ZeXyS_yVEnVzCVdo@debian> (raw)
In-Reply-To: <20240226185554.GA19542@altlinux.org>

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

Hi Alexander,

On Mon, Feb 26, 2024 at 08:55:54PM +0200, Dmitry V. Levin wrote:
> On Mon, Feb 26, 2024 at 03:08:56PM +0300, Alexander Ofitserov wrote:
> > Parameter O_NONBLOCK described in man doesn't exist anymore
> > in kernel versions 3.13+, which is quite old,
> > only O_TRUNC parameter present for current kernel version,
> > O_NONBLOCK does nothing.
> > 
> > v2 -> v3:
> > subsection Linux 3.12 and earlier renamed to O_NONBLOCK
> > removed info about arguments for kernels 3.12 and earlier
> > added semantic newlines
> > 
> > v1 -> v2:
> > added behaviour of syscall for kernel 3.12 and earlier
> > in history section
> > added commit hash to commit message
> 
> Looks like the change of the commit message introduced in v2
> has been reverted.

As Dmitry said, the commit message doesn't show the Linux hash anymore.
Could you check that?

Have 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 --]

      reply	other threads:[~2024-03-04 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 12:08 [PATCH v3] delete_module.2: Update man to current syscall behaviour Alexander Ofitserov
2024-02-26 18:55 ` Dmitry V. Levin
2024-03-04 16:09   ` 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=ZeXyS_yVEnVzCVdo@debian \
    --to=alx@kernel.org \
    --cc=branden@debian.org \
    --cc=dutyrok@altlinux.org \
    --cc=kovalev@altlinux.org \
    --cc=ldv@altlinux.org \
    --cc=linux-man@vger.kernel.org \
    --cc=oficerovas@altlinux.org \
    --cc=stefan.puiu@gmail.com \
    /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.