From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: linuxppc-dev@ozlabs.org
Cc: linux-kernel@vger.kernel.org,kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] powerpc/mpc5xxx: Use of_get_next_parent to simplify code
Date: Mon, 12 Oct 2015 07:05:11 +0200 [thread overview]
Message-ID: <mvff27$jm4$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1510112243420.2096@localhost6.localdomain6>
Le 11/10/2015 22:44, Julia Lawall a écrit :
>
>> of_get_next_parent can be used to simplify the while() loop and
>> avoid the need of a temp variable.
> Can you do something with the loop in __of_translate_address, in
> drivers/of/address.c? Is there not an iterator for this?
>
> julia
>
Hi Julia,
There does not seem to be any 'for_each_parent_of_node' or equivalent.
Best regards,
CJ
WARNING: multiple messages have this Message-ID (diff)
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: linux-kernel@vger.kernel.org
Cc: linuxppc-dev@ozlabs.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] powerpc/mpc5xxx: Use of_get_next_parent to simplify code
Date: Mon, 12 Oct 2015 07:05:11 +0200 [thread overview]
Message-ID: <mvff27$jm4$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1510112243420.2096@localhost6.localdomain6>
Le 11/10/2015 22:44, Julia Lawall a écrit :
>
>> of_get_next_parent can be used to simplify the while() loop and
>> avoid the need of a temp variable.
> Can you do something with the loop in __of_translate_address, in
> drivers/of/address.c? Is there not an iterator for this?
>
> julia
>
Hi Julia,
There does not seem to be any 'for_each_parent_of_node' or equivalent.
Best regards,
CJ
next prev parent reply other threads:[~2015-10-12 5:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 20:27 [PATCH] powerpc/mpc5xxx: Use of_get_next_parent to simplify code Christophe JAILLET
2015-10-11 20:27 ` Christophe JAILLET
2015-10-11 20:44 ` Julia Lawall
2015-10-11 20:44 ` Julia Lawall
2015-10-12 5:05 ` Christophe JAILLET [this message]
2015-10-12 5:05 ` Christophe JAILLET
2015-10-14 4:00 ` Michael Ellerman
2015-10-14 4:00 ` Michael Ellerman
2015-10-15 5:56 ` [PATCH v2] powerpc/mpc5xxx: Avoid dereferencing potentially freed memory Christophe JAILLET
2015-10-15 5:56 ` Christophe JAILLET
2015-10-15 6:36 ` Michael Ellerman
2015-10-15 6:36 ` Michael Ellerman
2015-10-16 6:20 ` Christophe JAILLET
2015-10-16 6:20 ` Christophe JAILLET
2015-10-16 7:15 ` Gabriel Paubert
2015-10-16 7:15 ` Gabriel Paubert
2015-10-16 9:49 ` Michael Ellerman
2015-10-16 9:49 ` Michael Ellerman
2015-10-16 20:05 ` Christophe JAILLET
2015-10-16 20:05 ` Christophe JAILLET
2015-10-19 4:38 ` Michael Ellerman
2015-10-19 4:38 ` Michael Ellerman
2015-10-15 11:11 ` powerpc/mpc5xxx: Use of_get_next_parent to simplify code Michael Ellerman
2015-10-15 11:11 ` Michael Ellerman
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='mvff27$jm4$1@ger.gmane.org' \
--to=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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.