All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eugene Korenevsky <ekorenevsky@gmail.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Baolin Wang <baolin.wang@linaro.org>
Subject: Re: [PATCH v6] USB hub_probe: rework ugly goto-into-compound-statement
Date: Mon, 21 Nov 2016 17:33:05 +0100	[thread overview]
Message-ID: <20161121163305.GA32606@kroah.com> (raw)
In-Reply-To: <20161119065545.GA5367@vnote>

On Sat, Nov 19, 2016 at 09:55:45AM +0300, Eugene Korenevsky wrote:
> Rework smelling code (goto inside compound statement). Perhaps this is
> legacy. Anyway such code is not appropriate for Linux kernel.
> 
> Signed-off-by: Eugene Korenevsky <ekorenevsky@gmail.com>
> ---
> Changes in v6: more pedantic conversion from `int` to `bool`; fix comment
> Changes in v5: make `bool` a return type of `hub_check_descriptor_sanity()`
> Changes in v4: fix typo
> Changes in v3: extract the code to static function
> Changes in v2: fix spaces instead of tab, add missing 'Signed-off-by'
> 
>  drivers/usb/core/hub.c | 38 +++++++++++++++++++++-----------------
>  1 file changed, 21 insertions(+), 17 deletions(-)
> 
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> index cbb1467..dbebfe4 100644
> --- a/drivers/usb/core/hub.c
> +++ b/drivers/usb/core/hub.c
> @@ -1722,10 +1722,28 @@ static void hub_disconnect(struct usb_interface *intf)
>  	kref_put(&hub->kref, hub_release);
>  }
>  
> +static bool hub_check_descriptor_sanity(struct usb_host_interface *desc)
> +{
> +	/* Some hubs have a subclass of 1, which AFAICT according to the */
> +	/*  specs is not defined, but it works */
> +	if (desc->desc.bInterfaceSubClass != 0 &&
> +	    desc->desc.bInterfaceSubClass != 1)
> +		return false;
> +
> +	/* Multiple endpoints? What kind of mutant ninja-hub is this? */
> +	if (desc->desc.bNumEndpoints != 1)
> +		return false;
> +
> +	/* If the first endpoint is not interrupt IN, we'd better punt! */
> +	if (!usb_endpoint_is_int_in(&desc->endpoint[0].desc))
> +		return false;
> +
> +        return true;
> +}
> +
>  static int hub_probe(struct usb_interface *intf, const struct usb_device_id *id)
>  {
>  	struct usb_host_interface *desc;
> -	struct usb_endpoint_descriptor *endpoint;
>  	struct usb_device *hdev;
>  	struct usb_hub *hub;
>  
> @@ -1800,25 +1818,11 @@ static int hub_probe(struct usb_interface *intf, const struct usb_device_id *id)
>  	}
>  #endif
>  
> -	/* Some hubs have a subclass of 1, which AFAICT according to the */
> -	/*  specs is not defined, but it works */
> -	if ((desc->desc.bInterfaceSubClass != 0) &&
> -	    (desc->desc.bInterfaceSubClass != 1)) {
> -descriptor_error:
> +	if (!hub_check_descriptor_sanity(desc)) {

Read that line out loud please, and tell me it makes sense:
	If not hub_check_descriptor_sanity().

Doesn't:
	If not hub_descriptor_is_sane()
make more sense?

thanks,

greg k-h

      reply	other threads:[~2016-11-21 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19  6:55 [PATCH v6] USB hub_probe: rework ugly goto-into-compound-statement Eugene Korenevsky
2016-11-21 16:33 ` Greg Kroah-Hartman [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=20161121163305.GA32606@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=baolin.wang@linaro.org \
    --cc=ekorenevsky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.