Received: by 10.223.176.46 with SMTP id f43csp1897112wra; Thu, 25 Jan 2018 01:39:28 -0800 (PST) X-Google-Smtp-Source: AH8x2263fE+qwf/ygRMhoP9a2GyBiYUKxJJFuzBKExrF+irQhdo/QqSsozckOm+TG+5Lu6ofrp+t X-Received: by 10.98.46.2 with SMTP id u2mr15586488pfu.30.1516873168098; Thu, 25 Jan 2018 01:39:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516873168; cv=none; d=google.com; s=arc-20160816; b=CCtc6QU3QJdIn9nQqf1WJz9EZLcaI8i6pUeC6HfjdetqHIyIxPreKILMf9Jn/JNrwp uzLDJdwloWwUbD0mGfpjMYCoNagUI0FKFCjRF4tVN4TLFvmuhzjjcM9a/XpgSbd2tJdG aj6MZe+l9BuBD+FsYGGb4049pfTMQiRc+x/+O2Cw8rdV4QqrJ3pXcukPDYX7aDA8N0wx SebkCkJq6KrJbw22KKPF3Se34TQrT1A7nMKfOXkethBIhhXKVUOYEFVzPoX7YNVMiPmm vsFFlRpdXZTY1nAyzzBtadZzzoumMKiUvNznEfHUpfa7webDcIkXne4tfD2n2GplIbap eo0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=qcAMTLd+AY2DBxfih692FAFBOgNPo/B/0Oo5CXT5FH0=; b=i5jLAbqJ53kwxtn598viUGUqF2aJRgo1yfIb1u90Pm46kbSCFICeTDsaLFn4Fpk0J+ XMcSiVpcYA1OuK7Kas/w+Qvgi9PMsbg7tfp8oa2aeDx42aHnNKZGQBu/YOzqEC6dy+S5 Uyai+AkTP2Km546FqQJmM/vd405hO6YbzLKhl7oZloaZHI/Rld/0EqX2gQDpYXsRU2Er plAlkXWedTR19DR/bv35inJqhtr9Jy64NsLBHckFc0GBdm182HJt9RQ0ME0ZDz1AormI EUDtO0Yk1K0A1YNIN/pSdwGnnFufxvZgS4pkrtQC0k2pQ50qlKIWhQLpZX90V9EUmJYf oS0Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=oTmzkP/b; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d7si1330253pgf.470.2018.01.25.01.39.14; Thu, 25 Jan 2018 01:39:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=oTmzkP/b; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751480AbeAYJiX (ORCPT + 99 others); Thu, 25 Jan 2018 04:38:23 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:55475 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751191AbeAYJiU (ORCPT ); Thu, 25 Jan 2018 04:38:20 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B118020CBE; Thu, 25 Jan 2018 04:38:17 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 25 Jan 2018 04:38:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=qcAMTLd+AY2DBxfih692FAFBOgNPo /B/0Oo5CXT5FH0=; b=oTmzkP/bZhqgcH3+/Biuy6zokX776wW+ZhvIQXMpF6PkC dGMpkwJHqpiwjUbyJ+wybcXpjJqRa10EOBccDK2zHHKxBLXXJ+wcbQ9VZmFNkZ1j ywHvI3bH63HKrckZjjBBdQfZ/4h1rrv8ti59GWwGRKq7a628xLjVUb6eNBZgiQBS dQHzIoD1QL+avfCvVUOoX8BCyRRvHcx7BhyMGoPlGsRJFQruo2gdYoGltF1QuVJY x0U+iEhivMULeU4JsGSBNd4hxT+cWkZOT1vCtLGeWA7waKmZcNaMdEVDsXr1x9r2 +vOrlAtYfqIsyQQE7NfWI7wAIJwFsIYYf7RZC5wrg== X-ME-Sender: Received: from localhost (lfbn-1-12258-90.w90-92.abo.wanadoo.fr [90.92.71.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 4435C24550; Thu, 25 Jan 2018 04:38:17 -0500 (EST) Date: Thu, 25 Jan 2018 10:38:17 +0100 From: Greg KH To: Ingo Molnar Cc: Benjamin Gilbert , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, x86@kernel.org, Borislav Petkov , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" Subject: Re: [PATCH 3/3] firmware: Fix up docs referring to FIRMWARE_IN_KERNEL Message-ID: <20180125093817.GB14894@kroah.com> References: <20180124020632.22905-1-benjamin.gilbert@coreos.com> <20180124020632.22905-4-benjamin.gilbert@coreos.com> <20180124074130.h35a6gghehnxr2st@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180124074130.h35a6gghehnxr2st@gmail.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 24, 2018 at 08:41:30AM +0100, Ingo Molnar wrote: > > * Benjamin Gilbert wrote: > > > We've removed the option, so stop talking about it. > > > > Signed-off-by: Benjamin Gilbert > > Cc: Borislav Petkov > > Cc: Thomas Gleixner > > Cc: Ingo Molnar > > Cc: H. Peter Anvin > > --- > > Documentation/driver-api/firmware/built-in-fw.rst | 7 +------ > > Documentation/x86/microcode.txt | 5 ++--- > > arch/x86/Kconfig | 6 +++--- > > 3 files changed, 6 insertions(+), 12 deletions(-) > > > > diff --git a/Documentation/driver-api/firmware/built-in-fw.rst b/Documentation/driver-api/firmware/built-in-fw.rst > > index 7300e66857f8..396cdf591ac5 100644 > > --- a/Documentation/driver-api/firmware/built-in-fw.rst > > +++ b/Documentation/driver-api/firmware/built-in-fw.rst > > @@ -11,13 +11,8 @@ options: > > * CONFIG_EXTRA_FIRMWARE > > * CONFIG_EXTRA_FIRMWARE_DIR > > > > -This should not be confused with CONFIG_FIRMWARE_IN_KERNEL, this is for drivers > > -which enables firmware to be built as part of the kernel build process. This > > -option, CONFIG_FIRMWARE_IN_KERNEL, will build all firmware for all drivers > > -enabled which ship its firmware inside the Linux kernel source tree. > > - > > There are a few reasons why you might want to consider building your firmware > > -into the kernel with CONFIG_EXTRA_FIRMWARE though: > > +into the kernel with CONFIG_EXTRA_FIRMWARE: > > > > * Speed > > * Firmware is needed for accessing the boot device, and the user doesn't > > diff --git a/Documentation/x86/microcode.txt b/Documentation/x86/microcode.txt > > index f57e1b45e628..aacd2f5e1a46 100644 > > --- a/Documentation/x86/microcode.txt > > +++ b/Documentation/x86/microcode.txt > > @@ -108,12 +108,11 @@ packages already put them there. > > ==================== > > > > The loader supports also loading of a builtin microcode supplied through > > -the regular firmware builtin method CONFIG_FIRMWARE_IN_KERNEL. Only > > -64-bit is currently supported. > > +the regular firmware builtin method CONFIG_EXTRA_FIRMWARE. Only 64-bit is > > +currently supported. > > s/regular firmware builtin method > /regular builtin firmware method I'll go edit that up by hand, thanks for the review. greg k-h