From: Frank Rowand <frowand.list@gmail.com>
To: Colin King <colin.king@canonical.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/dtc: fix spelling mistake "endpont" -> "endpoint"
Date: Tue, 16 Apr 2019 11:17:09 -0700 [thread overview]
Message-ID: <2c66cb65-fd22-39f8-4446-fc0cfd611e00@gmail.com> (raw)
In-Reply-To: <20190416111214.22107-1-colin.king@canonical.com>
Hi Colin,
On 4/16/19 4:12 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a FAIL message, fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> scripts/dtc/checks.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/dtc/checks.c b/scripts/dtc/checks.c
> index 4834e44b37b2..faddf6a57236 100644
> --- a/scripts/dtc/checks.c
> +++ b/scripts/dtc/checks.c
> @@ -1714,7 +1714,7 @@ static void check_graph_endpoint(struct check *c, struct dt_info *dti,
> return;
>
> if (!strprefixeq(node->name, node->basenamelen, "endpoint"))
> - FAIL(c, dti, node, "graph endpont node name should be 'endpoint'");
> + FAIL(c, dti, node, "graph endpoint node name should be 'endpoint'");
>
> check_graph_reg(c, dti, node);
>
>
Thanks for catching the error.
This file is imported from an upstream project. The error is fixed upstream in
commit 4762ad051ee0 ("checks: Fix spelling in check_graph_endpoint") in the
devicetree tools project. Rob pulls the changes from this project on a
periodic basis.
-Frank
prev parent reply other threads:[~2019-04-16 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 11:12 Colin King
2019-04-16 13:16 ` Mukesh Ojha
2019-04-16 18:17 ` Frank Rowand [this message]
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=2c66cb65-fd22-39f8-4446-fc0cfd611e00@gmail.com \
--to=frowand.list@gmail.com \
--cc=colin.king@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®