All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Christopher Hoover" <ch@murgatroid.com>
Cc: "'Jörn Engel'" <joern@wohnheim.fh-wedel.de>,
	"'Jamey Hicks'" <jamey.hicks@hp.com>,
	"'Conn Clark'" <clark@esteem.com>,
	"'MTD Mailing List'" <linux-mtd@lists.infradead.org>
Subject: Re: How does one mount an existing jffs2 partition so it is writeable?
Date: Tue, 20 Aug 2002 22:46:57 +0100	[thread overview]
Message-ID: <10406.1029880017@redhat.com> (raw)
In-Reply-To: <004801c24892$eead6000$7800000a@derelict>

ch@murgatroid.com said:
> That was my first thought. I submitted such a patch (-- it should be
> in the archives), but IIRC David didn't want it applied to CVS.  He
> suggested that I move this to the SA-1100 partition code.   I did
> that, but that has its own ugliness.

I never claimed not to be fickle. If your patch did the unlock 
automatically _only_ for the C3 flash which locks itself every power cycle, 
try me again :)

--
dwmw2

  reply	other threads:[~2002-08-20 21:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19 17:34 How does one mount an existing jffs2 partition so it is writeable? Conn Clark
2002-08-19 23:42 ` Jörn Engel
2002-08-20  0:01   ` Conn Clark
2002-08-20  0:25     ` Christopher Hoover
2002-08-20 10:21       ` David Woodhouse
2002-08-20 12:12         ` Jamey Hicks
2002-08-20 12:19           ` David Woodhouse
2002-08-20 13:12             ` Jörn Engel
2002-08-20 16:34           ` Christopher Hoover
2002-08-20 19:24             ` Jörn Engel
2002-08-20 21:45               ` Christopher Hoover
2002-08-20 21:46                 ` David Woodhouse [this message]
2002-08-20 17:26       ` Conn Clark
2002-08-20 18:02         ` Conn Clark
2002-08-20 18:18           ` Christopher Hoover
2002-08-20 18:42             ` Conn Clark
2002-08-20 21:50               ` Christopher Hoover
2002-08-20 10:10     ` Jörn Engel
     [not found] <000001c2489f$bf76d070$7c00000a@SNAGGLE>
2002-08-21  0:15 ` Conn Clark

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=10406.1029880017@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=ch@murgatroid.com \
    --cc=clark@esteem.com \
    --cc=jamey.hicks@hp.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.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 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.