From: Eric Paris <eparis@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, hpa@zytor.com
Subject: Re: irq_desc_lock_class is held when it is freed
Date: Sat, 31 Jan 2009 20:55:39 -0500 [thread overview]
Message-ID: <1233453339.19217.3.camel@localhost.localdomain> (raw)
In-Reply-To: <4984F8BF.8020903@kernel.org>
On Sat, 2009-01-31 at 17:19 -0800, Yinghai Lu wrote:
> [PATCH] x86: fix lock status with numa_migrate_irq_desc
>
> Impact: make the lock state consistent
>
> adjust lock sequence...
>
> Reported-by: Eric Paris <eparis@redhat.com>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Well it booted and isn't complaining, so:
Tested-by: Eric Paris <eparis@redhat.com>
prev parent reply other threads:[~2009-02-01 1:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 21:33 irq_desc_lock_class is held when it is freed Eric Paris
2009-01-31 22:50 ` Yinghai Lu
2009-02-01 1:05 ` Eric Paris
2009-02-01 1:19 ` Yinghai Lu
2009-02-01 1:55 ` Eric Paris [this message]
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=1233453339.19217.3.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=yinghai@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