From: Joe Perches <joe@perches.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [Ocfs2-devel] [RFC] treewide: cleanup unreachable breaks
Date: Sun, 18 Oct 2020 12:06:40 -0700 [thread overview]
Message-ID: <18981cad4ac27b4a22b2e38d40bd112432d4a4e7.camel@perches.com> (raw)
In-Reply-To: <20201018185943.GM20115@casper.infradead.org>
On Sun, 2020-10-18 at 19:59 +0100, Matthew Wilcox wrote:
> On Sat, Oct 17, 2020 at 09:09:28AM -0700, trix at redhat.com wrote:
> > clang has a number of useful, new warnings see
> > https://urldefense.com/v3/__https://clang.llvm.org/docs/DiagnosticsReference.html__;!!GqivPVa7Brio!Krxz78O3RKcB9JBMVo_F98FupVhj_jxX60ddN6tKGEbv_cnooXc1nnBmchm-e_O9ieGnyQ$
>
> Please get your IT department to remove that stupidity. If you can't,
> please send email from a non-Red Hat email address.
I didn't get it this way, neither did lore.
It's on your end.
https://lore.kernel.org/lkml/20201017160928.12698-1-trix at redhat.com/
> I don't understand why this is a useful warning to fix.
Precision in coding style intent and code minimization
would be the biggest factors IMO.
> What actual problem is caused by the code below?
Obviously none.
next prev parent reply other threads:[~2020-10-18 19:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 16:09 [Intel-wired-lan] [RFC] treewide: cleanup unreachable breaks trix
2020-10-17 16:24 ` Joe Perches
2020-10-17 18:21 ` [Intel-wired-lan] [Cocci] " Julia Lawall
2020-10-17 19:00 ` Joe Perches
2020-10-17 21:01 ` [Intel-wired-lan] " Dan Williams
2020-10-18 5:43 ` Greg KH
2020-10-18 14:04 ` Tom Rix
2020-10-19 19:42 ` Nick Desaulniers
2020-10-19 23:05 ` Jason Gunthorpe
2020-10-20 14:09 ` Tom Rix
2020-10-20 8:47 ` [Intel-wired-lan] [Ocfs2-devel] " John Haxby
2020-10-20 13:55 ` [Intel-wired-lan] " Tom Rix
2020-10-20 18:42 ` Joe Perches
2020-10-18 9:29 ` Hans de Goede
2020-10-18 18:59 ` [Intel-wired-lan] [Ocfs2-devel] " Matthew Wilcox
2020-10-18 19:06 ` Joe Perches [this message]
2020-10-18 19:13 ` James Bottomley
2020-10-18 19:16 ` Matthew Wilcox
2020-10-18 19:17 ` James Bottomley
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=18981cad4ac27b4a22b2e38d40bd112432d4a4e7.camel@perches.com \
--to=joe@perches.com \
--cc=intel-wired-lan@osuosl.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