netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Ceuleers <jan.ceuleers@computer.org>
To: David Miller <davem@davemloft.net>
Cc: 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 07:54:29 +0200	[thread overview]
Message-ID: <4FCD9F15.2050605@computer.org> (raw)
In-Reply-To: <20120604.155229.822064530175335346.davem@davemloft.net>

On 06/04/2012 09:52 PM, David Miller wrote:
> From: Jan Ceuleers <jan.ceuleers@computer.org>
> Date: Mon, 04 Jun 2012 21:11:09 +0200
> 
>> Well then I'm sorry but I won't be resubmitting
> 
> Because you can't test the build?
> 
> You absolutely can, on any architecture, that's how I found your typo.
> 
> Force the build with "make path/to/driver/foo.o" and scan through the
> non-architecture-specific warnings and errors.

I don't want to waste your time, and I'm sorry for having made a typo,
and I thank you for finding it, but I had tried that and hit the
following (I'm on x86):

  CC      drivers/net/ethernet/freescale/gianfar.o
drivers/net/ethernet/freescale/gianfar.c:91:21: fatal error: asm/reg.h:
No such file or directory
compilation terminated.
make[1]: *** [drivers/net/ethernet/freescale/gianfar.o] Error 1
make: *** [drivers/net/ethernet/freescale/gianfar.o] Error 2

That's without any of my patches applied.

The missing file exists only on some architectures:

janc@mordor:~/git/net-next$ find arch -name reg.h -print
arch/powerpc/boot/reg.h
arch/powerpc/include/asm/reg.h
arch/alpha/include/asm/reg.h
arch/mips/include/asm/reg.h
arch/arm/mach-bcmring/include/csp/reg.h

So your build environment happens to be one of powerpc, alpha or mips,
does it?

I will submit a v2 as RFC. Would the Freescale team please look at it?

Thanks, Jan

  reply	other threads:[~2012-06-05  5:54 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 [this message]
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
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=4FCD9F15.2050605@computer.org \
    --to=jan.ceuleers@computer.org \
    --cc=b06378@freescale.com \
    --cc=davem@davemloft.net \
    --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;
as well as URLs for NNTP newsgroup(s).