public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Ed Tomlinson <tomlins@cam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 34-mm2 ide problems - unexpected interrupt
Date: Thu, 12 Sep 2002 14:42:47 +0200	[thread overview]
Message-ID: <20020912124247.GA11471@suse.de> (raw)
In-Reply-To: <200209120838.44092.tomlins@cam.org>

On Thu, Sep 12 2002, Ed Tomlinson wrote:
> Hi,
> 
> Got this booting 34-mm2.  Think the are problems with the ide updates...
> UP no preempth.  Everything look ok up to the int loop.

just delete the printk from ide.c:ide_intr(), it's not useful on adapters
with shared interrupts. patch has already been sent to Linus.

feedback on success/problems with 34-mm2 (it seems to include bk patches
up until now?) ide would also be appreciated.

Jens


  reply	other threads:[~2002-09-12 12:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 12:38 34-mm2 ide problems - unexpected interrupt Ed Tomlinson
2002-09-12 12:42 ` Jens Axboe [this message]
2002-09-12 22:30   ` Ed Tomlinson
2002-09-13  6:06     ` Jens Axboe
2002-09-13 11:36       ` Ed Tomlinson
2002-09-14  1:42       ` Ed Tomlinson
2002-09-14  2:58         ` 34-bk current " Ed Tomlinson
2002-09-14 13:36           ` Jens Axboe
2002-09-14 19:39             ` Alan Cox

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=20020912124247.GA11471@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomlins@cam.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