From: Sascha Hauer <s.hauer@pengutronix.de>
To: Cory Tusar <Cory.Tusar@zii.aero>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
Chris Healy <Chris.Healy@zii.aero>
Subject: Re: [PATCH] ARM: zii-vf610-dev: Trivial spelling fix
Date: Mon, 17 Jun 2019 14:23:05 +0200 [thread overview]
Message-ID: <20190617122305.nd4g7tmajwvhjri6@pengutronix.de> (raw)
In-Reply-To: <20190614225432.31624-1-cory.tusar@zii.aero>
On Fri, Jun 14, 2019 at 10:58:32PM +0000, Cory Tusar wrote:
> s/Couln't/Couldn't/
>
> Signed-off-by: Cory Tusar <cory.tusar@zii.aero>
> ---
> arch/arm/boards/zii-vf610-dev/board.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks
Sascha
>
> diff --git a/arch/arm/boards/zii-vf610-dev/board.c b/arch/arm/boards/zii-vf610-dev/board.c
> index 90d453568..0697a1660 100644
> --- a/arch/arm/boards/zii-vf610-dev/board.c
> +++ b/arch/arm/boards/zii-vf610-dev/board.c
> @@ -91,7 +91,7 @@ static int zii_vf610_dev_print_clocks(void)
>
> ccm_np = of_find_compatible_node(NULL, NULL, "fsl,vf610-ccm");
> if (!ccm_np) {
> - pr_err("Couln't get CCM node\n");
> + pr_err("Couldn't get CCM node\n");
> return -ENOENT;
> }
>
> --
> 2.21.0
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-06-17 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 22:58 Cory Tusar
2019-06-17 12:23 ` Sascha Hauer [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=20190617122305.nd4g7tmajwvhjri6@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Chris.Healy@zii.aero \
--cc=Cory.Tusar@zii.aero \
--cc=barebox@lists.infradead.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