[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1395205885.8649.35.camel@joe-AO722>
Date: Tue, 18 Mar 2014 22:11:25 -0700
From: Joe Perches <joe@...ches.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Jean Sacren <sakiwit@...il.com>,
Alexander Smirnov <alex.bluesman.smirnov@...il.com>,
Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
linux-zigbee-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
Phoebe Buckheister <phoebe.buckheister@...m.fraunhofer.de>
Subject: Re: [PATCH net-next] ieee802154: fix variable declaration and
initializer
On Tue, 2014-03-18 at 21:35 -0700, Eric Dumazet wrote:
> On Tue, 2014-03-18 at 20:42 -0700, Joe Perches wrote:
> > On Tue, 2014-03-18 at 20:32 -0700, Eric Dumazet wrote:
> > > On Tue, 2014-03-18 at 21:19 -0600, Jean Sacren wrote:
> > >
> > > > 2) Fix the initializer by deleting the double logical negation
> > > > operators as they don't serve any purpose.
> > > >
> > > ...
> > > >
> > > > static int phy_set_lbt(struct wpan_phy *phy, struct genl_info *info)
> > > > {
> > > > - u8 on = !!nla_get_u8(info->attrs[IEEE802154_ATTR_LBT_ENABLED]);
> > >
> > > You do realize !!(a) is not equivalent to (a) ?
> >
> > It is when the type it's assigned to also changes
> > from u8 to bool.
>
> I was referring to the changelog, obviously, see how I carefully
> copy/pasted the relevant part ?
No, that's not obvious at all actually.
I would have used "Change the type to bool and remove
the now unnecessary !!" in the changelog to link Jean's
points 1 and 2, but your statement and the code and
commit log changes proposed by Jean don't match.
The type _did_ change as described in point 1.
> Stating it is a 'fix' is quite a false statement, I see no fix at all,
> maybe a cleanup, but I am not really convinced.
Perhaps "fix" is a more flexible word than you imagine.
Perhaps this a code style "fix" without logic change.
<shrug> I'm very ambivalent about it too.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists