From: Artem Savkov <asavkov@redhat.com>
To: Ruan Jinjie <ruanjinjie@huawei.com>
Cc: Ast@kernel.org, Daniel@iogearbox.net, Andrii@kernel.org,
Martin.lau@linux.dev, Song@kernel.org, Yonghong.song@linux.dev,
John.fastabend@gmail.com, Kpsingh@kernel.org, Sdf@google.com,
Haoluo@google.com, Jolsa@kernel.org, Mykolal@fb.com,
Shuah@kernel.org, Benjamin.tissoires@redhat.com,
Memxor@gmail.com, Iii@linux.ibm.com, Colin.i.king@gmail.com,
Awkrail01@gmail.com, Rdunlap@infradead.org,
Joannelkoong@gmail.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH -next v2] selftests/bpf: replace fall through comment by fallthrough pseudo-keyword
Date: Tue, 1 Aug 2023 09:47:35 +0200 [thread overview]
Message-ID: <20230801074735.GA571679@alecto.usersys.redhat.com> (raw)
In-Reply-To: <20230801065447.3609130-1-ruanjinjie@huawei.com>
Hi,
On Tue, Aug 01, 2023 at 02:54:47PM +0800, Ruan Jinjie wrote:
> Replace the existing /* fall through */ comments with the
> new pseudo-keyword macro fallthrough[1].
>
> [1] https://www.kernel.org/doc/html/v5.7/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through
>
> Signed-off-by: Ruan Jinjie <ruanjinjie@huawei.com>
> ---
> v2:
> - Update the subject and commit message.
I think what Alexei meant was subject-prefix which needs to be
'PATCH bpf-next'. You can read more about patch submission rules
in Documentation/bpf/bpf_devel_QA.rst.
--
Artem
next prev parent reply other threads:[~2023-08-01 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 6:54 [PATCH -next v2] selftests/bpf: replace fall through comment by fallthrough pseudo-keyword Ruan Jinjie
2023-08-01 7:38 ` Hou Tao
2023-08-01 8:17 ` Ruan Jinjie
2023-08-01 7:47 ` Artem Savkov [this message]
2023-08-01 8:17 ` Ruan Jinjie
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=20230801074735.GA571679@alecto.usersys.redhat.com \
--to=asavkov@redhat.com \
--cc=Andrii@kernel.org \
--cc=Ast@kernel.org \
--cc=Awkrail01@gmail.com \
--cc=Benjamin.tissoires@redhat.com \
--cc=Colin.i.king@gmail.com \
--cc=Daniel@iogearbox.net \
--cc=Haoluo@google.com \
--cc=Iii@linux.ibm.com \
--cc=Joannelkoong@gmail.com \
--cc=John.fastabend@gmail.com \
--cc=Jolsa@kernel.org \
--cc=Kpsingh@kernel.org \
--cc=Martin.lau@linux.dev \
--cc=Memxor@gmail.com \
--cc=Mykolal@fb.com \
--cc=Rdunlap@infradead.org \
--cc=Sdf@google.com \
--cc=Shuah@kernel.org \
--cc=Song@kernel.org \
--cc=Yonghong.song@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ruanjinjie@huawei.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