From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Joe Perches <joe@perches.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Francois Romieu <romieu@fr.zoreil.com>,
"Vineet Gupta" <Vineet.Gupta1@synopsys.com>,
Mischa Jonker <Mischa.Jonker@synopsys.com>,
Arnd Bergmann <arnd@arndb.de>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
"David S. Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Florian Fainelli <florian@openwrt.org>
Subject: Re: [PATCH v7] ethernet/arc/arc_emac - Add new driver
Date: Fri, 21 Jun 2013 12:25:48 +0000 [thread overview]
Message-ID: <4881796E12491D4BB15146FE0209CE643F5F5DBB@DE02WEMBXB.internal.synopsys.com> (raw)
In-Reply-To: <CAHp75Vf8A7YZGBtna7JAaacnJWq5+q_+m44eO13bChxKj6XZgQ@mail.gmail.com>
On 06/21/2013 04:15 PM, Andy Shevchenko wrote:
> On Fri, Jun 21, 2013 at 1:53 PM, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
>
> []
>
>> But during compilation on x86 one needs to enable OF. Which will lead to
>> compilation errors in other things.
>
> JFYI, x86 has at least one platform with official OF dependency.
> Once I actually tried to build kernel for Intel MID with OF enabled
> (it required a hack in the arch Kconfig, of course), compiled fine.
Ok, good to know it.
Any other comments on patch itself?
-Alexey
next prev parent reply other threads:[~2013-06-21 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 7:20 Alexey Brodkin
2013-06-21 10:32 ` Joe Perches
2013-06-21 10:53 ` Alexey Brodkin
2013-06-21 12:15 ` Andy Shevchenko
2013-06-21 12:25 ` Alexey Brodkin [this message]
2013-06-21 12:40 ` Andy Shevchenko
2013-06-21 14:43 ` Joe Perches
2013-06-21 15:58 ` Arnd Bergmann
2013-06-21 16:05 ` Joe Perches
2013-06-21 16:22 ` David Laight
2013-06-21 18:27 ` David Miller
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=4881796E12491D4BB15146FE0209CE643F5F5DBB@DE02WEMBXB.internal.synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Mischa.Jonker@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=florian@openwrt.org \
--cc=grant.likely@linaro.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rob.herring@calxeda.com \
--cc=romieu@fr.zoreil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®