netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org, mark.rutland@arm.com,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 0/3] Add R8A77980 GEther support
Date: Thu, 17 May 2018 14:53:57 -0400 (EDT)	[thread overview]
Message-ID: <20180517.145357.2037804925428844092.davem@davemloft.net> (raw)
In-Reply-To: <087c91a3-a451-6de7-5e0f-a835f8cc98f1@cogentembedded.com>

From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Wed, 16 May 2018 22:52:40 +0300

> Here's a set of 3 patches against DaveM's 'net-next.git' repo. They (gradually)
> add R8A77980 GEther support to the 'sh_eth' driver, starting with couple new
> register bits/values introduced with this chip, and ending with adding a new
> 'struct sh_eth_cpu_data' instance connected to the new DT "compatible" prop
> value...
> 
> [1/1] sh_eth: add RGMII support
> [2/3] sh_eth: add EDMR.NBST support
> [3/3] sh_eth: add R8A77980 support

Waiting for a respin of this, correcting the RGMII check in patch #1.

  parent reply	other threads:[~2018-05-17 18:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 19:52 [PATCH 0/3] Add R8A77980 GEther support Sergei Shtylyov
2018-05-16 19:56 ` [PATCH 1/3] sh_eth: add RGMII support Sergei Shtylyov
2018-05-16 20:30   ` Andrew Lunn
2018-05-16 20:34     ` Sergei Shtylyov
2018-05-16 20:37       ` Andrew Lunn
2018-05-17  8:15         ` Sergei Shtylyov
2018-05-16 19:58 ` [PATCH 2/3] sh_eth: add EDMR.NBST support Sergei Shtylyov
2018-05-17  8:12   ` Simon Horman
2018-05-16 20:00 ` [PATCH 3/3] sh_eth: add R8A77980 support Sergei Shtylyov
2018-05-17  8:56   ` Simon Horman
2018-05-17 18:53 ` David Miller [this message]
2018-05-18 11:00   ` [PATCH 0/3] Add R8A77980 GEther support Sergei Shtylyov

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=20180517.145357.2037804925428844092.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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).