From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Karol Lewandowski <k.lewandowsk@samsung.com>
Cc: linux-kernel@vger.kernel.org, lmctlx@gmail.com,
Michal Nazarewicz <mina86@mina86.com>,
Felipe Balbi <balbi@ti.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 3.14-stable] usb: gadget: f_fs: drop duplicate usb_functionfs_descs_head declaration
Date: Fri, 5 Sep 2014 12:58:53 -0700 [thread overview]
Message-ID: <20140905195853.GA26296@kroah.com> (raw)
In-Reply-To: <1409943884-13823-1-git-send-email-k.lewandowsk@samsung.com>
On Fri, Sep 05, 2014 at 09:04:44PM +0200, Karol Lewandowski wrote:
> Applicable for 3.14-stable only.
>
> This commit drops duplicate declaration of struct usb_functionfs_descs_head
> erronousely added in commit 28c5980b54 ("usb: gadget: f_fs: resurect
> usb_functionfs_descs_head structure").
>
> Fix from 28c5980b54 is applicable only for v3.15-rc1 and newer kernels.
>
> This fixes error in uapi:
>
> /src/linux$ make -C tools usb
>
> make: Entering directory '/src/linux/tools'
> DESCEND usb
> make[1]: Entering directory '/src/linux/tools/usb'
> gcc -Wall -Wextra -g -I../include -o testusb testusb.c -lpthread
> gcc -Wall -Wextra -g -I../include -o ffs-test ffs-test.c -lpthread
> In file included from ffs-test.c:41:0:
> ../../include/uapi/linux/usb/functionfs.h:42:8: error: redefinition of ‘struct usb_functionfs_descs_head’
> struct usb_functionfs_descs_head {
> ^
> ../../include/uapi/linux/usb/functionfs.h:31:8: note: originally defined here
> struct usb_functionfs_descs_head {
> ^
>
> Cc: Michal Nazarewicz <mina86@mina86.com>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: stable@vger.kernel.org
> Signed-off-by: Karol Lewandowski <k.lewandowsk@samsung.com>
> ---
> include/uapi/linux/usb/functionfs.h | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/include/uapi/linux/usb/functionfs.h b/include/uapi/linux/usb/functionfs.h
> index 29e9c7a..f279394 100644
> --- a/include/uapi/linux/usb/functionfs.h
> +++ b/include/uapi/linux/usb/functionfs.h
> @@ -27,24 +27,18 @@ struct usb_endpoint_descriptor_no_audio {
> __u8 bInterval;
> } __attribute__((packed));
>
> -/* Legacy format, deprecated as of 3.14. */
> -struct usb_functionfs_descs_head {
> - __le32 magic;
> - __le32 length;
> - __le32 fs_count;
> - __le32 hs_count;
> -} __attribute__((packed, deprecated));
>
> /*
> * All numbers must be in little endian order.
> */
>
> +/* Legacy format, deprecated as of 3.14. */
> struct usb_functionfs_descs_head {
> __le32 magic;
> __le32 length;
> __le32 fs_count;
> __le32 hs_count;
> -} __attribute__((packed));
> +} __attribute__((packed, deprecated));
>
> /*
> * Descriptors format:
> --
> 2.0.1
Ah, well, instead I should just revert
28c5980b5494b8163d6cba5a5007b6ec7e63de66 as it shouldn't have gone to
3.14-stable, right? I'll do that for the next round of stable releases
after this one.
thanks,
greg k-h
next prev parent reply other threads:[~2014-09-05 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 19:04 [PATCH 3.14-stable] usb: gadget: f_fs: drop duplicate usb_functionfs_descs_head declaration Karol Lewandowski
2014-09-05 19:58 ` Greg Kroah-Hartman [this message]
2014-09-06 11:00 ` Karol Lewandowski
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=20140905195853.GA26296@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@ti.com \
--cc=k.lewandowsk@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmctlx@gmail.com \
--cc=mina86@mina86.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.