From: Rusty Russell <rusty@rustcorp.com.au>
To: Anton Blanchard <anton@samba.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] Remove reference to kthread_create_on_cpu
Date: Tue, 9 Feb 2010 16:04:43 +1030 [thread overview]
Message-ID: <201002091604.43557.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100209040740.GB3702@kryten>
On Tue, 9 Feb 2010 02:37:40 pm Anton Blanchard wrote:
>
> kthread_create_on_cpu doesn't exist so update a comment in kthread.c to
> reflect this.
>
> Signed-off-by: Anton Blanchard <anton@samba.org>
Acked-by: Rusty Russell <rusty@rustcorp.com.au>
Thanks!
Rusty.
next prev parent reply other threads:[~2010-02-09 5:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 4:07 [PATCH] Remove reference to kthread_create_on_cpu Anton Blanchard
2010-02-09 5:34 ` Rusty Russell [this message]
2010-02-09 10:23 ` Jiri Kosina
2010-02-09 10:52 ` [tip:sched/core] kthread, sched: " tip-bot for Anton Blanchard
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=201002091604.43557.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox