From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] sh_eth: add R8A7791 support
Date: Wed, 25 Dec 2013 14:35:26 +0000 [thread overview]
Message-ID: <20131225143519.GA29115@verge.net.au> (raw)
In-Reply-To: <52BABC13.201@cogentembedded.com>
On Wed, Dec 25, 2013 at 03:05:55PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 25-12-2013 11:14, Simon Horman wrote:
>
> >>>Add support for yet another ARM member of the R-Car family, R-Car M2, also known
> >>>as R8A7791 -- it will share the code and data with previously added R8A7790.
> >>>Despite the Ether devices in these SoCs are indistinguishable at least from the
> >>>driver's point of view, we do introduce a new platform device ID "r8a7791-ether"
> >>>unlike the wildcard ID used for R8A7778/9 SoCs, due to newly established policy
> >>>for the Renesas SoCs.
>
> >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> >>Applied, thank you.
>
> >Hi Sergei, Hi Dave,
>
> >I don't seem to be able to find this in net-next.
>
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id”a12b15e4c575e0aa0ba5e24a4f213163a823d0
Thanks
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] sh_eth: add R8A7791 support
Date: Wed, 25 Dec 2013 23:35:26 +0900 [thread overview]
Message-ID: <20131225143519.GA29115@verge.net.au> (raw)
In-Reply-To: <52BABC13.201@cogentembedded.com>
On Wed, Dec 25, 2013 at 03:05:55PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 25-12-2013 11:14, Simon Horman wrote:
>
> >>>Add support for yet another ARM member of the R-Car family, R-Car M2, also known
> >>>as R8A7791 -- it will share the code and data with previously added R8A7790.
> >>>Despite the Ether devices in these SoCs are indistinguishable at least from the
> >>>driver's point of view, we do introduce a new platform device ID "r8a7791-ether"
> >>>unlike the wildcard ID used for R8A7778/9 SoCs, due to newly established policy
> >>>for the Renesas SoCs.
>
> >>>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> >>Applied, thank you.
>
> >Hi Sergei, Hi Dave,
>
> >I don't seem to be able to find this in net-next.
>
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=94a12b15e4c575e0aa0ba5e24a4f213163a823d0
Thanks
next prev parent reply other threads:[~2013-12-25 14:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 22:59 [PATCH v2] sh_eth: add R8A7791 support Sergei Shtylyov
2013-12-07 23:59 ` Sergei Shtylyov
2013-12-11 2:47 ` David Miller
2013-12-11 2:47 ` David Miller
2013-12-25 7:14 ` Simon Horman
2013-12-25 7:14 ` Simon Horman
2013-12-25 11:05 ` Sergei Shtylyov
2013-12-25 11:05 ` Sergei Shtylyov
2013-12-25 14:35 ` Simon Horman [this message]
2013-12-25 14:35 ` Simon Horman
2013-12-26 3:53 ` David Miller
2013-12-26 3:53 ` David Miller
2013-12-26 5:38 ` Simon Horman
2013-12-26 5:38 ` Simon Horman
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=20131225143519.GA29115@verge.net.au \
--to=horms@verge.net.au \
--cc=davem@davemloft.net \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.