All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hengqi Chen <hengqi.chen@gmail.com>
Cc: bpf@vger.kernel.org, loongarch@lists.linux.dev, andrii@kernel.org
Subject: Re: [PATCH bpf-next] libbpf: Add LoongArch support to bpf_tracing.h
Date: Tue, 03 Jan 2023 15:50:17 +0000	[thread overview]
Message-ID: <167276101738.20921.8564438436207074197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221231100757.3177034-1-hengqi.chen@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Sat, 31 Dec 2022 18:07:57 +0800 you wrote:
> Add PT_REGS macros for LoongArch ([0]).
> 
>   [0]: https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html
> 
> Signed-off-by: Hengqi Chen <hengqi.chen@gmail.com>
> ---
>  tools/lib/bpf/bpf_tracing.h | 23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: Add LoongArch support to bpf_tracing.h
    https://git.kernel.org/bpf/bpf-next/c/00883922ab40

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-01-03 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 10:07 [PATCH bpf-next] libbpf: Add LoongArch support to bpf_tracing.h Hengqi Chen
2023-01-03  6:53 ` Huacai Chen
2023-01-03 12:28   ` Daniel Borkmann
2023-01-03 12:31     ` Huacai Chen
2023-01-03 15:50 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-25 12:01 Hengqi Chen
2022-12-27  0:13 ` WANG Xuerui
2022-12-29 23:11 ` Andrii Nakryiko
2022-12-12  9:11 Hengqi Chen
2022-12-13  0:17 ` Andrii Nakryiko
2022-12-13 22:09   ` Andrii Nakryiko
2022-12-14  2:07     ` Hengqi Chen
2022-12-11  7:16 Hengqi Chen

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=167276101738.20921.8564438436207074197.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=hengqi.chen@gmail.com \
    --cc=loongarch@lists.linux.dev \
    /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.