public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Ivanishin <vlad@ispras.ru>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, Eric Dumazet <eric.dumazet@gmail.com>,
	Piergiorgio Beruto <piergiorgio.beruto@gmail.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [patch] recv.2: Mention SOCK_SEQPACKET in MSG_TRUNC flag description
Date: Sun, 05 Mar 2023 21:06:05 +0300	[thread overview]
Message-ID: <87v8jfcbua.fsf@ispras.ru> (raw)
In-Reply-To: <87ilfwgamh.fsf@ispras.ru> (Vladislav Ivanishin's message of "Mon, 20 Feb 2023 08:37:58 +0300")

Ping (there haven't been any objections to the current version of the
patch at https://lore.kernel.org/linux-man/87cz6fqa0z.fsf@ispras.ru/).

On Mon, Feb 20 2023, Vladislav Ivanishin <vlad@ispras.ru> wrote:
> Hi Alex; ping!
>
> On Mon, Feb 13 2023, Vladislav Ivanishin <vlad@ispras.ru> wrote:
>> On Sun, Feb 12 2023, Alejandro Colomar <alx.manpages@gmail.com> wrote:
>>> Thanks!  I CCd those involved in the referred commit.  I'll give them
>>> a week or so to have a look.
>>
>> Great, thank you!
>>
>>> Could you please ping me again in a week or so?
>>
>> No problem, will do.

  reply	other threads:[~2023-03-05 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 10:38 [patch] recv.2: Mention SOCK_SEQPACKET in MSG_TRUNC flag description Vladislav Ivanishin
2022-12-11 16:09 ` Alejandro Colomar
2023-02-12 13:38   ` Vladislav Ivanishin
2023-02-12 19:14     ` Alejandro Colomar
2023-02-13  5:38       ` Vladislav Ivanishin
2023-02-20  5:37         ` Vladislav Ivanishin
2023-03-05 18:06           ` Vladislav Ivanishin [this message]
2023-03-05 18:33             ` 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=87v8jfcbua.fsf@ispras.ru \
    --to=vlad@ispras.ru \
    --cc=alx.manpages@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=piergiorgio.beruto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox