From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH] batman-adv: Use eth_hw_addr_random compat also for kernel 3.3
Date: Wed, 28 Mar 2012 13:35:05 +0200 [thread overview]
Message-ID: <1332934505-22964-1-git-send-email-sven@narfation.org> (raw)
The changes for eth_hw_addr_random were not merged in linux 3.3. Therefore, the
compat layer has to provide it.
Signed-off-by: Sven Eckelmann <sven@narfation.org>
---
compat.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/compat.h b/compat.h
index 46de8b0..92379ef 100644
--- a/compat.h
+++ b/compat.h
@@ -132,13 +132,13 @@ void free_rcu_backbone_gw(struct rcu_head *rcu);
#endif /* < KERNEL_VERSION(3, 0, 0) */
-#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 3, 0)
+#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 4, 0)
static inline void eth_hw_addr_random(struct net_device *dev)
{
random_ether_addr(dev->dev_addr);
}
-#endif /* < KERNEL_VERSION(3, 0, 0) */
+#endif /* < KERNEL_VERSION(3, 4, 0) */
#endif /* _NET_BATMAN_ADV_COMPAT_H_ */
--
1.7.9.1
next reply other threads:[~2012-03-28 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 11:35 Sven Eckelmann [this message]
2012-03-28 15:03 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Use eth_hw_addr_random compat also for kernel 3.3 Marek Lindner
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=1332934505-22964-1-git-send-email-sven@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.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).