From: Michal Simek <monstr@monstr.eu>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: Fix Kconfig unmet dependencies for Microblaze EHCI
Date: Mon, 04 Apr 2011 11:31:30 +0200 [thread overview]
Message-ID: <4D998FF2.5050105@monstr.eu> (raw)
In-Reply-To: <4D998EDD.1080404@ru.mvista.com>
Sergei Shtylyov wrote:
> Hello.
>
> On 04-04-2011 13:20, Michal Simek wrote:
>
>> Disable USB_ARCH_HAS_EHCI in arch Kconfig and enable it in usb Kconfig
>
>> Warning log:
>> warning: (LOCKDEP&& FAULT_INJECTION_STACKTRACE_FILTER&&
>> LATENCYTOP&& FUNCTION_TRACER&&
>> KMEMCHECK) selects FRAME_POINTER which has unmet direct dependencies
>> (DEBUG_KERNEL&&
>> (CRIS || M68K || FRV || UML || AVR32 || SUPERH || BLACKFIN || MN10300) ||
>> ARCH_WANT_FRAME_POINTERS)
>
> Hm, what this has to do with USB_ARCH_HAS_EHCI?
aaah. c&p error. I was doing two patches and copy the same warning to both.
There should be:
warning: (MICROBLAZE) selects USB_ARCH_HAS_EHCI which has unmet direct
dependencies (USB_SUPPORT)
Will replace it!
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
prev parent reply other threads:[~2011-04-04 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 9:20 [PATCH] usb: Fix Kconfig unmet dependencies for Microblaze EHCI Michal Simek
2011-04-04 9:20 ` [PATCH] ftrace: Build without frame pointers on Microblaze Michal Simek
2011-04-14 6:48 ` Michal Simek
2011-04-21 2:17 ` Steven Rostedt
2011-04-21 5:42 ` Michal Simek
2011-04-27 15:57 ` [tip:perf/urgent] " tip-bot for Michal Simek
2011-04-04 9:26 ` [PATCH] usb: Fix Kconfig unmet dependencies for Microblaze EHCI Sergei Shtylyov
2011-04-04 9:31 ` Michal Simek [this message]
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=4D998FF2.5050105@monstr.eu \
--to=monstr@monstr.eu \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sshtylyov@mvista.com \
/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).