From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Jim Ramsay <kernel@jimramsay.com>
Cc: Thiago Galesi <thiagogalesi@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Possible MTD bug in 2.6.15
Date: Sun, 23 Apr 2006 09:45:11 +0200 [thread overview]
Message-ID: <20060423074511.GA19326@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <4789af9e0604222048g5a10b573pf687f137a2e99042@mail.gmail.com>
On Sat, 22 April 2006 21:48:28 -0600, Jim Ramsay wrote:
>
> And really, it's not a big stretch from what the code currently does
> to what my patch changes. At this point in the code, we know for a
> fact that we already have at least one flash chip. The math that's
> going on here with the 'max_chips' variable is to check if there is
> actually more than one physical chip implementing the entire reported
> size. The only mistake is that the math goes too far, shifting the
> count down to zero if the reported size is too small. This
> 'max_chips' should never be allowed to be lower than 1, because we
> really do know that there is at least one flash chip.
In a setup like yours, someone should go and educate hardware
developers.
Anyway, if you add a CONFIG_BROKEN_HARDWARE of some sorts to your
patch and send it to the proper list (linux-mtd@lists.infradead.org),
I don't have a problem with your patch.
Jörn
--
To announce that there must be no criticism of the President, or that we
are to stand by the President, right or wrong, is not only unpatriotic
and servile, but is morally treasonable to the American public.
-- Theodore Roosevelt, Kansas City Star, 1918
next prev parent reply other threads:[~2006-04-23 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1145723704.3524.TMDA@mail.tag.jimramsay.com>
2006-04-22 16:49 ` Fw: " Jim Ramsay
2006-04-22 17:08 ` Thiago Galesi
2006-04-23 3:48 ` Jim Ramsay
2006-04-23 7:45 ` Jörn Engel [this message]
2006-04-19 16:49 Jim Ramsay
2006-04-19 17:06 ` Thiago Galesi
2006-04-19 17:43 ` Pekka Enberg
2006-05-30 12:30 ` 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=20060423074511.GA19326@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=kernel@jimramsay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thiagogalesi@gmail.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
all inboxes | Powered by JetHome®