summaryrefslogtreecommitdiff
path: root/target/linux/generic
diff options
context:
space:
mode:
authorRafał Miłecki <zajec5@gmail.com>2015-09-08 16:43:10 +0000
committerRafał Miłecki <zajec5@gmail.com>2015-09-08 16:43:10 +0000
commit255d7ad8ba1cc4ce05f9b2a6ef6e1c205cd481b0 (patch)
tree114932497e37bf3287b3a35901c86719ebfd2847 /target/linux/generic
parentf8a689d276cb8549fa9768cba7d12adf180ac1c4 (diff)
downloadmtk-20170518-255d7ad8ba1cc4ce05f9b2a6ef6e1c205cd481b0.zip
mtk-20170518-255d7ad8ba1cc4ce05f9b2a6ef6e1c205cd481b0.tar.gz
mtk-20170518-255d7ad8ba1cc4ce05f9b2a6ef6e1c205cd481b0.tar.bz2
kernel: describe bridge patch "remove IPv6 depependency of bridge in 2.6.38+"
It was initially added in r27237 by jow as patch from Jonas. SVN-Revision: 46826
Diffstat (limited to 'target/linux/generic')
-rw-r--r--target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch13
-rw-r--r--target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch13
-rw-r--r--target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch13
3 files changed, 39 insertions, 0 deletions
diff --git a/target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch b/target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch
index 3f0dcd3..25f49c0 100644
--- a/target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch
+++ b/target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch
@@ -1,3 +1,16 @@
+From: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
+Subject: [PATCH] bridge: remove IPv6 depependency of bridge in 2.6.38+
+
+Since 2.6.38 the bridge module has a dependency to IPv6 if IPv6 is
+enabled. Since the IPv6 module isn't exactly lightweight and bridge also
+only needs a single function from IPv6, it's rather easy to create a
+common "lib" module with a RCU pointer to the actual implementation, if
+the IPv6 module is loaded (although slightly hackish).
+
+The codepath seems to be only taken when using IPv6, so there should be
+no negative side effects when IPv6 isn't loaded. I did not measure how
+big the performance impact is.
+---
--- a/include/net/addrconf.h
+++ b/include/net/addrconf.h
@@ -88,6 +88,12 @@ int ipv6_rcv_saddr_equal(const struct so
diff --git a/target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch b/target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch
index 50e4fe4..6842d97 100644
--- a/target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch
+++ b/target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch
@@ -1,3 +1,16 @@
+From: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
+Subject: [PATCH] bridge: remove IPv6 depependency of bridge in 2.6.38+
+
+Since 2.6.38 the bridge module has a dependency to IPv6 if IPv6 is
+enabled. Since the IPv6 module isn't exactly lightweight and bridge also
+only needs a single function from IPv6, it's rather easy to create a
+common "lib" module with a RCU pointer to the actual implementation, if
+the IPv6 module is loaded (although slightly hackish).
+
+The codepath seems to be only taken when using IPv6, so there should be
+no negative side effects when IPv6 isn't loaded. I did not measure how
+big the performance impact is.
+---
--- a/include/net/addrconf.h
+++ b/include/net/addrconf.h
@@ -91,6 +91,12 @@ int ipv6_rcv_saddr_equal(const struct so
diff --git a/target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch b/target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch
index 001d2c6..b18f33e 100644
--- a/target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch
+++ b/target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch
@@ -1,3 +1,16 @@
+From: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
+Subject: [PATCH] bridge: remove IPv6 depependency of bridge in 2.6.38+
+
+Since 2.6.38 the bridge module has a dependency to IPv6 if IPv6 is
+enabled. Since the IPv6 module isn't exactly lightweight and bridge also
+only needs a single function from IPv6, it's rather easy to create a
+common "lib" module with a RCU pointer to the actual implementation, if
+the IPv6 module is loaded (although slightly hackish).
+
+The codepath seems to be only taken when using IPv6, so there should be
+no negative side effects when IPv6 isn't loaded. I did not measure how
+big the performance impact is.
+---
--- a/include/net/addrconf.h
+++ b/include/net/addrconf.h
@@ -91,6 +91,12 @@ int ipv6_rcv_saddr_equal(const struct so