From: Joe Perches <joe@perches.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: arch/mips/mm/tlbex.c:2243:3: warning: unannotated fall-through between switch labels
Date: Tue, 23 Nov 2021 10:21:38 -0800 [thread overview]
Message-ID: <81039009afd63eaac721201a961a4a39c3dd3990.camel@perches.com> (raw)
In-Reply-To: <20211123181648.GA9405@embeddedor>
On Tue, 2021-11-23 at 12:16 -0600, Gustavo A. R. Silva wrote:
> On Tue, Nov 23, 2021 at 09:59:58AM -0800, Joe Perches wrote:
> > On Tue, 2021-11-23 at 11:56 -0600, Gustavo A. R. Silva wrote:
> > > On Tue, Nov 23, 2021 at 09:25:17AM -0800, Joe Perches wrote:
> > > > On Tue, 2021-11-23 at 10:50 -0600, Gustavo A. R. Silva wrote:
> > > > > On Tue, Nov 23, 2021 at 12:52:30AM -0800, Joe Perches wrote:
> > > > > >
> > > > > > Perhaps this would be better:
> > > > >
> > > > > Feel free to send a proper patch.
> > > >
> > > > I commented on your proposed patch.
> > >
> > > And I reply giving you an option if you want to proceed.
> > >
> > > > And I'd prefer you actually look at and improve the code instead
> > > > of merely silencing warnings.
> > >
> > > If this is a matter of preference then I should express my preferences, too.
> > > So, I prefer to give you the opportunity of improving the code and not being
> > > pedantic at the same time. :)
> >
> > It appears to be difficult to give you suggestions on how to improve
> > what you do.
>
> No; that's appreciated.
> What I suggest you to improve is how you communicate it,
:) Thanks. I'll try.
> and to take into account a "Feel free to send a proper patch."
I'm not much for sending actual patches as when I do I get accusations
of being an excessively trivial patch submitter.
And I prefer to communicate in code where feasible rather than
expand all the code into words. But if you prefer:
The indentation used for the fallthrough addition in your patch is
incorrect.
In addition, the brace location in this code is poor.
There is an unnecessary open and close brace around the default case.
Please remove the unnecessary braces and move the default case to the
more typical end-of-block location of the switch statement.
I believe the diff I posted was more efficient than the text above.
cheers, Joe
prev parent reply other threads:[~2021-11-23 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 23:51 kernel test robot
2021-11-23 0:55 ` Gustavo A. R. Silva
2021-11-23 8:52 ` Joe Perches
2021-11-23 16:50 ` Gustavo A. R. Silva
2021-11-23 17:25 ` Joe Perches
2021-11-23 17:56 ` Gustavo A. R. Silva
2021-11-23 17:59 ` Joe Perches
2021-11-23 18:16 ` Gustavo A. R. Silva
2021-11-23 18:21 ` Joe Perches [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=81039009afd63eaac721201a961a4a39c3dd3990.camel@perches.com \
--to=joe@perches.com \
--cc=gustavoars@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.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®