From: Greg Kroah-Hartman <gregkh@suse.de>
To: linux-kernel@vger.kernel.org
Cc: matt mooney <mfm@muteddisk.com>, Greg Kroah-Hartman <gregkh@suse.de>
Subject: [PATCH 05/11] driver-core: modify FIRMWARE_IN_KERNEL help message
Date: Tue, 26 Jul 2011 21:05:15 -0700 [thread overview]
Message-ID: <1311739521-11014-5-git-send-email-gregkh@suse.de> (raw)
In-Reply-To: <1311739521-11014-1-git-send-email-gregkh@suse.de>
From: matt mooney <mfm@muteddisk.com>
The help message for the configuration variable was inconsistent
with the way "make firmware_install" really works.
Signed-off-by: matt mooney <mfm@muteddisk.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
drivers/base/Kconfig | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
index 5fe7fd2..52c6758 100644
--- a/drivers/base/Kconfig
+++ b/drivers/base/Kconfig
@@ -84,10 +84,10 @@ config FIRMWARE_IN_KERNEL
help
The kernel source tree includes a number of firmware 'blobs'
that are used by various drivers. The recommended way to
- use these is to run "make firmware_install" and to copy the
- resulting binary files created in usr/lib/firmware/ of the
- kernel tree to /lib/firmware/ on your system so that they can
- be loaded by userspace helpers on request.
+ use these is to run "make firmware_install", which, after
+ converting ihex files to binary, copies all of the needed
+ binary files in firmware/ to /lib/firmware/ on your system so
+ that they can be loaded by userspace helpers on request.
Enabling this option will build each required firmware blob
into the kernel directly, where request_firmware() will find
--
1.7.6
next prev parent reply other threads:[~2011-07-27 4:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 4:57 [GIT PATCH] driver core merge for 3.1 Greg KH
2011-07-27 4:05 ` [PATCH 01/11] pti: pti_tty_install documentation mispelling Greg Kroah-Hartman
2011-07-27 4:05 ` [PATCH 02/11] DOCUMENTATION: Update overview.txt in Doc/driver-model Greg Kroah-Hartman
2011-07-27 4:05 ` [PATCH 03/11] DOCUMENTATION: Replace create_device() with device_create() Greg Kroah-Hartman
2011-07-27 4:05 ` [PATCH 04/11] driver-core: Kconfig grammar corrections in firmware configuration Greg Kroah-Hartman
2011-07-27 4:05 ` Greg Kroah-Hartman [this message]
2011-07-27 4:05 ` [PATCH 06/11] driver core: add more help description for "path to uevent helper" Greg Kroah-Hartman
2011-07-27 4:05 ` [PATCH 07/11] Documentation/zh_CN: Fix messy code file email-clients.txt Greg Kroah-Hartman
2011-07-27 4:05 ` [PATCH 08/11] firmware: gsmi: remove sysfs entries when unload the module Greg Kroah-Hartman
2011-07-27 4:05 ` [PATCH 09/11] uio: uio_pdrv_genirq: Add OF support Greg Kroah-Hartman
2011-07-27 8:17 ` Hans J. Koch
2011-07-27 4:05 ` [PATCH 10/11] debugfs: add documentation for debugfs_create_x64 Greg Kroah-Hartman
2011-07-27 4:05 ` [PATCH 11/11] updated Documentation/ja_JP/SubmittingPatches Greg Kroah-Hartman
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=1311739521-11014-5-git-send-email-gregkh@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mfm@muteddisk.com \
/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
Powered by JetHome