From: Greg KH <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Alexander Usyskin <alexander.usyskin@intel.com>
Subject: Re: [char-misc-next 04/11] mei: revamp client disconnection flow
Date: Fri, 3 Apr 2015 16:19:46 +0200 [thread overview]
Message-ID: <20150403141946.GA26293@kroah.com> (raw)
In-Reply-To: <1427408887-27979-4-git-send-email-tomas.winkler@intel.com>
On Fri, Mar 27, 2015 at 12:28:00AM +0200, Tomas Winkler wrote:
> Split disconnected state into two parts first reception disconnect
> response from the firmware and second actually setting of disconnected
> state. Book keeping data are needed for processing and after firmware
> disconnected the client and are cleaned when setting the disconnected
> state in mei_cl_set_disconneted() function.
> Add mei_cl_send_disconnect to reduce code duplication.
>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> ---
> drivers/misc/mei/bus.c | 2 -
> drivers/misc/mei/client.c | 158 +++++++++++++++++++++++++++++++++----------
> drivers/misc/mei/client.h | 3 +
> drivers/misc/mei/hbm.c | 8 +--
> drivers/misc/mei/interrupt.c | 46 +------------
> drivers/misc/mei/main.c | 9 +--
> drivers/misc/mei/mei_dev.h | 3 +-
> 7 files changed, 134 insertions(+), 95 deletions(-)
This patch fails to apply to my tree, so I'm stopping here in applying
the series :(
next prev parent reply other threads:[~2015-04-03 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 22:27 [char-misc-next 01/11] mei: fix mei_poll operation Tomas Winkler
2015-03-26 22:27 ` [char-misc-next 02/11] mei: use mei_cl_is_connected consistently Tomas Winkler
2015-03-26 22:27 ` [char-misc-next 03/11] mei: replace check for connection instead of transitioning Tomas Winkler
2015-03-26 22:28 ` [char-misc-next 04/11] mei: revamp client disconnection flow Tomas Winkler
2015-04-03 14:19 ` Greg KH [this message]
2015-04-05 11:00 ` Winkler, Tomas
2015-04-05 13:18 ` Greg KH
2015-04-06 10:19 ` Winkler, Tomas
2015-03-26 22:28 ` [char-misc-next 05/11] mei: revamp client connection Tomas Winkler
2015-03-26 22:28 ` [char-misc-next 06/11] mei: add a reference from the host client to the me client Tomas Winkler
2015-03-26 22:28 ` [char-misc-next 07/11] mei: fix flow control for single buffer clients Tomas Winkler
2015-03-26 22:28 ` [char-misc-next 08/11] mei: support for fixed address clients Tomas Winkler
2015-03-26 22:28 ` [char-misc-next 09/11] mei: connection to fixed address clients from user-space Tomas Winkler
2015-03-26 22:28 ` [char-misc-next 10/11] mei: drop iamthif_mtu from device structure Tomas Winkler
2015-03-26 22:28 ` [char-misc-next 11/11] mei: txe: fix incorrect indentation 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=20150403141946.GA26293@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--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