From: davej@redhat.com (Dave Jones)
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
sensors@stimpy.netroedge.com
Subject: 2.6.3rc4 ali1535 i2c driver rmmod oops.
Date: Thu, 19 May 2005 06:24:42 +0000 [thread overview]
Message-ID: <20040218041734.GK6242@redhat.com> (raw)
In-Reply-To: <20040218040153.GB6729@kroah.com>
On Tue, Feb 17, 2004 at 08:01:54PM -0800, Greg KH wrote:
> Oh nevermind, that's just a dumb driver. It's doing a release_region on
> memory it didn't get. Stupid, stupid, stupid...
>
> Dave can you verify that this patch fixes the problem for you?
yep, 1 rmmod bug down, 16 billion to go.
thanks for fixing this up.
Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
sensors@stimpy.netroedge.com
Subject: Re: 2.6.3rc4 ali1535 i2c driver rmmod oops.
Date: Wed, 18 Feb 2004 04:17:34 +0000 [thread overview]
Message-ID: <20040218041734.GK6242@redhat.com> (raw)
In-Reply-To: <20040218040153.GB6729@kroah.com>
On Tue, Feb 17, 2004 at 08:01:54PM -0800, Greg KH wrote:
> Oh nevermind, that's just a dumb driver. It's doing a release_region on
> memory it didn't get. Stupid, stupid, stupid...
>
> Dave can you verify that this patch fixes the problem for you?
yep, 1 rmmod bug down, 16 billion to go.
thanks for fixing this up.
Dave
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 3:15 2.6.3rc4 ali1535 i2c driver rmmod oops Dave Jones
2004-02-18 3:47 ` Linus Torvalds
2004-02-18 3:49 ` Dave Jones
2004-02-18 4:00 ` Linus Torvalds
2004-02-18 4:02 ` Dave Jones
2004-02-18 4:34 ` viro
2004-02-18 4:01 ` Greg KH
2005-05-19 6:24 ` Greg KH
2004-02-18 4:17 ` Dave Jones [this message]
2005-05-19 6:24 ` Dave Jones
2004-02-21 7:19 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-02-24 0:27 ` Greg KH
2005-05-19 6:24 ` Greg KH
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=20040218041734.GK6242@redhat.com \
--to=davej@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.