From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.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>,
linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/2] Documentation/admin-guide: remove use of "rdev"
Date: Thu, 24 Sep 2020 10:50:57 -0600 [thread overview]
Message-ID: <20200924105057.00fa0cf8@lwn.net> (raw)
In-Reply-To: <20200918015640.8439-1-rdunlap@infradead.org>
On Thu, 17 Sep 2020 18:56:38 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> Remove mention of using "rdev" to set boot device, video mode,
> or ramdisk information for the booting kernel.
>
>
> 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"
Applied, thanks.
jon
prev parent reply other threads:[~2020-09-24 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 1:56 Randy Dunlap
2020-09-18 1:56 ` [RFC PATCH v2 1/2] Documentation/admin-guide: README & svga: " Randy Dunlap
2020-09-20 14:55 ` Martin Mareš
2020-09-18 1:56 ` [RFC PATCH v2 2/2] Documentation/admin-guide: blockdev/ramdisk: " Randy Dunlap
2020-09-24 16:50 ` Jonathan Corbet [this message]
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=20200924105057.00fa0cf8@lwn.net \
--to=corbet@lwn.net \
--cc=axboe@kernel.dk \
--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=rdunlap@infradead.org \
--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®