From: Piotr Hosowicz <piotr@hosowicz.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Jiri Slaby <jirislaby@gmail.com>,
"Justin P. Mattock" <justinmattock@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: What's up with wireless drivers?
Date: Mon, 24 May 2010 04:54:01 +0200 [thread overview]
Message-ID: <4BF9EA49.8050007@example.com> (raw)
In-Reply-To: <20100523145319.89008e2e.rdunlap@xenotime.net>
On 23.05.2010 23:53, Randy Dunlap wrote:
> On Sun, 23 May 2010 20:28:53 +0200 Piotr Hosowicz wrote:
>
>> On 23.05.2010 19:50, Jiri Slaby wrote:
>>> On 05/23/2010 03:54 PM, Piotr Hosowicz wrote:
>>>> And they had built flawlessly. But main build with make-kpkg
>>>> kernel_image nevertheless still fails. I don;t know what to do. I don't
>>>> want to do those strace's, because it will take awfully long.
>>>
>>> Why don't you just look at the actual error which is likely somewhere
>>> above because of parallel build? And when you are posting outputs, first
>>> switch your locale to en so that we can parse the output.
>>
>> I tried again and the error is about CEPH. I attach the typescript. I am
>> totaly confused, now build breakse in yet another place than before.
>>
>> Regards,
>>
>> Piotr Hosowicz
>>
>> PS: I ordered make modules without calling make first, I on't know if
>> it's ok.
>
>
> CC [M] fs/ceph/msgpool.o
> fs/ceph/msgpool.c: In function ___ceph_msgpool_put___:
> fs/ceph/msgpool.c:173: error: implicit declaration of function ___kref_set___
> make[2]: *** [fs/ceph/msgpool.o] B____d 1
> make[1]: *** [fs/ceph] B____d 2
> make: *** [fs] B____d 2
>
>
> Known problem, but I haven't seen a fix for it yet.
>
> And note how it says Error 1, not just Error 2.
> Error 1 is the primary error. Just showing us Error 2 is mostly useless.
Thanks, the kernel is built and booted as you can see, but there is an
error after boot, I'll start a separate thread about it.
Regards,
Piotr Hosowicz
--
"Bardzo fajna firma, tylko czasami nie płaci. Do jej głównych
zalet należą: ekspres ciśnieniowy (ale tylko na jednym z pię-
ter) oraz fajne widoki z salki konferencyjnej. No i jakieś
pół roku temu odeszło 90% pracowników działu IT, ale może nie
mieli racji ;)"
NP: Slash - Ghost (Feat. Ian Astbury)
NB: 2.6.34-20100524-0407
next prev parent reply other threads:[~2010-05-24 2:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 20:53 What's up with wireless drivers? Piotr Hosowicz
2010-05-21 21:07 ` John W. Linville
2010-05-21 21:21 ` Piotr Hosowicz
2010-05-21 21:31 ` Piotr Hosowicz
2010-05-21 22:12 ` Randy Dunlap
2010-05-21 22:20 ` Piotr Hosowicz
2010-05-22 8:40 ` Piotr Hosowicz
2010-05-22 12:43 ` Piotr Hosowicz
2010-05-22 13:13 ` Piotr Hosowicz
2010-05-22 13:35 ` Justin P. Mattock
2010-05-22 13:40 ` Piotr Hosowicz
2010-05-22 13:44 ` Justin P. Mattock
2010-05-22 14:04 ` Piotr Hosowicz
2010-05-22 14:17 ` Justin P. Mattock
2010-05-22 14:21 ` Piotr Hosowicz
2010-05-23 13:54 ` Piotr Hosowicz
2010-05-23 17:50 ` Jiri Slaby
2010-05-23 18:28 ` Piotr Hosowicz
2010-05-23 21:53 ` Randy Dunlap
2010-05-24 2:54 ` Piotr Hosowicz [this message]
2010-05-23 17:53 ` Randy Dunlap
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=4BF9EA49.8050007@example.com \
--to=piotr@hosowicz.com \
--cc=jirislaby@gmail.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.