From: Paul Mundt <lethal@linux-sh.org>
To: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Cc: linux-sh@vger.kernel.org, Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: Fix compile error of Solution Engine
Date: Tue, 29 Jul 2008 08:39:56 +0000 [thread overview]
Message-ID: <20080729083956.GC29389@linux-sh.org> (raw)
In-Reply-To: <488EAC95.4060507@renesas.com>
On Tue, Jul 29, 2008 at 02:37:25PM +0900, Nobuhiro Iwamatsu wrote:
> When I compiled Solution Engine, this become compile error
> because plaform device of sh_eth device becomes enable.
> When sh7710/sh7712 which could use sh_eth was chosen,
> revised it so that platform device of sh_eth device became enable.
>
> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Cc: linux-sh@vger.kernel.org, Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: Fix compile error of Solution Engine
Date: Tue, 29 Jul 2008 17:39:56 +0900 [thread overview]
Message-ID: <20080729083956.GC29389@linux-sh.org> (raw)
In-Reply-To: <488EAC95.4060507@renesas.com>
On Tue, Jul 29, 2008 at 02:37:25PM +0900, Nobuhiro Iwamatsu wrote:
> When I compiled Solution Engine, this become compile error
> because plaform device of sh_eth device becomes enable.
> When sh7710/sh7712 which could use sh_eth was chosen,
> revised it so that platform device of sh_eth device became enable.
>
> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Applied, thanks.
next prev parent reply other threads:[~2008-07-29 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 5:37 [PATCH] sh: Fix compile error of Solution Engine Nobuhiro Iwamatsu
2008-07-29 5:37 ` Nobuhiro Iwamatsu
2008-07-29 8:39 ` Paul Mundt [this message]
2008-07-29 8:39 ` Paul Mundt
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=20080729083956.GC29389@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=bunk@kernel.org \
--cc=iwamatsu.nobuhiro@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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 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.