All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Greg KH <greg@kroah.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	Haiyang Zhang <haiyangz@microsoft.com>,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [PATCH] net/hyperv: Advertise hv_netvsc instead of netvsc as driver name
Date: Thu, 8 Mar 2012 19:38:20 +0100	[thread overview]
Message-ID: <20120308183820.GA25015@aepfle.de> (raw)
In-Reply-To: <20120308174220.GB17192@kroah.com>

On Thu, Mar 08, Greg KH wrote:

> On Thu, Mar 08, 2012 at 05:12:21PM +0100, Olaf Hering wrote:
> > On Thu, Mar 08, Greg KH wrote:
> > 
> > > > hwinfo uses it to recognize a network interface (storage in case of
> > > > hv_storvsc).
> > > 
> > > That tool should report the real module name, not rely on the name to
> > > match based on the structure, if you really care about the real module
> > > name.
> > 
> > Its about the driver symlink, not the module name. 
> > 
> > I think most, if not all, (relevant) drivers use some sort of
> > KBUILD_MODNAME. Why should this driver be any different?
> 
> It shouldn't, I'm not saying that at all.  I'm only objecting to the
> insistance that this be something worthwhile for 3.3-final which should
> be out any day now.

Since its an API we could settle on the new string, which is already in
distro use.

Olaf

  reply	other threads:[~2012-03-08 18:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 19:05 [PATCH] net/hyperv: Advertise hv_netvsc instead of netvsc as driver name Haiyang Zhang
2012-03-07 19:22 ` Greg KH
2012-03-07 19:22   ` Greg KH
2012-03-07 19:57   ` Haiyang Zhang
2012-03-07 20:17 ` Olaf Hering
2012-03-07 20:49   ` Greg KH
2012-03-07 20:49     ` Greg KH
2012-03-08  6:16     ` Olaf Hering
2012-03-08 15:52       ` Greg KH
2012-03-08 15:52         ` Greg KH
2012-03-08 16:12         ` Olaf Hering
2012-03-08 17:42           ` Greg KH
2012-03-08 18:38             ` Olaf Hering [this message]
2012-03-08 18:45               ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120308183820.GA25015@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=davem@davemloft.net \
    --cc=devel@linuxdriverproject.org \
    --cc=greg@kroah.com \
    --cc=haiyangz@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.