linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai Heng Feng <kai.heng.feng@canonical.com>
To: Mario.Limonciello@dell.com
Cc: Greg KH <gregkh@linuxfoundation.org>,
	David Miller <davem@davemloft.net>,
	hayeswang@realtek.co, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] r8152: disable rx checksum offload on Dell TB dock
Date: Tue, 28 Nov 2017 17:40:29 +0800	[thread overview]
Message-ID: <ABAD63E7-FB7B-48C0-9EEA-6B5B7B32721D@canonical.com> (raw)
In-Reply-To: <20b73046763d48848bfbf152e518e0e4@ausx13mpc120.AMER.DELL.COM>



> On 27 Nov 2017, at 11:13 PM, <Mario.Limonciello@dell.com> <Mario.Limonciello@dell.com> wrote:
> 
> This is quite surprising to me too.  The externally plugged in r8153 dongle,
> was it connected over type C port or over type A port?  AFAIK Type C port is
> actually Alpine ridge pass through port.  It is not connected to XHCI controller
> or USB hub.

Over the front type A port, which connects to SMSC hub then ASMedia controller.

The type C port indeed connects to AR directly, hence no such issue.

Kai-Heng

      reply	other threads:[~2017-11-28  9:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23  6:38 [PATCH] r8152: disable rx checksum offload on Dell TB dock Kai-Heng Feng
2017-11-23  7:58 ` Greg KH
2017-11-23  8:53   ` Kai Heng Feng
2017-11-23  9:24     ` Greg KH
2017-11-24  3:44       ` Kai Heng Feng
2017-11-24  8:28         ` Greg KH
2017-11-24  8:29           ` Greg KH
2017-11-24  8:59             ` Kai Heng Feng
2017-11-27 15:11               ` Mario.Limonciello
2017-11-24  8:57           ` Kai Heng Feng
2017-11-27 15:13         ` Mario.Limonciello
2017-11-28  9:40           ` Kai Heng Feng [this message]

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=ABAD63E7-FB7B-48C0-9EEA-6B5B7B32721D@canonical.com \
    --to=kai.heng.feng@canonical.com \
    --cc=Mario.Limonciello@dell.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hayeswang@realtek.co \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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).