From: Ivan Mikhaylov <ivan@ru.ibm.com>
To: "Ben Hutchings" <ben@decadent.org.uk>
Cc: "" <netdev@vger.kernel.org>, "" <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] ethtool: add new emac_regs struct from driver, add new chip types.
Date: Wed, 7 Oct 2015 11:41:31 +0400 [thread overview]
Message-ID: <20151007114131.78a925c0@fr-ThinkPad-W520> (raw)
In-Reply-To: <20150925081545.26cbb101@fr-ThinkPad-W520>
On Fri, 25 Sep 2015 08:15:45 +0400
"Ivan Mikhaylov" <ivan@ru.ibm.com> wrote:
ping
> * add new version of emac_regs struct from driver structure
> perspective and passing size from actual struct size, not from memory
> area variable which set in dts file.
> * add three types of network chips for new struct : emac, emac4,
> emac4sync.
> * add emac4sync processing in print_emac_regs.
> * this commit fixing problem with output of MII sections for new
> driver versions.
>
> Signed-off-by: Ivan Mikhaylov <ivan@ru.ibm.com>
> ---
next prev parent reply other threads:[~2015-10-07 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 10:46 [PATCH] ethtool: add new emac_regs struct from driver, add new chip types Ivan Mikhaylov
2015-09-25 4:15 ` Ivan Mikhaylov
2015-10-07 7:41 ` Ivan Mikhaylov [this message]
2015-10-09 2:24 ` Ben Hutchings
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=20151007114131.78a925c0@fr-ThinkPad-W520 \
--to=ivan@ru.ibm.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@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