public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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: Tue, 14 Jan 2003 23:18:33 +0000	[thread overview]
Message-ID: <5351.1042586313@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20030114214510.GC19834@wohnheim.fh-wedel.de>

joern@wohnheim.fh-wedel.de said:
>  IMHO this is the wrong place. This should go into drivers/mtd/chips/
> cfi_cmdset*.c.

I disagree. All chips -- or at least all NOR chips -- are going to want to
use the same implmementation it because there's almost no point in actually
having their own.

Maybe having it in chips/chipreg.c makes almost as much sense, but there 
are standalone devices like the LART driver which would want it.

--
dwmw2

  reply	other threads:[~2003-01-14 22:47 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 [this message]
2003-01-15  0:19     ` Jörn Engel
2003-01-15  0:23       ` David Woodhouse

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=5351.1042586313@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