The patch titled
e1000e triggers sparc32 gcc bug
has been added to the -mm tree. Its filename is
e1000e-triggers-sparc32-gcc-bug.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: e1000e triggers sparc32 gcc bug
From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
... and isn't possible on sparc32 boxen anyway, unless somebody had done
JavaStation with PCIE lately.
Signed-off-by: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Acked-by: David S. Miller <davem@xxxxxxxxxxxxx>
Cc: Jeff Garzik <jgarzik@xxxxxxxxx>
Cc: Auke Kok <auke-jan.h.kok@xxxxxxxxx>
Cc: Jesse Brandeburg <jesse.brandeburg@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/net/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/net/Kconfig~e1000e-triggers-sparc32-gcc-bug drivers/net/Kconfig
--- a/drivers/net/Kconfig~e1000e-triggers-sparc32-gcc-bug
+++ a/drivers/net/Kconfig
@@ -2011,7 +2011,7 @@ config E1000_DISABLE_PACKET_SPLIT
config E1000E
tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
- depends on PCI
+ depends on PCI && (!SPARC32 || BROKEN)
default E1000
---help---
This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
_
Patches currently in -mm which might be from viro@xxxxxxxxxxxxxxxxxx are
origin.patch
git-kvm.patch
e1000e-triggers-sparc32-gcc-bug.patch
git-scsi-misc.patch
ecryptfs-protect-crypt_stat-flags-in-ecryptfs_open.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
