Re: [PATCH bpf-next 2/2] libbpf: use 100-character limit to make bpf_tracing.h easier to read

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH bpf-next 2/2] libbpf: use 100-character limit to make bpf_tracing.h easier to read
From: Yonghong Song <yhs@xxxxxx>
Date: Wed, 22 Dec 2021 16:27:24 -0800
Cc: <kernel-team@xxxxxx>, Kenta Tada <Kenta.Tada@xxxxxxxx>, Hengqi Chen <hengqi.chen@xxxxxxxxx>, Björn Töpel <bjorn@xxxxxxxxxx>, Ilya Leoshkevich <iii@xxxxxxxxxxxxx>
In-reply-to: <20211222213924.1869758-2-andrii@kernel.org>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1



On 12/22/21 1:39 PM, Andrii Nakryiko wrote:

Improve bpf_tracing.h's macro definition readability by keeping them
single-line and better aligned. This makes it easier to follow all those
variadic patterns.

Signed-off-by: Andrii Nakryiko <andrii@xxxxxxxxxx>


Acked-by: Yonghong Song <yhs@xxxxxx>

References:
- [PATCH bpf-next 1/2] libbpf: normalize PT_REGS_xxx() macro definitions
  - From: Andrii Nakryiko
- [PATCH bpf-next 2/2] libbpf: use 100-character limit to make bpf_tracing.h easier to read
  - From: Andrii Nakryiko

Prev by Date: Re: [PATCH bpf-next 1/2] libbpf: normalize PT_REGS_xxx() macro definitions
Next by Date: Re: [PATCH bpf-next v3 3/3] bpftool: Implement btfgen
Previous by thread: [PATCH bpf-next 2/2] libbpf: use 100-character limit to make bpf_tracing.h easier to read
Next by thread: Re: [PATCH bpf-next 1/2] libbpf: normalize PT_REGS_xxx() macro definitions
Index(es):
- Date
- Thread

[Index of Archives] [Linux Samsung SoC] [Linux Rockchip SoC] [Linux Actions SoC] [Linux for Synopsys ARC Processors] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux