From: Stefan Sperling <stefan@binarchy.net>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] convert airo wireless driver to module_param
Date: Tue, 09 Nov 2004 22:56:09 +0000 [thread overview]
Message-ID: <20041109225609.GA11279@dice.seeling33.de> (raw)
In-Reply-To: <20041109212957.GA9496@dice.seeling33.de>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Tue, Nov 09, 2004 at 02:29:07PM -0800, Randy.Dunlap wrote:
> >I'll try again and make everything invisible except debug/verbosity flags.
> >Since you mentioned bitmasks, is it safe to make irq bitmasks writable as
> >well?
> >I made them read-only.
>
> I mentioned bitmasks because some debug variables aren't boolean,
> they are bit flags, or sometimes they are an integer (debug level).
Oops, I misread that one, sorry.
I only found IRQ bitmasks among the parameters, thus I mixed that up...
> No, I don't think that irq bitmasks should be writeable.
> Having any system reource data writeable (like IRQ) is asking for
> trouble IMO.
no way! ;-)
thanks
stefan
--
Give me a fish and I will eat today.
Teach me to fish and I will eat forever.
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-11-09 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 21:29 [KJ] [PATCH] convert airo wireless driver to module_param Stefan Sperling
2004-11-09 21:38 ` Randy.Dunlap
2004-11-09 22:05 ` Stefan Sperling
2004-11-09 22:21 ` Stefan Sperling
2004-11-09 22:28 ` Randy.Dunlap
2004-11-09 22:29 ` Greg KH
2004-11-09 22:29 ` Randy.Dunlap
2004-11-09 22:56 ` Stefan Sperling [this message]
2004-11-09 22:58 ` Stefan Sperling
2004-11-09 23:16 ` Stefan Sperling
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=20041109225609.GA11279@dice.seeling33.de \
--to=stefan@binarchy.net \
--cc=kernel-janitors@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 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.