From: Jonathan Corbet <corbet@lwn.net>
To: Jiakai Xu <jiakaipeanut@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>, Jiakai Xu <jiakaiPeanut@gmail.com>
Subject: Re: [PATCH v3] Documentation/admin-guide: fix typo and comment in cscope example
Date: Fri, 21 Nov 2025 10:30:24 -0700 [thread overview]
Message-ID: <87o6ovthsf.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251119065727.3500015-1-jiakaiPeanut@gmail.com>
Jiakai Xu <jiakaipeanut@gmail.com> writes:
> This patch updates the Linux documentation for cscope, fixing two issues:
> 1. Corrects the typo in the command line:
> c"scope -d -p10 -> cscope -d -p10
> 2. Fixes the related documentation comment for clarity and correctness:
> cscope by default cscope.out database.
> ->
> cscope by default uses the cscope.out database.
>
> Signed-off-by: Jiakai Xu <jiakaiPeanut@gmail.com>
> ---
>
> Changes since v2:
> * Fixed line-wrapping issues to ensure patch applies cleanly.
> * Formatting improvements in the commit message.
> Thanks to Jonathan Corbet for pointing out this additional correction.
>
> Changes since v1:
> * Added the second fix for the documentation comment line.
> Thanks to Randy Dunlap for pointing out this additional correction.
>
> References:
> * [PATCH] Documentation/admin-guide: fix typo in cscope command example
> https://lore.kernel.org/linux-doc/6017104c-740d-43db-bc53-58751ec57282@infradead.org/T/#t
> * [PATCH v2] Documentation/admin-guide: fix typo and comment in cscope example
> https://lore.kernel.org/linux-doc/871plv5mlf.fsf@trenco.lwn.net/T/#m10f8ec032dd57eaf7388939da3722c9f4b599b33
> Documentation/admin-guide/workload-tracing.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2025-11-21 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 6:57 Jiakai Xu
2025-11-19 21:29 ` Randy Dunlap
2025-11-21 17:30 ` 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=87o6ovthsf.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=jiakaipeanut@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®