From: sdf@google.com
To: Kang Minchul <tegongkang@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] libbpf: Fixed various checkpatch issues
Date: Mon, 14 Nov 2022 09:19:00 -0800 [thread overview]
Message-ID: <Y3J4hJFl2pZacGCb@google.com> (raw)
In-Reply-To: <20221113190648.38556-1-tegongkang@gmail.com>
On 11/14, Kang Minchul wrote:
> This patch series contains various checkpatch fixes
> in btf.c, libbpf.c, ringbuf.c.
> I know these are trivial but some issues are hard to ignore
> and I think these checkpatch issues are accumulating.
> v1 -> v2: changed cover letter message.
> Kang Minchul (3):
> libbpf: checkpatch: Fixed code alignments in btf.c
> libbpf: Fixed various checkpatch issues in libbpf.c
> libbpf: checkpatch: Fixed code alignments in ringbuf.c
Acked-by: Stanislav Fomichev <sdf@google.com>
> tools/lib/bpf/btf.c | 5 +++--
> tools/lib/bpf/libbpf.c | 45 +++++++++++++++++++++++++----------------
> tools/lib/bpf/ringbuf.c | 4 ++--
> 3 files changed, 33 insertions(+), 21 deletions(-)
> --
> 2.34.1
next prev parent reply other threads:[~2022-11-14 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 19:06 [PATCH v2 0/3] libbpf: Fixed various checkpatch issues Kang Minchul
2022-11-13 19:06 ` [PATCH v2 1/3] libbpf: checkpatch: Fixed code alignments in btf.c Kang Minchul
2022-11-13 19:06 ` [PATCH v2 2/3] libbpf: Fixed various checkpatch issues in libbpf.c Kang Minchul
2022-11-13 19:06 ` [PATCH v2 3/3] libbpf: checkpatch: Fixed code alignments in ringbuf.c Kang Minchul
2022-11-14 17:19 ` sdf [this message]
2022-11-14 19:50 ` [PATCH v2 0/3] libbpf: Fixed various checkpatch issues 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=Y3J4hJFl2pZacGCb@google.com \
--to=sdf@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
--cc=tegongkang@gmail.com \
--cc=yhs@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