Re: [PATCH bpf-next v10 1/9] bpf: Drop duplicate blank lines in verifier

mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed

From: Leon Hwang <leon.hwang@linux.dev>
To: Emil Tsalapatis <emil@etsalapatis.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	Jiri Olsa <jolsa@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	Quentin Monnet <qmo@kernel.org>, Shuah Khan <shuah@kernel.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v10 1/9] bpf: Drop duplicate blank lines in verifier
Date: Tue, 21 Jul 2026 21:48:09 +0800	[thread overview]
Message-ID: <b74c1688-fc14-449d-9ca8-3910361d15e2@linux.dev> (raw)
In-Reply-To: <ae2ceb0f-0b83-4490-9c4c-d070df6fb869@linux.dev>

On 2026/7/17 13:28, Leon Hwang wrote:
> On 17/7/26 13:08, Emil Tsalapatis wrote:
>> On Wed Jul 15, 2026 at 11:32 AM EDT, Leon Hwang wrote:
>>> There are many adjacent blank lines in the verifier that have accumulated
>>> over time.
>>>
>>> Drop them for cleanup.
>>>
>>> No functional changes intended.
>>
>>
>> Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
> 
> Thanks for your review.
> 
>>
>> What about the files we factored out of the verifier? E.g., backtrack.c
>> also has the same issue.
> 
> 
> Probably, I can post a patch to clean all adjacent blank lines in
> kernel/bpf/ when posting another series.


Will drop all adjacent blank lines in kernel/bpf/ in the next revision,
as I'm planning to post the next revision.

Thanks,
Leon

next prev parent reply	other threads:[~2026-07-21 13:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 15:32 [PATCH bpf-next v10 0/9] bpf: Introduce global percpu data Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 1/9] bpf: Drop duplicate blank lines in verifier Leon Hwang
2026-07-17  5:08   ` Emil Tsalapatis
2026-07-17  5:28     ` Leon Hwang
2026-07-21 13:48       ` Leon Hwang [this message]
2026-07-15 15:32 ` [PATCH bpf-next v10 2/9] bpf: Introduce global percpu data Leon Hwang
2026-07-17  6:25   ` Emil Tsalapatis
2026-07-20  4:59     ` Leon Hwang
2026-07-20 22:55       ` Emil Tsalapatis
2026-07-15 15:32 ` [PATCH bpf-next v10 3/9] libbpf: Probe percpu data feature Leon Hwang
2026-07-17 21:52   ` Emil Tsalapatis
2026-07-15 15:32 ` [PATCH bpf-next v10 4/9] libbpf: Add support for global percpu data Leon Hwang
2026-07-17 21:39   ` Emil Tsalapatis
2026-07-20  4:59     ` Leon Hwang
2026-08-03  1:50       ` Leon Hwang
2026-08-04 22:38       ` Andrii Nakryiko
2026-07-15 15:32 ` [PATCH bpf-next v10 5/9] bpftool: Generate skeleton " Leon Hwang
2026-07-17 21:52   ` Emil Tsalapatis
2026-07-20  5:00     ` Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 6/9] selftests/bpf: Add tests to verify " Leon Hwang
2026-07-15 16:11   ` bot+bpf-ci
2026-07-16  5:30     ` Leon Hwang
2026-07-17 22:47   ` Emil Tsalapatis
2026-07-20  5:02     ` Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 7/9] selftests/bpf: Test direct reading/writing read-only percpu_array map Leon Hwang
2026-07-17 22:49   ` Emil Tsalapatis
2026-07-20  5:03     ` Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 8/9] selftests/bpf: Test verifier log for global percpu data Leon Hwang
2026-07-17 22:50   ` Emil Tsalapatis
2026-07-15 15:32 ` [PATCH bpf-next v10 9/9] selftests/bpf: Verify bpf_iter " Leon Hwang
2026-07-17 23:11   ` Emil Tsalapatis

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=b74c1688-fc14-449d-9ca8-3910361d15e2@linux.dev \
    --to=leon.hwang@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-patches-bot@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=qmo@kernel.org \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=yonghong.song@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

all inboxes | Powered by JetHome®