public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stuart_Hayes@Dell.com
Cc: akpm@linux-foundation.org, gregkh@suse.de, malattia@linux.it,
	linux-kernel@vger.kernel.org, dbrownell@users.sourceforge.net,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] bug removing ehci-hcd
Date: Thu, 7 Jun 2007 16:16:44 -0700	[thread overview]
Message-ID: <20070607231644.GA8936@kroah.com> (raw)
In-Reply-To: <DFEF91B22ED07447AB6AA4B237F913F9524D64@ausx3mpc125.aus.amer.dell.com>

On Thu, May 31, 2007 at 10:26:10AM -0500, Stuart_Hayes@Dell.com wrote:
> 
> I wasn't actually able to reproduce the bug myself, but I guess it is
> pretty obvious that I shouldn't have called cpufreq_unregister_notifier
> with a spinlock held.  I haven't been doing this long enough to know
> exactly which kernel this patch should be against, so let me know if
> this ins't good.  Thanks!
> 
> 
> This patch (for the 2.6.21.3 kernel plus previously sent cpufreq
> notifier patch) fixes a bug caused by calling
> cpufreq_unregister_notifier (which can sleep) while holding a spinlock.
> 
> Signed-off-by: Stuart Hayes <stuart_hayes@dell.com>

Thanks, I've merged this with your previous patch.  Sorry for the
previous confusion as to where this patch was applied against (ended up
in my -stable queue...)

thanks,

greg k-h


      parent reply	other threads:[~2007-06-07 23:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21  2:44 [2.6.22-rc1-mm1] ehci-hcd - BUG: scheduling while atomic: rmmod/0x00000001/4568 Mattia Dongili
2007-05-25 21:40 ` Greg KH
2007-05-25 22:00   ` Andrew Morton
2007-05-29 15:14     ` Stuart_Hayes
2007-05-29 16:33       ` Andrew Morton
2007-05-31 15:26         ` [linux-usb-devel] [PATCH] bug removing ehci-hcd Stuart_Hayes
2007-06-07  4:19           ` Greg KH
2007-06-07  5:52             ` Satyam Sharma
2007-06-07  6:14               ` Satyam Sharma
2007-06-07 23:16           ` Greg KH [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=20070607231644.GA8936@kroah.com \
    --to=greg@kroah.com \
    --cc=Stuart_Hayes@Dell.com \
    --cc=akpm@linux-foundation.org \
    --cc=dbrownell@users.sourceforge.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=malattia@linux.it \
    /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