[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1451386623.30729.353.camel@linux.intel.com>
Date: Tue, 29 Dec 2015 12:57:03 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>, linux-acpi@...r.kernel.org
Subject: Re: [PATCH v2 2/3] device property: the secondary fwnode needs to
depend on the primary
On Tue, 2015-12-29 at 10:40 +0200, Heikki Krogerus wrote:
> Hi Andy,
>
> Found a bug from my code..
>
> > diff --git a/drivers/base/property.c b/drivers/base/property.c
> > index 0b22c8a..6c04d18 100644
> > --- a/drivers/base/property.c
> > +++ b/drivers/base/property.c
> > @@ -218,7 +218,7 @@ bool fwnode_property_present(struct
> > fwnode_handle *fwnode, const char *propname)
> > bool ret;
> >
> > ret = __fwnode_property_present(fwnode, propname);
> > - if (ret == false && fwnode->secondary)
> > + if (ret == false && fwnode && fwnode->secondary)
> > ret = __fwnode_property_present(fwnode->secondary,
> > propname);
> > return ret;
> > }
> > @@ -423,7 +423,7 @@
> > EXPORT_SYMBOL_GPL(device_property_match_string);
> > int _ret_;
> > \
> > _ret_ = FWNODE_PROP_READ(_fwnode_, _propname_, _type_,
> > _proptype_, \
> > _val_, _nval_);
> > \
> > - if (_ret_ == -EINVAL && _fwnode_->secondary)
> > \
> > + if (_ret_ == -EINVAL && fwnode && _fwnode_->secondary)
> > \
>
> This should be .._fwnode_ && _fwnode_->secondary)
Yeah, we compiled it correctly due to fwnode presents in all
occurrences of this macro.
I will fix and resend a new version.
>
> > _ret_ = FWNODE_PROP_READ(_fwnode_->secondary,
> > _propname_, _type_, \
> > _proptype_, _val_, _nval_);
> > \
> > _ret_;
> > \
>
>
> Cheers,
>
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists