Re: [E1000-devel] [PATCH net-next 0/8] etherdevice: Rename random_ether_addr to eth_random_addr
On Thu, Jul 12, 2012 at 10:33:04PM -0700, Joe Perches wrote: net-next commit ad7eee98be (etherdevice: introduce eth_broadcast_addr) added a new style API. Rename random_ether_addr to eth_random_addr to create some API symmetry. Joe Perches (8): etherdevice: Rename random_ether_addr to eth_random_addr if you're really renaming the function, then this patch alone will break all of the below users. That should all be a single patch, I'm afraid. ethernet: Use eth_random_addr net: usb: Use eth_random_addr wireless: Use eth_random_addr drivers/net: Use eth_random_addr s390: Use eth_random_addr usb: Use eth_random_addr arch: Use eth_random_addr arch/blackfin/mach-bf537/boards/stamp.c |2 +- arch/c6x/kernel/soc.c |2 +- arch/mips/ar7/platform.c |4 ++-- arch/mips/powertv/powertv_setup.c |6 +++--- arch/um/drivers/net_kern.c|2 +- drivers/net/ethernet/atheros/atl1c/atl1c_hw.c |2 +- drivers/net/ethernet/atheros/atlx/atl1.c |2 +- drivers/net/ethernet/atheros/atlx/atl2.c |2 +- drivers/net/ethernet/ethoc.c |2 +- drivers/net/ethernet/intel/igb/igb_main.c |4 ++-- drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c|2 +- drivers/net/ethernet/lantiq_etop.c|2 +- drivers/net/ethernet/micrel/ks8851.c |2 +- drivers/net/ethernet/micrel/ks8851_mll.c |2 +- drivers/net/ethernet/smsc/smsc911x.c |2 +- drivers/net/ethernet/ti/cpsw.c|2 +- drivers/net/ethernet/tile/tilegx.c|2 +- drivers/net/ethernet/wiznet/w5100.c |2 +- drivers/net/ethernet/wiznet/w5300.c |2 +- drivers/net/ethernet/xilinx/xilinx_axienet_main.c |2 +- drivers/net/tun.c |2 +- drivers/net/usb/smsc75xx.c|2 +- drivers/net/usb/smsc95xx.c|2 +- drivers/net/usb/usbnet.c |2 +- drivers/net/wimax/i2400m/driver.c |2 +- drivers/net/wireless/adm8211.c|2 +- drivers/net/wireless/p54/eeprom.c |2 +- drivers/net/wireless/rt2x00/rt2400pci.c |2 +- drivers/net/wireless/rt2x00/rt2500pci.c |2 +- drivers/net/wireless/rt2x00/rt2500usb.c |2 +- drivers/net/wireless/rt2x00/rt2800lib.c |2 +- drivers/net/wireless/rt2x00/rt61pci.c |2 +- drivers/net/wireless/rt2x00/rt73usb.c |2 +- drivers/net/wireless/rtl818x/rtl8180/dev.c|2 +- drivers/net/wireless/rtl818x/rtl8187/dev.c|2 +- drivers/s390/net/qeth_l2_main.c |2 +- drivers/s390/net/qeth_l3_main.c |2 +- drivers/usb/atm/xusbatm.c |4 ++-- drivers/usb/gadget/u_ether.c |2 +- include/linux/etherdevice.h | 14 -- 40 files changed, 52 insertions(+), 50 deletions(-) -- 1.7.8.111.gad25c.dirty -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- balbi signature.asc Description: Digital signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
Re: [E1000-devel] [PATCH net-next 0/8] etherdevice: Rename random_ether_addr to eth_random_addr
From: Felipe Balbi ba...@ti.com Date: Mon, 16 Jul 2012 13:14:38 +0300 if you're really renaming the function, then this patch alone will break all of the below users. That should all be a single patch, I'm afraid. It would help if you actually read his patches before saying what they might or might not do. He provides a macro in the first patch that provides the old name, and this will get removed at the end. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
Re: [E1000-devel] [PATCH net-next 0/8] etherdevice: Rename random_ether_addr to eth_random_addr
Hi, On Mon, Jul 16, 2012 at 03:29:01AM -0700, David Miller wrote: From: Felipe Balbi ba...@ti.com Date: Mon, 16 Jul 2012 13:14:38 +0300 if you're really renaming the function, then this patch alone will break all of the below users. That should all be a single patch, I'm afraid. It would help if you actually read his patches before saying what they might or might not do. He provides a macro in the first patch that provides the old name, and this will get removed at the end. that's why I put an if there. The subject was misleading and I really couldn't bother going search for the patch on the mail archives. Anyway, if nothing will be broken then for drivers/usb/gadget/: Acked-by: Felipe Balbi ba...@ti.com -- balbi signature.asc Description: Digital signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
Re: [E1000-devel] [PATCH net-next 0/8] etherdevice: Rename random_ether_addr to eth_random_addr
From: Felipe Balbi ba...@ti.com Date: Mon, 16 Jul 2012 14:12:19 +0300 Acked-by: Felipe Balbi ba...@ti.com You need to provide this in a reply to the patch you actually want to ACK, so that the patch tracking system attaches your ACK to the proper patch. Thank you. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
[E1000-devel] Coaching and Counseling, 30 - 31 Juli 2012 di Jakarta
Your email client cannot read this email. To view it online, please go here: http://www.solutioncentreindonesia.com/mm/display.php?M=16912C=661d88d746197c1376c21d5547a358f8S=11L=1N=5 To stop receiving these emails:http://www.solutioncentreindonesia.com/mm/unsubscribe.php?M=16912C=661d88d746197c1376c21d5547a358f8L=1N=11 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
Re: [E1000-devel] 82571EB: Detected Hardware Unit Hang
On Sun, 2012-07-15 at 10:35 -0300, Henrique de Moraes Holschuh wrote: On Sun, 15 Jul 2012, Dave, Tushar N wrote: Somehow setting max payload to 256 from BIOS does not set this value for all devices. I believe this is a BIOS bug. And preferably, Linux should complain about it. Since we know it is going to cause problems, and since we know it does happen, we should be raising a ruckus about it in the kernel log (and probably fixing it to min(path) while at it)... Is this something that should be raised as a feature request with the PCI/PCIe subsystem? The feature is there, but we ended up with: commit 5f39e6705faade2e89d119958a8c51b9b6e2c53c Author: Jon Mason ma...@myri.com Date: Mon Oct 3 09:50:20 2011 -0500 PCI: Disable MPS configuration by default But you are welcome to share use of the fixup_mpss_256() quirk. Ben. -- Ben Hutchings, Staff Engineer, Solarflare Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
Re: [E1000-devel] 82571EB: Detected Hardware Unit Hang
On Mon, 16 Jul 2012, Ben Hutchings wrote: On Sun, 2012-07-15 at 10:35 -0300, Henrique de Moraes Holschuh wrote: On Sun, 15 Jul 2012, Dave, Tushar N wrote: Somehow setting max payload to 256 from BIOS does not set this value for all devices. I believe this is a BIOS bug. And preferably, Linux should complain about it. Since we know it is going to cause problems, and since we know it does happen, we should be raising a ruckus about it in the kernel log (and probably fixing it to min(path) while at it)... Is this something that should be raised as a feature request with the PCI/PCIe subsystem? The feature is there, but we ended up with: commit 5f39e6705faade2e89d119958a8c51b9b6e2c53c Author: Jon Mason ma...@myri.com Date: Mon Oct 3 09:50:20 2011 -0500 PCI: Disable MPS configuration by default But you are welcome to share use of the fixup_mpss_256() quirk. Meh. I'd be happy with a warning if MPSS decreases when walking up to the tree root... i.e. a warning if any child has a MPSS larger than the parent. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
Re: [E1000-devel] 82571EB: Detected Hardware Unit Hang
On Mon, Jul 16, 2012 at 9:08 AM, Henrique de Moraes Holschuh h...@hmh.eng.br wrote: On Mon, 16 Jul 2012, Ben Hutchings wrote: On Sun, 2012-07-15 at 10:35 -0300, Henrique de Moraes Holschuh wrote: On Sun, 15 Jul 2012, Dave, Tushar N wrote: Somehow setting max payload to 256 from BIOS does not set this value for all devices. I believe this is a BIOS bug. And preferably, Linux should complain about it. Since we know it is going to cause problems, and since we know it does happen, we should be raising a ruckus about it in the kernel log (and probably fixing it to min(path) while at it)... Is this something that should be raised as a feature request with the PCI/PCIe subsystem? The feature is there, but we ended up with: commit 5f39e6705faade2e89d119958a8c51b9b6e2c53c Author: Jon Mason ma...@myri.com Date: Mon Oct 3 09:50:20 2011 -0500 PCI: Disable MPS configuration by default But you are welcome to share use of the fixup_mpss_256() quirk. Meh. I'd be happy with a warning if MPSS decreases when walking up to the tree root... i.e. a warning if any child has a MPSS larger than the parent. You can add pci=pcie_bus_safe to the kernel params and it should resolve your issue. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
Re: [E1000-devel] [PATCH net-next 0/8] etherdevice: Rename random_ether_addr to eth_random_addr
From: Joe Perches j...@perches.com Date: Thu, 12 Jul 2012 22:33:04 -0700 net-next commit ad7eee98be (etherdevice: introduce eth_broadcast_addr) added a new style API. Rename random_ether_addr to eth_random_addr to create some API symmetry. Series applied, thanks Joe. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel#174; Ethernet, visit http://communities.intel.com/community/wired
