mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] of: base: of_new_property(): use xstrdup() instead of strdup()
Date: Wed, 19 Apr 2017 13:20:26 +0300	[thread overview]
Message-ID: <20170419132026.5ac56ed0b7fc52b8ad61477d@gmail.com> (raw)
In-Reply-To: <20170417104210.8196-3-antonynpavlov@gmail.com>

On Mon, 17 Apr 2017 13:42:10 +0300
Antony Pavlov <antonynpavlov@gmail.com> wrote:

> At the moment of_new_property() uses xfunctions for memory
> allocation so we can use xstrdup() instead of strdup()
> for code simplification.
> 
> A side effect of this commmit is that
> the of_new_property() function can't return NULL
> anymore if CONFIG_OFTREE is set.

If of_new_property() can't return NULL we can skip all numerous
checks after of_new_property() call. So the checks are actual only
if CONFIG_OFTREE isn't set.

Have you any sugestions on removing of_new_property() return value checks?


> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> ---
>  drivers/of/base.c | 7 +------
>  1 file changed, 1 insertion(+), 6 deletions(-)
> 
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 1161ce9793..c9bdd91810 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -1802,12 +1802,7 @@ struct property *of_new_property(struct device_node *node, const char *name,
>  	struct property *prop;
>  
>  	prop = xzalloc(sizeof(*prop));
> -	prop->name = strdup(name);
> -	if (!prop->name) {
> -		free(prop);
> -		return NULL;
> -	}
> -
> +	prop->name = xstrdup(name);
>  	prop->length = len;
>  	prop->value = xzalloc(len);
>  
> -- 
> 2.11.0
> 


-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-04-19 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 10:42 [PATCH 0/2] of: base: some simplifications Antony Pavlov
2017-04-17 10:42 ` [PATCH 1/2] of: base: exclude memcpy-like code from of_property_write_u8_array() Antony Pavlov
2017-04-17 10:42 ` [PATCH 2/2] of: base: of_new_property(): use xstrdup() instead of strdup() Antony Pavlov
2017-04-19 10:20   ` Antony Pavlov [this message]
2017-04-19 10:19     ` Sascha Hauer
2017-04-19  9:47 ` [PATCH 0/2] of: base: some simplifications Sascha Hauer

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=20170419132026.5ac56ed0b7fc52b8ad61477d@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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