From: patchwork-bot+netdevbpf@kernel.org
To: Kang Minchul <tegongkang@gmail.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, 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 19:50:15 +0000 [thread overview]
Message-ID: <166845541560.2198.17027977446805211141.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221113190648.38556-1-tegongkang@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 14 Nov 2022 04:06:45 +0900 you 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.
>
> [...]
Here is the summary with links:
- [v2,1/3] libbpf: checkpatch: Fixed code alignments in btf.c
https://git.kernel.org/bpf/bpf-next/c/c7694ac340b0
- [v2,2/3] libbpf: Fixed various checkpatch issues in libbpf.c
https://git.kernel.org/bpf/bpf-next/c/e3ba8e4e8c19
- [v2,3/3] libbpf: checkpatch: Fixed code alignments in ringbuf.c
https://git.kernel.org/bpf/bpf-next/c/b486d19a0ab0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-14 19:50 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 ` [PATCH v2 0/3] libbpf: Fixed various checkpatch issues sdf
2022-11-14 19:50 ` patchwork-bot+netdevbpf [this message]
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=166845541560.2198.17027977446805211141.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=sdf@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.