[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46bf05a81237ed716bf06b48891fcd7c129eae5d.camel@perches.com>
Date: Thu, 26 Mar 2020 11:55:17 -0700
From: Joe Perches <joe@...ches.com>
To: David Miller <davem@...emloft.net>, florinel.iordache@....com
Cc: netdev@...r.kernel.org, andrew@...n.ch, f.fainelli@...il.com,
hkallweit1@...il.com, linux@...linux.org.uk,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
robh+dt@...nel.org, mark.rutland@....com, kuba@...nel.org,
corbet@....net, shawnguo@...nel.org, leoyang.li@....com,
madalin.bucur@....nxp.com, ioana.ciornei@....com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 6/9] net: phy: add backplane kr driver support
On Thu, 2020-03-26 at 11:53 -0700, David Miller wrote:
> From: Florinel Iordache <florinel.iordache@....com>
> Date: Thu, 26 Mar 2020 15:51:19 +0200
>
> > +static void kr_reset_master_lane(struct kr_lane_info *krln)
> > +{
> > + struct phy_device *bpphy = krln->bpphy;
> > + struct backplane_phy_info *bp_phy = bpphy->priv;
> > + const struct lane_io_ops *lane_ops = krln->bp_phy->bp_dev.lane_ops;
>
> Please use reverse christmas tree ordering for local variables.
How (any why) do you suggest the first 2 entries here
should be ordered?
Powered by blists - more mailing lists