From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/9] usb: host: isp1362-hcd: mark expected switch fall-through
Date: Wed, 1 Nov 2017 18:38:51 +0100 [thread overview]
Message-ID: <20171101173851.GA23225@kroah.com> (raw)
In-Reply-To: <20171101122740.Horde._xxQDVAhVsVPYpvze4g7UsU@gator4166.hostgator.com>
On Wed, Nov 01, 2017 at 12:27:40PM -0500, Gustavo A. R. Silva wrote:
>
> Quoting Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
>
> > On Wed, Oct 25, 2017 at 02:05:05PM -0500, Gustavo A. R. Silva wrote:
> > > Greg,
> > >
> > > Quoting "Gustavo A. R. Silva" <garsilva@embeddedor.com>:
> > >
> > > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> > > > where we are expecting to fall through.
> > > >
> > > > Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
> > > > ---
> > > > drivers/usb/host/isp1362-hcd.c | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/drivers/usb/host/isp1362-hcd.c
> > > b/drivers/usb/host/isp1362-hcd.c
> > > > index 9b7e307..753d576 100644
> > > > --- a/drivers/usb/host/isp1362-hcd.c
> > > > +++ b/drivers/usb/host/isp1362-hcd.c
> > > > @@ -1578,6 +1578,7 @@ static int isp1362_hub_control(struct usb_hcd
> > > > *hcd, u16 typeReq, u16 wValue,
> > > > spin_lock_irqsave(&isp1362_hcd->lock, flags);
> > > > isp1362_write_reg32(isp1362_hcd, HCRHSTATUS, RH_HS_OCIC);
> > > > spin_unlock_irqrestore(&isp1362_hcd->lock, flags);
> > > > + /* fall through */
> > >
> > > I'm suspicious this should be a 'break' instead.
> > >
> > > What do you think?
> >
> > Yeah, this should be a 'break', care to make that patch up instead?
> >
>
> Sure thing.
>
> Just some questions about the process to follow:
>
> Should I send a v2 replying to this particular thread only? like [PATCH v2
> 6/9]
> or should I send just a new patch separated from this patch series? I guess
> this is the case.
Brand new patch is fine, this is gone from my patch queue.
> Some maintainers have told me that in cases where a particular patch in the
> series needs an update, the complete patchset should be sent again.
> But I think that depends on the functional impact the patch has over
> the whole patchset.
Yes, it all depends, the rest of these patches are already in my tree.
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-01 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 18:48 [PATCH 0/9] mark expected switch fall-throughs Gustavo A. R. Silva
2017-10-25 18:48 ` [PATCH 1/9] usb: host: fotg210-hcd: mark expected switch fall-through Gustavo A. R. Silva
2017-10-25 18:49 ` [PATCH 2/9] usb: host: xhci: " Gustavo A. R. Silva
2017-10-25 18:49 ` [PATCH 3/9] usb: host: xhci-mem: " Gustavo A. R. Silva
2017-10-25 18:49 ` [PATCH 4/9] usb: host: ohci-hcd: " Gustavo A. R. Silva
2017-10-25 18:49 ` [PATCH 5/9] usb: host: ehci-hcd: " Gustavo A. R. Silva
2017-10-25 18:49 ` [PATCH 6/9] usb: host: isp1362-hcd: " Gustavo A. R. Silva
2017-10-25 19:05 ` Gustavo A. R. Silva
2017-11-01 16:01 ` Greg Kroah-Hartman
2017-11-01 17:27 ` Gustavo A. R. Silva
2017-11-01 17:38 ` Greg Kroah-Hartman [this message]
2017-11-01 17:41 ` Gustavo A. R. Silva
2017-10-25 18:49 ` [PATCH 7/9] usb: host: oxu210hp-hcd: " Gustavo A. R. Silva
2017-10-25 18:49 ` [PATCH 8/9] usb: host: xhci-hub: " Gustavo A. R. Silva
2017-10-25 18:49 ` [PATCH 9/9] usb: host: pci-quirks: " Gustavo A. R. Silva
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=20171101173851.GA23225@kroah.com \
--to=gregkh@linuxfoundation.org \
--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