From: Bin Liu <b-liu@ti.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-usb@vger.kernel.org,
Felipe Balbi <balbi@kernel.org>, Petr Cvek <petr.cvek@tul.cz>
Subject: usb: gadget: uvc: Missing files for configfs interface
Date: Fri, 9 Feb 2018 14:02:42 -0600 [thread overview]
Message-ID: <20180209200242.GA32164@uda0271908> (raw)
On Fri, Feb 09, 2018 at 08:51:03PM +0100, Greg KH wrote:
> On Fri, Feb 09, 2018 at 01:23:43PM -0600, Bin Liu wrote:
> > From: Petr Cvek <petr.cvek@tul.cz>
> >
> > commit c8cd751060b149997b9de53a494fb1490ded72c5 upstream.
> >
> > Commit 76e0da34c7ce ("usb-gadget/uvc: use per-attribute show and store
> > methods") caused a stringification of an undefined macro argument "aname",
> > so three UVC parameters (streaming_interval, streaming_maxpacket and
> > streaming_maxburst) were named "aname".
> >
> > Add the definition of "aname" to the main macro and name the filenames as
> > originaly intended.
> >
> > Signed-off-by: Petr Cvek <petr.cvek@tul.cz>
> > Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
> > Signed-off-by: Bin Liu <b-liu@ti.com>
> > ---
> > drivers/usb/gadget/function/uvc_configfs.c | 16 ++++++++--------
> > 1 file changed, 8 insertions(+), 8 deletions(-)
>
> What stable kernel(s) do you want this applied to?
The commit 76e0da34c7ce which causes the regression is introduced in
v4.4, so I would think this patch have to be applied down to v4.4.
FYI, I tested this patch on v4.4 and v4.9.
Thanks,
-Bin.
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-02-09 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 20:02 Bin Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-09 19:51 usb: gadget: uvc: Missing files for configfs interface Greg Kroah-Hartman
2018-02-09 19:23 Bin Liu
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=20180209200242.GA32164@uda0271908 \
--to=b-liu@ti.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=petr.cvek@tul.cz \
--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 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).