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 02/18 V2] mei: revamp me clients list handling
Date: Sun, 1 Mar 2015 19:37:57 -0800 [thread overview]
Message-ID: <20150302033757.GA19294@kroah.com> (raw)
In-Reply-To: <1423905288-12830-1-git-send-email-tomas.winkler@intel.com>
On Sat, Feb 14, 2015 at 11:14:48AM +0200, Tomas Winkler wrote:
> 1. Use rw lock to access the me_clients list
>
> 2. Reuse already defined find functions also when
> removing particular me client
>
> 3. Add wrappers for addition and deletion
>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> ---
> V2: add missing mei_me_cl_put() calls to mei_host_client_init
Crap, I applied v1, and didn't see this, can you send a fix-up patch
that is the difference here?
thanks,
greg k-h
prev parent reply other threads:[~2015-03-02 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 9:14 [char-misc-next 02/18 V2] mei: revamp me clients list handling Tomas Winkler
2015-03-02 3:37 ` Greg KH [this message]
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=20150302033757.GA19294@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