From: Ding Tianhong <dingtianhong@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: arnd@arndb.de, robh+dt@kernel.org, grant.likely@linaro.org,
agraf@suse.de, sergei.shtylyov@cogentembedded.com,
linux-arm-kernel@lists.infradead.org, eric.dumazet@gmail.com,
xuwei5@hisilicon.com, zhangfei.gao@linaro.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux@arm.linux.org.uk
Subject: Re: [PATCH net-next v12 3/3] net: hisilicon: new hip04 ethernet driver
Date: Wed, 14 Jan 2015 12:22:20 +0800 [thread overview]
Message-ID: <54B5EEFC.5020902@huawei.com> (raw)
In-Reply-To: <20150113.230611.375062426344934847.davem@davemloft.net>
On 2015/1/14 12:06, David Miller wrote:
> From: Ding Tianhong <dingtianhong@huawei.com>
> Date: Tue, 13 Jan 2015 17:11:30 +0800
>
>> +static int hip04_alloc_ring(struct net_device *ndev, struct device *d)
>> +{
>> + struct hip04_priv *priv = netdev_priv(ndev);
>> + int i;
>> +
>> + priv->tx_desc = dma_alloc_coherent(d,
>> + TX_DESC_NUM * sizeof(struct tx_desc),
>> + &priv->tx_desc_dma, GFP_KERNEL);
>
> When a function call spans multiple lines, the arguments on the
> second and subsequent lines should start at the first column
> after the openning parenthesis of the function call.
>
> If you are only using TAB characters, your indentation is likely
> to be incorrect.
>
Sorry for the mistake.
>> + /*
>> + * BQL will try to keep the TX queue as short as possible, but it can't
>> + * be faster than tx_coalesce_usecs, so we need a fast timeout here,
>> + * but also long enough to gather up enough frames to ensure we don't
>> + * get more interrupts than necessary.
>> + * 200us is enough for 16 frames of 1500 bytes at gigabit ethernet rate
>> + */
>
> Comments in the networking should be:
>
> /* Formatted
> * like this.
> */
>
yes.
>> + priv->phy_node = of_parse_phandle(node, "phy-handle", 0);
>> + if (priv->phy_node) {
>> + priv->phy = of_phy_connect(ndev, priv->phy_node,
>> + &hip04_adjust_link, 0, priv->phy_mode);
>
> Please align the arguments to this function call correctly, as
> per above.
>
Ok, I will check them again.
Ding
> Thanks.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
prev parent reply other threads:[~2015-01-14 4:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 9:11 [PATCH net-next v12 0/3] add hisilicon hip04 ethernet driver Ding Tianhong
2015-01-13 9:11 ` [PATCH net-next v12 1/3] Documentation: add Device tree bindings for Hisilicon hip04 ethernet Ding Tianhong
2015-01-13 9:11 ` [PATCH net-next v12 2/3] net: hisilicon: new hip04 MDIO driver Ding Tianhong
2015-01-13 9:11 ` [PATCH net-next v12 3/3] net: hisilicon: new hip04 ethernet driver Ding Tianhong
[not found] ` <1421140290-5492-4-git-send-email-dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-01-14 4:06 ` David Miller
2015-01-14 4:22 ` Ding Tianhong [this message]
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=54B5EEFC.5020902@huawei.com \
--to=dingtianhong@huawei.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.org \
/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).