From: Bagas Sanjaya <bagasdotme@gmail•com>
To: Vegard Nossum <vegard.nossum@oracle•com>,
Suzuki K Poulose <suzuki.poulose@arm•com>,
Mike Leach <mike.leach@linaro•org>,
James Clark <james.clark@arm•com>, Leo Yan <leo.yan@linaro•org>,
Jonathan Corbet <corbet@lwn•net>
Cc: coresight@lists•linaro.org, linux-arm-kernel@lists•infradead.org,
linux-doc@vger•kernel.org, linux-kernel@vger•kernel.org,
Mathieu Poirier <mathieu.poirier@linaro•org>,
Rob Herring <robh@kernel•org>,
linux-next@vger•kernel.org,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: [PATCH] Documentation: coresight: fix `make refcheckdocs` warning
Date: Mon, 23 Oct 2023 11:53:56 +0700 [thread overview]
Message-ID: <ZTX8ZPY3NQE_5cGX@debian.me> (raw)
In-Reply-To: <20231022185806.919434-1-vegard.nossum@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
On Sun, Oct 22, 2023 at 08:58:06PM +0200, Vegard Nossum wrote:
> -See Documentation/devicetree/bindings/arm/arm,coresight-\*.yaml for details.
> +See ``Documentation/devicetree/bindings/arm/arm,coresight-*.yaml`` for details.
Oh, I should have inlined that path when I fixed the original warning. Anyway,
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail•com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-23 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 18:58 [PATCH] Documentation: coresight: fix `make refcheckdocs` warning Vegard Nossum
2023-10-23 4:53 ` Bagas Sanjaya [this message]
2023-10-25 10:22 ` Suzuki K Poulose
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=ZTX8ZPY3NQE_5cGX@debian.me \
--to=bagasdotme@gmail$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=coresight@lists$(echo .)linaro.org \
--cc=james.clark@arm$(echo .)com \
--cc=leo.yan@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mathieu.poirier@linaro$(echo .)org \
--cc=mike.leach@linaro$(echo .)org \
--cc=robh@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=suzuki.poulose@arm$(echo .)com \
--cc=vegard.nossum@oracle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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