public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Sridhar Samudrala <sridhar.samudrala@intel.com>,
	linux-man@vger.kernel.org, netdev@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: Re: [patch] socket.7: document SO_INCOMING_NAPI_ID
Date: Wed, 28 Oct 2020 07:15:18 +0100	[thread overview]
Message-ID: <606f44d0-2542-9027-2154-3191e47f0a6f@gmail.com> (raw)
In-Reply-To: <b3df59a9-a2c3-20c8-7563-e974e596dd2a@gmail.com>

On 10/28/20 7:13 AM, Michael Kerrisk (man-pages) wrote:
> On 10/28/20 2:15 AM, Sridhar Samudrala wrote:
>> Add documentation for SO_INCOMING_NAPI_ID in socket.7 man page.
> 
> Hello Sridhar,
> 
> Thank you!
> 
> Would it be possible for you to resubmit the patch, with a commit
> message that says how you obtained or verified the information.
> This info is useful for review, but also for understand changes
> when people look at the history in the future.

D'oh! One thing I should have checked before I hit send, I guess:

[[
commit 6d4339028b350efbf87c61e6d9e113e5373545c9
Author: Sridhar Samudrala <sridhar.samudrala@intel.com>
Date:   Fri Mar 24 10:08:36 2017 -0700

    net: Introduce SO_INCOMING_NAPI_ID
]]

But, it helps if you tell me that in the accompanying mail
message.

Thanks again for the patch. I';ll apply and fix the newlines.

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2020-10-28 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1603847722-29024-1-git-send-email-sridhar.samudrala@intel.com>
2020-10-28  6:13 ` [patch] socket.7: document SO_INCOMING_NAPI_ID Michael Kerrisk (man-pages)
2020-10-28  6:15   ` Michael Kerrisk (man-pages) [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=606f44d0-2542-9027-2154-3191e47f0a6f@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sridhar.samudrala@intel.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