On Wed, Jul 1, 2015 at 3:10 AM, Tomeu Vizoso <tomeu.vizoso@xxxxxxxxxxxxx> wrote: > So code that isn't protected by CONFIG_OF can still build. Is something in mainline/next broken? If not do you have a user? > > Signed-off-by: Tomeu Vizoso <tomeu.vizoso@xxxxxxxxxxxxx> > --- > include/linux/of.h | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/include/linux/of.h b/include/linux/of.h > index edc068d..8922448 100644 > --- a/include/linux/of.h > +++ b/include/linux/of.h > @@ -673,6 +673,9 @@ static inline void of_property_clear_flag(struct property *p, unsigned long flag > > #define of_match_ptr(_ptr) NULL > #define of_match_node(_matches, _node) NULL > +#define for_each_property_of_node(dn, pp) \ > + for (; NULL; ) > + We normally add empty functions that the iterator calls rather than an empty for loop. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
