All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nicos@pcsystems.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ PATCH ]: disable pcspeaker kernel: 2.4.2 - 2.4.5
Date: Wed, 30 May 2001 14:52:07 +0200	[thread overview]
Message-ID: <3B14ECF7.937C2A8@pcsystems.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0105301414080.6313-200000@localhost.localdomain>

Hi!


Where did you put the config.in entries to ?
This way it would be enabled all the time... okay...
I like that, too.
In the version I set up, I used the config.in entries,
because if you use disable pc_speaker, there is at
least one more int in the kernel. This is surely now much,
but as it is not needed all the time, I thought about choosing it
from menuconfig/config/...

So in short:

less code / one int more in the kernel
or
more code and #ifs / one int less in the kernel

What do you think is better ? I agree that the above one
is nicer code, but in fact I would prefer the second solution.

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.

Regards,

Nico

  reply	other threads:[~2001-05-30 12:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30 12:10 [ PATCH ]: disable pcspeaker kernel: 2.4.2 - 2.4.5 Nico Schottelius
2001-05-30 12:21 ` Ingo Molnar
2001-05-30 12:52   ` Nico Schottelius [this message]
2001-05-30 13:50     ` Masoud Sharbiani
  -- strict thread matches above, loose matches on Subject: below --
2001-05-30 14:00 Ingo Molnar
2001-05-30 14:27 ` Nico Schottelius
2001-05-30 15:25   ` Ingo Molnar
2001-05-30 21:32     ` Daniel Phillips
2001-05-31 12:55       ` Nico Schottelius

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=3B14ECF7.937C2A8@pcsystems.de \
    --to=nicos@pcsystems.de \
    --cc=linux-kernel@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.