mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: randy_dunlap <rdunlap@xenotime.net>
To: Dominik Karall <dominik.karall@gmx.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc1-mm1
Date: Fri, 1 Jul 2005 19:55:30 -0700	[thread overview]
Message-ID: <20050701195530.5e4e2b4e.rdunlap@xenotime.net> (raw)
In-Reply-To: <200507020443.27889.dominik.karall@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 755 bytes --]

On Sat, 2 Jul 2005 04:43:23 +0200 Dominik Karall wrote:

| On Friday 01 July 2005 13:40, Andrew Morton wrote:
| > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc1/2.
| >6.13-rc1-mm1/
| 
| I get this warning on modules_install:
| WARNING: /lib/modules/2.6.13-rc1-mm1/kernel/net/ieee80211/ieee80211.ko needs 
| unknown symbol is_broadcast_ether_addr


From:	Bernhard Rosenkraenzer <bero@arklinux.org>
To:	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] 2.6.13-rc1-mm1 unresolved symbols
Date:	Fri, 1 Jul 2005 18:18:17 +0200
Organization: Ark Linux team
User-Agent: KMail/1.8.1

ipw2200 in 2.6.13-rc1-mm1 makes use of is_broadcast_ether_addr, which was 
removed.

The attached patch restores that function for now.

---


[-- Attachment #2: 2.6.13-rc1-mm1-restore-is_broadcast_ether_addr.patch --]
[-- Type: application/octet-stream, Size: 632 bytes --]

--- linux-2.6.13-rc1/include/net/ieee80211.h.ark	2005-07-01 17:46:22.000000000 +0200
+++ linux-2.6.13-rc1/include/net/ieee80211.h	2005-07-01 17:47:26.000000000 +0200
@@ -627,6 +627,11 @@
 #define MAC_FMT "%02x:%02x:%02x:%02x:%02x:%02x"
 #define MAC_ARG(x) ((u8*)(x))[0],((u8*)(x))[1],((u8*)(x))[2],((u8*)(x))[3],((u8*)(x))[4],((u8*)(x))[5]
 
+extern inline int is_broadcast_ether_addr(const u8 *addr)
+{
+	return ((addr[0] == 0xff) && (addr[1] == 0xff) && (addr[2] == 0xff) &&
+		(addr[3] == 0xff) && (addr[4] == 0xff) && (addr[5] == 0xff));
+}
 
 #define CFG_IEEE80211_RESERVE_FCS (1<<0)
 #define CFG_IEEE80211_COMPUTE_FCS (1<<1)


  reply	other threads:[~2005-07-02  2:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 11:40 2.6.13-rc1-mm1 Andrew Morton
2005-07-01 12:33 ` 2.6.13-rc1-mm1 Daniel Andersen
2005-07-01 22:05 ` 2.6.13-rc1-mm1 Rafael J. Wysocki
2005-07-02  3:19   ` Firewire/SBP2 and the -mm tree (was: Re: 2.6.13-rc1-mm1) Rogério Brito
2005-07-02  4:34     ` Rogério Brito
2005-07-02  9:56     ` Firewire/SBP2 and the -mm tree Stefan Richter
2005-07-03  5:33       ` Rogério Brito
2005-07-03 18:04         ` Rogério Brito
2005-07-03 20:03           ` Stefan Richter
2005-07-04 20:05             ` Rogério Brito
2005-07-02 13:39     ` Firewire/SBP2 and the -mm tree (was: Re: 2.6.13-rc1-mm1) Ben Collins
2005-07-04 20:27   ` 2.6.13-rc1-mm1 Alexey Dobriyan
2005-07-02  0:22 ` [PATCH] sched: consider migration thread with smp nice Con Kolivas
2005-07-02  2:43 ` 2.6.13-rc1-mm1 Dominik Karall
2005-07-02  2:55   ` randy_dunlap [this message]
2005-07-02  5:39 ` 2.6.13-rc1-mm1 Grant Coady
2005-07-02  9:16 ` 2.6.13-rc1-mm1: git-mtd.patch breaks i386 compile Adrian Bunk
2005-07-02  9:37   ` Thomas Gleixner
2005-07-04 23:04     ` Thomas Gleixner
2005-07-04 12:36 ` 2.6.13-rc1-mm1 Joseph Fannin
2005-07-02 16:50 2.6.13-rc1-mm1 Zoltan Boszormenyi

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=20050701195530.5e4e2b4e.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@osdl.org \
    --cc=dominik.karall@gmx.net \
    --cc=linux-kernel@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

Powered by JetHome