Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1343919 > unrolled thread

[PATCH net 0/3] r8169:issues fix.

Started byChunhao Lin <hau@realtek.com>
First post2016-02-26 09:50 +0100
Last post2016-03-02 17:40 +0100
Articles 3 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH net 0/3] r8169:issues fix. Chunhao Lin <hau@realtek.com> - 2016-02-26 09:50 +0100
    Re: [PATCH net 0/3] r8169:issues fix. David Miller <davem@davemloft.net> - 2016-03-01 21:30 +0100
      RE: [PATCH net 0/3] r8169:issues fix. Hau <hau@realtek.com> - 2016-03-02 17:40 +0100

#1343919 — [PATCH net 0/3] r8169:issues fix.

FromChunhao Lin <hau@realtek.com>
Date2016-02-26 09:50 +0100
Subject[PATCH net 0/3] r8169:issues fix.
Message-ID<r6mg3-tV-9@gated-at.bofh.it>
This series of patches fix 3 issues that are listed below.

Chunhao Lin (3):
  r8169:fix nic sometimes doesn't work after changing the mac address.
  r8169:eliminate error message in using ethtool -S when nic is down.
  r8169: Enable RX_MULTI_EN for RTL_GIGA_MAC_VER_41~48

 drivers/net/ethernet/realtek/r8169.c | 22 ++++++++++++++++------
 1 file changed, 16 insertions(+), 6 deletions(-)

-- 
1.9.1

[toc] | [next] | [standalone]


#1347002

FromDavid Miller <davem@davemloft.net>
Date2016-03-01 21:30 +0100
Message-ID<r7Z5D-5Mg-9@gated-at.bofh.it>
In reply to#1343919
From: Chunhao Lin <hau@realtek.com>
Date: Fri, 26 Feb 2016 16:40:43 +0800

> This series of patches fix 3 issues that are listed below.
> 
> Chunhao Lin (3):
>   r8169:fix nic sometimes doesn't work after changing the mac address.
>   r8169:eliminate error message in using ethtool -S when nic is down.
>   r8169: Enable RX_MULTI_EN for RTL_GIGA_MAC_VER_41~48

I don't agree with changes #1 and #2.

If you are going to go to a model where every single configuration
operation is recorded in software and performed at resume time, then
really do it and fix it in the whole driver.  As currently coded you
are leaving lots of known bugs in the driver.

#2 is even a worse situation.  If you are going to handle things this
way you must sync the counters when the suspend happens, so that the
statistics get call receives up to date values.

[toc] | [prev] | [next] | [standalone]


#1348308

FromHau <hau@realtek.com>
Date2016-03-02 17:40 +0100
Message-ID<r8hYC-1Lj-23@gated-at.bofh.it>
In reply to#1347002
> I don't agree with changes #1 and #2.
> 
> If you are going to go to a model where every single configuration operation
> is recorded in software and performed at resume time, then really do it and
> fix it in the whole driver.  As currently coded you are leaving lots of known
> bugs in the driver.
> 
> #2 is even a worse situation.  If you are going to handle things this way you
> must sync the counters when the suspend happens, so that the statistics get
> call receives up to date values.

Thanks for your advice. I will send #3 patch first. Then modify #1 and #2 patch and resend these two patches.

 ------Please consider the environment before printing this e-mail.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web