All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Stephen Cameron <smcameron@yahoo.com>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] cpqfc driver for 2.5.1-pre5 tree
Date: Mon, 10 Dec 2001 15:07:01 +0100	[thread overview]
Message-ID: <20011210140701.GF5095@suse.de> (raw)
In-Reply-To: <20011206164206.58598.qmail@web12304.mail.yahoo.com>
In-Reply-To: <20011206164206.58598.qmail@web12304.mail.yahoo.com>

On Thu, Dec 06 2001, Stephen Cameron wrote:
> 
> Hi folks, 
> 
> Here is a patch for the cpqfc driver to make it compile and run in the 2.5.1-pre5
> tree.  I feel obligated to mention that I did see messages along the lines
> of "running *really* low on DMA buffers" coming from scsi_merge.c, but
> Jens told me not to worry about that, so here's the patch.  
> 
> It gets rid of the io_request_lock dependency, and silences a few
> annoying printks that the driver has been spewing on startup.

Thanks!

-- 
Jens Axboe


      reply	other threads:[~2001-12-10 14:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 16:42 [PATCH] cpqfc driver for 2.5.1-pre5 tree Stephen Cameron
2001-12-10 14:07 ` Jens Axboe [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=20011210140701.GF5095@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smcameron@yahoo.com \
    --cc=torvalds@transmeta.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.