linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Hannemann <arnd@arndnet.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>,
	b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43legacy: Fix compile on ARM architecture
Date: Thu, 11 Nov 2010 18:48:48 +0100	[thread overview]
Message-ID: <4CDC2C80.6030807@arndnet.de> (raw)
In-Reply-To: <4cdc2b80.RuMMb1PuVmklU3JJ%Larry.Finger@lwfinger.net>

Am 11.11.2010 18:44, schrieb Larry Finger:
> From: Arnd Hannemann <arnd@arndnet.de>
> 
> When b43legacy is compiled on the arm platform, the following errors are seen:
> 
>   CC [M]  drivers/net/wireless/b43legacy/xmit.o
> In file included from include/net/dst.h:11,
> from drivers/net/wireless/b43legacy/xmit.c:31:
> include/net/dst_ops.h:28: error: expected ':', ',', ';', '}' or '__attribute__'
>    before '____cacheline_aligned_in_smp'
> include/net/dst_ops.h: In function 'dst_entries_get_fast':
> include/net/dst_ops.h:33: error: 'struct dst_ops' has no member named
>    'pcpuc_entries'
> include/net/dst_ops.h: In function 'dst_entries_get_slow':
> include/net/dst_ops.h:41: error: 'struct dst_ops' has no member named
>    'pcpuc_entries'
> include/net/dst_ops.h: In function 'dst_entries_add':
> include/net/dst_ops.h:49: error: 'struct dst_ops' has no member named
>    'pcpuc_entries'
> include/net/dst_ops.h: In function 'dst_entries_init':
> include/net/dst_ops.h:55: error: 'struct dst_ops' has no member named
>    'pcpuc_entries'
> include/net/dst_ops.h: In function 'dst_entries_destroy':
> include/net/dst_ops.h:60: error: 'struct dst_ops' has no member named
>    'pcpuc_entries'
> make[4]: *** [drivers/net/wireless/b43legacy/xmit.o] Error 1
> make[3]: *** [drivers/net/wireless/b43legacy] Error 2
> make[2]: *** [drivers/net/wireless] Error 2
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
> 
> The cause is a missing include of <linux/cache.h>, which is present for
> i386 and x86_64 architectures, but not for arm.
> 
> Signed-off-by: Arnd Hannemann <arnd@arndnet.de>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@kernel.org>
> ---
> 
> John,
> 
> Once I get the ability to cross-compile ARM architecture, I will check to
> see if the equivalent patch is needed for b43.

b43 compiles fine for me for the same target.

Thanks,
Arnd

> 
> Larry
> ---
> 
> Index: linux-2.6/include/net/dst_ops.h
> ===================================================================
> --- linux-2.6.orig/include/net/dst_ops.h
> +++ linux-2.6/include/net/dst_ops.h
> @@ -2,6 +2,7 @@
>  #define _NET_DST_OPS_H
>  #include <linux/types.h>
>  #include <linux/percpu_counter.h>
> +#include <linux/cache.h>
>  
>  struct dst_entry;
>  struct kmem_cachep;
> 


  reply	other threads:[~2010-11-11 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 17:44 [PATCH] b43legacy: Fix compile on ARM architecture Larry Finger
2010-11-11 17:48 ` Arnd Hannemann [this message]
2010-11-11 18:02   ` Larry Finger

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=4CDC2C80.6030807@arndnet.de \
    --to=arnd@arndnet.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).