mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH] dtc: fix spelling mistake "mmory" -> "memory"
Date: Thu, 17 Oct 2019 14:08:12 -0500	[thread overview]
Message-ID: <4aa3bcde-1ad1-98ec-8deb-4a8ab1bbb41c@gmail.com> (raw)
In-Reply-To: <20190911093123.11312-1-colin.king@canonical.com>

Hi Rob,


On 09/11/2019 04:31, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> There is a spelling mistake in an error message. Fix it.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  scripts/dtc/fdtput.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/dtc/fdtput.c b/scripts/dtc/fdtput.c
> index a363c3cabc59..3755e5f68a5a 100644
> --- a/scripts/dtc/fdtput.c
> +++ b/scripts/dtc/fdtput.c
> @@ -84,7 +84,7 @@ static int encode_value(struct display_info *disp, char **arg, int arg_count,
>  			value_size = (upto + len) + 500;
>  			value = realloc(value, value_size);
>  			if (!value) {
> -				fprintf(stderr, "Out of mmory: cannot alloc "
> +				fprintf(stderr, "Out of memory: cannot alloc "
>  					"%d bytes\n", value_size);
>  				return -1;
>  			}
> 

This is a very old version of the upstream file.  update-dtc-source.sh does
not pull new versions of this file.

We don't actually build fdtput, is there any reason to not just remove
scripts/dtc/fdtput.c?

-Frank

  reply	other threads:[~2019-10-17 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  9:31 Colin King
2019-10-17 19:08 ` Frank Rowand [this message]
2019-10-20 18:56   ` 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=4aa3bcde-1ad1-98ec-8deb-4a8ab1bbb41c@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

Powered by JetHome