From: "Ariel Otilibili-Anieli" <Ariel.Otilibili-Anieli@eurecom.fr>
To: "Andrii Nakryiko" <andrii.nakryiko@gmail.com>
Cc: "Quentin Monnet" <qmo@qmon.net>,
bpf@vger.kernel.org, "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] selftests/bpf: clear out Python syntax warnings
Date: Sat, 11 Jan 2025 01:31:53 +0100 [thread overview]
Message-ID: <45fce-6781bc00-f9-4f02af00@63714014> (raw)
In-Reply-To: <CAEf4BzbO=R-=4a2s8OF0Vhs+L4g+z0bwLm4q56eVRoWr6m5Zrw@mail.gmail.com>
Hi Andrii,
On Saturday, January 11, 2025 01:23 CET, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
> On Fri, Dec 20, 2024 at 8:28 AM Ariel Otilibili-Anieli
> <Ariel.Otilibili-Anieli@eurecom.fr> wrote:
>
> Seems like this was never applied, right? Ariel, can you please rebase
> on latest bpf-next, add Quentin's tested-by and reviewed-by and
> resend, so BPF CI can do another run on it? Thanks.
>
Thanks for looking onto the patch. From this link, I can tell it was applied on bpf-next. Right?
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=c5d2bac978c5
Regards,
Ariel
next prev parent reply other threads:[~2025-01-11 0:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 21:57 [PATCH 0/1] clear out Python syntax warnings Ariel Otilibili
2024-12-11 21:57 ` [PATCH 1/1] selftests/bpf: " Ariel Otilibili
2024-12-20 16:24 ` Quentin Monnet
2024-12-20 16:28 ` Ariel Otilibili-Anieli
2025-01-11 0:23 ` Andrii Nakryiko
2025-01-11 0:31 ` Ariel Otilibili-Anieli [this message]
2024-12-17 21:10 ` [PING] " Ariel Otilibili-Anieli
2024-12-20 17:00 ` [PATCH 0/1] " patchwork-bot+netdevbpf
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=45fce-6781bc00-f9-4f02af00@63714014 \
--to=ariel.otilibili-anieli@eurecom.fr \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=qmo@qmon.net \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox