Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 14/28] rt2x00: Create rt2x00lib module
Date: Wed, 28 Feb 2007 16:57:49 +0100	[thread overview]
Message-ID: <200702281657.50102.IvDoorn@gmail.com> (raw)
In-Reply-To: <1172677754.5015.24.camel@johannes.berg>

On Wednesday 28 February 2007 16:49, Johannes Berg wrote:
> On Wed, 2007-02-28 at 16:43 +0100, Ivo van Doorn wrote:
> 
> > Nothing depended on RT2X00_LIB, I only had the drivers select RT2X00_LIB.
> > So something has changed or I am missing something. ;)
> 
> No, I found what's up.
> 
> You need to change it to
> 
> config RT2X00_LIB
>         tristate
>         depends on RT2X00
> 
> (note that it has no human-readable name)

Ah ok. Thanks.

> Btw. It appears that you can build debugfs support as a module while
> drivers are built in. Not good.

Thanks for the tip. I'll try to fix this.

Both things will end up in a new patch which I will send as soon as I have that
debugfs config option fixed. :)

Ivo

  reply	other threads:[~2007-02-28 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 14:07 [PATCH 14/28] rt2x00: Create rt2x00lib module Ivo van Doorn
2007-02-28 14:50 ` Johannes Berg
2007-02-28 15:12   ` Ivo van Doorn
2007-02-28 15:25     ` Johannes Berg
2007-02-28 15:34       ` Ivo van Doorn
2007-02-28 15:39         ` Johannes Berg
2007-02-28 15:43           ` Ivo van Doorn
2007-02-28 15:49             ` Johannes Berg
2007-02-28 15:57               ` Ivo van Doorn [this message]
2007-02-28 16:00                 ` Johannes Berg
2007-02-28 16:08                   ` Ivo van Doorn
2007-02-28 16:07       ` Holger Schurig
2007-02-28 16:13         ` Johannes Berg

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=200702281657.50102.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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