From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Mikulas Patocka <mpatocka@redhat.com>,
Ross Zwisler <zwisler@kernel.org>,
Colin Ian King <colin.king@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
dm-devel@redhat.com, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Documentation: dm writecache: documentation fixes
Date: Sat, 2 Jul 2022 11:23:48 +0700 [thread overview]
Message-ID: <20220702042350.23187-1-bagasdotme@gmail.com> (raw)
Two small documentation fixes for writecache functionality of device
mapper. The shortlog below should be self-explanatory.
Cc: Alasdair Kergon <agk@redhat.com>
Cc: Mike Snitzer <snitzer@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Mikulas Patocka <mpatocka@redhat.com>
Cc: Ross Zwisler <zwisler@kernel.org>
Cc: Colin Ian King <colin.king@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: dm-devel@redhat.com
Cc: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Bagas Sanjaya (2):
Documentation: dm writecache: Add missing blank line before optional
parameters
Documentation: dm writecache: Render status list as list
Documentation/admin-guide/device-mapper/writecache.rst | 2 ++
1 file changed, 2 insertions(+)
base-commit: 089866061428ec9bf67221247c936792078c41a4
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2022-07-02 4:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 4:23 Bagas Sanjaya [this message]
2022-07-02 4:23 ` [PATCH 1/2] Documentation: dm writecache: Add missing blank line before optional parameters Bagas Sanjaya
2022-07-02 4:23 ` [PATCH 2/2] Documentation: dm writecache: Render status list as list Bagas Sanjaya
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=20220702042350.23187-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=agk@redhat.com \
--cc=colin.king@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zwisler@kernel.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).