From: Wang Weidong <wangweidong1@huawei.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] 8139cp: remove a won't occurred BUG_ON
Date: Mon, 27 Jan 2014 09:14:49 +0800 [thread overview]
Message-ID: <52E5B309.1080402@huawei.com> (raw)
In-Reply-To: <1390778623.2735.69.camel@deadeye.wl.decadent.org.uk>
On 2014/1/27 7:23, Ben Hutchings wrote:
> On Sun, 2014-01-26 at 16:33 +0800, Wang Weidong wrote:
>> when variable i go to the BUG_ON the value is equal to the CP_NUM_STATS,
>> so the BUG_ON won't occur, so remove it
>
> We hope that every BUG_ON() does not occur, but that doesn't mean they
> should be removed. This check is meant to catch mistakes when adding
> new statistics.
>
> Ben.
>
Hi, Ben.
Yeah, but I think If someone would add new statistics, he should take into account
it instead the BUG_ON helper.
And that, I found some other drivers' get_ethtool_stats no have BUG_ON. Should we
add the BUG_ON into them?
Regards,
Wang
>> Signed-off-by: Wang Weidong <wangweidong1@huawei.com>
>> ---
>> drivers/net/ethernet/realtek/8139cp.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/realtek/8139cp.c b/drivers/net/ethernet/realtek/8139cp.c
>> index 737c1a8..b70e184 100644
>> --- a/drivers/net/ethernet/realtek/8139cp.c
>> +++ b/drivers/net/ethernet/realtek/8139cp.c
>> @@ -1585,7 +1585,6 @@ static void cp_get_ethtool_stats (struct net_device *dev,
>> tmp_stats[i++] = le16_to_cpu(nic_stats->tx_abort);
>> tmp_stats[i++] = le16_to_cpu(nic_stats->tx_underrun);
>> tmp_stats[i++] = cp->cp_stats.rx_frags;
>> - BUG_ON(i != CP_NUM_STATS);
>>
>> dma_free_coherent(&cp->pdev->dev, sizeof(*nic_stats), nic_stats, dma);
>> }
>
next prev parent reply other threads:[~2014-01-27 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 8:33 [PATCH net-next] 8139cp: remove a won't occurred BUG_ON Wang Weidong
2014-01-26 23:23 ` Ben Hutchings
2014-01-27 1:14 ` Wang Weidong [this message]
2014-01-27 11:54 ` Ben Hutchings
2014-01-27 12:57 ` Wang Weidong
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=52E5B309.1080402@huawei.com \
--to=wangweidong1@huawei.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).