From: David Woodhouse <dwmw2@infradead.org>
To: Radu Corlan <rcorlan@pcnet.ro>
Cc: linux-mtd@lists.infradead.org
Subject: Re: nftl problem
Date: Tue, 26 Feb 2002 18:12:08 +0000 [thread overview]
Message-ID: <1436.1014747128@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10202261939200.608-100000@pinot.profis.ro>
rcorlan@pcnet.ro said:
> Before i gave up on nftl, i found the following problem: nftl accesses
> the flash through the read_ecc and write_ecc function pointers in the
> slave mtd_info structure. However, when the slave structure is
> initialised, only the read and write function pointers are filled, not
> the read_ecc and write_ecc; i got kernel panic out of this, which got
> away when i filled the fields.
I don't recall receiving your patch for this.
--
dwmw2
next prev parent reply other threads:[~2002-02-26 18:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10202252006450.731-100000@pinot.profis.ro>
2002-02-25 18:44 ` problem in nand.c v 1.16 Thomas Gleixner
2002-02-26 6:21 ` Radu Corlan
2002-02-26 6:30 ` Support for parallel access in nand chips Radu Corlan
2002-02-25 23:58 ` Thomas Gleixner
2002-02-26 8:26 ` Radu Corlan
2002-02-26 1:25 ` David Woodhouse
2002-02-26 20:24 ` Radu Corlan
2002-02-26 13:45 ` Thomas Gleixner
2002-02-26 21:11 ` Radu Corlan
2002-02-27 0:46 ` nftl problem Radu Corlan
2002-02-26 18:03 ` Thomas Gleixner
2002-02-27 1:30 ` Radu Corlan
2002-02-26 18:37 ` Thomas Gleixner
2002-02-27 1:42 ` Radu Corlan
2002-02-27 2:00 ` Radu Corlan
2002-02-26 19:10 ` Thomas Gleixner
2002-02-26 18:12 ` David Woodhouse [this message]
2002-02-27 1:37 ` Radu Corlan
2002-02-26 18:57 ` 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=1436.1014747128@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rcorlan@pcnet.ro \
/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