From: Eric Dumazet <eric.dumazet@gmail.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: Jan Ceuleers <jan.ceuleers@computer.org>,
David Miller <davem@davemloft.net>,
b06378@freescale.com, joe@perches.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 5/5] gianfar_ethtool: coding style and whitespace cleanups
Date: Tue, 05 Jun 2012 13:10:11 +0200 [thread overview]
Message-ID: <1338894611.2760.2327.camel@edumazet-glaptop> (raw)
In-Reply-To: <4550590.BhQA539plh@flexo>
On Tue, 2012-06-05 at 12:54 +0200, Florian Fainelli wrote:
> Hi,
>
> On Tuesday 05 June 2012 12:49:43 Jan Ceuleers wrote:
> > The error I quoted was a fatal error, meaning that compilation did not
> > proceed beyond the point to which the error pertained (inclusion of a
> > header that does not exist in my arch). So I cannot test-compile the
> > driver on my arch and draw any conclusions from that beyond line 91.
>
> What about you setup a cross-compiler and build for one of these architectures
> where the driver is enabled?
That pretty easy IMHO : http://www.kernel.org/pub/tools/crosstool/
next prev parent reply other threads:[~2012-06-05 11:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 16:31 [PATCH net-next 0/5] gianfar: coding style cleanups Jan Ceuleers
2012-06-04 16:31 ` [PATCH net-next 1/5] gianfar: whitespace cleanup - pointers Jan Ceuleers
2012-06-04 16:31 ` [PATCH net-next 2/5] gianfar: comment cleanup Jan Ceuleers
2012-06-04 16:31 ` [PATCH net-next 3/5] gianfar: various coding style and whitespace cleanups Jan Ceuleers
2012-06-04 16:31 ` [PATCH net-next 4/5] gianfar: Remove superfluous initialisations Jan Ceuleers
2012-06-04 16:31 ` [PATCH net-next 5/5] gianfar_ethtool: coding style and whitespace cleanups Jan Ceuleers
2012-06-04 18:08 ` David Miller
2012-06-04 19:11 ` Jan Ceuleers
2012-06-04 19:52 ` David Miller
2012-06-05 5:54 ` Jan Ceuleers
2012-06-05 9:14 ` David Miller
2012-06-05 10:49 ` Jan Ceuleers
2012-06-05 10:54 ` Florian Fainelli
2012-06-05 11:10 ` Eric Dumazet [this message]
2012-06-05 13:42 ` Jan Ceuleers
2012-06-05 21:38 ` David Miller
2012-06-05 21:37 ` 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=1338894611.2760.2327.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=b06378@freescale.com \
--cc=davem@davemloft.net \
--cc=florian@openwrt.org \
--cc=jan.ceuleers@computer.org \
--cc=joe@perches.com \
--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