From: Simon Horman <horms@verge•net.au>
To: David Miller <davem@davemloft•net>
Cc: sergei.shtylyov@cogentembedded•com, netdev@vger•kernel.org,
linux-sh@vger•kernel.org
Subject: Re: [PATCH v2] sh_eth: add R8A7791 support
Date: Thu, 26 Dec 2013 14:38:46 +0900 [thread overview]
Message-ID: <20131226053846.GD11739@verge.net.au> (raw)
In-Reply-To: <20131225.225330.1097876354324226061.davem@davemloft.net>
On Wed, Dec 25, 2013 at 10:53:30PM -0500, David Miller wrote:
> From: Simon Horman <horms@verge•net.au>
> Date: Wed, 25 Dec 2013 16:14:51 +0900
>
> > On Tue, Dec 10, 2013 at 09:47:54PM -0500, David Miller wrote:
> >> From: Sergei Shtylyov <sergei.shtylyov@cogentembedded•com>
> >> Date: Sun, 8 Dec 2013 02:59:18 +0300
> >>
> >> > 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.
>
> Check 'net', I might have put it there.
Thanks, I have found it.
I had messed up my remotes and was looking in net instead of net-next.
It is present in net-next.
prev parent reply other threads:[~2013-12-26 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 23:59 [PATCH v2] sh_eth: add R8A7791 support Sergei Shtylyov
2013-12-11 2:47 ` David Miller
2013-12-25 7:14 ` Simon Horman
2013-12-25 11:05 ` Sergei Shtylyov
2013-12-25 14:35 ` Simon Horman
2013-12-26 3:53 ` David Miller
2013-12-26 5:38 ` Simon Horman [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=20131226053846.GD11739@verge.net.au \
--to=horms@verge$(echo .)net.au \
--cc=davem@davemloft$(echo .)net \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sergei.shtylyov@cogentembedded$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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