BPF List
 help / color / mirror / Atom feed
From: "Ariel Otilibili-Anieli" <Ariel.Otilibili-Anieli@eurecom.fr>
To: "Ariel Otilibili" <ariel.otilibili-anieli@eurecom.fr>
Cc: bpf@vger.kernel.org, "Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Andrii Nakryiko" <andrii@kernel.org>
Subject: [PING] clear out Python syntax warnings
Date: Tue, 17 Dec 2024 22:10:27 +0100	[thread overview]
Message-ID: <2f7a8a-6761e900-9a95-1d1363a0@43143619> (raw)
In-Reply-To: <20241211220012.714055-1-ariel.otilibili-anieli@eurecom.fr>

Hello,

Is there any news on the series? I got this warning from patchwork-ci:

https://github.com/kernel-patches/bpf/actions/runs/12379738694/job/34555356286

I am looking forward your feedback,
Ariel

On Wednesday, December 11, 2024 22:57 CET, Ariel Otilibili <ariel.otilibili-anieli@eurecom.fr> wrote:

> Hello,
> 
> This is my first patch to the list; your feedback is much appreciated.
> 
> I have been using GNU/Linux for more than a decade, and discovered eBPF recently.
> 
> Thank you
> 
> Ariel Otilibili (1):
>   selftests/bpf: clear out Python syntax warnings
> 
>  .../selftests/bpf/test_bpftool_synctypes.py   | 28 +++++++++----------
>  1 file changed, 14 insertions(+), 14 deletions(-)
> 
> -- 
> 2.47.1
>


  parent reply	other threads:[~2024-12-17 21:10 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
2024-12-17 21:10 ` Ariel Otilibili-Anieli [this message]
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=2f7a8a-6761e900-9a95-1d1363a0@43143619 \
    --to=ariel.otilibili-anieli@eurecom.fr \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /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