From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: 'Sebastian Andrzej Siewior' <bigeasy@linutronix.de>
Cc: gregkh@suse.de, linux-arm-msm@vger.kernel.org, balbi@ti.com,
ablay@codeaurora.org,
"'open list:USB GADGET/PERIPH...'" <linux-usb@vger.kernel.org>,
'open list' <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH/RESEND 3/5 v4] usb: Configure endpoint according to gadget speed.
Date: Wed, 13 Apr 2011 12:56:27 +0300 [thread overview]
Message-ID: <001701cbf9c1$11875fc0$34961f40$@org> (raw)
In-Reply-To: <20110411141404.GC4018@linutronix.de>
> >+ /* find descriptors */
> >+ for (d_spd = next_ep_desc(speed_desc); d_spd;
> >+ d_spd = next_ep_desc(d_spd+1)) {
>
> this might look better if you would something like the list_for_each()
> macro.
The function next_ep_desc() goes over the endpoint descriptors (struct
usb_descriptor_header). It's not a list so I don't see how the
list_for_each() macro can be used here. Am I missing something?
> > /**
> >+ * config_ep_by_speed() - configures the given endpoint
> >+ * according to gadget speed.
> >+ * @g: pointer to the gadget
> >+ * @f: usb function
> >+ * @_ep: the endpoint to configure
> >+ *
> >+ * Return: error code, 0 on success
> >+ *
> >+ * This function chooses the right descriptors for a given
> >+ * endpoint according to gadget speed and saves in in the
> >+ * endpoint desc field. If the endpoint already has a descriptor
> >+ * assigned to it - overwrites it with currently corresponding
> >+ * descriptor. The endpoint maxpacket field is updated according
> >+ * to the choosen descriptor.
> >+ * Note: the supplied function should hold all the descriptors
> >+ * for supported speeds
> >+ */
>
> You have the same comment (including the same typo) here and in the .c.
> Please use only on (in the .c file) as they will go async.
Thanks for noticing that!
What do you mean by "they will go async"? Is there some sort of automation
that updates the comments for functions from c files to the headers? I'm not
familiar with such...
Best regards,
Tanya Brokhman
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-04-13 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 8:04 [PATCH/RESEND 3/5 v4] usb: Configure endpoint according to gadget speed Tatyana Brokhman
2011-04-11 14:14 ` Sebastian Andrzej Siewior
2011-04-13 9:56 ` Tanya Brokhman [this message]
2011-04-13 10:05 ` Michal Nazarewicz
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='001701cbf9c1$11875fc0$34961f40$@org' \
--to=tlinder@codeaurora.org \
--cc=ablay@codeaurora.org \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@suse.de \
--cc=linux-arm-msm@vger.kernel.org \
--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).