From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Benjamin Fair <b-fair-l0cyMroinI0@public.gmane.org>
Cc: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] libfdt: add missing errors to fdt_strerror()
Date: Fri, 4 Nov 2016 07:18:59 +1100 [thread overview]
Message-ID: <20161103201859.GA4282@umbus> (raw)
In-Reply-To: <1478188062-8219-1-git-send-email-b-fair-l0cyMroinI0@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Thu, Nov 03, 2016 at 10:47:42AM -0500, Benjamin Fair wrote:
> Some error values were missing from the table which meant that they could
> not be translated by fdt_strerror().
>
> Signed-off-by: Benjamin Fair <b-fair-l0cyMroinI0@public.gmane.org>
Applied, thanks.
> ---
> libfdt/fdt_strerror.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/libfdt/fdt_strerror.c b/libfdt/fdt_strerror.c
> index 4ab3eb7..9677a18 100644
> --- a/libfdt/fdt_strerror.c
> +++ b/libfdt/fdt_strerror.c
> @@ -77,6 +77,9 @@ static struct fdt_errtabent fdt_errtable[] = {
> FDT_ERRTABENT(FDT_ERR_BADVERSION),
> FDT_ERRTABENT(FDT_ERR_BADSTRUCTURE),
> FDT_ERRTABENT(FDT_ERR_BADLAYOUT),
> + FDT_ERRTABENT(FDT_ERR_INTERNAL),
> + FDT_ERRTABENT(FDT_ERR_BADNCELLS),
> + FDT_ERRTABENT(FDT_ERR_BADVALUE),
> FDT_ERRTABENT(FDT_ERR_BADOVERLAY),
> FDT_ERRTABENT(FDT_ERR_NOPHANDLES),
> };
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-11-03 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 15:47 [PATCH] libfdt: add missing errors to fdt_strerror() Benjamin Fair
[not found] ` <1478188062-8219-1-git-send-email-b-fair-l0cyMroinI0@public.gmane.org>
2016-11-03 20:18 ` David Gibson [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=20161103201859.GA4282@umbus \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=b-fair-l0cyMroinI0@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jdl-CYoMK+44s/E@public.gmane.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).