Re: [PATCH v2 0/9] of: fix compatible-child-node lookups

2018-10-24 Thread Johan Hovold
On Tue, Oct 23, 2018 at 01:32:56PM -0500, Rob Herring wrote: > On Tue, Oct 23, 2018 at 4:21 AM Johan Hovold wrote: > > > > Hi Rob, > > > > On Tue, Sep 04, 2018 at 03:05:57PM +0200, Johan Hovold wrote: > > > I think Rob will be picking up any patches that remain by the end of the > > > release

Re: [PATCH v2 0/9] of: fix compatible-child-node lookups

2018-10-24 Thread Johan Hovold
On Tue, Oct 23, 2018 at 01:32:56PM -0500, Rob Herring wrote: > On Tue, Oct 23, 2018 at 4:21 AM Johan Hovold wrote: > > > > Hi Rob, > > > > On Tue, Sep 04, 2018 at 03:05:57PM +0200, Johan Hovold wrote: > > > I think Rob will be picking up any patches that remain by the end of the > > > release

Re: [PATCH v2 0/9] of: fix compatible-child-node lookups

2018-10-23 Thread Rob Herring
On Tue, Oct 23, 2018 at 4:21 AM Johan Hovold wrote: > > Hi Rob, > > On Tue, Sep 04, 2018 at 03:05:57PM +0200, Johan Hovold wrote: > > Hi all, > > > > On Mon, Aug 27, 2018 at 10:21:44AM +0200, Johan Hovold wrote: > > > Several drivers currently use of_find_compatible_node() to lookup child > > >

Re: [PATCH v2 0/9] of: fix compatible-child-node lookups

2018-10-23 Thread Rob Herring
On Tue, Oct 23, 2018 at 4:21 AM Johan Hovold wrote: > > Hi Rob, > > On Tue, Sep 04, 2018 at 03:05:57PM +0200, Johan Hovold wrote: > > Hi all, > > > > On Mon, Aug 27, 2018 at 10:21:44AM +0200, Johan Hovold wrote: > > > Several drivers currently use of_find_compatible_node() to lookup child > > >

Re: [PATCH v2 0/9] of: fix compatible-child-node lookups

2018-10-23 Thread Johan Hovold
Hi Rob, On Tue, Sep 04, 2018 at 03:05:57PM +0200, Johan Hovold wrote: > Hi all, > > On Mon, Aug 27, 2018 at 10:21:44AM +0200, Johan Hovold wrote: > > Several drivers currently use of_find_compatible_node() to lookup child > > nodes while failing to notice that the of_find_ functions search the >

Re: [PATCH v2 0/9] of: fix compatible-child-node lookups

2018-10-23 Thread Johan Hovold
Hi Rob, On Tue, Sep 04, 2018 at 03:05:57PM +0200, Johan Hovold wrote: > Hi all, > > On Mon, Aug 27, 2018 at 10:21:44AM +0200, Johan Hovold wrote: > > Several drivers currently use of_find_compatible_node() to lookup child > > nodes while failing to notice that the of_find_ functions search the >

Re: [PATCH v2 0/9] of: fix compatible-child-node lookups

2018-09-04 Thread Johan Hovold
Hi all, On Mon, Aug 27, 2018 at 10:21:44AM +0200, Johan Hovold wrote: > Several drivers currently use of_find_compatible_node() to lookup child > nodes while failing to notice that the of_find_ functions search the > entire tree depth-first (from a given start node) and therefore can > match

Re: [PATCH v2 0/9] of: fix compatible-child-node lookups

2018-09-04 Thread Johan Hovold
Hi all, On Mon, Aug 27, 2018 at 10:21:44AM +0200, Johan Hovold wrote: > Several drivers currently use of_find_compatible_node() to lookup child > nodes while failing to notice that the of_find_ functions search the > entire tree depth-first (from a given start node) and therefore can > match

[PATCH v2 0/9] of: fix compatible-child-node lookups

2018-08-27 Thread Johan Hovold
Several drivers currently use of_find_compatible_node() to lookup child nodes while failing to notice that the of_find_ functions search the entire tree depth-first (from a given start node) and therefore can match unrelated nodes. The fact that these functions also drop a reference to the node

[PATCH v2 0/9] of: fix compatible-child-node lookups

2018-08-27 Thread Johan Hovold
Several drivers currently use of_find_compatible_node() to lookup child nodes while failing to notice that the of_find_ functions search the entire tree depth-first (from a given start node) and therefore can match unrelated nodes. The fact that these functions also drop a reference to the node