From: Frank Haverkamp <haver@vnet.ibm.com>
To: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Schmidt <alexs@linux.vnet.ibm.com>,
MTD Mailinglist <linux-mtd@lists.infradead.org>,
Frank Haverkamp <haver@vnet.ibm.com>
Subject: ubi-utils: Fix and enhancement for nand2bin
Date: Wed, 26 Sep 2007 13:49:48 +0200 [thread overview]
Message-ID: <1190807388.21594.20.camel@august> (raw)
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
Hi Artem,
due to a recent problem I needed to analyze, I produced a fix and a
functionality enhancement for our nand2bin tool. Please consider pulling
the two changes from my mtd-utils git if you find them ok.
Regards,
Frank
--
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032
Boeblingen, Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Herbert Kircher, Sitz der Gesellschaft: Böblingen,
Registergericht: Amtsgericht Stuttgart, HRB 243294
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5269 bytes --]
reply other threads:[~2007-09-26 11:50 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=1190807388.21594.20.camel@august \
--to=haver@vnet.ibm.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=alexs@linux.vnet.ibm.com \
--cc=dwmw2@infradead.org \
--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