All of lore.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Dave Jones <davej@suse.de>,
	marcelo@conectiva.com.br, lkml <linux-kernel@vger.kernel.org>,
	"Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Subject: Re: [Patch] tsc-disable_A5
Date: 14 Jun 2002 16:44:30 -0700	[thread overview]
Message-ID: <1024098271.4358.8.camel@cog> (raw)
In-Reply-To: <Pine.LNX.4.44.0206141827510.31514-100000@chaos.physics.uiowa.edu>

On Fri, 2002-06-14 at 16:29, Kai Germaschewski wrote:
> I suppose you could it rewrite like
> 
> ...
> CONFIG_X86_WANT_TSC=y (or whatever)
> ...
> 
> if [ some_condition ]; then
>   define_bool CONFIG_X86_TSC n
> else
>   define_bool CONFIG_X86_TSC $CONFIG_X86_WANT_TSC
> fi
> 
> Not exactly elegant, but it should work ;)

Yep, my first release was done in a similar fashion, but Alan suggested
the patch take on its current form. There may be cases where we want to
know if we have a TSC even if we don't want to use them. 

Thread link:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0205.3/1188.html

Thanks for the suggestion,
-john


  reply	other threads:[~2002-06-14 23:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14 18:35 [Patch] tsc-disable_A5 john stultz
2002-06-14 18:53 ` Benjamin LaHaise
2002-06-18  0:48   ` Kurt Garloff
2002-06-18  1:31     ` john stultz
2002-06-14 18:57 ` Dave Jones
2002-06-14 19:04   ` john stultz
2002-06-14 19:56     ` Dave Jones
2002-06-14 23:29       ` Kai Germaschewski
2002-06-14 23:44         ` john stultz [this message]
2002-06-24  2:09 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2002-06-14 21:53 Mikael Pettersson
2002-06-14 22:11 ` john stultz
2002-06-15 14:13 Mikael Pettersson
2002-06-19 13:58 ` Maciej W. Rozycki

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=1024098271.4358.8.camel@cog \
    --to=johnstul@us.ibm.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=davej@suse.de \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.