[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a7490d2-7553-f0cb-8a57-9c8412259060@solid-run.com>
Date: Thu, 28 Apr 2022 15:52:45 +0300
From: Josua Mayer <josua@...id-run.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, alvaro.karsz@...id-run.com,
Michael Hennerich <michael.hennerich@...log.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH v3 2/3] net: phy: adin: add support for clock output
\o/
Am 28.04.22 um 15:21 schrieb Andrew Lunn:
>> +static int adin_config_clk_out(struct phy_device *phydev)
>> +{
>> + struct device *dev = &phydev->mdio.dev;
>> + const char *val = NULL;
>> + u8 sel = 0;
>> +
>> + device_property_read_string(dev, "adi,phy-output-clock", &val);
>> + if(!val) {
> I'm pretty sure the coding style requires a space between if and (.
In fact it does :(
>
> Did you use checkpatch on this?
I remember doing it, but my mind is playing tricks on me - as right now
checkpatch is clearly telling me 7 occurences of this style violation ...
Thank you for the fast reply, I'll make sure to fix this in a v4, if any.
Do you want a v4 for this? Or is it worth waiting for more feedback now?
sincerely
Josua Mayer
Powered by blists - more mailing lists