linux-kernel - Re: [char-misc-next 01/12 v3] mei: Rename mei_device to mei

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] [day] [month] [year] [list]

Date:	Mon, 11 Mar 2013 13:34:21 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Winkler, Tomas" <tomas.winkler@...el.com>
Subject: Re: [char-misc-next 01/12 v3] mei: Rename mei_device to mei_host

On Monday 11 March 2013, Samuel Ortiz wrote:
> > I don't have a strong opinion here, so that would be fine with me.
> > Greg, Arnd, would mei_cl_device and mei_cl_driver be an acceptable compromise?
> I'm re-opening this topic now that the merge window is closed: So would you
> guys take mei_cl_device and mei_cl_driver as an acceptable solution or (as you
> hinted earlier) are mei_device and mei_driver the only naming scheme that
> you'd accept ?

I'd prefer the latter, but I wouldn't insist on it if you have good reasons
to use the former.

	Arnd
--
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/