linux-kernel - Re: [PATCH] net/hyperv: Advertise hv_netvsc instead of netvsc as driver name

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120308184545.GA1100@kroah.com>
Date:	Thu, 8 Mar 2012 10:45:45 -0800
From:	Greg KH <greg@...ah.com>
To:	Olaf Hering <olaf@...fle.de>
Cc:	davem@...emloft.net, netdev@...r.kernel.org,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org
Subject: Re: [PATCH] net/hyperv: Advertise hv_netvsc instead of netvsc as
 driver name

On Thu, Mar 08, 2012 at 07:38:20PM +0100, Olaf Hering wrote:
> 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.

I don't really understand, but in the end, it's not up to me, it's up to
the network maintainer when he wants to merge this to Linus.  If it were
up to me, I would wait for 3.4.

good luck,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/