From: Huacai Chen <chenhuacai@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Hengqi Chen <hengqi.chen@gmail.com>,
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, 3 Jan 2023 20:31:47 +0800 [thread overview]
Message-ID: <CAAhV-H7+XeCmxCbpEqWzDt+S_UabPLyyn+uGe7qCkr-HbYCRrQ@mail.gmail.com> (raw)
In-Reply-To: <9d2d3268-6558-2387-7d26-0fc51c365204@iogearbox.net>
OK, bpf-next is also fine for me.
Acked-by: Huacai Chen <chenhuacai@loongson.cn>
On Tue, Jan 3, 2023 at 8:28 PM Daniel Borkmann <daniel@iogearbox.net> wrote:
>
> On 1/3/23 7:53 AM, Huacai Chen wrote:
> > LGTM, I will queue this patch for loongarch-next if no one has
> > objections. Thank you.
>
> To avoid potential merge conflicts for the next dev cycle, any objections if
> you could Ack it and we'd take it via bpf-next tree instead?
>
> Thanks,
> Daniel
next prev parent reply other threads:[~2023-01-03 12:32 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 [this message]
2023-01-03 15:50 ` patchwork-bot+netdevbpf
-- 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=CAAhV-H7+XeCmxCbpEqWzDt+S_UabPLyyn+uGe7qCkr-HbYCRrQ@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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 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).