From: Darren Hart <dvhart@infradead.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] intel_scu_ipc: move local memory initialization out of a mutex
Date: Tue, 14 Jul 2015 19:47:06 +0000 [thread overview]
Message-ID: <20150714194706.GA35521@vmdeb7> (raw)
In-Reply-To: <1436798694-6907-1-git-send-email-christophe.jaillet@wanadoo.fr>
On Mon, Jul 13, 2015 at 04:44:54PM +0200, Christophe JAILLET wrote:
> '{ }' and memset will both reset the cbuf buffer.
> Only once is enough and this can be done outside fo the mutex.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Queued, thanks Christophe.
--
Darren Hart
Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@infradead.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] intel_scu_ipc: move local memory initialization out of a mutex
Date: Tue, 14 Jul 2015 12:47:06 -0700 [thread overview]
Message-ID: <20150714194706.GA35521@vmdeb7> (raw)
In-Reply-To: <1436798694-6907-1-git-send-email-christophe.jaillet@wanadoo.fr>
On Mon, Jul 13, 2015 at 04:44:54PM +0200, Christophe JAILLET wrote:
> '{ }' and memset will both reset the cbuf buffer.
> Only once is enough and this can be done outside fo the mutex.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Queued, thanks Christophe.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-07-14 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 14:44 [PATCH] intel_scu_ipc: move local memory initialization out of a mutex Christophe JAILLET
2015-07-13 14:44 ` Christophe JAILLET
2015-07-14 19:47 ` Darren Hart [this message]
2015-07-14 19:47 ` Darren Hart
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=20150714194706.GA35521@vmdeb7 \
--to=dvhart@infradead.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.