From: Jon Mason
Date: Mon, 15 May 2017 13:37:09 -0400
> I would prefer #1, as I would not want to break something that was
> currently working. However, I think we should add much error logging
> here to let people know their DT is hosed (instead of silently
> working). So, this would mean appl
On Fri, May 12, 2017 at 6:52 PM, Florian Fainelli wrote:
> On 05/12/2017 09:22 AM, David Miller wrote:
>> From: Julia Lawall
>> Date: Fri, 12 May 2017 22:54:23 +0800 (SGT)
>>
>>> Device node iterators put the previous value of the index variable, so an
>>> explicit put causes a double put.
>> ..
On Fri, 12 May 2017, Florian Fainelli wrote:
> On 05/12/2017 09:22 AM, David Miller wrote:
> > From: Julia Lawall
> > Date: Fri, 12 May 2017 22:54:23 +0800 (SGT)
> >
> >> Device node iterators put the previous value of the index variable, so an
> >> explicit put causes a double put.
> > ...
>
On 05/12/2017 09:22 AM, David Miller wrote:
> From: Julia Lawall
> Date: Fri, 12 May 2017 22:54:23 +0800 (SGT)
>
>> Device node iterators put the previous value of the index variable, so an
>> explicit put causes a double put.
> ...
>> @@ -169,7 +169,6 @@ int mdio_mux_init(struct device *dev,
>>
From: Julia Lawall
Date: Fri, 12 May 2017 22:54:23 +0800 (SGT)
> Device node iterators put the previous value of the index variable, so an
> explicit put causes a double put.
...
> @@ -169,7 +169,6 @@ int mdio_mux_init(struct device *dev,
> if (r) {
> mdiobus_
Device node iterators put the previous value of the index variable, so an
explicit put causes a double put.
In particular, of_mdiobus_register can fail before doing anything
interesting, so one could view it as a no-op from the reference count
point of view.
Generated by: scripts/coccinelle/itera