From: Greg KH <gregkh@linuxfoundation.org>
To: William Wu <william.wu@rock-chips.com>
Cc: stern@rowland.harvard.edu, Chris.Wulff@biamp.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
frank.wang@rock-chips.com, jianwei.zheng@rock-chips.com,
yue.long@rock-chips.com
Subject: Re: [PATCH v2] usb: gadget: f_hid: Fix zero length packet transfer
Date: Mon, 25 Aug 2025 09:09:37 +0200 [thread overview]
Message-ID: <2025082512-flatfoot-verbose-3cd5@gregkh> (raw)
In-Reply-To: <1756095266-5736-1-git-send-email-william.wu@rock-chips.com>
On Mon, Aug 25, 2025 at 12:14:26PM +0800, William Wu wrote:
> Set the hid req->zero flag of ep0/in_ep to true by default,
> then the UDC drivers can transfer a zero length packet at
> the end if the hid transfer with size divisible to EPs max
> packet size according to the USB 2.0 spec.
>
> Signed-off-by: William Wu <william.wu@rock-chips.com>
> ---
> drivers/usb/gadget/function/f_hid.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/gadget/function/f_hid.c b/drivers/usb/gadget/function/f_hid.c
> index 8e1d1e8..307ea56 100644
> --- a/drivers/usb/gadget/function/f_hid.c
> +++ b/drivers/usb/gadget/function/f_hid.c
> @@ -511,7 +511,7 @@ static ssize_t f_hidg_write(struct file *file, const char __user *buffer,
> }
>
> req->status = 0;
> - req->zero = 0;
> + req->zero = 1;
> req->length = count;
> req->complete = f_hidg_req_complete;
> req->context = hidg;
> @@ -967,7 +967,7 @@ static int hidg_setup(struct usb_function *f,
> return -EOPNOTSUPP;
>
> respond:
> - req->zero = 0;
> + req->zero = 1;
> req->length = length;
> status = usb_ep_queue(cdev->gadget->ep0, req, GFP_ATOMIC);
> if (status < 0)
> --
> 2.0.0
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2025-08-25 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 4:14 [PATCH v2] usb: gadget: f_hid: Fix zero length packet transfer William Wu
2025-08-25 7:09 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-26 10:28 William Wu
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=2025082512-flatfoot-verbose-3cd5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Chris.Wulff@biamp.com \
--cc=frank.wang@rock-chips.com \
--cc=jianwei.zheng@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=william.wu@rock-chips.com \
--cc=yue.long@rock-chips.com \
/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