RE: r8152: data corruption in various scenarios

2019-01-07 Thread Mario.Limonciello
> -Original Message- > From: Mark Lord > Sent: Monday, January 7, 2019 12:06 PM > To: Limonciello, Mario; hayesw...@realtek.com; kai.heng.f...@canonical.com > Cc: aatt...@nicira.com; da...@davemloft.net; g...@kroah.com; > rom...@fr.zoreil.com; netdev@vger.kernel.org; nic_s...@realtek.com;

RE: r8152: data corruption in various scenarios

2019-01-07 Thread Mario.Limonciello
> -Original Message- > From: Hayes Wang > Sent: Sunday, January 6, 2019 9:54 PM > To: Mark Lord; Kai Heng Feng > Cc: Ansis Atteka; David Miller; g...@kroah.com; rom...@fr.zoreil.com; > netdev@vger.kernel.org; nic_swsd; linux-ker...@vger.kernel.org; linux- > u...@vger.kernel.org; Limonciell

RE: [PATCH] r8152: limit MAC pass-through to one device

2018-10-10 Thread Mario.Limonciello
> > MAC address having to be unique, a MAC coming from the host > must be used at most once at a time. Hence the users must > be recorded and additional users must fall back to conventional > methods. I checked with the internal team and actually applies pass through MAC on both Windows Realtek d

RE: [PATCH v2] r8152: disable RX aggregation on Dell TB16 dock

2018-01-18 Thread Mario.Limonciello
> -Original Message- > From: Kai Heng Feng [mailto:kai.heng.f...@canonical.com] > Sent: Thursday, January 18, 2018 10:57 AM > To: David Miller > Cc: Hayes Wang ; gre...@linuxfoundation.org; linux- > u...@vger.kernel.org; netdev@vger.kernel.org; linux-ker...@vger.kernel.org; > Limonciello,

RE: [PATCH] r8152: disable rx checksum offload on Dell TB dock

2017-11-27 Thread Mario.Limonciello
> -Original Message- > From: Kai Heng Feng [mailto:kai.heng.f...@canonical.com] > Sent: Thursday, November 23, 2017 9:44 PM > To: Greg KH > Cc: David Miller ; hayesw...@realtek.co; linux- > u...@vger.kernel.org; netdev@vger.kernel.org; LKML ker...@vger.kernel.org>; Limonciello, Mario > S

RE: [PATCH] r8152: disable rx checksum offload on Dell TB dock

2017-11-27 Thread Mario.Limonciello
> -Original Message- > From: Kai Heng Feng [mailto:kai.heng.f...@canonical.com] > Sent: Friday, November 24, 2017 3:00 AM > To: Greg KH > Cc: David Miller ; hayesw...@realtek.co; linux- > u...@vger.kernel.org; netdev@vger.kernel.org; LKML ker...@vger.kernel.org>; Limonciello, Mario > Sub

RE: [PATCH 17/22] platform/x86: alienware-wmi: fix format string overflow warning

2017-07-14 Thread Mario.Limonciello
> -Original Message- > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: Friday, July 14, 2017 7:07 AM > To: linux-ker...@vger.kernel.org; Darren Hart ; Andy > Shevchenko > Cc: Greg Kroah-Hartman ; Linus Torvalds > ; Guenter Roeck ; > a...@linux-foundation.org; netdev@vger.kernel.org; Dav

RE: [PATCH v8 3/8] thunderbolt: Communication with the ICM (firmware)

2016-12-19 Thread Mario.Limonciello
Dell - Internal Use - Confidential > > There is small problem, though. On non-Apple systems the host controller only > appears when something is connected to thunderbolt ports. So the char device > would not be there all the time. However, I think we can still notify the > userspace by sending

RE: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

2016-11-22 Thread Mario.Limonciello
> Here are a couple of additional questions: > > - When the network interface is created, there is no IP address > assigned (or negotiated ?) on the Linux side. But it is done on the > MacOS side. And in the Linux kernel logs I can also read the message: > "ready for ThunderboltIP negotiatio

RE: [PATCH v8 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

2016-10-21 Thread Mario.Limonciello
> -Original Message- > From: Amir Levy [mailto:amir.jer.l...@intel.com] > Sent: Wednesday, September 28, 2016 9:44 AM > To: gre...@linuxfoundation.org > Cc: andreas.noe...@gmail.com; bhelg...@google.com; cor...@lwn.net; > linux-ker...@vger.kernel.org; linux-...@vger.kernel.org; > netdev@vge