public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Erwin Authried <eauth@softsys.co.at>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Simon Barber <simon@barber.net>,
	linux-mtd@lists.infradead.org
Subject: Re: Bug in mtdblock_ro
Date: Thu, 15 Nov 2001 14:51:38 +0100	[thread overview]
Message-ID: <20011115145138.A2078@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <003d01c16c58$71c0d7f0$7f01010a@instant802.com>; from simon@barber.net on Tue, Nov 13, 2001 at 07:32:42AM -0800

Hi!

>>> 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.
>
> 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.

Erwin, this appears to be your code, if MODULE_AUTHOR is correct. Can
you have a look at it?
And David, Erwin, do you mind if I indent the request function to
Linus' beloved style? Makes reading so much easier.

Jörn

-- 
Every good work of software starts by 
scratching a developer's personal itch.

      reply	other threads:[~2001-11-15 13:43 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
2001-11-15 13:51         ` Jörn Engel [this message]

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=20011115145138.A2078@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=dwmw2@infradead.org \
    --cc=eauth@softsys.co.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=simon@barber.net \
    /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