From: Michal Nazarewicz <mina86@mina86.com>
To: balbi@ti.com, mgautam@codeaurora.org, andrzej.p@samsung.com
Cc: jin.can.zhuang@intel.com, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org, david.a.cohen@intel.com,
hang.yuan@intel.com
Subject: Re: [PATCH] usb: gadget: f_fs: add usb_functionfs_descs_head_v2
Date: Tue, 02 Sep 2014 14:45:44 +0200 [thread overview]
Message-ID: <xa1twq9mry13.fsf@mina86.com> (raw)
In-Reply-To: <20140902065836.GA23094@intel.com>
On Tue, Sep 02 2014, Zhuang Jin Can <jin.can.zhuang@intel.com> wrote:
> Add usb_functionfs_descs_head_v2 structure for the new layout of
> descriptors.
NAK. It's a duplicate of <https://lkml.org/lkml/2014/6/6/128> and even
more importantly, the format of the header is not fixed past the flags
field (e.g. fs_count may be missing), so fs_count, hs_count and ss_count
cannot be in the structure.
> Signed-off-by: Zhuang Jin Can <jin.can.zhuang@intel.com>
> ---
> include/uapi/linux/usb/functionfs.h | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/include/uapi/linux/usb/functionfs.h b/include/uapi/linux/usb/functionfs.h
> index 0154b28..0b3f9fc 100644
> --- a/include/uapi/linux/usb/functionfs.h
> +++ b/include/uapi/linux/usb/functionfs.h
> @@ -32,6 +32,15 @@ struct usb_endpoint_descriptor_no_audio {
> __u8 bInterval;
> } __attribute__((packed));
>
> +struct usb_functionfs_descs_head_v2 {
> + __le32 magic;
> + __le32 length;
> + __le32 flags;
> + __le32 fs_count;
> + __le32 hs_count;
> + __le32 ss_count;
> +} __attribute__((packed));
> +
> /* Legacy format, deprecated as of 3.14. */
> struct usb_functionfs_descs_head {
> __le32 magic;
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
prev parent reply other threads:[~2014-09-02 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 6:58 [PATCH] usb: gadget: f_fs: add usb_functionfs_descs_head_v2 Zhuang Jin Can
2014-09-02 12:45 ` Michal Nazarewicz [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=xa1twq9mry13.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=david.a.cohen@intel.com \
--cc=hang.yuan@intel.com \
--cc=jin.can.zhuang@intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgautam@codeaurora.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).