From: Zumeng Chen <zumeng.chen@gmail.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: Netdev <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Siva Reddy Kallam <siva.kallam@broadcom.com>,
"prashant.sreedharan@broadcom.com" <prashant@broadcom.com>,
David Miller <davem@davemloft.net>,
Zumeng Chen <zumeng.chen@windriver.com>
Subject: Re: [v2 PATCH 1/1] tg3: fix meaningless hw_stats reading after tg3_halt memset 0 hw_stats
Date: Wed, 2 May 2018 18:27:54 +0800 [thread overview]
Message-ID: <5af186f8-9718-c295-4e34-e84dd78ea157@gmail.com> (raw)
In-Reply-To: <CACKFLikg+p_1iDQtd0XN8tJaKtAgX0jfxGXuoqxhDJZ922UkUg@mail.gmail.com>
On 2018年05月02日 13:12, Michael Chan wrote:
> On Tue, May 1, 2018 at 5:42 PM, Zumeng Chen <zumeng.chen@gmail.com> wrote:
>
>> diff --git a/drivers/net/ethernet/broadcom/tg3.h b/drivers/net/ethernet/broadcom/tg3.h
>> index 3b5e98e..c61d83c 100644
>> --- a/drivers/net/ethernet/broadcom/tg3.h
>> +++ b/drivers/net/ethernet/broadcom/tg3.h
>> @@ -3102,6 +3102,7 @@ enum TG3_FLAGS {
>> TG3_FLAG_ROBOSWITCH,
>> TG3_FLAG_ONE_DMA_AT_ONCE,
>> TG3_FLAG_RGMII_MODE,
>> + TG3_FLAG_HALT,
> I think you should be able to use the existing INIT_COMPLETE flag
No, it will bring the uncertain factors into the existed complicate
logic of INIT_COMPLETE.
And I think it's very simple logic here to fix the meaningless hw_stats
reading and the problem
of commit f5992b72. I even suspect if you have read INIT_COMPLETE
related codes carefully.
Cheers,
Zumeng
> and
> not have to add a new flag.
>
>> /* Add new flags before this comment and TG3_FLAG_NUMBER_OF_FLAGS */
>> TG3_FLAG_NUMBER_OF_FLAGS, /* Last entry in enum TG3_FLAGS */
>> --
>> 2.9.3
>>
next prev parent reply other threads:[~2018-05-02 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 0:42 [v2 PATCH 1/1] tg3: fix meaningless hw_stats reading after tg3_halt memset 0 hw_stats Zumeng Chen
2018-05-02 5:12 ` Michael Chan
2018-05-02 10:27 ` Zumeng Chen [this message]
2018-05-02 17:32 ` Michael Chan
2018-05-03 0:30 ` Zumeng Chen
2018-05-03 5:04 ` Michael Chan
2018-05-05 2:40 ` Zumeng Chen
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=5af186f8-9718-c295-4e34-e84dd78ea157@gmail.com \
--to=zumeng.chen@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=prashant@broadcom.com \
--cc=siva.kallam@broadcom.com \
--cc=zumeng.chen@windriver.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).