From: "Bruno Sobreira França" <brunofrancadevsec@gmail.com>
Cc: "Bruno Sobreira França" <brunofrancadevsec@gmail.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Gabriel Somlo" <gsomlo@gmail.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] soc/tegra: Resolve a spelling error in the tegra194-cbb.c
Date: Wed, 22 Oct 2025 01:54:54 +0000 [thread overview]
Message-ID: <20251022015511.7257-1-brunofrancadevsec@gmail.com> (raw)
I aim to join the Linux Kernel Mentorship Program, so I'm currently a
ddressinng minor issues in the kernel.
Signed-off-by: Bruno Sobreira França <brunofrancadevsec@gmail.com>
---
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..9a52cd3aea65 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 transacation 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:
--
2.43.0
next reply other threads:[~2025-10-22 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 1:54 Bruno Sobreira França [this message]
2025-10-22 7:00 ` [PATCH] soc/tegra: Resolve a spelling error in the tegra194-cbb.c 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=20251022015511.7257-1-brunofrancadevsec@gmail.com \
--to=brunofrancadevsec@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=arnd@arndb.de \
--cc=gsomlo@gmail.com \
--cc=jonathanh@nvidia.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;
as well as URLs for NNTP newsgroup(s).