All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: shane@agendacomputing.com
Cc: Linus Torvalds <torvalds@transmeta.com>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	parsley@roanoke.edu, linux-kernel@vger.kernel.org
Subject: Re: Patch (repost): cramfs memory corruption fix
Date: Mon, 08 Jan 2001 14:34:49 +0000	[thread overview]
Message-ID: <7849.978964489@redhat.com> (raw)
In-Reply-To: <01010812305810.02165@www.easysolutions.net>
In-Reply-To: <01010812305810.02165@www.easysolutions.net>  <Pine.LNX.4.10.10101071938540.28661-100000@penguin.transmeta.com> <23514.978959516@redhat.com>


shane@agendacomputing.com said:
>  While the topic is raised..., I've hacked up cramfs for linear
> addressing to  kill the "double buffering" effiect.  However as David
> mentions the block  device support thing is an issue here.  What is a
> reasonable way to allow a  cramfs partition to access the device
> directly, like the patch that I wrote,  and be picked up in a
> reasonable way by the init system?

So far, I just cheat. JFFS doesn't need a block device, but uses the minor# 
to determine which MTD device to use. You could use the same trick.

--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-08 14:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-07  6:41 Patch (repost): cramfs memory corruption fix Adam J. Richter
2001-01-07 13:53 ` Alan Cox
2001-01-07 19:26   ` Linus Torvalds
2001-01-07 19:42     ` Alan Cox
2001-01-07 19:56       ` Linus Torvalds
2001-01-07 21:11         ` Rik van Riel
2001-01-07 21:20           ` Alan Cox
2001-01-08  6:56           ` Eric W. Biederman
2001-01-07 21:54         ` Chris Wedgwood
2001-01-08 13:37         ` Christoph Rohland
2001-01-08 14:19           ` Christoph Hellwig
2001-01-08 14:43             ` Christoph Rohland
2001-01-08 14:42           ` Alan Cox
2001-01-08 14:49             ` Christoph Rohland
2001-01-07 20:39       ` David L. Parsley
2001-01-08 18:27         ` Linus Torvalds
2001-01-08  3:46 ` Linus Torvalds
2001-01-08 13:11   ` David Woodhouse
2001-01-08 12:30     ` Shane Nay
2001-01-08 14:34     ` David Woodhouse [this message]
2001-01-10 23:30   ` [PATCH] one-liner fix for bforget() honoring BH_Protected; was: " David L. Parsley
2001-01-11  4:23     ` Linus Torvalds

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=7849.978964489@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parsley@roanoke.edu \
    --cc=shane@agendacomputing.com \
    --cc=torvalds@transmeta.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 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.