From: Murali Karicheri <m-karicheri2@ti.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: "open list:TI NETCP ETHERNET DRIVER" <netdev@vger.kernel.org>
Subject: Re: rtk8168 driver help needed
Date: Tue, 24 May 2016 17:57:38 -0400 [thread overview]
Message-ID: <5744CE52.7000209@ti.com> (raw)
In-Reply-To: <20160520003152.GB22420@electric-eye.fr.zoreil.com>
On 05/19/2016 08:31 PM, Francois Romieu wrote:
> Murali Karicheri <m-karicheri2@ti.com> :
> [...]
>> Do you what could be wrong with rtk8168?
>
> Hardly.
>
> What do the device registers (ethtool -d) and device stats (ethtool -S)
> look like ?
Will dump in the next opportunity and respond
>
> (please trim useless material from previous mail)
>
Ok. Will keep in mind next time.
--
Murali Karicheri
Linux Kernel, Keystone
prev parent reply other threads:[~2016-05-24 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 22:02 rtk8168 driver help needed Murali Karicheri
2016-05-06 22:03 ` Murali Karicheri
2016-05-07 8:35 ` Francois Romieu
2016-05-09 14:54 ` Murali Karicheri
2016-05-09 17:25 ` Murali Karicheri
2016-05-09 18:13 ` Murali Karicheri
2016-05-19 21:38 ` Murali Karicheri
2016-05-20 0:31 ` Francois Romieu
2016-05-24 21:57 ` Murali Karicheri [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=5744CE52.7000209@ti.com \
--to=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).