From: Jonathan Corbet <corbet@lwn.net>
To: Simon Horman <simon.horman@corigine.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
oss-drivers@corigine.com
Subject: Re: [PATCH] docs: arm: tcm: Fix typo in description of TCM and MMU usage
Date: Thu, 09 Jun 2022 10:01:01 -0600 [thread overview]
Message-ID: <87fskd4yiq.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220603112729.222398-1-simon.horman@corigine.com>
Simon Horman <simon.horman@corigine.com> writes:
> Correct a typo in the description of interaction between
> the TCM and MMU.
>
> Found by inspection.
>
> Signed-off-by: Louis Peens <louis.peens@corigine.com>
> Signed-off-by: Simon Horman <simon.horman@corigine.com>
Here too I have to ask: what does this signoff chain mean? If two
developers were needed for a single-character typo fix, then a
Co-developed-by line is appropriate. If you are forwarding a patch from
Louis, then a From: line to get the authorship right is indicated ... ?
> Documentation/arm/tcm.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/arm/tcm.rst b/Documentation/arm/tcm.rst
> index b256f9783883..1dc6c39220f9 100644
> --- a/Documentation/arm/tcm.rst
> +++ b/Documentation/arm/tcm.rst
> @@ -34,7 +34,7 @@ CPU so it is usually wise not to overlap any physical RAM with
> the TCM.
>
> The TCM memory can then be remapped to another address again using
> -the MMU, but notice that the TCM if often used in situations where
> +the MMU, but notice that the TCM is often used in situations where
> the MMU is turned off. To avoid confusion the current Linux
> implementation will map the TCM 1 to 1 from physical to virtual
Thanks,
jon
next prev parent reply other threads:[~2022-06-09 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 11:27 [PATCH] docs: arm: tcm: Fix typo in description of TCM and MMU usage Simon Horman
2022-06-09 16:01 ` Jonathan Corbet [this message]
2022-06-09 16:44 ` Simon Horman
2022-06-09 17:27 ` Jonathan Corbet
2022-06-09 17:54 ` Simon Horman
2022-06-09 18:26 ` Jonathan Corbet
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=87fskd4yiq.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=simon.horman@corigine.com \
/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).