From: Jon Hunter <jonathanh@nvidia.com>
To: "Bruno Sobreira França" <brunofrancadevsec@gmail.com>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"Gabriel Somlo" <gsomlo@gmail.com>,
"Herve Codina" <herve.codina@bootlin.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] soc/tegra: Resolve a spelling error in the tegra194-cbb.c
Date: Thu, 23 Oct 2025 15:24:23 +0100 [thread overview]
Message-ID: <4a8decc1-3538-4040-898c-20a8e6d43617@nvidia.com> (raw)
In-Reply-To: <20251022174531.1751-1-brunofrancadevsec@gmail.com>
On 22/10/2025 18:45, Bruno Sobreira França wrote:
> Hi, this commit resolves a spelling error in the tegra194-cbb.c.
>
> Signed-off-by: Bruno Sobreira França <brunofrancadevsec@gmail.com>
> ---
> Changes in v2
> - Really fix the spelling error
> ---
> drivers/soc/tegra/cbb/tegra194-cbb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/soc/tegra/cbb/tegra194-cbb.c b/drivers/soc/tegra/cbb/tegra194-cbb.c
> index 846b17ffc2f9..e1deda188fdb 100644
> --- a/drivers/soc/tegra/cbb/tegra194-cbb.c
> +++ b/drivers/soc/tegra/cbb/tegra194-cbb.c
> @@ -1836,7 +1836,7 @@ print_errlog1_2(struct seq_file *file, struct tegra194_cbb *cbb,
> }
>
> /*
> - * Print transcation type, error code and description from ErrLog0 for all
> + * Print transaction type, error code and description from ErrLog0 for all
> * errors. For NOC slave errors, all relevant error info is printed using
> * ErrLog0 only. But additional information is printed for errors from
> * APB slaves because for them:
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2025-10-23 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 17:45 [PATCH v2] soc/tegra: Resolve a spelling error in the tegra194-cbb.c Bruno Sobreira França
2025-10-23 6:12 ` Herve Codina
2025-10-23 14:24 ` Jon Hunter [this message]
2025-10-23 16:16 ` Uwe Kleine-König
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=4a8decc1-3538-4040-898c-20a8e6d43617@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=andersson@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=brunofrancadevsec@gmail.com \
--cc=gsomlo@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@baylibre.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