All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: yang.yang29@zte.com.cn, corbet@lwn.net, kuba@kernel.org
Cc: davem@davemloft.net, hannes@cmpxchg.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH linux-next] docs: proc.rst: add softnet_stat
Date: Wed, 7 Dec 2022 16:10:25 +0700	[thread overview]
Message-ID: <35cb3dad-7bae-7713-3bad-b151fa6831dd@gmail.com> (raw)
In-Reply-To: <202212071423496852423@zte.com.cn>

On 12/7/22 13:23, yang.yang29@zte.com.cn wrote:
> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> index e224b6d5b642..9d5fd9424e8b 100644
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -1284,6 +1284,7 @@ support this. Table 1-9 lists the files and their meaning.
>   rt_cache      Routing cache
>   snmp          SNMP data
>   sockstat      Socket statistics
> + softnet_stat  Per-CPU incoming packets queues statistics of online CPUs
>   tcp           TCP  sockets
>   udp           UDP sockets
>   unix          UNIX domain sockets

Add softnet_stat to what table? I have to read the actual documentation
and found that you mean /proc/net table. Please mention that in patch
subject.

Regardless, this patch is from ZTE people, for which they have a
reputation for ignoring critical code reviews and "atypical" email
setup that needs to be fixed (try searching for `tc:"zte.com.cn" AND
f:"gregkh@linuxfoundation.org"` on LKML for details). If you can
receive this email, please hit "Reply all", "Group Reply" or similar.
Remember don't top-post, reply inline with appropriate context instead.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara


  reply	other threads:[~2022-12-07  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  6:23 [PATCH linux-next] docs: proc.rst: add softnet_stat yang.yang29
2022-12-07  9:10 ` Bagas Sanjaya [this message]
2022-12-07  9:51   ` yang.yang29

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=35cb3dad-7bae-7713-3bad-b151fa6831dd@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=hannes@cmpxchg.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yang.yang29@zte.com.cn \
    /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.