public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles.lane@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, LM Sensors <sensors@stimpy.netroedge.com>
Subject: Re: Who should I write to about this OOPS in 2,6,11-mm3?
Date: Mon, 21 Mar 2005 21:59:05 -0500	[thread overview]
Message-ID: <a44ae5cd050321185947448028@mail.gmail.com> (raw)
In-Reply-To: <20050321184011.78808b8d.akpm@osdl.org>

Yes, I just did.  I used the .config options I mentioned earlier.  I
am currently testing the suggested patches and options offered by the
sensors developers.

BTW, I am cross posting because I am not sure how often the LM Sensors
folks read the linux-kernel list.  Please don't reply to both lists.

    Miles


On Mon, 21 Mar 2005 18:40:11 -0800, Andrew Morton <akpm@osdl.org> wrote:
> "Antonino A. Daplas" <adaplas@hotpop.com> wrote:
> >
> > FYI, the original topic of this thread, though, was an oops in
> >  i2c_add_driver() as mentioned in this thread:
> >
> >  http://marc.theaimsgroup.com/?l=linux-kernel&m=111076667232062&w=2
> >
> >  Unfortunately, nobody can reproduce this oops.
> 
> Miles, are you still able to reproduce the i2c_add_driver() oops in
> 2.6.12-rc1 or 2.6.12-rc1-mm1?
> 
> Thanks.
>

      reply	other threads:[~2005-03-22  3:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a44ae5cd05031416392e3addd5@mail.gmail.com>
     [not found] ` <200503180702.42247.adaplas@hotpop.com>
     [not found]   ` <20050317154226.24c1f8f8.akpm@osdl.org>
     [not found]     ` <200503180754.21258.adaplas@hotpop.com>
2005-03-22  2:40       ` Who should I write to about this OOPS in 2,6,11-mm3? Andrew Morton
2005-03-22  2:59         ` Miles Lane [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=a44ae5cd050321185947448028@mail.gmail.com \
    --to=miles.lane@gmail.com \
    --cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox