From: Ben Hutchings <ben@decadent.org.uk>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org
Subject: Re: Build failures in v3.2-stable-queue
Date: Fri, 08 Sep 2017 18:22:54 +0100 [thread overview]
Message-ID: <1504891374.2713.16.camel@decadent.org.uk> (raw)
In-Reply-To: <20170908164801.GA8916@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
On Fri, 2017-09-08 at 09:48 -0700, Guenter Roeck wrote:
> Seen in various builds.
>
> drivers/usb/dwc3/gadget.c:1941:9: error:
> 'struct dwc3_event_buffer' has no member named 'flags'
> drivers/usb/dwc3/gadget.c:1941:19: error:
> 'DWC3_EVENT_PENDING' undeclared
Thanks, I have already found and dropped the offending patch but not
yet pushed.
Ben.
--
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-08 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 16:48 Build failures in v3.2-stable-queue Guenter Roeck
2017-09-08 17:22 ` Ben Hutchings [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-05 14:35 Guenter Roeck
2015-07-21 22:37 Guenter Roeck
2015-07-21 23:11 ` Ben Hutchings
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=1504891374.2713.16.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux@roeck-us.net \
--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