From: Jakub Kicinski <kuba@kernel.org>
To: heng guo <heng.guo@windriver.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
netdev@vger.kernel.org, Filip Pudak <filip.pudak@windriver.com>,
Richard.Danter@windriver.com
Subject: Re: [NETWORKING] IPSTATS_MIB_OUTOCTETS increment is duplicated in SNMP
Date: Thu, 17 Aug 2023 17:58:06 -0700 [thread overview]
Message-ID: <20230817175806.5a20d592@kernel.org> (raw)
In-Reply-To: <9a10520c-bfa9-2089-7d01-8ce215c48063@windriver.com>
On Thu, 17 Aug 2023 11:32:43 +0800 heng guo wrote:
> Linux version: 5.10.154
> Platform: ARM nxp-ls1028
Linux development doesn't happen in stable trees.
Can you reproduce this problem on Linus's tree?
If so please rebase the patch and resend it
(after reading how to submit patches to Linux).
prev parent reply other threads:[~2023-08-18 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 3:32 [NETWORKING] IPSTATS_MIB_OUTOCTETS increment is duplicated in SNMP heng guo
2023-08-18 0:58 ` Jakub Kicinski [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=20230817175806.5a20d592@kernel.org \
--to=kuba@kernel.org \
--cc=Richard.Danter@windriver.com \
--cc=davem@davemloft.net \
--cc=filip.pudak@windriver.com \
--cc=heng.guo@windriver.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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;
as well as URLs for NNTP newsgroup(s).