From: Artem Bityutskiy <dedekind1@gmail.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] libmtd: allow write operations when MEMWRITE is not supported
Date: Sat, 17 Dec 2011 17:11:22 +0200 [thread overview]
Message-ID: <1324134682.4240.43.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <8762hf44v4.fsf@macbook.be.48ers.dk>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On Sat, 2011-12-17 at 16:03 +0100, Peter Korsgaard wrote:
> >>>>> "Artem" == Artem Bityutskiy <dedekind1@gmail.com> writes:
>
> Hi,
>
> >> > I guess this require an urgent mtd-utils release.
>
> Artem> OK, I've cut mtd-utils-1.4.9 bug-fix release, this time with my
> Artem> new script, so I hope nothing is forgotten.
>
> Artem> Peter, please, update - this release fixes a bad bug which breaks NOR
> Artem> erase operation in not-yet-released 3.2 kernel.
>
> Thanks for the heads up, I was just about to rebase a NOR-using platform
> to 3.2.
>
> Updated buildroot. It builds fine here, so it seems like the script is
> working.
Notice also than now we also provide the mtd-utils-1.4.9.tar.bz2.asc
tarball signature and we also sign the mtd-utils tags.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-17 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 19:45 [PATCH] libmtd: allow write operations when MEMWRITE is not supported Brian Norris
2011-12-12 21:26 ` Artem Bityutskiy
2011-12-12 21:40 ` Brian Norris
2011-12-17 14:44 ` Artem Bityutskiy
2011-12-17 15:03 ` Peter Korsgaard
2011-12-17 15:11 ` Artem Bityutskiy [this message]
2011-12-19 18:45 ` Brian Norris
2011-12-19 20:38 ` Artem Bityutskiy
2011-12-12 21:29 ` Artem Bityutskiy
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=1324134682.4240.43.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=jacmet@sunsite.dk \
--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.