The patch titled
Subject: irq: tsk->comm is an array
has been added to the -mm tree. Its filename is
irq-tsk-comm-is-an-array.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Alan Cox <alan@xxxxxxxxxxxxxxx>
Subject: irq: tsk->comm is an array
The array check is useless so remove it.
Signed-off-by: Alan Cox <alan@xxxxxxxxxxxxxxx>
Cc: David Rientjes <rientjes@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/irq/manage.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN kernel/irq/manage.c~irq-tsk-comm-is-an-array kernel/irq/manage.c
--- a/kernel/irq/manage.c~irq-tsk-comm-is-an-array
+++ a/kernel/irq/manage.c
@@ -792,8 +792,9 @@ static void irq_thread_dtor(struct callb
action = kthread_data(tsk);
+ /* FIXME: locking */
pr_err("exiting task \"%s\" (%d) is an active IRQ thread (irq %d)\n",
- tsk->comm ? tsk->comm : "", tsk->pid, action->irq);
+ tsk->comm, tsk->pid, action->irq);
desc = irq_to_desc(action->irq);
_
Patches currently in -mm which might be from alan@xxxxxxxxxxxxxxx are
fanotify-fix-missing-break.patch
linux-next.patch
irq-tsk-comm-is-an-array.patch
drivers-message-fusion-mptscsihc-missing-break.patch
binfmt_elf-fix-corner-case-kfree-of-uninitialized-data.patch
binfmt_elf-fix-corner-case-kfree-of-uninitialized-data-checkpatch-fixes.patch
fork-unshare-remove-dead-code.patch
binfmt_elfc-use-get_random_int-to-fix-entropy-depleting.patch
binfmt_elfc-use-get_random_int-to-fix-entropy-depleting-fix.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
