netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mugunthan V N <mugunthanvnm@ti.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<devicetree-discuss@lists.ozlabs.org>,
	<linux-omap@vger.kernel.org>, <benoit.cousson@linaro.org>,
	<paul@pwsan.com>, Matus Ujhelyi <ujhelyi.m@gmail.com>
Subject: Re: [net-next PATCH 1/8] drivers: net: phy: at803x code cleanup on register and unregister driver
Date: Tue, 4 Jun 2013 18:13:22 +0530	[thread overview]
Message-ID: <51ADE0EA.7060008@ti.com> (raw)
In-Reply-To: <51ADD73E.40405@cogentembedded.com>

On 6/4/2013 5:32 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 04-06-2013 10:10, Mugunthan V N wrote:
>
>> Make use of phy_drivers_register/phy_drivers_unregister to 
>> register/unregister
>> multiple phy drivers in a single module.
>
>> Cc: Matus Ujhelyi <ujhelyi.m@gmail.com>
>> Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
>> ---
>>   drivers/net/phy/at803x.c |   35 ++++++++++-------------------------
>>   1 file changed, 10 insertions(+), 25 deletions(-)
>
>> diff --git a/drivers/net/phy/at803x.c b/drivers/net/phy/at803x.c
>> index 45cbc10..a1063e1 100644
>> --- a/drivers/net/phy/at803x.c
>> +++ b/drivers/net/phy/at803x.c
>> @@ -108,8 +108,9 @@ static int at803x_config_init(struct phy_device 
>> *phydev)
>>       return 0;
>>   }
>>
>> -/* ATHEROS 8035 */
>> -static struct phy_driver at8035_driver = {
>> +static struct phy_driver at803x_driver[] = {
>> +{
>> +    /* ATHEROS 8035 */
>>       .phy_id        = 0x004dd072,
>>       .name        = "Atheros 8035 ethernet",
>>       .phy_id_mask    = 0xffffffef,
>
>     That's improper indentation. Needs to be shifted by one tab.
This indentation is as per the coding style followed in all ethernet
phy drivers. If this need so to be changed, it must be a separate patch
for all the ethernet phy drivers.
>
>> @@ -136,32 +135,18 @@ static struct phy_driver at8030_driver = {
>>       .driver        = {
>>           .owner = THIS_MODULE,
>>       },
>> -};
>> +} };
>
>    Looks ugly...
This is also the same as per the style followed in ethernet phy drivers
Please refer the below grep output

$ grep -rnaI "} };" drivers/net/phy/*
drivers/net/phy/at803x.c:201:} };
drivers/net/phy/bcm63xx.c:101:} };
drivers/net/phy/bcm87xx.c:217:} };
drivers/net/phy/broadcom.c:829:} };
drivers/net/phy/cicada.c:130:} };
drivers/net/phy/davicom.c:183:} };
drivers/net/phy/icplus.c:254:} };
drivers/net/phy/lxt.c:313:} };
drivers/net/phy/micrel.c:323:} };
drivers/net/phy/smsc.c:242:} };
drivers/net/phy/ste10Xp.c:113:} };
drivers/net/phy/vitesse.c:192:} };

Regards
Mugunthan V N

  reply	other threads:[~2013-06-04 12:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  6:10 [net-next PATCH 0/8] add phy driver for Atheros AR8031 and CPSW phy-mode DT enhancement Mugunthan V N
2013-06-04  6:10 ` [net-next PATCH 1/8] drivers: net: phy: at803x code cleanup on register and unregister driver Mugunthan V N
2013-06-04 12:02   ` Sergei Shtylyov
2013-06-04 12:43     ` Mugunthan V N [this message]
2013-06-04 13:43       ` Sergei Shtylyov
2013-06-04  6:10 ` [net-next PATCH 2/8] drivers: net: phy: at803x: seperate wol specific code to wol standard apis Mugunthan V N
2013-06-04  6:10 ` [net-next PATCH 3/8] drivers: net: phy: at803x: add interface mode support Mugunthan V N
2013-06-04  6:10 ` [net-next PATCH 4/8] drivers: net: phy: at803x: add support for AT8031 Mugunthan V N
2013-06-04  6:10 ` [net-next PATCH 5/8] ARM: OMAP2+: omap2plus_defconfig: Enable Atheros support Mugunthan V N
2013-06-04  6:10 ` [net-next PATCH 6/8] ARM: dts: AM33XX: Add CPSW phy_id device tree data to am335x-evmsk Mugunthan V N
2013-06-04  6:10 ` [net-next PATCH 7/8] drivers: net: ethernet: cpsw: add phy-mode support to cpsw driver Mugunthan V N
2013-06-04  6:10 ` [net-next PATCH 8/8] ARM: dts: AM33XX: Add phy-mode to CPSW node Mugunthan V N
2013-06-04 21:17 ` [net-next PATCH 0/8] add phy driver for Atheros AR8031 and CPSW phy-mode DT enhancement David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51ADE0EA.7060008@ti.com \
    --to=mugunthanvnm@ti.com \
    --cc=benoit.cousson@linaro.org \
    --cc=davem@davemloft.net \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=ujhelyi.m@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).