mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Kees Cook <keescook@chromium.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Wimplicit-fallthrough patches for 5.3-rc1
Date: Sun, 21 Jul 2019 16:13:32 -0500	[thread overview]
Message-ID: <52f02f6a-ca0f-261c-a1c1-716cb0d9adf2@embeddedor.com> (raw)
In-Reply-To: <858bd3e0-ffc5-07e1-d1d9-37c3d2a1d595@embeddedor.com>

Hi Linus,

I noticed you didn't merge these changes in v5.3-rc1.

Should I send them again for rc2?

Do you have any comments on this pull-request?

Thanks
--
Gustavo

On 7/18/19 3:28 PM, Gustavo A. R. Silva wrote:
> 
> 
> On 7/10/19 4:36 PM, Stephen Rothwell wrote:
>> Hi Gustavo,
>>
>> On Wed, 10 Jul 2019 13:14:10 -0500 "Gustavo A. R. Silva" <gustavo@embeddedor.com> wrote:
>>>
>>> At some point during this development cycle, we reached the quota of zero
>>> fall-through warnings, but people continued introducing such warnings. So,
>>> it seems we are now pretty much ready for enabling -Wimplicit-fallthrough
>>> globally. Before it turns into a never ending story. :)
>>
>> Sounds good to me.  My mail was, I guess, just a heads up to Linus that
>> he will see some new warnings in his test build if he merges your
>> tree.  Thanks for addressing them.
>>
> Yep. Thanks, Stephen.
> 
> Linus:
> 
> After you have merged all the trees containing fall-through patches, you might
> see the following warnings:
> 
> arch/x86/events/intel/core.c:4957:8: warning: this statement may fall through [-Wimplicit-fallthrough=]
> arch/x86/events/intel/core.c:5006:8: warning: this statement may fall through [-Wimplicit-fallthrough=]
> drivers/mtd/nand/onenand/onenand_base.c:3261:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
> 
> for which I already have patches ready to be applied, but I didn't include them
> in my pull-request because such patches don't apply to 5.2-rc2, on which I based
> my -next tree for v5.3.
> 
> We can coordinate and I can send you the patches that address those and any other
> warning that you might see after merging my pull-request and just before you release
> 5.3-rc1. So we can have the -Wimplicit-fallthrough option globally enabled in
> 5.3-rc1 and zero fall-through warnings.
> 
> What do you think?
> 
> Thanks
> --
> Gustavo
> 

      reply	other threads:[~2019-07-21 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 18:20 Gustavo A. R. Silva
2019-07-10  4:15 ` Stephen Rothwell
2019-07-10 18:14   ` Gustavo A. R. Silva
2019-07-10 21:36     ` Stephen Rothwell
2019-07-18 20:28       ` Gustavo A. R. Silva
2019-07-21 21:13         ` Gustavo A. R. Silva [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=52f02f6a-ca0f-261c-a1c1-716cb0d9adf2@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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

all inboxes | Powered by JetHome®