From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>, Karel Zak <kzak@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Martin Mares <mj@ucw.cz>,
linux-video@atrey.karlin.mff.cuni.cz,
"H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [RFC PATCH 0/2] Documentation/admin-guide: remove use of "rdev"
Date: Mon, 31 Aug 2020 22:38:20 -0700 [thread overview]
Message-ID: <20200901053822.9374-1-rdunlap@infradead.org> (raw)
Remove mention of using "rdev" to set boot device, video mode,
or ramdisk information for the booting kernel.
FIX patch 1/2 Subject:
Cc: Karel Zak <kzak@redhat.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Martin Mares <mj@ucw.cz>
Cc: linux-video@atrey.karlin.mff.cuni.cz
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
[RFC PATCH 1/2] Documentation/admin-guide: README & svga: remove use of "rdev"
[RFC PATCH 2/2] Documentation/admin-guide: blockdev/ramdisk: remove use of "rdev"
Documentation/admin-guide/README.rst | 6 -
Documentation/admin-guide/blockdev/ramdisk.rst | 70 ++++----------
Documentation/admin-guide/kernel-parameters.txt | 9 -
Documentation/admin-guide/svga.rst | 6 -
4 files changed, 33 insertions(+), 58 deletions(-)
next reply other threads:[~2020-09-01 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 5:38 Randy Dunlap [this message]
2020-09-01 5:38 ` [RFC PATCH 1/2] Documentation/admin-guide: README & svga: " Randy Dunlap
2020-09-01 5:40 ` H. Peter Anvin
2020-09-01 5:38 ` [RFC PATCH 2/2] Documentation/admin-guide: blockdev/ramdisk: " Randy Dunlap
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=20200901053822.9374-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=kzak@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-video@atrey.karlin.mff.cuni.cz \
--cc=mj@ucw.cz \
--cc=paul.gortmaker@windriver.com \
--cc=viro@zeniv.linux.org.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
all inboxes | Powered by JetHome®