From: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sh: Add support sh_eth to cpu of sh4
Date: Tue, 24 Feb 2009 16:38:41 +0900 [thread overview]
Message-ID: <49A3A401.7080002@renesas.com> (raw)
In-Reply-To: <200902240232.05696.vapier@gentoo.org>
Mike Frysinger wrote:
> On Tuesday 24 February 2009 02:20:40 Nobuhiro Iwamatsu wrote:
>> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
>> ---
>> cpu/sh4/cpu.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/cpu/sh4/cpu.c b/cpu/sh4/cpu.c
>> index 52b6cfd..be410ab 100644
>> --- a/cpu/sh4/cpu.c
>> +++ b/cpu/sh4/cpu.c
>> @@ -23,6 +23,7 @@
>>
>> #include <common.h>
>> #include <command.h>
>> +#include <netdev.h>
>> #include <asm/processor.h>
>> #include <asm/cache.h>
>
> this change doesnt really seem to jive with the changelog. adding a header
> implies fixing of warning/build breakage, not "Add support sh_eth to cpu of
> sh4" ...
> -mike
Thanks,
I will change changelog and resend.
Best regards,
Nobuhiro
prev parent reply other threads:[~2009-02-24 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 7:20 [U-Boot] [PATCH] sh: Add support sh_eth to cpu of sh4 Nobuhiro Iwamatsu
2009-02-24 7:32 ` Mike Frysinger
2009-02-24 7:38 ` Nobuhiro Iwamatsu [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=49A3A401.7080002@renesas.com \
--to=iwamatsu.nobuhiro@renesas.com \
--cc=u-boot@lists.denx.de \
/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