From: David Cohen <david.a.cohen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: balbi@ti.com, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: g_ffs: fix compilation warning
Date: Fri, 04 Oct 2013 15:03:54 -0700 [thread overview]
Message-ID: <524F3B4A.7070107@linux.intel.com> (raw)
In-Reply-To: <20131004215156.GA10629@kroah.com>
On 10/04/2013 02:51 PM, Greg KH wrote:
> On Fri, Oct 04, 2013 at 02:48:46PM -0700, David Cohen wrote:
>> Due to lack of "u_ether.h" header file, g_ffs.c compiles with following
>> warning:
>
> It does? In what tree/branch/release is this happening?
This is intended for Linus' 3.12-rc3. Haven't checked any other kernel.
In my compilation I disabled USB Host support and enabled DWC3 (gadget
only) with ePCI + NOP_USB_XCEIV.
Br, David
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2013-10-04 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 21:48 [PATCH] usb: g_ffs: fix compilation warning David Cohen
2013-10-04 21:51 ` Greg KH
2013-10-04 22:03 ` David Cohen [this message]
2013-10-04 22:08 ` David Cohen
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=524F3B4A.7070107@linux.intel.com \
--to=david.a.cohen@linux.intel.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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