From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Linas Vepstas <linasvepstas@gmail.com>
Cc: Matt Fleming <matt@console-pimps.org>, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH] powerpc/eeh: remove eeh_event_handler()->daemonize()
Date: Tue, 16 Aug 2011 21:08:58 +0200 [thread overview]
Message-ID: <20110816190858.GA4890@redhat.com> (raw)
daemonize() is only needed when a user-space task does kernel_thread().
eeh_event_handler() thread is created by the worker kthread, and thus
it doesn't need the soon-to-be-deprecated daemonize().
Note: looks like eeh_event_wq can be static and it can do all work
itself without kernel_thread().
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
---
arch/powerpc/platforms/pseries/eeh_event.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- 3.1/arch/powerpc/platforms/pseries/eeh_event.c~3_daemonize_eeh 2011-04-06 21:33:42.000000000 +0200
+++ 3.1/arch/powerpc/platforms/pseries/eeh_event.c 2011-08-16 21:03:56.000000000 +0200
@@ -60,7 +60,7 @@ static int eeh_event_handler(void * dumm
struct eeh_event *event;
struct pci_dn *pdn;
- daemonize ("eehd");
+ set_task_comm(current, "eehd");
set_current_state(TASK_INTERRUPTIBLE);
spin_lock_irqsave(&eeh_eventlist_lock, flags);
next reply other threads:[~2011-08-16 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 19:08 Oleg Nesterov [this message]
2011-08-16 19:17 ` [PATCH] powerpc/eeh: remove eeh_event_handler()->daemonize() Benjamin Herrenschmidt
2011-08-16 19:24 ` Linas Vepstas
2011-08-16 19:29 ` Tejun Heo
2011-08-16 21:38 ` Linas Vepstas
2011-08-16 19:26 ` Tejun Heo
2011-08-17 17:27 ` Oleg Nesterov
2011-08-18 7:34 ` Tejun Heo
2011-08-16 21:27 ` Matt Fleming
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=20110816190858.GA4890@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linasvepstas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=paulus@samba.org \
--cc=tj@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