From: Jani Monoses <jani@iv.ro>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: remove NOT_IN_RAM handling
Date: Thu, 20 Nov 2003 12:43:00 -0000 [thread overview]
Message-ID: <20031120143136.68a54d20.jani@iv.ro> (raw)
In-Reply-To: <20031120123931.GB9114@lunn.ch>
>
> Humm. This needs some discussion. There may not be any drivers in the
> anoncvs repository using this, but there could be people with there
> own private flash drivers which use this interface. Do we want to
> break such drivers?
>
> Anybody with an opinion is welcome to comment.
I thought there might be others using old drivers but to change them to
work with this is simple. And if they track CVS they are definitely able
to do such a small change. Of course others might have other opinions.
Jani
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-11-20 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031120130610.0fde112f.jani@iv.ro>
2003-11-20 12:39 ` Andrew Lunn
2003-11-20 12:43 ` Jani Monoses [this message]
2003-11-20 13:44 ` Gary Thomas
2003-11-20 14:03 ` Jani Monoses
2003-11-20 14:11 ` Gary Thomas
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=20031120143136.68a54d20.jani@iv.ro \
--to=jani@iv.ro \
--cc=ecos-discuss@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).