public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel K." <dk@uw.no>
To: Peter Oruba <peter.oruba@amd.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 8/9] [PATCH 8/9] x86: Major refactoring.
Date: Sat, 26 Jul 2008 09:11:48 +0000	[thread overview]
Message-ID: <488AEA54.2030703@uw.no> (raw)
In-Reply-To: <20080725162003.347794240@amd.com>

Peter Oruba wrote:
> Refactored code by introducing a two-module solution. There is one
> general module in which vendor specific modules can hook into.
>  
>  config MICROCODE
> -	tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
> +	tristate "/dev/cpu/microcode - microcode support"
>  	select FW_LOADER
>  	---help---
>  	  If you say Y here, you will be able to update the microcode on
> @@ -791,14 +791,28 @@ config MICROCODE
>  	  actual microcode binary data itself which is not shipped with the
>  	  Linux kernel.
>  
> -	  For latest news and information on obtaining all the required
> -	  ingredients for this driver, check:
> -	  <http://www.urbanmyth.org/microcode/>.
> +	  This option selects the general module only, you need to select
> +	  at least one vendor specific module as well.
>  
>  	  To compile this driver as a module, choose M here: the
>  	  module will be called microcode.
>  
> -config MICROCODE_OLD_INTERFACE
> +config MICROCODE_INTEL
> +       tristate "Intel microcode patch loading support"
> +       depends on MICROCODE

	default MICROCODE

so that users doing make oldconfig don't get a surprise?

> +       select FW_LOADER
> +       --help---
> +         This options enables microcode patch loading support for Intel
> +         processors.
> +
> +         For latest news and information on obtaining all the required
> +         Intel ingredients for this driver, check:
> +         <http://www.urbanmyth.org/microcode/>.
> +
> +         This driver is only available as a module: the module
> +         will be called microcode_intel.  
> +
> +   config MICROCODE_OLD_INTERFACE

Kill the extra spaces.


Daniel K.

  reply	other threads:[~2008-07-26  9:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 16:17 [patch 0/9] x86: AMD microcode patch loading support Peter Oruba
2008-07-25 16:17 ` [patch 1/9] [PATCH 1/9] x86: Moved Intel microcode patch loader declarations to seperate header file Peter Oruba
2008-07-25 16:17 ` [patch 2/9] [PATCH 2/9] x86: Typedef removal Peter Oruba
2008-07-25 16:17 ` [patch 3/9] [PATCH 3/9] x86: Moved per CPU microcode structure declaration to header file Peter Oruba
2008-07-25 16:17 ` [patch 4/9] [PATCH 4/9] x86: Code split to two parts Peter Oruba
2008-07-25 16:17 ` [patch 5/9] [PATCH 5/9] x86: Structure declaration renaming Peter Oruba
2008-07-25 16:17 ` [patch 6/9] [PATCH 6/9] x86: Add AMD specific declarations Peter Oruba
2008-07-25 16:17 ` [patch 7/9] [PATCH 7/9] x86: First step of refactoring, introducing microcode_ops Peter Oruba
2008-07-25 16:17 ` [patch 8/9] [PATCH 8/9] x86: Major refactoring Peter Oruba
2008-07-26  9:11   ` Daniel K. [this message]
2008-07-25 16:17 ` [patch 9/9] [PATCH 9/9] x86: AMD microcode patch loading support Peter Oruba
2008-07-26  8:00   ` Rabin Vincent
2008-07-25 16:44 ` [PATCH] x86: Add entry to MAINTAINERS file Peter Oruba
2008-07-26 13:37 ` [patch 0/9] x86: AMD microcode patch loading support Ingo Molnar

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=488AEA54.2030703@uw.no \
    --to=dk@uw.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peter.oruba@amd.com \
    --cc=tglx@linutronix.de \
    --cc=tigran@aivazian.fsnet.co.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox