From: Jeff Garzik <jeff@garzik.org>
To: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Cc: netdev <netdev@vger.kernel.org>,
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
Linux-sh <linux-sh@vger.kernel.org>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH v3] net: sh_eth: Add support of SH7763 to sh_eth
Date: Wed, 30 Jul 2008 17:22:17 -0400 [thread overview]
Message-ID: <4890DB89.7020701@garzik.org> (raw)
In-Reply-To: <48684011.5020201@renesas.com>
Nobuhiro Iwamatsu wrote:
> Jeff Garzik wrote:
>> Nobuhiro Iwamatsu wrote:
>>> SH7763 has Ethernet core same as SH7710/SH7712.
>>> Positions of some registry are different, but the basic part is the same.
>>> I add support of ethernet of sh7763 to sh_eth.
>>>
>>> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
>>> ---
>>> drivers/net/Kconfig | 4 +-
>>> drivers/net/sh_eth.c | 202 ++++++++++++++++++++-----
>>> drivers/net/sh_eth.h | 425 +++++++++++++++++++++++++++++++++++++-------------
>>> 3 files changed, 482 insertions(+), 149 deletions(-)
>> ACK but failed to apply
>
> Sorry, I checked the patch, and corrected that the patch was able to be applied.
> Please apply.
>
> Best regards,
> Nobuhiro
>
> ------->
>
> SH7763 has Ethernet core same as SH7710/SH7712.
> Positions of some registry are different, but the basic part is the same.
> I add support of ethernet of sh7763 to sh_eth.
>
> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
> ---
> drivers/net/Kconfig | 4 +-
> drivers/net/sh_eth.c | 202 ++++++++++++++++++++-----
> drivers/net/sh_eth.h | 426 +++++++++++++++++++++++++++++++++++++-------------
> 3 files changed, 482 insertions(+), 150 deletions(-)
applied
prev parent reply other threads:[~2008-07-30 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 10:25 [PATCH] net: sh_eth: Add support of SH7763 to sh_eth Nobuhiro Iwamatsu
2008-06-27 6:09 ` Jeff Garzik
2008-06-30 2:08 ` [PATCH v3] " Nobuhiro Iwamatsu
2008-07-23 4:10 ` Nobuhiro Iwamatsu
2008-07-30 21:22 ` Jeff Garzik [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=4890DB89.7020701@garzik.org \
--to=jeff@garzik.org \
--cc=iwamatsu.nobuhiro@renesas.com \
--cc=iwamatsu@nigauri.org \
--cc=lethal@linux-sh.org \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).