From: greg@kroah.com (Greg KH)
To: LKML <linux-kernel@vger.kernel.org>,
Sensors <sensors@stimpy.netroedge.com>,
Martin Schlemmer <azarah@gentoo.org>
Subject: [RFC PATCH] Re: [OOPS] w83781d during rmmod (2.5.69-bk17)
Date: Thu, 19 May 2005 06:23:58 +0000 [thread overview]
Message-ID: <20030605194734.GA6238@kroah.com> (raw)
In-Reply-To: <20030605023922.GA8943@earth.solarsys.private>
On Wed, Jun 04, 2003 at 10:39:22PM -0400, Mark M. Hoffman wrote:
> * Greg KH <greg@kroah.com> [2003-06-02 10:20:40 -0700]:
> > On Sun, Jun 01, 2003 at 10:38:08AM -0400, Mark M. Hoffman wrote:
> > >
> > > This patch against 2.5.70 works for me vs. an SMBus adapter. It needs
> > > re-testing against an ISA adapter since my particular chip is SMBus only.
> >
> > I've applied this and will send it off to Linus in a bit.
>
> Thanks!
>
> This patch fixes the various return values in the w83781d_detect()
> error paths. It also cleans up some formatting here and there.
> It should be applied on top of the previous one.
>
> It works for me; same caveat as above w.r.t. ISA.
Applied, thanks.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: LKML <linux-kernel@vger.kernel.org>,
Sensors <sensors@stimpy.netroedge.com>,
Martin Schlemmer <azarah@gentoo.org>
Subject: Re: [RFC PATCH] Re: [OOPS] w83781d during rmmod (2.5.69-bk17)
Date: Thu, 5 Jun 2003 12:47:34 -0700 [thread overview]
Message-ID: <20030605194734.GA6238@kroah.com> (raw)
In-Reply-To: <20030605023922.GA8943@earth.solarsys.private>
On Wed, Jun 04, 2003 at 10:39:22PM -0400, Mark M. Hoffman wrote:
> * Greg KH <greg@kroah.com> [2003-06-02 10:20:40 -0700]:
> > On Sun, Jun 01, 2003 at 10:38:08AM -0400, Mark M. Hoffman wrote:
> > >
> > > This patch against 2.5.70 works for me vs. an SMBus adapter. It needs
> > > re-testing against an ISA adapter since my particular chip is SMBus only.
> >
> > I've applied this and will send it off to Linus in a bit.
>
> Thanks!
>
> This patch fixes the various return values in the w83781d_detect()
> error paths. It also cleans up some formatting here and there.
> It should be applied on top of the previous one.
>
> It works for me; same caveat as above w.r.t. ISA.
Applied, thanks.
greg k-h
next prev parent reply other threads:[~2005-05-19 6:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 18:37 [OOPS] w83781d during rmmod (2.5.69-bk17) Mark M. Hoffman
2005-05-19 6:23 ` Mark M. Hoffman
2005-05-19 6:23 ` Mark D. Studebaker
2003-06-01 14:38 ` [RFC PATCH] " Mark M. Hoffman
2005-05-19 6:23 ` Mark M. Hoffman
2003-06-02 17:20 ` Greg KH
2005-05-19 6:23 ` Greg KH
2003-06-03 5:22 ` Martin Schlemmer
2005-05-19 6:23 ` Martin Schlemmer
2003-06-03 19:43 ` Philip Pokorny
2005-05-19 6:23 ` Philip Pokorny
2003-06-04 5:57 ` Martin Schlemmer
2005-05-19 6:23 ` Martin Schlemmer
2003-06-05 2:39 ` Mark M. Hoffman
2005-05-19 6:23 ` Mark M. Hoffman
2003-06-05 19:47 ` Greg KH [this message]
2005-05-19 6:23 ` Greg KH
2003-06-09 5:34 ` Martin Schlemmer
2005-05-19 6:23 ` Martin Schlemmer
2003-06-10 5:38 ` Martin Schlemmer
2005-05-19 6:23 ` Martin Schlemmer
2003-06-10 5:41 ` OOPS w83781d during rmmod (2.5.70-bk1[1234]) Mark M. Hoffman
2005-05-19 6:23 ` Mark M. Hoffman
2003-06-10 5:51 ` Martin Schlemmer
2005-05-19 6:23 ` Martin Schlemmer
2003-06-11 5:44 ` Martin Schlemmer
2005-05-19 6:23 ` Martin Schlemmer
2003-06-12 6:57 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d during rmmod (2.5.70-bk1[1234])) Martin Schlemmer
2005-05-19 6:23 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d Martin Schlemmer
2003-06-13 2:36 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d during rmmod (2.5.70-bk1[1234])) Mark M. Hoffman
2005-05-19 6:23 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d Mark M. Hoffman
2003-06-13 6:08 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d during rmmod (2.5.70-bk1[1234])) Martin Schlemmer
2005-05-19 6:23 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS Martin Schlemmer
2003-06-14 6:26 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d during rmmod (2.5.70-bk1[1234])) Martin Schlemmer
2005-05-19 6:24 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS Martin Schlemmer
2003-06-16 18:41 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d during rmmod (2.5.70-bk1[1234])) Greg KH
2005-05-19 6:24 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d Greg KH
2003-09-03 20:54 ` [PATCH 2.6] Fix conversion from milli volts in store_in_reg() for w83781d.c Martin Schlemmer
2005-05-19 6:24 ` [PATCH 2.6] Fix conversion from milli volts in store_in_reg() for Martin Schlemmer
2003-09-04 18:40 ` [PATCH 2.6] Fix conversion from milli volts in store_in_reg() for w83781d.c Greg KH
2005-05-19 6:24 ` [PATCH 2.6] Fix conversion from milli volts in store_in_reg() for Greg KH
2003-09-07 15:41 ` [PATCH 2.6] Fix conversion from milli volts in store_in_reg() for w83781d.c Andrey Borzenkov
2005-05-19 6:24 ` [PATCH 2.6] Fix conversion from milli volts in store_in_reg() for Andrey Borzenkov
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=20030605194734.GA6238@kroah.com \
--to=greg@kroah.com \
--cc=azarah@gentoo.org \
--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.