From: Michal Nazarewicz <mina86@mina86.com>
To: "Maxin B. John" <maxin.john@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: matt.fleming@intel.com, matthias.fend@wolfvision.net,
balbi@ti.com, linux-usb@vger.kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Maxin B. John" <maxin.john@enea.com>
Subject: Re: [PATCH] tools: usb: ffs-test: Fix build failure
Date: Thu, 21 Feb 2013 07:44:42 +0100 [thread overview]
Message-ID: <xa1tfw0qdv39.fsf@mina86.com> (raw)
In-Reply-To: <CAMhs6YxGWaLgt58HeumVzstU=373WRYMTsf8uFKnQ9nEFboj7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Thu, Feb 21 2013, Maxin B. John wrote:
> Hi,
>
> On Thu, Feb 21, 2013 at 2:06 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> On Thu, Feb 21, 2013 at 01:57:51AM +0200, maxin.john@gmail.com wrote:
>>> From: "Maxin B. John" <maxin.john@enea.com>
>>>
>>> Fixes this build failure:
>>> gcc -Wall -Wextra -g -lpthread -I../include -o testusb testusb.c
>>> gcc -Wall -Wextra -g -lpthread -I../include -o ffs-test ffs-test.c
>>> In file included from ffs-test.c:41:0:
>>> ../../include/linux/usb/functionfs.h:4:39: fatal error:
>>> uapi/linux/usb/functionfs.h: No such file or directory
>>> compilation terminated.
>>> make: *** [ffs-test] Error 1
>>
>> This is a build failure where, 3.8, or linux-next, or somewhere else?
>
> It is in 3.8
This also happens in 3.7. [commit
5e1ddb481776a487b15b40579a000b279ce527c9: UAPI: (Scripted) Disintegrate
include/linux/usb] is the culprit.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2.2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-02-21 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 23:57 maxin.john
2013-02-21 0:06 ` Greg KH
2013-02-21 0:22 ` Maxin B. John
2013-02-21 6:44 ` Michal Nazarewicz [this message]
2013-02-21 6:42 ` Michal Nazarewicz
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=xa1tfw0qdv39.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matthias.fend@wolfvision.net \
--cc=maxin.john@enea.com \
--cc=maxin.john@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®