From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] usb: Use well-known descriptor sizes when parsing configuration
Date: Fri, 19 Jul 2013 23:06:57 +0200 [thread overview]
Message-ID: <20130719230657.246af302@lilith> (raw)
In-Reply-To: <1374264728-27496-1-git-send-email-jwerner@chromium.org>
Hi Julius,
On Fri, 19 Jul 2013 13:12:08 -0700, Julius Werner
<jwerner@chromium.org> wrote:
> The existing USB configuration parsing code relies on the descriptors'
> own length values when reading through the configuration blob. Since the
> size of those descriptors is always well-defined, we should rather use
> the known sizes instead of trusting device-provided values to be
> correct. Also adds some safety to potential out-of-order descriptors.
>
> Change-Id: I16f69dfdd6793aa0fe930b5148d4521f3e5c3090
> Signed-off-by: Julius Werner <jwerner@chromium.org>
> ---
> common/usb.c | 87 [...]
As I had already asked for V2, please insert patch history right after
commit message delimiter '---'.
Amicalement,
--
Albert.
prev parent reply other threads:[~2013-07-19 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 20:12 [U-Boot] [PATCH v3] usb: Use well-known descriptor sizes when parsing configuration Julius Werner
2013-07-19 21:06 ` Albert ARIBAUD [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=20130719230657.246af302@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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