From: Andrew Morton <akpm@osdl.org>
To: Anton Blanchard <anton@samba.org>
Cc: ak@suse.de, davem@redhat.com, linux-arch@vger.kernel.org
Subject: Re: pci_map_single return value
Date: Thu, 18 Mar 2004 16:55:50 -0800 [thread overview]
Message-ID: <20040318165550.3f5068b4.akpm@osdl.org> (raw)
In-Reply-To: <20040319001448.GP28212@krispykreme>
Anton Blanchard <anton@samba.org> wrote:
>
> > Another addition here:
> >
> > Please note that the sg cannot be mapped again if it has been mapped once.
> > The mapping process is allowed to destroy information in the sg.
> >
> > [some drivers do this currently and it causes problems]
> >
> > > +As with the other mapping interfaces, dma_map_sg can fail. When it
> > > +does, 0 is returned and a driver should take appropriate action.
> >
> > Please make this stronger. A block driver should definitely abort the
> > request, otherwise you can kiss your super block good-bye.
>
> Better late than never. Andrew does this look OK to you?
Spose so. Does this mean driver patches are on the way?
next prev parent reply other threads:[~2004-03-19 0:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031212155752.GD17683@krispykreme>
[not found] ` <20031212175104.07dc8444.ak@suse.de>
[not found] ` <20031212192131.GF17683@krispykreme>
[not found] ` <20031213220444.4c526afa.davem@redhat.com>
[not found] ` <20040102120121.GT28023@krispykreme>
[not found] ` <20040102133454.22daa451.ak@suse.de>
2004-03-19 0:14 ` pci_map_single return value Anton Blanchard
2004-03-19 0:41 ` David S. Miller
2004-03-19 0:55 ` Andrew Morton [this message]
2004-03-19 1:37 ` Anton Blanchard
2004-03-19 14:16 ` James Bottomley
2004-03-19 16:57 ` James Bottomley
2004-03-19 18:55 ` David S. Miller
2004-03-19 21:01 ` James Bottomley
2004-03-19 21:05 ` Andi Kleen
2004-03-20 0:13 ` James Bottomley
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=20040318165550.3f5068b4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=linux-arch@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 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.