From: patchwork-bot+bpf@kernel.org
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/3] samples: bpf: split xdpsock stats into new struct
Date: Tue, 06 Oct 2020 18:50:04 +0000 [thread overview]
Message-ID: <160201020450.15578.15216583134041941419.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201002133612.31536-1-ciara.loftus@intel.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 2 Oct 2020 13:36:10 +0000 you wrote:
> New statistics will be added in future commits. In preparation for this,
> let's split out the existing statistics into their own struct.
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
> samples/bpf/xdpsock_user.c | 123 +++++++++++++++++++++----------------
> 1 file changed, 69 insertions(+), 54 deletions(-)
Here is the summary with links:
- [bpf-next,1/3] samples: bpf: split xdpsock stats into new struct
https://git.kernel.org/bpf/bpf-next/c/2e8806f032f5
- [bpf-next,2/3] samples: bpf: count syscalls in xdpsock
https://git.kernel.org/bpf/bpf-next/c/60dc609dbd54
- [bpf-next,3/3] samples: bpf: driver interrupt statistics in xdpsock
https://git.kernel.org/bpf/bpf-next/c/67ed375530e2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-10-06 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 13:36 [PATCH bpf-next 1/3] samples: bpf: split xdpsock stats into new struct Ciara Loftus
2020-10-02 13:36 ` [PATCH bpf-next 2/3] samples: bpf: count syscalls in xdpsock Ciara Loftus
2020-10-03 5:20 ` Yonghong Song
2020-10-02 13:36 ` [PATCH bpf-next 3/3] samples: bpf: driver interrupt statistics " Ciara Loftus
2020-10-03 5:17 ` [PATCH bpf-next 1/3] samples: bpf: split xdpsock stats into new struct Yonghong Song
2020-10-06 18:50 ` patchwork-bot+bpf [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=160201020450.15578.15216583134041941419.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ciara.loftus@intel.com \
--cc=netdev@vger.kernel.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 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.