From: David Woodhouse <dwmw2@infradead.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Simon Evans <spse@secret.org.uk>, linux-mtd@lists.infradead.org
Subject: Re: default readv/writev functions
Date: Wed, 15 Jan 2003 00:23:22 +0000 [thread overview]
Message-ID: <6905.1042590202@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20030115001930.GD19834@wohnheim.fh-wedel.de>
joern@wohnheim.fh-wedel.de said:
> How about the STMicro flashes with built-in ecc checks? Write less
> than 8 bytes per vector element and you're dead. Other than that, you
> are right. A central version is better for almost all chips.
The intention is that drivers can set their own readv/writev methods to
point at these default functions, _if_ they want to. Chips which can't use
these functions can still provide their own.
Think of it like generic_file_read etc. for file systems. You use them if
you don't have special requirements -- otherwise you write your own.
--
dwmw2
prev parent reply other threads:[~2003-01-14 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 15:35 default readv/writev functions Simon Evans
2003-01-14 21:45 ` Jörn Engel
2003-01-14 23:18 ` David Woodhouse
2003-01-15 0:19 ` Jörn Engel
2003-01-15 0:23 ` David Woodhouse [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=6905.1042590202@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=spse@secret.org.uk \
/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