From: Greg KH <gregkh@linuxfoundation.org>
To: 冷静 <3090101217@zju.edu.cn>
Cc: balbi@kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, pavel.hofman@ivitera.com,
ruslan.bilovol@gmail.com, Jing Leng <jleng@ambarella.com>
Subject: Re: [PATCH v3] usb: gadget: f_uac1: add different speed transfers support
Date: Wed, 16 Feb 2022 11:38:30 +0100 [thread overview]
Message-ID: <YgzUJhcFk1FAKfJV@kroah.com> (raw)
In-Reply-To: <13396706.ae161.17f005864cf.Coremail.3090101217@zju.edu.cn>
On Wed, Feb 16, 2022 at 10:24:27AM +0800, 冷静 wrote:
> Hi Greg KH,
>
> Sorry for the trouble, as a new contributor to kernel.
> Although I have readed the document that how to submit patches,
> I'm still missing some details.
>
> > Where is the patch version information?
> The new patch adds more detailed patch description and adds
> 'static' before 'struct usb_ss_ep_comp_descriptor ac_int_ep_desc_comp'.
As the documentation states, that goes below the --- line.
Please look at the hundreds of examples of other patch series being sent
with new versions. And again, the documentation should show you how to
do this.
> > Why are you setting values to 0 when you do not have to as that is the
> > default value?
> This modification is similar to uac2.
> On page 362 of the USB3.2 specification.
> bMaxBurst is 0 means that no burst transfer.
> bmAttributes is 0 means that no mult.
That is not what I was referring to. If you do not set a field in a
static structure, it is by default set to 0. You do not have to define
it again.
thanks,
greg k-h
next prev parent reply other threads:[~2022-02-16 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 7:43 [PATCH] usb: gadget: f_uac1: add superspeed transfer support 3090101217
2022-02-14 10:38 ` Greg KH
2022-02-14 14:05 ` [PATCH v2] usb: gadget: f_uac1: add different speed transfers support 3090101217
2022-02-14 14:48 ` Greg KH
2022-02-15 3:08 ` [PATCH v3] " 3090101217
2022-02-15 14:08 ` Greg KH
2022-02-16 2:24 ` 冷静
2022-02-16 10:38 ` Greg KH [this message]
2022-02-17 5:10 ` Jing Leng
2022-02-17 5:19 ` [PATCH v4] " 3090101217
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=YgzUJhcFk1FAKfJV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=3090101217@zju.edu.cn \
--cc=balbi@kernel.org \
--cc=jleng@ambarella.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pavel.hofman@ivitera.com \
--cc=ruslan.bilovol@gmail.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