From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/5] checks: Add Warning for stricter node name character checking
Date: Tue, 31 Jan 2017 14:14:34 +1100 [thread overview]
Message-ID: <20170131031434.GK14879@umbus.fritz.box> (raw)
In-Reply-To: <20170124174534.3865-3-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
On Tue, Jan 24, 2017 at 11:45:31AM -0600, Rob Herring wrote:
> While '#', '?', '.', '+', '*', and '_' are considered valid characters,
> their use is discouraged in recommended practices.
>
> Testing this found a few cases of '.'. The majority of the warnings were
> all from underscores.
Hmm. The Opal firmware on POWER8 machines uses both '.' and '#' in
node names in some places. So I'm not terribly convinced this is a
good idea.
> Signed-off-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> ---
> checks.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/checks.c b/checks.c
> index a0d4a9d968d7..0c78d69316bc 100644
> --- a/checks.c
> +++ b/checks.c
> @@ -252,6 +252,17 @@ static void check_node_name_chars(struct check *c, struct dt_info *dti,
> }
> ERROR(node_name_chars, check_node_name_chars, PROPNODECHARS "@");
>
> +static void check_node_name_chars_strict(struct check *c, struct dt_info *dti,
> + struct node *node)
> +{
> + int n = strspn(node->name, c->data);
> +
> + if (n < node->basenamelen)
> + FAIL(c, "Character '%c' not recommended in node %s",
> + node->name[n], node->fullpath);
> +}
> +WARNING(node_name_chars_strict, check_node_name_chars_strict, PROPNODECHARSSTRICT);
> +
> static void check_node_name_format(struct check *c, struct dt_info *dti,
> struct node *node)
> {
> @@ -737,6 +748,7 @@ static struct check *check_table[] = {
> &device_type_is_string, &model_is_string, &status_is_string,
>
> &property_name_chars_strict,
> + &node_name_chars_strict,
>
> &addr_size_cells, ®_format, &ranges_format,
>
--
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 --]
next prev parent reply other threads:[~2017-01-31 3:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 17:45 [PATCH 0/5] dtc unit-address and character set checks Rob Herring
[not found] ` <20170124174534.3865-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-24 17:45 ` [PATCH 1/5] checks: Add Warning for stricter property name character checking Rob Herring
[not found] ` <20170124174534.3865-2-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-31 0:32 ` David Gibson
2017-01-24 17:45 ` [PATCH 2/5] checks: Add Warning for stricter node " Rob Herring
[not found] ` <20170124174534.3865-3-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-31 3:14 ` David Gibson [this message]
[not found] ` <20170131031434.GK14879-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-01-31 13:46 ` Rob Herring
2017-01-24 17:45 ` [PATCH 3/5] checks: Warn on node name unit-addresses with '0x' or leading 0s Rob Herring
[not found] ` <20170124174534.3865-4-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-31 0:17 ` David Gibson
2017-01-24 17:45 ` [PATCH 4/5] checks: Add infrastructure for setting bus type of nodes Rob Herring
[not found] ` <20170124174534.3865-5-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-31 0:26 ` David Gibson
[not found] ` <20170131002634.GD14879-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-02-01 21:54 ` Rob Herring
2017-02-01 21:54 ` Rob Herring
2017-02-06 2:14 ` David Gibson
2017-01-24 17:45 ` [PATCH 5/5] checks: Add bus checks for PCI buses Rob Herring
[not found] ` <20170124174534.3865-6-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-25 22:37 ` Stephen Boyd
2017-01-27 22:54 ` 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=20170131031434.GK14879@umbus.fritz.box \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.