From: Colin King <colin.king@canonical.com>
To: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Kévin L'hôpital" <kevin.lhopital@bootlin.com>,
linux-media@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] media: i2c: fix spelling mistakes: "enpoint" -> "endpoint"
Date: Wed, 13 Jan 2021 10:05:17 +0000 [thread overview]
Message-ID: <20210113100517.10959-1-colin.king@canonical.com> (raw)
From: Colin Ian King <colin.king@canonical.com>
There are two spelling mistakes in dev_err messages. Fix these.
Signed-off-by: Colin Ian King <colin.king@canonical.com>
---
drivers/media/i2c/ov5648.c | 2 +-
drivers/media/i2c/ov8865.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/ov5648.c b/drivers/media/i2c/ov5648.c
index 609aa67b54ce..46ad0a539853 100644
--- a/drivers/media/i2c/ov5648.c
+++ b/drivers/media/i2c/ov5648.c
@@ -2453,7 +2453,7 @@ static int ov5648_probe(struct i2c_client *client)
handle = fwnode_graph_get_next_endpoint(dev_fwnode(dev), NULL);
if (!handle) {
- dev_err(dev, "unable to find enpoint node\n");
+ dev_err(dev, "unable to find endpoint node\n");
return -EINVAL;
}
diff --git a/drivers/media/i2c/ov8865.c b/drivers/media/i2c/ov8865.c
index fda5a55979aa..fd5be8ef079c 100644
--- a/drivers/media/i2c/ov8865.c
+++ b/drivers/media/i2c/ov8865.c
@@ -2799,7 +2799,7 @@ static int ov8865_probe(struct i2c_client *client)
handle = fwnode_graph_get_next_endpoint(dev_fwnode(dev), NULL);
if (!handle) {
- dev_err(dev, "unable to find enpoint node\n");
+ dev_err(dev, "unable to find endpoint node\n");
return -EINVAL;
}
--
2.29.2
next reply other threads:[~2021-01-13 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 10:05 Colin King [this message]
2021-01-14 8:49 ` [PATCH][next] media: i2c: fix spelling mistakes: "enpoint" -> "endpoint" Paul Kocialkowski
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=20210113100517.10959-1-colin.king@canonical.com \
--to=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kevin.lhopital@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=sakari.ailus@linux.intel.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