mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Shawn Landden <shawn@git.icu>, linux-kernel@vger.kernel.org
Cc: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
	Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] Use fall-through attribute rather than magic comments
Date: Sat, 16 Mar 2019 16:42:27 -0500	[thread overview]
Message-ID: <919be4e2-a0a5-abaa-fd7c-abed244a7393@embeddedor.com> (raw)
In-Reply-To: <20190316033841.7659-1-shawn@git.icu>

Shawn,

On 3/15/19 10:38 PM, Shawn Landden wrote:
> The -Wimplicit-fallthrough warning recognizes magic comments
> https://developers.redhat.com/blog/2017/03/10/wimplicit-fallthrough-in-gcc-7/
> It is my opinion that magic comments are a bad idea. Comments should not
> change the interpretation (even regarding errors) of C code.
> (It also happens to break distcc as distcc compiles pre-processed .i files.)
> 

This is not the first time we discuss this topic. Please, read the archive.

We are going to complete the ongoing work first and, after that, I personally
will consider applying this kind of tree-wide change, or any other that may
serve to the same purpose, to my tree.  At this moment this change will only
create confusion and potentially bring a halt to the main idea behind all this,
which is to enable -Wimplicit-fallthrough.  There are only ~100 of these warnings
left in linux-next.

Having said that, please, cultivate the practice of showing every code you touch
to a compiler first before proposing any patches. Otherwise, your opinions and
ideas won't be that popular.

Also, if your intention was to do a tree-wide change to replace all the existing
fall-through comments, you failed to take into account all the info contained
in the article you mention, which by the way is incomplete.

Thanks
--
Gustavo

  parent reply	other threads:[~2019-03-16 21:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16  3:38 Shawn Landden
2019-03-16  8:08 ` Joe Perches
2019-03-16 21:42 ` Gustavo A. R. Silva [this message]
2019-03-18 12:22 ` kbuild test robot
2019-03-18 12:30 ` kbuild test robot
2019-03-19 10:34 ` kbuild test robot
2019-03-19 10:34 ` [PATCH] fix semicolon.cocci warnings kbuild test robot
2019-06-17 15:56 ` [PATCH] Use fall-through attribute rather than magic comments Pavel Machek
2019-06-17 16:25   ` Joe Perches
2019-06-17 16:41     ` David Laight
2019-06-18  7:34     ` Pavel Machek
2019-06-18  9:30       ` Joe Perches
2019-06-18 10:45         ` Pavel Machek

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=919be4e2-a0a5-abaa-fd7c-abed244a7393@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn@git.icu \
    /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

all inboxes | Powered by JetHome®