On Wed, May 2, 2018 at 5:30 PM, Zumeng Chen <zumeng.chen@xxxxxxxxx> wrote:
On 2018å05æ03æ 01:32, Michael Chan wrote:I don't want to see another flag added that is practically the same as
On Wed, May 2, 2018 at 3:27 AM, Zumeng Chen <zumeng.chen@xxxxxxxxx> wrote:
On 2018å05æ02æ 13:12, Michael Chan wrote:We should use an existing flag whenever appropriate
On Tue, May 1, 2018 at 5:42 PM, Zumeng Chen <zumeng.chen@xxxxxxxxx>
wrote:
diff --git a/drivers/net/ethernet/broadcom/tg3.hI think you should be able to use the existing INIT_COMPLETE flag
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,
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.
I disagree. This is sort of blahblah...
!INIT_COMPLETE. The driver already has close to one hundred flags.
Adding a new flag that is similar to an existing flag will just make
the code more difficult to understand and maintain.
If you don't want to fix it the cleaner way, Siva or I will fix it.