From: Li Zhijian <lizhijian@fujitsu.com>
To: nvdimm@lists.linux.dev, alison.schofield@intel.com
Cc: linux-cxl@vger.kernel.org, Li Zhijian <lizhijian@fujitsu.com>,
Dave Jiang <dave.jiang@intel.com>
Subject: [ndctl PATCH v4 4/4] Documentation/cxl/cxl-monitor.txt: Fix inaccurate description
Date: Tue, 11 Jul 2023 19:53:44 +0800 [thread overview]
Message-ID: <20230711115344.562823-5-lizhijian@fujitsu.com> (raw)
In-Reply-To: <20230711115344.562823-1-lizhijian@fujitsu.com>
No syslog is supported by cxl-monitor
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
---
V2: add Reviewed-by tag
---
Documentation/cxl/cxl-monitor.txt | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/cxl/cxl-monitor.txt b/Documentation/cxl/cxl-monitor.txt
index 3fc992e4d4d9..c284099f16c3 100644
--- a/Documentation/cxl/cxl-monitor.txt
+++ b/Documentation/cxl/cxl-monitor.txt
@@ -39,8 +39,7 @@ OPTIONS
--log=::
Send log messages to the specified destination.
- "<file>":
- Send log messages to specified <file>. When fopen() is not able
- to open <file>, log messages will be forwarded to syslog.
+ Send log messages to specified <file>.
- "standard":
Send messages to standard output.
--
2.29.2
next prev parent reply other threads:[~2023-07-11 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 11:53 [ndctl PATCH v4 0/4] cxl/monitor and ndctl/monitor fixes Li Zhijian
2023-07-11 11:53 ` [ndctl PATCH v4 1/4] cxl/monitor: Enable default_log and refactor sanity check Li Zhijian
2023-07-11 17:57 ` Alison Schofield
2023-07-11 11:53 ` [ndctl PATCH v4 2/4] cxl/monitor: replace monitor.log_file with monitor.ctx.log_file Li Zhijian
2023-07-11 17:57 ` Alison Schofield
2023-07-11 11:53 ` [ndctl PATCH v4 3/4] ndctl: use strcmp for reserved word in monitor commands Li Zhijian
2023-07-11 17:58 ` Alison Schofield
2023-07-11 11:53 ` Li Zhijian [this message]
2023-07-11 17:58 ` [ndctl PATCH v4 4/4] Documentation/cxl/cxl-monitor.txt: Fix inaccurate description Alison Schofield
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=20230711115344.562823-5-lizhijian@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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.