From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jim Lin <jilin@nvidia.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [1/6] usb: hub:Extend usb_hub_clear_tt_buffer parameter
Date: Sat, 27 Apr 2019 08:58:23 +0200 [thread overview]
Message-ID: <20190427065823.GC28250@kroah.com> (raw)
On Fri, Apr 26, 2019 at 10:50:06PM +0800, Jim Lin wrote:
> Extend usb_hub_clear_tt_buffer parameter to specify device number
> that will have the TT state of its hub cleared.
>
> Signed-off-by: Jim Lin <jilin@nvidia.com>
> ---
> drivers/usb/core/hub.c | 5 +++--
> include/linux/usb/hcd.h | 2 +-
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> index 15a2934dc29d..4dec054c9776 100644
> --- a/drivers/usb/core/hub.c
> +++ b/drivers/usb/core/hub.c
> @@ -840,6 +840,7 @@ int usb_hub_set_port_power(struct usb_device *hdev, struct usb_hub *hub,
> /**
> * usb_hub_clear_tt_buffer - clear control/bulk TT state in high speed hub
> * @urb: an URB associated with the failed or incomplete split transaction
> + * @devnum : device number that will have the TT state of its hub cleared
> *
> * High speed HCDs use this to tell the hub driver that some split control or
> * bulk transaction failed in a way that requires clearing internal state of
> @@ -851,7 +852,7 @@ int usb_hub_set_port_power(struct usb_device *hdev, struct usb_hub *hub,
> *
> * Return: 0 if successful. A negative error code otherwise.
> */
> -int usb_hub_clear_tt_buffer(struct urb *urb)
> +int usb_hub_clear_tt_buffer(struct urb *urb, int devnum)
> {
> struct usb_device *udev = urb->dev;
> int pipe = urb->pipe;
> @@ -873,7 +874,7 @@ int usb_hub_clear_tt_buffer(struct urb *urb)
> /* info that CLEAR_TT_BUFFER needs */
> clear->tt = tt->multi ? udev->ttport : 1;
> clear->devinfo = usb_pipeendpoint (pipe);
> - clear->devinfo |= udev->devnum << 4;
> + clear->devinfo |= devnum << 4;
> clear->devinfo |= usb_pipecontrol(pipe)
> ? (USB_ENDPOINT_XFER_CONTROL << 11)
> : (USB_ENDPOINT_XFER_BULK << 11);
> diff --git a/include/linux/usb/hcd.h b/include/linux/usb/hcd.h
> index 695931b03684..01720f1f7d62 100644
> --- a/include/linux/usb/hcd.h
> +++ b/include/linux/usb/hcd.h
> @@ -559,7 +559,7 @@ struct usb_tt_clear {
> struct usb_host_endpoint *ep;
> };
>
> -extern int usb_hub_clear_tt_buffer(struct urb *urb);
> +extern int usb_hub_clear_tt_buffer(struct urb *urb, int devnum);
> extern void usb_ep0_reinit(struct usb_device *);
>
> /* (shifted) direction/type/recipient from the USB 2.0 spec, table 9.2 */
> --
> 2.1.4
You just broke the build with this patch. No individual patch can ever
do that, they all have to be stand-alone.
Also, when you send a patch series, please make it such that they are
"linked" together. git send-email does this automatically, I don't know
how you sent these, but it did not work that way :(
Also, always use scripts/get_maintainer.pl to determine who to send the
patches to. You missed all of the maintainers and developers who need
to review your patches :(
sorry,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Jim Lin <jilin@nvidia.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] usb: hub:Extend usb_hub_clear_tt_buffer parameter
Date: Sat, 27 Apr 2019 08:58:23 +0200 [thread overview]
Message-ID: <20190427065823.GC28250@kroah.com> (raw)
Message-ID: <20190427065823.3eJ_uMp-dkJvAdYDQS5AhLRHPanuNDzUVU8xG-cXIz4@z> (raw)
In-Reply-To: <1556290206-9393-1-git-send-email-jilin@nvidia.com>
On Fri, Apr 26, 2019 at 10:50:06PM +0800, Jim Lin wrote:
> Extend usb_hub_clear_tt_buffer parameter to specify device number
> that will have the TT state of its hub cleared.
>
> Signed-off-by: Jim Lin <jilin@nvidia.com>
> ---
> drivers/usb/core/hub.c | 5 +++--
> include/linux/usb/hcd.h | 2 +-
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
> index 15a2934dc29d..4dec054c9776 100644
> --- a/drivers/usb/core/hub.c
> +++ b/drivers/usb/core/hub.c
> @@ -840,6 +840,7 @@ int usb_hub_set_port_power(struct usb_device *hdev, struct usb_hub *hub,
> /**
> * usb_hub_clear_tt_buffer - clear control/bulk TT state in high speed hub
> * @urb: an URB associated with the failed or incomplete split transaction
> + * @devnum : device number that will have the TT state of its hub cleared
> *
> * High speed HCDs use this to tell the hub driver that some split control or
> * bulk transaction failed in a way that requires clearing internal state of
> @@ -851,7 +852,7 @@ int usb_hub_set_port_power(struct usb_device *hdev, struct usb_hub *hub,
> *
> * Return: 0 if successful. A negative error code otherwise.
> */
> -int usb_hub_clear_tt_buffer(struct urb *urb)
> +int usb_hub_clear_tt_buffer(struct urb *urb, int devnum)
> {
> struct usb_device *udev = urb->dev;
> int pipe = urb->pipe;
> @@ -873,7 +874,7 @@ int usb_hub_clear_tt_buffer(struct urb *urb)
> /* info that CLEAR_TT_BUFFER needs */
> clear->tt = tt->multi ? udev->ttport : 1;
> clear->devinfo = usb_pipeendpoint (pipe);
> - clear->devinfo |= udev->devnum << 4;
> + clear->devinfo |= devnum << 4;
> clear->devinfo |= usb_pipecontrol(pipe)
> ? (USB_ENDPOINT_XFER_CONTROL << 11)
> : (USB_ENDPOINT_XFER_BULK << 11);
> diff --git a/include/linux/usb/hcd.h b/include/linux/usb/hcd.h
> index 695931b03684..01720f1f7d62 100644
> --- a/include/linux/usb/hcd.h
> +++ b/include/linux/usb/hcd.h
> @@ -559,7 +559,7 @@ struct usb_tt_clear {
> struct usb_host_endpoint *ep;
> };
>
> -extern int usb_hub_clear_tt_buffer(struct urb *urb);
> +extern int usb_hub_clear_tt_buffer(struct urb *urb, int devnum);
> extern void usb_ep0_reinit(struct usb_device *);
>
> /* (shifted) direction/type/recipient from the USB 2.0 spec, table 9.2 */
> --
> 2.1.4
You just broke the build with this patch. No individual patch can ever
do that, they all have to be stand-alone.
Also, when you send a patch series, please make it such that they are
"linked" together. git send-email does this automatically, I don't know
how you sent these, but it did not work that way :(
Also, always use scripts/get_maintainer.pl to determine who to send the
patches to. You missed all of the maintainers and developers who need
to review your patches :(
sorry,
greg k-h
next prev reply other threads:[~2019-04-27 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 14:50 [1/6] usb: hub:Extend usb_hub_clear_tt_buffer parameter Jim Lin
2019-04-26 14:50 ` [PATCH 1/6] " Jim Lin
2019-04-27 6:58 ` Greg Kroah-Hartman [this message]
2019-04-27 6:58 ` Greg KH
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=20190427065823.GC28250@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jilin@nvidia.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;
as well as URLs for NNTP newsgroup(s).