From: Thayne Harbaugh <tharbaugh@lnxi.com>
To: linux-mtd@lists.infradead.org
Subject: broken cfi_cmdset_0001.c
Date: 04 Nov 2003 12:33:14 -0700 [thread overview]
Message-ID: <1067974394.6281.1886.camel@tubarao> (raw)
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
A while ago I committed an "improvement" to cfi_cmdset_0001.c that would
skip writing a cfi_word if it was identical to what was already
written. Apparently, even though I thought I had, I didn't test this.
This resulted in cfi_cmdset_0001.c r1.131 being horribly broken. Please
use r1.130 or r1.132.
My apologies.
--
Thayne Harbaugh
Linux Networx
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-11-04 19:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1067974394.6281.1886.camel@tubarao \
--to=tharbaugh@lnxi.com \
--cc=linux-mtd@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.