From: Johannes Berg <johannes@sipsolutions.net>
To: alex1000@comcast.net
Cc: linville@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: Error building latest wireles-dev
Date: Thu, 23 Nov 2006 20:54:01 +0100 [thread overview]
Message-ID: <1164311641.24475.8.camel@johannes.berg> (raw)
In-Reply-To: <112320061932.9051.4565F756000A19370000235B2207001641CFCFCFCE980A040E@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
On Thu, 2006-11-23 at 19:32 +0000, alex1000@comcast.net wrote:
> I get following errors when running 'make modules'
Well yes. It's a dev tree and API changes broke all drivers.
I can only suggest you actually read wireless dev related posts.
Especially wireless-dev update announcements can sometimes be helpful :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-11-23 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 19:32 Error building latest wireles-dev alex1000
2006-11-23 19:54 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-23 20:58 alex1000
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=1164311641.24475.8.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=alex1000@comcast.net \
--cc=linville@tuxdriver.com \
--cc=netdev@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