From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH bpf-next] perf: mute libbpf API deprecations temporarily
Date: Fri, 3 Dec 2021 12:47:27 +1100 [thread overview]
Message-ID: <20211203124727.5a718792@canb.auug.org.au> (raw)
In-Reply-To: <CAEf4BzZe7bc6cRopJG4L6Et8OjCiGym8XzJPx_8NpyScwg_i=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Hi Andrii,
On Thu, 2 Dec 2021 17:00:40 -0800 Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>
> This patch (when applied to bpf-next) should fix the build failure you
> reported in your recent "linux-next: build failure after merge of the
> bpf-next tree" email (that I didn't get directly, but thankfully
> Alexei forwarded to me). Can you please also cc bpf@vger.kernel.orgfor
> future bpf-next tree issues, as that's a more directly related mailing
> list (ideally also cc me at andrii@kernel.org directly so that we
> don't rely on Gmail not dropping the email, I've, unfortunately, had
> multiple problems with this recently). Thanks for understanding!
Hopefully that patch will be applied soon :-)
I have added the bpf list and you to my contacts for the bpf and
bpf-next trees in linux-next.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-12-03 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 0:46 [PATCH bpf-next] perf: mute libbpf API deprecations temporarily Andrii Nakryiko
2021-12-03 1:00 ` Andrii Nakryiko
2021-12-03 1:47 ` Stephen Rothwell [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=20211203124727.5a718792@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=kernel-team@fb.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