From: "Leubner, Achim" <Achim_Leubner@adaptec.com>
To: "Christoph Hellwig" <hch@lst.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: HEADS UP for gdth driver users
Date: Tue, 25 Apr 2006 12:54:28 +0200 [thread overview]
Message-ID: <EF6AF37986D67948AD48624A3E5D93AFAA960D@mtce2k01.adaptec.com> (raw)
Thanks for your help. I will make the patch, test it and send it out as
soon as possible to put it into the 2.6.18 cycle.
Thanks,
Achim
=======================
Achim Leubner
Software Engineer / RAID drivers
ICP vortex GmbH / Adaptec Inc.
Phone: +49-351-8718291
-----Original Message-----
From: Christoph Hellwig [mailto:hch@lst.de]
Sent: Dienstag, 25. April 2006 12:33
To: Leubner, Achim
Cc: Christoph Hellwig; linux-kernel@vger.kernel.org
Subject: Re: HEADS UP for gdth driver users
On Mon, Apr 24, 2006 at 02:21:00PM +0200, Leubner, Achim wrote:
> Is there any news on that? Can we use the scsi_get/put_command()
functions for allocating a "struct scsi_cmnd" or should we allocate it
with kmalloc() or somehow like that? Or, Christoph, did you already make
the second patch for the gdth driver?
> We want to bring the gdth driver up to date as soon as possible. Any
help is greatly appreciated!
Sorry, I didn't have time to look at this yet. scsi_get/put_command()
sems ok for now, if you have time to look at this now it would be good
if you could look at it. It's too late for 2.6.17 already, but having
it early in the 2.6.18 cycle would be very helpful.
next reply other threads:[~2006-04-25 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 10:54 Leubner, Achim [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-16 9:21 Leubner, Achim
2006-06-09 11:03 Leubner, Achim
2006-06-09 18:33 ` Andrew Morton
2006-06-09 18:34 ` Andrew Morton
2006-06-10 10:03 ` Ingo Oeser
2006-04-24 12:21 Leubner, Achim
2006-04-25 10:33 ` Christoph Hellwig
2006-04-18 14:41 Leubner, Achim
2006-03-10 11:04 Leubner, Achim
2006-03-08 13:19 Christoph Hellwig
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=EF6AF37986D67948AD48624A3E5D93AFAA960D@mtce2k01.adaptec.com \
--to=achim_leubner@adaptec.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®