public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <bkgoodman@bradgoodman.com>
To: <marcelo.tosatti@cyclades.com>
Cc: <rainer.weikusat@sncag.com>, <bkgoodman@bradgoodman.com>,
	<alan@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4.27 - MTD cfi_cmdset_0002.c - Duplicate cleanup in error path
Date: Thu, 19 Aug 2004 16:18:11 -0400 (EDT)	[thread overview]
Message-ID: <15724.12.172.68.51.1092946691.squirrel@server18.wavepath.com> (raw)
In-Reply-To: <20040819155405.GC4396@logos.cnet>

I noticed it in the 2.4.28-pre1 changelog.

I had concidered doing it has he described - I figured though as a
first-time submitter, the less I touched, the more comfortable people
would feel with it ;-)

Thanks,

-BKG

>
> Applied Rainer's patch, its equivalent and I his
> "consisteny with other algorithms" point is a good one.
>
> Thanks guys!
>
> On Sat, Jul 24, 2004 at 03:14:03PM +0800, Rainer Weikusat wrote:
>> "bradgoodman.com" <bkgoodman@bradgoodman.com> writes:
>> > Patch to 2.4.x: Corrects an obvious error where all of the cleanups
>> are done twice in the event of a chip programming error. This can
>> result in kernel BUG() getting called on subsequent programming
>> attempts.
> <snip>
>> That way, it is consistent with the other low-level chip access
>> functions. But the algorithm is per se buggy, anyway, because except
>> if DQ5 was raised before, the chip is not 'ready' (for reading array
>> data), but still in programming mode and will remain there until the
>> 'embedded programming algorithm' stops, because (according to the
>> docs) a reset command will not be accepted until DQ5 has been raised
>> and the opportunityto check for that is gone after the syscall
>> returned to the caller.




      reply	other threads:[~2004-08-19 20:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 19:47 [PATCH] 2.4.27 - MTD cfi_cmdset_0002.c - Duplicate cleanup in error path bradgoodman.com
2004-07-24  7:14 ` Rainer Weikusat
2004-08-19 15:54   ` Marcelo Tosatti
2004-08-19 20:18     ` bkgoodman [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=15724.12.172.68.51.1092946691.squirrel@server18.wavepath.com \
    --to=bkgoodman@bradgoodman.com \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=rainer.weikusat@sncag.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox