From: Xie XiuQi <xiexiuqi@huawei.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Sheng Yang <sheng@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jens Axboe <jens.axboe@oracle.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] generic-ipi: Fix misleading smp_call_function_any() description
Date: Mon, 19 Aug 2013 09:47:02 +0800 [thread overview]
Message-ID: <52117916.80107@huawei.com> (raw)
In-Reply-To: <51F5E6F8.1000801@huawei.com>
Cc: Ingo Molnar <mingo@elte.hu>
On 2013/7/29 11:52, Xie XiuQi wrote:
> After commit:8969a5ede0f9e17da4b943712429aef2c9bcd82b
> "generic-ipi: remove kmalloc()", wait = 0 can be guaranteed.
>
> Signed-off-by: Xie XiuQi <xiexiuqi@huawei.com>
> Cc: Sheng Yang <sheng@linux.intel.com>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Jens Axboe <jens.axboe@oracle.com>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> ---
> kernel/smp.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/kernel/smp.c b/kernel/smp.c
> index fe9f773..b1c9034 100644
> --- a/kernel/smp.c
> +++ b/kernel/smp.c
> @@ -278,8 +278,6 @@ EXPORT_SYMBOL(smp_call_function_single);
> * @wait: If true, wait until function has completed.
> *
> * Returns 0 on success, else a negative status code (if no cpus were online).
> - * Note that @wait will be implicitly turned on in case of allocation failures,
> - * since we fall back to on-stack allocation.
> *
> * Selection preference:
> * 1) current cpu if in @mask
>
next prev parent reply other threads:[~2013-08-19 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 3:52 [PATCH] generic-ipi: Fix misleading smp_call_function_any() description Xie XiuQi
2013-08-19 1:47 ` Xie XiuQi [this message]
2013-08-19 9:55 ` [tip:core/locking] generic-ipi/locking: " tip-bot for Xie XiuQi
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=52117916.80107@huawei.com \
--to=xiexiuqi@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=sheng@linux.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 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.