Re: [PATCH] drivers/base/core.c: always output device renaming messages.

[Greg KH <gregkh@linuxfoundation.org>]

On Fri, Oct 11, 2013 at 10:08:09AM -0600, Bjorn Helgaas wrote:
> [+cc Don, e1000-devel]
> 
> On Fri, Oct 11, 2013 at 9:35 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Fri, Oct 11, 2013 at 10:58:18AM +0800, ethan.zhao wrote:
> >> From: "ethan.zhao" <ethan.kernel@gmail.com>
> >>
> >> While loading ixgbevf driver,every vf detected will be output as the
> >> same name 'eth4':
> >>
> >>  ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver -
> >>  version 2.8.7
> >>  Copyright (c) 2009-2012 Intel Corporation.
> >>  ixgbevf 0000:20:10.0: enabling device (0000 -> 0002)
> >>  ixgbe 0000:20:00.0 eth0: VF Reset msg received from vf 0
> >>  ixgbevf 0000:20:10.0: irq 199 for MSI/MSI-X
> >>  ixgbevf 0000:20:10.0: irq 200 for MSI/MSI-X
> >>  ixgbevf: eth%d: ixgbevf_init_interrupt_scheme: Multiqueue Disabled: Rx Queue
> >>  count = 1, Tx Queue count = 1
> >
> > What is that message?  That's not good, "eth%d"?
> 
> Just a reminder that ixgbevf 2.8.7 is not the driver version that's in
> the kernel tree, so it's easy to spend time on mainline issue that
> have been fixed in the out-of-tree versions, or vice versa.
> 
> Per Don, the latest ixgbevf driver is here:
> https://sourceforge.net/projects/e1000/files/ixgbevf%20stable/

I hate to ask why isn't this merged upstream, but given that this is an
Intel network driver, I know the answer :(

Thanks for pointing this out, saved me a trip through the kernel tree...

greg k-h

> 
> Bjorn