From: Breno Leitao <leitao@debian.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, dsahern@kernel.org,
"open list:WIREGUARD SECURE NETWORK TUNNEL"
<wireguard@lists.zx2c4.com>
Subject: Re: [PATCH net-next v2 1/2] wireguard: Leverage core stats allocator
Date: Thu, 14 Mar 2024 02:24:58 -0700 [thread overview]
Message-ID: <ZfLCakKfDmC/JNPV@gmail.com> (raw)
In-Reply-To: <CAHmME9oPPtJXd8DsA+xXvbdN7T0PbAM5kYpQj32KZXv9bKP1ng@mail.gmail.com>
On Wed, Mar 13, 2024 at 09:35:43PM -0600, Jason A. Donenfeld wrote:
> On Wed, Mar 13, 2024 at 9:27 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >
> > On Wed, Mar 13, 2024 at 9:24 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> > >
> > > I applied this series to the wireguard tree. Thanks for the patches.
> >
> > Actually, sorry, nevermind. 1/2 is fine, but 2/2 results in `ip -stats
> > link ...` returning all zeros.
>
> Ahh, okay, required some more commits from 6.8. Okay, seems to be
> working. I'll let this cook a bit and then push it up in a while.
Right, it requires the following commit, which is already in net-next
and 6.9 by now.
3e2f544dd8a33b2f6 ("net: get stats64 if device if driver is configured")
Thanks Jason!
prev parent reply other threads:[~2024-11-18 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 11:27 Breno Leitao
2024-03-08 11:27 ` [PATCH net-next v2 2/2] wireguard: Remove generic .ndo_get_stats64 Breno Leitao
2024-03-11 9:22 ` Simon Horman
2024-03-11 9:22 ` [PATCH net-next v2 1/2] wireguard: Leverage core stats allocator Simon Horman
2024-03-14 3:23 ` Jason A. Donenfeld
2024-03-14 3:27 ` Jason A. Donenfeld
2024-03-14 3:35 ` Jason A. Donenfeld
2024-03-14 9:24 ` Breno Leitao [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=ZfLCakKfDmC/JNPV@gmail.com \
--to=leitao@debian.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).