public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 2/4] mei: support for dynamic clients
Date: Sun, 24 May 2015 11:25:31 -0700	[thread overview]
Message-ID: <20150524182531.GA6291@kroah.com> (raw)
In-Reply-To: <1432204551-3470-2-git-send-email-tomas.winkler@intel.com>

On Thu, May 21, 2015 at 01:35:49PM +0300, Tomas Winkler wrote:
> HBM version 2.0 and above allows ME clients in the system to
> register/unregister after the system is fully initialized.
> Clients may be added or removed after enum_resp message was
> received
> 
> 1. To preserve backward compatibility the driver can opt-in to receive
> client add messages by setting allow_add field in enum_req
> 
> 2. A new client is added upon reception of MEI_HBM_ADD_CLIENT_REQ_CMD
> 
> 3. A client is removed in a lazy manner when connection request
> respond with MEI_HBMS_CLIENT_NOT_FOUND status
> 
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>

Is this patch, and the rest, safe to add since I didn't apply your other
patch?

I'll stop here, please fix up and resend what is left.

thanks,

greg k-h

  reply	other threads:[~2015-05-24 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 10:35 [char-misc-next 1/4] mei: export hbm features to debugfs under devstate Tomas Winkler
2015-05-21 10:35 ` [char-misc-next 2/4] mei: support for dynamic clients Tomas Winkler
2015-05-24 18:25   ` Greg KH [this message]
2015-05-21 10:35 ` [char-misc-next 3/4] mei: disconnect on connection request timeout Tomas Winkler
2015-05-21 10:35 ` [char-misc-next 4/4] mei: fix the KDoc formating Tomas Winkler
2015-05-22  5:24 ` [char-misc-next 1/4] mei: export hbm features to debugfs under devstate Greg KH
2015-05-22 20:03   ` Winkler, Tomas

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=20150524182531.GA6291@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