From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rt2x00: split RT2X00 option
Date: Wed, 28 Feb 2007 19:45:28 +0100 [thread overview]
Message-ID: <200702281945.28426.IvDoorn@gmail.com> (raw)
In-Reply-To: <1172687756.5015.65.camel@johannes.berg>
On Wednesday 28 February 2007 19:35, Johannes Berg wrote:
> On Wed, 2007-02-28 at 19:26 +0100, Ivo van Doorn wrote:
>
> > Make the debug(fs) config options depend on this new
> > config option.
>
> I like that.
:)
> > config RT2X00_DEBUGFS
> > tristate "Ralink debugfs support"
> > - depends on RT2X00 && DEBUG_FS
> > + depends on RT2X00 && RT2X00_LIB && DEBUG_FS
> > ---help---
> > Enable creation of debugfs files for the rt2x00 drivers.
> > These debugfs files support both reading and writing of the
>
> If you think hard about it, this also solves the problem of having
> drivers built-in when the debugfs module isn't.
Actually it doesn't fix that problem. :( It remains possible to
compile all drivers into the kernel but keeping rt2x00debug.ko as
module. But the solution really would be:
> But couldn't you just
> link the debugfs module into the lib module instead of making it an own
> module? I don't see any point in having it separate since there will be
> a dependency anyway.
My words exactly. ;)
Merging those 2 modules has been placed on my todo list,
I'll try to have this done as soon as possible.
Ivo
next prev parent reply other threads:[~2007-02-28 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 18:26 [PATCH] rt2x00: split RT2X00 option Ivo van Doorn
2007-02-28 18:35 ` Johannes Berg
2007-02-28 18:45 ` Ivo van Doorn [this message]
2007-02-28 18:53 ` Johannes Berg
2007-02-28 19:02 ` Ivo van Doorn
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=200702281945.28426.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 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.