mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@linaro.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Darren Hart <darren.hart@intel.com>
Subject: Re: [PATCH 1/1] of: base, fix of_property_read_string_helper kernel-doc
Date: Wed, 26 Nov 2014 13:27:53 +0000	[thread overview]
Message-ID: <20141126132753.CE20FC4099B@trevor.secretlab.ca> (raw)
In-Reply-To: <1416572589-4953-1-git-send-email-jslaby@suse.cz>

On Fri, 21 Nov 2014 13:23:09 +0100
, Jiri Slaby <jslaby@suse.cz>
 wrote:
> It referenced of_property_read_string_util whereas the function name
> is of_property_read_string_helper.
> 
> Introduced in a87fa1d81a9fb5e9adca9820e16008c40ad09f33 (of: Fix
> overflow bug in string property parsing functions). Found out when
> reviewing the stable 3.12 queue.
> 
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Cc: Grant Likely <grant.likely@linaro.org>
> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Darren Hart <darren.hart@intel.com>

Applied, thanks.

g.

> ---
>  drivers/of/base.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 37de43ef22fc..76d8307a1cd5 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -1359,7 +1359,7 @@ int of_property_match_string(struct device_node *np, const char *propname,
>  EXPORT_SYMBOL_GPL(of_property_match_string);
>  
>  /**
> - * of_property_read_string_util() - Utility helper for parsing string properties
> + * of_property_read_string_helper() - Utility helper for parsing string properties
>   * @np:		device node from which the property value is to be read.
>   * @propname:	name of the property to be searched.
>   * @out_strs:	output array of string pointers.
> -- 
> 2.1.3
> 


      reply	other threads:[~2014-11-26 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 12:23 Jiri Slaby
2014-11-26 13:27 ` Grant Likely [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=20141126132753.CE20FC4099B@trevor.secretlab.ca \
    --to=grant.likely@linaro.org \
    --cc=arnd@arndb.de \
    --cc=darren.hart@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --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

all inboxes | Powered by JetHome®