Searched hist:253303 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-10.2-release/sys/modules/igb/ | ||
| H A D | Makefile | diff 253303 Fri Jul 12 22:43:46 MDT 2013 jfv Change the E1000 driver option header handling to match the ixgbe driver. As it was, when building them as a module INET and INET6 are not defined. In these drivers it does not cause a panic, however it does result in different behavior in the ioctl routine when you are using a module vs static, and I think the behavior should be the same. MFC after: 3 days |
| /freebsd-10.2-release/sys/modules/em/ | ||
| H A D | Makefile | diff 253303 Fri Jul 12 22:43:46 MDT 2013 jfv Change the E1000 driver option header handling to match the ixgbe driver. As it was, when building them as a module INET and INET6 are not defined. In these drivers it does not cause a panic, however it does result in different behavior in the ioctl routine when you are using a module vs static, and I think the behavior should be the same. MFC after: 3 days |
| /freebsd-10.2-release/sys/dev/e1000/ | ||
| H A D | if_lem.c | diff 253303 Fri Jul 12 22:43:46 MDT 2013 jfv Change the E1000 driver option header handling to match the ixgbe driver. As it was, when building them as a module INET and INET6 are not defined. In these drivers it does not cause a panic, however it does result in different behavior in the ioctl routine when you are using a module vs static, and I think the behavior should be the same. MFC after: 3 days |
| H A D | if_igb.c | diff 253303 Fri Jul 12 22:43:46 MDT 2013 jfv Change the E1000 driver option header handling to match the ixgbe driver. As it was, when building them as a module INET and INET6 are not defined. In these drivers it does not cause a panic, however it does result in different behavior in the ioctl routine when you are using a module vs static, and I think the behavior should be the same. MFC after: 3 days |
| H A D | if_em.c | diff 253303 Fri Jul 12 22:43:46 MDT 2013 jfv Change the E1000 driver option header handling to match the ixgbe driver. As it was, when building them as a module INET and INET6 are not defined. In these drivers it does not cause a panic, however it does result in different behavior in the ioctl routine when you are using a module vs static, and I think the behavior should be the same. MFC after: 3 days |
Completed in 186 milliseconds