public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Gregory Schallert <gschallert@dawning.com>
To: mark.langsdorf@amd.com
Cc: mtd@infradead.org
Subject: Re: Problems with AMD CFI chips
Date: Thu, 02 Nov 2000 14:16:57 -0500	[thread overview]
Message-ID: <3A01BDA9.52756588@dawning.com> (raw)
In-Reply-To: 0FA1031B65A9D111960900805F9FA8E103B9F19F@txexmta8.amd.com

>    Also, when does jffs attempt to clean out the dirty
> space?

On an aside, how does jffs schedule the clean up and is this really CPU
intensive?



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-11-02 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 17:19 Problems with AMD CFI chips mark.langsdorf
2000-11-02 19:16 ` Gregory Schallert [this message]
2000-11-02 22:36   ` David Woodhouse
2000-11-02 22:31 ` David Woodhouse
2000-11-03 18:29 ` Compile problems Gregory Schallert
2000-11-04  2:20   ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2000-10-31 17:47 Problems with AMD CFI chips mark.langsdorf
2000-10-31 17:55 ` 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=3A01BDA9.52756588@dawning.com \
    --to=gschallert@dawning.com \
    --cc=mark.langsdorf@amd.com \
    --cc=mtd@infradead.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