public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Dmitry Konyshev <dmitry.konyshev@auriga.ru>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: nand driver bug?
Date: Thu, 15 Apr 2004 11:49:47 +0400	[thread overview]
Message-ID: <407E3E9B.70903@auriga.ru> (raw)
In-Reply-To: <200404141744.15766.tglx@linutronix.de>

Thomas Gleixner wrote:

>>    The driver happens to fall in BUG in nand_select_chip when writing
>>the last page of a device. It's trying to select_chip in nand_write_ecc
>>even in case there's nothing left to write.
>>    
>>
>
>Yep, you're right. I noticed this already and fixed it, but did not yet commit 
>it, as I changed a lot of other things.
>Should be fixed until tomorrow morning
>
>  
>
Any changes should be done in boards' drivers? Fresh CVS version oopses 
in nand_scan.

wbr, Dmitry

  reply	other threads:[~2004-04-15  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 15:32 nand driver bug? Dmitry Konyshev
2004-04-14 15:44 ` Thomas Gleixner
2004-04-15  7:49   ` Dmitry Konyshev [this message]
2004-04-15  7:56     ` Thomas Gleixner

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=407E3E9B.70903@auriga.ru \
    --to=dmitry.konyshev@auriga.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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