1. 14 3月, 2010 1 次提交
    • J
      drivers/net/tulip/eeprom.c: fix bogus "(null)" in tulip init messages · c251c7f7
      Joe Perches 提交于
      On Wed, 2010-03-10 at 08:41 -0800, David Miller wrote:
      > From: Mikael Pettersson <mikpe@it.uu.se>
      > Date: Wed, 10 Mar 2010 16:33:28 +0100
      > > Booting 2.6.34-rc1 on a machine with a tulip nic I see
      > > a number of kernel messages that include "(null)" where
      > > previous kernels included the string "tulip0":
      > CC:'ing the guilty party :-)  It's one of the following
      > commits:
      
      Thanks Mikael.
      
      Anonymity has some good attributes.
      Blame avoidance is one of them.
      
      I've broad shoulders.  It's me, then Dwight Howard...
      
      There might be another few of these where ->name or ->dev
      was used before struct device or net_device was registered.
      I'll go back and check.
      
      tulip_core has:
      
      	if (tp->flags & HAS_MEDIA_TABLE) {
      		sprintf(dev->name, DRV_NAME "%d", board_idx);	/* hack */
      		tulip_parse_eeprom(dev);
      		strcpy(dev->name, "eth%d");			/* un-hack */
      	}
      
      So I don't feel _too_ bad.
      
      tulip_parse_eeprom is done before register_netdev so the logging
      there can not use netdev_<level> or dev_<level>(&dev->dev
      Signed-off-by: NJoe Perches <joe@perches.com>
      Tested-by: NMikael Pettersson <mikpe@it.uu.se>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c251c7f7
  2. 19 2月, 2010 1 次提交
  3. 13 2月, 2010 1 次提交
  4. 01 2月, 2010 13 次提交
  5. 23 1月, 2010 1 次提交
  6. 08 1月, 2010 2 次提交
  7. 04 12月, 2009 1 次提交
  8. 19 11月, 2009 1 次提交
  9. 04 9月, 2009 1 次提交
  10. 01 9月, 2009 1 次提交
  11. 15 8月, 2009 1 次提交
  12. 03 8月, 2009 1 次提交
  13. 09 7月, 2009 1 次提交
  14. 06 7月, 2009 2 次提交
  15. 13 6月, 2009 1 次提交
  16. 11 6月, 2009 1 次提交
  17. 02 5月, 2009 1 次提交
  18. 14 4月, 2009 1 次提交
  19. 07 4月, 2009 1 次提交
  20. 19 3月, 2009 1 次提交
    • K
      tulip: fix crash on iface up with shirq debug · 69145635
      Kyle McMartin 提交于
      Tulip is currently doing request_irq before it has done its
      initialization. This is usually not a problem because it hasn't
      enable interrupts yet, but with DEBUG_SHIRQ on, we call the irq handler
      when registering the interrupt as a sanity check.
      
      This can result in a NULL ptr dereference, so call tulip_init_ring
      before request_irq, and add a free_ring function to do the freeing
      now shared with tulip_close.
      
      Tested with a shell loop running ifup, ifdown in a loop a few hundred
      times with DEBUG_SHIRQ on.
      Signed-off-by: NKyle McMartin <kyle@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      69145635
  21. 14 3月, 2009 1 次提交
  22. 27 2月, 2009 1 次提交
  23. 18 2月, 2009 2 次提交
  24. 09 2月, 2009 1 次提交
  25. 03 2月, 2009 1 次提交