public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: kXuan <kxuanobj@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] recv.2: tfix
Date: Mon, 5 Jul 2021 21:05:35 +0200	[thread overview]
Message-ID: <cf56a0f9-8612-29ea-92da-ba113dee16ce@gmail.com> (raw)
In-Reply-To: <20210705082907.1513197-1-kxuanobj@gmail.com>

Hello.

On 7/5/21 10:29 AM, kXuan wrote:
> The recv.2 misspelled `SO_EE_OFFENDER` to `SOCK_EE_OFFENDER`.
> 
> This patch fix this typo.
> 
> Signed-off-by: kXuan <kxuanobj@gmail.com>

Patch applied.

Thanks,

Alex

> ---
>   man2/recv.2 | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man2/recv.2 b/man2/recv.2
> index 2659957a6..884c86355 100644
> --- a/man2/recv.2
> +++ b/man2/recv.2
> @@ -196,7 +196,7 @@ number of the queued error.
>   is the origin code of where the error originated.
>   The other fields are protocol-specific.
>   The macro
> -.B SOCK_EE_OFFENDER
> +.B SO_EE_OFFENDER
>   returns a pointer to the address of the network object
>   where the error originated from given a pointer to the ancillary message.
>   If this address is not known, the
> 


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-07-05 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05  8:29 [PATCH] recv.2: tfix kXuan
2021-07-05 19:05 ` Alejandro Colomar (man-pages) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-13 12:21 Akihiro Motoki
     [not found] ` <CALhU9tm5JFXVrXFqTw=PaNQ42PmUSa+v7WfNMR+RAX4DAOkg0Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-13 12:28   ` Michael Kerrisk (man-pages)

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=cf56a0f9-8612-29ea-92da-ba113dee16ce@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=kxuanobj@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@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