From: Jens Axboe <axboe@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: dmaas@dcine.com, linux-kernel@vger.kernel.org
Subject: Re: SCSI tape crashes
Date: Wed, 31 Oct 2001 09:53:41 +0100 [thread overview]
Message-ID: <20011031095341.A5111@suse.de> (raw)
In-Reply-To: <20011031093353.F631@suse.de> <20011031.004311.85410732.davem@redhat.com> <20011031094650.H631@suse.de> <20011031.004919.61505836.davem@redhat.com>
In-Reply-To: <20011031.004919.61505836.davem@redhat.com>
On Wed, Oct 31 2001, David S. Miller wrote:
> From: Jens Axboe <axboe@suse.de>
> Date: Wed, 31 Oct 2001 09:46:50 +0100
>
> How is this different from my init_sg proposal? :-). The above looks
> fine to me, I just think it is important that we take care of this.
>
> My impression was that you wanted to do something like:
>
> sgl = kmalloc();
> init_sg(sgl, nents);
>
> for_each_ent() {
> ... existing code ..
> }
>
> If what you really meant was semantically identicaly to what I have
> proposed, I'm completely in agreement with it. Please submit patches.
Yep, init_sg_entry is probably a better name... I'll hack up and submit
soonish.
--
Jens Axboe
next prev parent reply other threads:[~2001-10-31 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.cdhetrv.1828dgd@ifi.uio.no>
[not found] ` <fa.j17q3gv.m6e1ju@ifi.uio.no>
2001-10-30 16:58 ` SCSI tape crashes (was Re: BUG() in asm/pci.h:142 with 2.4.13) Dan Maas
2001-10-31 8:33 ` Jens Axboe
[not found] ` <20011031.004311.85410732.davem@redhat.com>
[not found] ` <20011031094650.H631@suse.de>
2001-10-31 8:49 ` SCSI tape crashes David S. Miller
2001-10-31 8:53 ` Jens Axboe [this message]
2001-10-25 17:32 BUG() in asm/pci.h:142 with 2.4.13 Jens Axboe
2001-10-26 0:25 ` SCSI tape crashes (was Re: BUG() in asm/pci.h:142 with 2.4.13) David S. Miller
2001-10-26 2:26 ` Jeff V. Merkey
2001-10-26 1:32 ` SCSI tape crashes David S. Miller
2001-10-26 3:56 ` Jeff V. Merkey
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=20011031095341.A5111@suse.de \
--to=axboe@suse.de \
--cc=davem@redhat.com \
--cc=dmaas@dcine.com \
--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