From: Jakub Kicinski <kuba@kernel.org>
To: Heng Guo <heng.guo@windriver.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <filip.pudak@windriver.com>
Subject: Re: [PATCH] net-next: fix IPSTATS_MIB_OUTFORWDATAGRAMS increment after fragment check
Date: Fri, 13 Oct 2023 10:01:24 -0700 [thread overview]
Message-ID: <20231013100124.47148d24@kernel.org> (raw)
In-Reply-To: <20231011015137.27262-1-heng.guo@windriver.com>
On Wed, 11 Oct 2023 09:51:37 +0800 Heng Guo wrote:
> Subject: [PATCH] net-next: fix IPSTATS_MIB_OUTFORWDATAGRAMS increment after fragment check
Applied, thank you!
For future reference - the net-next goes into the prefix (git
format-patch --subject-prefix="PATCH net-next") and does not
replace the commit prefix. So:
[PATCH net-next] net: fix
^ \
net-next here this stays as net
next prev parent reply other threads:[~2023-10-13 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 0:59 [PATCH 0/1] Issue description and debug Heng Guo
2023-10-08 0:59 ` [PATCH 1/1] net-next: fix IPSTATS_MIB_OUTFORWDATAGRAMS increment after fragment check Heng Guo
2023-10-10 16:26 ` David Ahern
2023-10-11 1:51 ` [PATCH] " Heng Guo
2023-10-13 17:01 ` Jakub Kicinski [this message]
2023-10-13 17:10 ` patchwork-bot+netdevbpf
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=20231013100124.47148d24@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=filip.pudak@windriver.com \
--cc=heng.guo@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.