From: Steffen Klassert <steffen.klassert@secunet.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
herbert@gondor.hengli.com.au, gang.chen@asianux.com
Subject: Re: [PATCH] kernel/padata.c: Register hotcpu notifier after initialization
Date: Tue, 27 Aug 2013 11:30:41 +0200 [thread overview]
Message-ID: <20130827093041.GD7660@secunet.com> (raw)
In-Reply-To: <1377256353-7979-1-git-send-email-richard@nod.at>
On Fri, Aug 23, 2013 at 01:12:33PM +0200, Richard Weinberger wrote:
> padata_cpu_callback() takes pinst->lock, to avoid taking
> an uninitialized lock, register the notifier after it's
> initialization.
>
> Signed-off-by: Richard Weinberger <richard@nod.at>
Looks ok,
Acked-by: Steffen Klassert <steffen.klassert@secunet.com>
next prev parent reply other threads:[~2013-08-27 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 11:12 [PATCH] kernel/padata.c: Register hotcpu notifier after initialization Richard Weinberger
2013-08-27 9:30 ` Steffen Klassert [this message]
2013-08-29 4:43 ` Herbert Xu
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=20130827093041.GD7660@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=gang.chen@asianux.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
/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