linux-kernel - Re: [char-misc-next 01/15 V2] mei: bus: fix drivers and devices names confusion

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]

Message-ID: <20150723043029.GA21247@kroah.com>
Date:	Wed, 22 Jul 2015 21:30:29 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Tomas Winkler <tomas.winkler@...el.com>
Cc:	arnd@...db.de, linux-kernel@...r.kernel.org
Subject: Re: [char-misc-next 01/15 V2] mei: bus: fix drivers and devices
 names confusion

On Mon, Jun 15, 2015 at 09:56:41PM +0300, Tomas Winkler wrote:
> In the mei bus layer there is use of different variables
> of driver and device types with no clear naming convention.
> There are generic struct device and struct driver,
> then mei_cl_{device, driver}, and finally mei_device which
> in this context serves as a bus device.
> 
> The patch sets following naming convention:
> 
> the variables of type struct device remains dev
> the variables of type struct driver remains drv
> the variables of type struct mei_cl_device are now cldev
> the variables of type struct mei_cl_driver are now cldrv
> the variables of type struct mei_device are now bus, in bus
> layer context
> 
> Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>

Due to the changes in Linus's tree, this doesn't apply to 4.2-rc3.  Can
you refresh this series and resend?  Same for the other outstanding mei
patches you have sent that I haven't applied.

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/