public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Simon Barber" <simon@barber.net>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: Bug in mtdblock_ro
Date: Tue, 13 Nov 2001 07:32:42 -0800	[thread overview]
Message-ID: <003d01c16c58$71c0d7f0$7f01010a@instant802.com> (raw)
In-Reply-To: 20011113125222.A2490@wohnheim.fh-wedel.de

I'm travelling right now - so I can't, sorry - but it's a version I checked
out from the anon CVS a few days (maybe 10) ago. With this bug fix it works
great for me. Without the fix I get a kernel panic on trying to mount a
mtd_ro partition as rootfs.

Simon

----- Original Message -----
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Simon Barber" <simon@barber.net>
Cc: <linux-mtd@lists.infradead.org>
Sent: Tuesday, November 13, 2001 3:52 AM
Subject: Re: Bug in mtdblock_ro


> Moin!
>
> > the call in mtdblock_request to MTD_READ/WRITE passes nr_sectors, it
should
> > pass current_nr_sectors.
>
> Could you quickly add, what version has this problem? The filename
> should be enough. When I get back from vacation (Thursday), I will
> have a look at it.
>
> Jörn
>
> --
> If you treat your beta-testers as if they're your most valuable resource,
> they will respond by becoming your most valuable resource.

  reply	other threads:[~2001-11-13 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05 16:22 MTD partitioning rewrite finished Jörn Engel
2001-11-06 12:39 ` Jörn Engel
2001-11-06 13:11   ` Bug in mtdblock_ro Simon Barber
2001-11-13 11:52     ` Jörn Engel
2001-11-13 15:32       ` Simon Barber [this message]
2001-11-15 13:51         ` Jörn Engel

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='003d01c16c58$71c0d7f0$7f01010a@instant802.com' \
    --to=simon@barber.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox