From: Jan Ceuleers <jan.ceuleers@computer.org>
To: Florian Fainelli <florian@openwrt.org>
Cc: 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 15:42:09 +0200 [thread overview]
Message-ID: <4FCE0CB1.50508@computer.org> (raw)
In-Reply-To: <4550590.BhQA539plh@flexo>
On 06/05/2012 12:54 PM, Florian Fainelli wrote:
> What about you setup a cross-compiler and build for one of these architectures
> where the driver is enabled?
I have now managed to cross-compile the two files I'm touching; thanks
very much to Florian for assisting me off-list. Will send v3 (no changes
relative to RFC v2).
Jan
next prev parent reply other threads:[~2012-06-05 13:45 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
2012-06-05 13:42 ` Jan Ceuleers [this message]
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=4FCE0CB1.50508@computer.org \
--to=jan.ceuleers@computer.org \
--cc=b06378@freescale.com \
--cc=davem@davemloft.net \
--cc=florian@openwrt.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 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.