From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jaya Kumar <jayakumar.lkml@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problems after 2nd bootup with NAND and ubifs/ubi
Date: Fri, 24 Aug 2012 15:03:12 +0300 [thread overview]
Message-ID: <1345809792.2848.300.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CADqH6Vx_doWcOFP6N8qSV-h+KdZi8cqdxyHCROf-SKFvUiYNhg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
On Wed, 2012-08-15 at 15:19 +0800, Jaya Kumar wrote:
> Hi mtd/ubifs friends,
>
> First off, thanks for your work, especially providing the backport to
> 2.6.37. I found that to be very useful.
Hi, sorry for long delay, I think we recently fixed this and the fixes
are added to the ubifs-v2.6.37.git backport tree as well.
--
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:[~2012-08-24 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 7:19 Problems after 2nd bootup with NAND and ubifs/ubi Jaya Kumar
2012-08-16 5:50 ` Jaya Kumar
2012-08-24 12:03 ` Artem Bityutskiy [this message]
2012-08-24 12:13 ` Artem Bityutskiy
2012-09-03 10:31 ` Jaya Kumar
2012-09-04 9:31 ` 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=1345809792.2848.300.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=jayakumar.lkml@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox