From: Thomas Gleixner <tglx@linutronix.de>
To: akpm@osdl.org
Cc: seto.hidetoshi@jp.fujitsu.com, arjan@infradead.org,
mingo@elte.hu, LKML <linux-kernel@vger.kernel.org>
Subject: Re: + cpei-gets-warning-at-kernel-irq-migrationc27-move_masked_irq.patch added to -mm tree
Date: Wed, 06 Dec 2006 08:03:57 +0100 [thread overview]
Message-ID: <1165388637.24604.175.camel@localhost.localdomain> (raw)
In-Reply-To: <200612060644.kB66ihYx025965@shell0.pdx.osdl.net>
On Tue, 2006-12-05 at 22:44 -0800, akpm@osdl.org wrote:
> It works, the warning disappeared and irqbalance still runs well.
>
> Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
> Cc: Arjan van de Ven <arjan@infradead.org>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
Good catch.
Acked-by: Thomas Gleixner <tglx@linutronix.de>
>
> kernel/irq/proc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff -puN kernel/irq/proc.c~cpei-gets-warning-at-kernel-irq-migrationc27-move_masked_irq kernel/irq/proc.c
> --- a/kernel/irq/proc.c~cpei-gets-warning-at-kernel-irq-migrationc27-move_masked_irq
> +++ a/kernel/irq/proc.c
> @@ -54,7 +54,8 @@ static int irq_affinity_write_proc(struc
> unsigned int irq = (int)(long)data, full_count = count, err;
> cpumask_t new_value, tmp;
>
> - if (!irq_desc[irq].chip->set_affinity || no_irq_affinity)
> + if (!irq_desc[irq].chip->set_affinity || no_irq_affinity ||
> + CHECK_IRQ_PER_CPU(irq_desc[irq].status))
> return -EIO;
>
> err = cpumask_parse_user(buffer, count, new_value);
> _
>
> Patches currently in -mm which might be from seto.hidetoshi@jp.fujitsu.com are
>
> cpei-gets-warning-at-kernel-irq-migrationc27-move_masked_irq.patch
>
parent reply other threads:[~2006-12-06 7:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200612060644.kB66ihYx025965@shell0.pdx.osdl.net>]
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=1165388637.24604.175.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=seto.hidetoshi@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox