From: Greg KH <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next 01/15 V2] mei: bus: fix drivers and devices names confusion
Date: Wed, 22 Jul 2015 21:30:29 -0700 [thread overview]
Message-ID: <20150723043029.GA21247@kroah.com> (raw)
In-Reply-To: <1434394615-3754-2-git-send-email-tomas.winkler@intel.com>
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@intel.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
next prev parent reply other threads:[~2015-07-23 4:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 18:56 [char-misc-next 00/15 V2] revamp mei bus Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 01/15 V2] mei: bus: fix drivers and devices names confusion Tomas Winkler
2015-07-23 4:30 ` Greg KH [this message]
2015-06-15 18:56 ` [char-misc-next 02/15 V2] mei: bus: rename nfc.c to bus-fixup.c Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 03/15 V2] mei: bus: move driver api functions at the start of the file Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 04/15] mei: bus: rename uevent handler to mei_cl_device_uevent Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 05/15 V2] mei: bus: don't enable events implicitly in device enable Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 06/15 V2] mei: bus: report if event registration failed Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 07/15 V2] mei: bus: revamp device matching Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 08/15 V2] mei: bus: revamp probe and remove functions Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 09/15 V2] mei: bus: add reference to bus device in struct mei_cl_client Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 10/15 V2] mei: bus: add me client device list infrastructure Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 11/15 V2] mei: bus: enable running fixup routines before device registration Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 12/15] mei: bus: blacklist the nfc info client Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 13/15] mei: bus: blacklist clients by number of connections Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 14/15 V2] mei: bus: simplify how we build nfc bus name Tomas Winkler
2015-06-15 18:56 ` [char-misc-next 15/15 V2] mei: bus: link client devices instead of host clients Tomas Winkler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150723043029.GA21247@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox