From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: [PATCH 2/2] btrfs-progs: Describe device scan -d is a deprecated option in manpage
Date: Thu, 10 Mar 2016 08:08:31 +0900 [thread overview]
Message-ID: <56E0ACEF.5050701@jp.fujitsu.com> (raw)
In-Reply-To: <56E0AC1B.3020405@jp.fujitsu.com>
It's already marked as deprecated in cmd_device_scan_usage().
commit 5444864e5605 ("btrfs-progs: remove BTRFS_SCAN_PROC scan method")
Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
---
Documentation/btrfs-device.asciidoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/btrfs-device.asciidoc b/Documentation/btrfs-device.asciidoc
index bd878f4..bf16a94 100644
--- a/Documentation/btrfs-device.asciidoc
+++ b/Documentation/btrfs-device.asciidoc
@@ -89,8 +89,8 @@ Scan devices for a btrfs filesystem.
If one or more devices are passed, these are scanned for a btrfs filesystem.
If no devices are passed, btrfs uses block devices containing btrfs
filesystem as listed by blkid.
-Finally, if '--all-devices' or '-d' is passed, all the devices under /dev are
-scanned.
+Finally, '--all-devices' or '-d' is the deprecated option. If it is passed,
+its behavior is the same as if no devices are passed.
*stats* [-z] <path>|<device>::
Read and print the device IO stats for all mounted devices of the filesystem
--
2.7.0
next prev parent reply other threads:[~2016-03-09 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 23:04 [PATCH 1/2] btrfs-progs: Remove unnecessary variable devstart from cmd_device_scan() Satoru Takeuchi
2016-03-09 23:08 ` Satoru Takeuchi [this message]
2016-03-10 13:36 ` [PATCH 2/2] btrfs-progs: Describe device scan -d is a deprecated option in manpage David Sterba
2016-03-10 13:27 ` [PATCH 1/2] btrfs-progs: Remove unnecessary variable devstart from cmd_device_scan() David Sterba
2016-03-10 23:18 ` Satoru Takeuchi
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=56E0ACEF.5050701@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=linux-btrfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.