From: Artem Bityutskiy <dedekind@infradead.org>
To: Corentin Chary <corentincj@iksaif.net>
Cc: linux-mtd@lists.infradead.org, vapier.adi@gmail.com
Subject: Re: [PATCH 0/3] libubi / mkfs.ubifs #2
Date: Mon, 11 May 2009 17:29:37 +0300 [thread overview]
Message-ID: <1242052177.27996.139.camel@localhost.localdomain> (raw)
In-Reply-To: <1241862068-10596-1-git-send-email-corentincj@iksaif.net>
On Sat, 2009-05-09 at 11:41 +0200, Corentin Chary wrote:
> These patchs will allow mkfs.ubifs to write the image directly
> on an UBI volume. This time libubi is used. I couldn't manage to
> make the Makefile works correctly, even with Mike trick for dependencies.
> Mike, could you help me on that ?
> You can still make it compile with "cd ubi-utils; make; cd ../mkfs.ubifs; make"
Just pushed the first 2 of your patches. Also, there is
a similar problem in libmtd - I've fixed that too. And
I walked through all memset calls and amended/fixed them
as well.
Thanks. Will look at the third patch later.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-05-11 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 9:41 [PATCH 0/3] libubi / mkfs.ubifs #2 Corentin Chary
2009-05-09 9:41 ` [PATCH 1/3] libubi: add ubi_is_mapped() function Corentin Chary
2009-05-09 9:41 ` [PATCH 2/3] libubi: fix multiple memory corruptions Corentin Chary
2009-05-09 9:41 ` [PATCH 3/3] mkfs.ubifs: use libubi to format UBI volume Corentin Chary
2009-05-13 8:12 ` Artem Bityutskiy
2009-05-13 8:38 ` Corentin Chary
2009-05-13 8:46 ` Artem Bityutskiy
2009-05-11 7:02 ` [PATCH 0/3] libubi / mkfs.ubifs #2 Corentin Chary
2009-05-11 7:19 ` Artem Bityutskiy
2009-05-11 7:21 ` Artem Bityutskiy
2009-05-11 7:23 ` Artem Bityutskiy
2009-05-11 7:37 ` Mike Frysinger
2009-05-11 7:58 ` Corentin Chary
2009-05-11 14:29 ` Artem Bityutskiy [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=1242052177.27996.139.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=corentincj@iksaif.net \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@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