linux-kernel - RE: [PATCH 1/1] Staging: hv: Move the mouse driver out of staging

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.LNX.2.00.1110291904190.3541@pobox.suse.cz>
Date:	Sat, 29 Oct 2011 19:05:08 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	Greg KH <gregkh@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org>,
	"ohering@...e.com" <ohering@...e.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: RE: [PATCH 1/1] Staging: hv: Move the mouse driver out of staging

On Fri, 28 Oct 2011, KY Srinivasan wrote:

> > > > >  obj-$(CONFIG_HID_WACOM)		+= hid-wacom.o
> > > > >  obj-$(CONFIG_HID_WALTOP)	+= hid-waltop.o
> > > > >  obj-$(CONFIG_HID_WIIMOTE)	+= hid-wiimote.o
> > > > > +obj-$(CONFIG_HYPERV_MOUSE)	+= hv_mouse.o
> > > >
> > > > I'd prefer a bit to follow the current naming of the drivers in
> > > > drivers/hid directory ... all the device-specific (vendor-specific)
> > > > drivers currently are called hid-<vendor> or similar.
> > > >
> > > > We could talk about changing this naming scheme, but before we reach any
> > > > conclusion on this, I'd prefer this to stay for all drivers if possible.
> > >
> > > Do you want the driver module to conform to the naming scheme you have?
> > > Greg, in the past has resisted changing driver names, but I have no objection
> > > to conforming to the naming convention you have.
> > 
> > I recommend following the proper naming scheme.  As this driver is
> > auto-loaded when the virtual hardware is seen, the name really doesn't
> > matter at all.
> > 
> > So, how about 'hid-hyperv' or 'hid-hv'?
> 
> I will go with hid-hv  if there are no objections.

OK by me, thanks.

-- 
Jiri Kosina
SUSE Labs
--
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/