All of lore.kernel.org
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] of: fix incorrect return value of of_find_matching_node_and_match()
Date: Sun, 20 Jan 2013 21:27:53 -0600	[thread overview]
Message-ID: <50FCB5B9.8000802@gmail.com> (raw)
In-Reply-To: <CAJuYYwT++66UUT5wdZh=B=VC7s2=T4w0qO6G7CEG6eCHT5WBCg@mail.gmail.com>

On 01/20/2013 03:56 PM, Thomas Abraham wrote:
> On 20 January 2013 13:50, Rob Herring <robherring2@gmail.com> wrote:
>> On 01/19/2013 12:20 PM, Thomas Abraham wrote:
>>> The of_find_matching_node_and_match() function incorrectly sets the matched
>>> entry to 'matches' when the compatible value of a node matches one of the
>>> possible values. This results in incorrectly selecting the the first entry in
>>> the 'matches' list as the matched entry. Fix this by noting down the result of
>>> the call to of_match_node() and setting that as the matched entry.
>>
>> Looks fine, but is this breaking something in 3.8 or can it wait for 3.9?
> 
> Yes, it can wait for 3.9. I am using this function while adding device
> tree support for timers on exynos platform which will probably merged
> in 3.9.

Applied for 3.9. It's in my for-next branch on sources.calxeda.com. This
is a stable branch.

Rob

> 
> Thanks,
> Thomas.
> 
>>
>> Rob
>>
>>>
>>> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
>>> ---
>>>  drivers/of/base.c |    6 ++++--
>>>  1 files changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/of/base.c b/drivers/of/base.c
>>> index 2390ddb..960ae5b 100644
>>> --- a/drivers/of/base.c
>>> +++ b/drivers/of/base.c
>>> @@ -612,6 +612,7 @@ struct device_node *of_find_matching_node_and_match(struct device_node *from,
>>>                                       const struct of_device_id **match)
>>>  {
>>>       struct device_node *np;
>>> +     const struct of_device_id *m;
>>>
>>>       if (match)
>>>               *match = NULL;
>>> @@ -619,9 +620,10 @@ struct device_node *of_find_matching_node_and_match(struct device_node *from,
>>>       read_lock(&devtree_lock);
>>>       np = from ? from->allnext : of_allnodes;
>>>       for (; np; np = np->allnext) {
>>> -             if (of_match_node(matches, np) && of_node_get(np)) {
>>> +             m = of_match_node(matches, np);
>>> +             if (m && of_node_get(np)) {
>>>                       if (match)
>>> -                             *match = matches;
>>> +                             *match = m;
>>>                       break;
>>>               }
>>>       }
>>>

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Thomas Abraham <thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] of: fix incorrect return value of of_find_matching_node_and_match()
Date: Sun, 20 Jan 2013 21:27:53 -0600	[thread overview]
Message-ID: <50FCB5B9.8000802@gmail.com> (raw)
In-Reply-To: <CAJuYYwT++66UUT5wdZh=B=VC7s2=T4w0qO6G7CEG6eCHT5WBCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 01/20/2013 03:56 PM, Thomas Abraham wrote:
> On 20 January 2013 13:50, Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> On 01/19/2013 12:20 PM, Thomas Abraham wrote:
>>> The of_find_matching_node_and_match() function incorrectly sets the matched
>>> entry to 'matches' when the compatible value of a node matches one of the
>>> possible values. This results in incorrectly selecting the the first entry in
>>> the 'matches' list as the matched entry. Fix this by noting down the result of
>>> the call to of_match_node() and setting that as the matched entry.
>>
>> Looks fine, but is this breaking something in 3.8 or can it wait for 3.9?
> 
> Yes, it can wait for 3.9. I am using this function while adding device
> tree support for timers on exynos platform which will probably merged
> in 3.9.

Applied for 3.9. It's in my for-next branch on sources.calxeda.com. This
is a stable branch.

Rob

> 
> Thanks,
> Thomas.
> 
>>
>> Rob
>>
>>>
>>> Signed-off-by: Thomas Abraham <thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>>> ---
>>>  drivers/of/base.c |    6 ++++--
>>>  1 files changed, 4 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/of/base.c b/drivers/of/base.c
>>> index 2390ddb..960ae5b 100644
>>> --- a/drivers/of/base.c
>>> +++ b/drivers/of/base.c
>>> @@ -612,6 +612,7 @@ struct device_node *of_find_matching_node_and_match(struct device_node *from,
>>>                                       const struct of_device_id **match)
>>>  {
>>>       struct device_node *np;
>>> +     const struct of_device_id *m;
>>>
>>>       if (match)
>>>               *match = NULL;
>>> @@ -619,9 +620,10 @@ struct device_node *of_find_matching_node_and_match(struct device_node *from,
>>>       read_lock(&devtree_lock);
>>>       np = from ? from->allnext : of_allnodes;
>>>       for (; np; np = np->allnext) {
>>> -             if (of_match_node(matches, np) && of_node_get(np)) {
>>> +             m = of_match_node(matches, np);
>>> +             if (m && of_node_get(np)) {
>>>                       if (match)
>>> -                             *match = matches;
>>> +                             *match = m;
>>>                       break;
>>>               }
>>>       }
>>>

  reply	other threads:[~2013-01-21  3:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 18:20 [PATCH] of: fix incorrect return value of of_find_matching_node_and_match() Thomas Abraham
2013-01-19 18:27 ` Thomas Abraham
2013-01-20 21:50 ` Rob Herring
2013-01-20 21:50   ` Rob Herring
2013-01-20 21:56   ` Thomas Abraham
2013-01-20 21:56     ` Thomas Abraham
2013-01-21  3:27     ` Rob Herring [this message]
2013-01-21  3:27       ` Rob Herring
2013-01-21  3:48       ` Thomas Abraham
2013-01-21  3:48         ` Thomas Abraham

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=50FCB5B9.8000802@gmail.com \
    --to=robherring2@gmail.com \
    --cc=linux-arm-kernel@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 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.