From: Ricardo Ribalda <ribalda@chromium.org>
To: kvm@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
devicetree@vger.kernel.org,
Ricardo Ribalda <ribalda@chromium.org>,
Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] of: overlay: Fix trivial typo
Date: Tue, 20 Dec 2022 23:20:32 +0100 [thread overview]
Message-ID: <20221220-permited-v1-3-52ea9857fa61@chromium.org> (raw)
In-Reply-To: <20221220-permited-v1-0-52ea9857fa61@chromium.org>
Permitted is spelled with two t.
Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
---
drivers/of/overlay.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/of/overlay.c b/drivers/of/overlay.c
index ed4e6c144a68..2e01960f1aeb 100644
--- a/drivers/of/overlay.c
+++ b/drivers/of/overlay.c
@@ -1121,7 +1121,7 @@ static int node_overlaps_later_cs(struct overlay_changeset *remove_ovcs,
* The topmost check is done by exploiting this property. For each
* affected device node in the log list we check if this overlay is
* the one closest to the tail. If another overlay has affected this
- * device node and is closest to the tail, then removal is not permited.
+ * device node and is closest to the tail, then removal is not permitted.
*/
static int overlay_removal_is_ok(struct overlay_changeset *remove_ovcs)
{
--
2.39.0.314.g84b9a713c41-goog-b4-0.11.0-dev-696ae
next prev parent reply other threads:[~2022-12-20 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 22:20 [PATCH 0/3] spelling: Fix some trivial typos Ricardo Ribalda
2022-12-20 22:20 ` [PATCH 1/3] scripts/spelling.txt: Add permitted Ricardo Ribalda
2022-12-20 22:20 ` [PATCH 2/3] KVM: x86: Fix trivial typo Ricardo Ribalda
2022-12-21 12:42 ` Philippe Mathieu-Daudé
2022-12-20 22:20 ` Ricardo Ribalda [this message]
2022-12-21 12:42 ` [PATCH 3/3] of: overlay: " Philippe Mathieu-Daudé
2022-12-22 14:43 ` Rob Herring
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=20221220-permited-v1-3-52ea9857fa61@chromium.org \
--to=ribalda@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@joelfernandes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).