From: Nico Schottelius <nicos@pcsystems.de>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ PATCH ]: disable pcspeaker kernel: 2.4.2 - 2.4.5
Date: Wed, 30 May 2001 16:27:53 +0200 [thread overview]
Message-ID: <3B150369.D47ED28F@pcsystems.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0105301559310.1240-100000@localhost.localdomain>
> > less code / one int more in the kernel
> > or
> > more code and #ifs / one int less in the kernel
>
> if the #ifdefs bloat the code 4 times the size of the simple patch, then
> we obviously want 4 bytes more in the kernel.
Okay.
> > And what about the code from kernel/sys.c ? The version you provided
> > doesn't take care of what's the default value of pcspeaker. This would
> > make it undefined, which is not really good.
>
> the default value is 0, that is good enough.
hmm.. I don't think so... value of 1 would be much better, because
0 normally disables the speaker.
So setting somewhere pcspeaker_enabled = 1 should be better
than having it with 0.
So in kernel/sysctl.c:
int pcspeaker_enabled = 1;
or anybody against this ?
Nico
next prev parent reply other threads:[~2001-05-30 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 14:00 [ PATCH ]: disable pcspeaker kernel: 2.4.2 - 2.4.5 Ingo Molnar
2001-05-30 14:27 ` Nico Schottelius [this message]
2001-05-30 15:25 ` Ingo Molnar
2001-05-30 21:32 ` Daniel Phillips
2001-05-31 12:55 ` Nico Schottelius
-- strict thread matches above, loose matches on Subject: below --
2001-05-30 12:10 Nico Schottelius
2001-05-30 12:21 ` Ingo Molnar
2001-05-30 12:52 ` Nico Schottelius
2001-05-30 13:50 ` Masoud Sharbiani
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=3B150369.D47ED28F@pcsystems.de \
--to=nicos@pcsystems.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.