From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] Small number of aesthetic/dependency cleanups in usr/Kconfig
Date: Mon, 20 Jun 2016 07:38:54 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1606200733410.16925@localhost.localdomain> (raw)
* Remove superfluous dependencies on BLK_DEV_INITRD.
* Couple grammar fixes.
* Add proper hyphenation.
* Add periods at end of some help sentences.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
only place i'm not absolutely confident is the removal of those
dependency lines but, AFAICT, this Kconfig file is sourced only from
init/Kconfig, which contains:
if BLK_DEV_INITRD
source "usr/Kconfig"
endif
so unless that Kconfig file is sourced from elsewhere, this should be
fine.
diff --git a/usr/Kconfig b/usr/Kconfig
index 572dcf7..392021d 100644
--- a/usr/Kconfig
+++ b/usr/Kconfig
@@ -26,7 +26,7 @@ config INITRAMFS_ROOT_UID
depends on INITRAMFS_SOURCE!=""
default "0"
help
- This setting is only meaningful if the INITRAMFS_SOURCE is
+ This setting is only meaningful if the INITRAMFS_SOURCE
contains a directory. Setting this user ID (UID) to something
other than "0" will cause all files owned by that UID to be
owned by user root in the initial ramdisk image.
@@ -38,7 +38,7 @@ config INITRAMFS_ROOT_GID
depends on INITRAMFS_SOURCE!=""
default "0"
help
- This setting is only meaningful if the INITRAMFS_SOURCE is
+ This setting is only meaningful if the INITRAMFS_SOURCE
contains a directory. Setting this group ID (GID) to something
other than "0" will cause all files owned by that GID to be
owned by group root in the initial ramdisk image.
@@ -47,54 +47,48 @@ config INITRAMFS_ROOT_GID
config RD_GZIP
bool "Support initial ramdisks compressed using gzip"
- depends on BLK_DEV_INITRD
default y
select DECOMPRESS_GZIP
help
- Support loading of a gzip encoded initial ramdisk or cpio buffer.
+ Support loading of a gzip-encoded initial ramdisk or cpio buffer.
If unsure, say Y.
config RD_BZIP2
bool "Support initial ramdisks compressed using bzip2"
default y
- depends on BLK_DEV_INITRD
select DECOMPRESS_BZIP2
help
- Support loading of a bzip2 encoded initial ramdisk or cpio buffer
+ Support loading of a bzip2-encoded initial ramdisk or cpio buffer.
If unsure, say N.
config RD_LZMA
bool "Support initial ramdisks compressed using LZMA"
default y
- depends on BLK_DEV_INITRD
select DECOMPRESS_LZMA
help
- Support loading of a LZMA encoded initial ramdisk or cpio buffer
+ Support loading of a LZMA-encoded initial ramdisk or cpio buffer.
If unsure, say N.
config RD_XZ
bool "Support initial ramdisks compressed using XZ"
- depends on BLK_DEV_INITRD
default y
select DECOMPRESS_XZ
help
- Support loading of a XZ encoded initial ramdisk or cpio buffer.
+ Support loading of a XZ-encoded initial ramdisk or cpio buffer.
If unsure, say N.
config RD_LZO
bool "Support initial ramdisks compressed using LZO"
default y
- depends on BLK_DEV_INITRD
select DECOMPRESS_LZO
help
- Support loading of a LZO encoded initial ramdisk or cpio buffer
+ Support loading of a LZO-encoded initial ramdisk or cpio buffer.
If unsure, say N.
config RD_LZ4
bool "Support initial ramdisks compressed using LZ4"
default y
- depends on BLK_DEV_INITRD
select DECOMPRESS_LZ4
help
- Support loading of a LZ4 encoded initial ramdisk or cpio buffer
+ Support loading of a LZ4-encoded initial ramdisk or cpio buffer.
If unsure, say N.
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
reply other threads:[~2016-06-20 11:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.20.1606200733410.16925@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).