From: Jens Axboe <axboe@kernel.dk>
To: Joe Perches <joe@perches.com>,
Daniel Thompson <daniel.thompson@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-pm@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-security-module@vger.kernel.org, linux-audit@redhat.com,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [Kgdb-bugreport] [PATCH] kernel: convert switch/case fallthrough comments to fallthrough;
Date: Wed, 23 Oct 2019 21:39:01 -0600 [thread overview]
Message-ID: <2808c960-6178-17b8-23d7-a6945987a658@kernel.dk> (raw)
In-Reply-To: <bff0a1c4fc69b83c763ffbce42a0152e1573499a.camel@perches.com>
On 10/23/19 12:49 PM, Joe Perches wrote:
> On Mon, 2019-10-21 at 10:09 +0100, Daniel Thompson wrote:
>> On Fri, Oct 18, 2019 at 09:35:08AM -0700, Joe Perches wrote:
>>> Use the new pseudo keyword "fallthrough;" and not the
>>> various /* fallthrough */ style comments.
>>>
>>> Signed-off-by: Joe Perches <joe@perches.com>
>>> ---
>>>
>>> This is a single patch for the kernel/ source tree,
>>> which would otherwise be sent through as separate
>>> patches to 19 maintainer sections.
>>
>> For the kernel/debug/ files:
>>
>> Acked-by: Daniel Thompson <daniel.thompson@linaro.org>
>>
>> Will you be putting this in an immutable branch once you've collected
>> enough acks?
>
> No, I expect Linus will either run the script
> or apply this patch one day.
Please coordinate and get something like this run/applied a few days
before -rc1 to cause the least amount of needless merge issues.
--
Jens Axboe
prev parent reply other threads:[~2019-10-24 3:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 16:35 [PATCH] kernel: convert switch/case fallthrough comments to fallthrough; Joe Perches
2019-10-21 9:09 ` [Kgdb-bugreport] " Daniel Thompson
2019-10-23 18:49 ` Joe Perches
2019-10-24 3:39 ` Jens Axboe [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=2808c960-6178-17b8-23d7-a6945987a658@kernel.dk \
--to=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=joe@perches.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-audit@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).