linux-kernel - Re: [char-misc-next 01/11 V2] mei: bus: Initial MEI bus type implementation

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

Date:	Mon, 11 Feb 2013 06:30:51 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Tomas Winkler <tomas.winkler@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [char-misc-next 01/11 V2] mei: bus: Initial MEI bus type
 implementation

On Mon, Feb 11, 2013 at 02:46:12PM +0100, Samuel Ortiz wrote:
> > You already have a 'struct mei_device', which refers to the PCI device
> > that owns the bus, and has clients attached to it. While it may be
> > a little confusing to people that already worked with the current
> > mei code, I think it would help to rename the existing 'mei_device'
> > to 'mei_host' or something else that feels appropriate, and introduce
> > the new structure as 'mei_device' derived from 'struct device', again
> > matching what most other subsystems do.
> I understand, and I agree it would make sense. As we're aiming at having this
> patchset merged during the next merge window, would it be ok to have this
> renaming phase as a follow up patch ?

Do you mean for 3.9?  Sorry, my trees are now closed for new stuff like
this for 3.9, this will all have to wait for 3.10, so you have plenty of
time to get it right.  No need to rush.

thanks,

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/