From: Alejandro Colomar <alx.manpages@gmail.com>
To: Vladislav Ivanishin <vlad@ispras.ru>
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, 5 Mar 2023 19:33:19 +0100 [thread overview]
Message-ID: <c03f1c96-2e86-df36-0ecc-474579fc4023@gmail.com> (raw)
In-Reply-To: <87v8jfcbua.fsf@ispras.ru>
[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]
Hi Vlad,
On 3/5/23 19:06, Vladislav Ivanishin wrote:
> 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!
Thanks for both pings, and sorry for the delay :)
Patch applied.
Cheers,
Alex
>>
>> 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.
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-03-05 18:33 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
2023-03-05 18:33 ` 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=c03f1c96-2e86-df36-0ecc-474579fc4023@gmail.com \
--to=alx.manpages@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=piergiorgio.beruto@gmail.com \
--cc=vlad@ispras.ru \
/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