From: Chris Brandt <Chris.Brandt@renesas.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
"David S. Miller" <davem@davemloft.net>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH RFT 0/5] sh_eth: get rid of the dedicated regiseter mapping for RZ/A1 (R7S72100)
Date: Fri, 7 Feb 2020 15:51:31 +0000 [thread overview]
Message-ID: <TY1PR01MB156298E4D2741ED7A64C81F58A1C0@TY1PR01MB1562.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TY1PR01MB1562CFDEE9179DC7578A99CD8A1C0@TY1PR01MB1562.jpnprd01.prod.outlook.com>
> On Fri, Feb 7, 2020, Chris Brandt wrote:
> On Mon, Feb 3, 2020, Sergei Shtylyov wrote:
> > so far: in the ethtool API for the register dump. I'd appreciate
> > if Chris Brandt could sanity-test this patch set as he seem to
> > still have the RZ/A1 hardware...
>
> Works on a Renesas RZ/A1H RSK board.
For the series:
Tested-by: Chris Brandt <chris.brandt@renesas.com>
prev parent reply other threads:[~2020-02-07 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 19:34 [PATCH RFT 0/5] sh_eth: get rid of the dedicated regiseter mapping for RZ/A1 (R7S72100) Sergei Shtylyov
2020-02-03 19:40 ` [PATCH RFT 1/5] sh_eth: check sh_eth_cpu_data::no_tx_cntrs when dumping registers Sergei Shtylyov
2020-02-03 19:42 ` [PATCH RFT 2/5] sh_eth: check sh_eth_cpu_data::cexcr " Sergei Shtylyov
2020-02-03 19:44 ` [PATCH RFT 3/5] sh_eth: check sh_eth_cpu_data::no_xdfar " Sergei Shtylyov
2020-02-03 19:49 ` [PATCH RFT 4/5] sh_eth: add sh_eth_cpu_data::gecmr flag Sergei Shtylyov
2020-02-03 19:51 ` [PATCH RFT 5/5] sh_eth: use Gigabit register map for R7S72100 Sergei Shtylyov
2020-02-03 20:01 ` Sergei Shtylyov
2020-02-04 3:35 ` [PATCH RFT 0/5] sh_eth: get rid of the dedicated regiseter mapping for RZ/A1 (R7S72100) Chris Brandt
2020-02-07 15:25 ` Chris Brandt
2020-02-07 15:40 ` Sergei Shtylyov
2020-02-07 15:51 ` Chris Brandt [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=TY1PR01MB156298E4D2741ED7A64C81F58A1C0@TY1PR01MB1562.jpnprd01.prod.outlook.com \
--to=chris.brandt@renesas.com \
--cc=davem@davemloft.net \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).