public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bin Liu <b-liu@ti.com>,
	"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: musb_core: mark expected switch fall-through
Date: Mon, 30 Oct 2017 09:51:18 +0100	[thread overview]
Message-ID: <20171030085118.GA28997@kroah.com> (raw)
In-Reply-To: <20171027165614.GB65@LTA0271908.dhcp.ti.com>

On Fri, Oct 27, 2017 at 11:56:14AM -0500, Bin Liu wrote:
> On Fri, Oct 27, 2017 at 06:49:49PM +0200, Greg Kroah-Hartman wrote:
> > On Fri, Oct 27, 2017 at 11:44:47AM -0500, Bin Liu wrote:
> > > Hi,
> > > 
> > > On Mon, Oct 23, 2017 at 10:10:43PM -0500, Gustavo A. R. Silva wrote:
> > > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> > > > where we are expecting to fall through.
> > > > 
> > > > Addresses-Coverity-ID: 1397608
> > > > Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
> > > 
> > > Applied with the above Coverity-ID message removed.
> > 
> > Why?  It's good to track these things.
> 
> hmm, I thought we don't want non-kernel related information in the commit
> message.

This is kernel-related information.

We don't want foolish "Id:" lines, from gerrit instances, as they are no
help at all because we can not do anything with them.

We _do_ want identifiers that are globally unique that provide real
information, like public bugzilla ids, and tools like coverity.  So for
things like this, always keep them on.

I've added it back by hand now.

thanks,

greg k-h

  reply	other threads:[~2017-10-30  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24  3:10 [PATCH] usb: musb_core: mark expected switch fall-through Gustavo A. R. Silva
2017-10-27 16:44 ` Bin Liu
2017-10-27 16:49   ` Greg Kroah-Hartman
2017-10-27 16:56     ` Bin Liu
2017-10-30  8:51       ` Greg Kroah-Hartman [this message]
2017-10-30 13:18         ` Bin Liu

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=20171030085118.GA28997@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=b-liu@ti.com \
    --cc=garsilva@embeddedor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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