All of lore.kernel.org
 help / color / mirror / Atom feed
From: hujianyang <hujianyang@huawei.com>
To: <artem.bityutskiy@linux.intel.com>
Cc: Richard Weinberger <richard@nod.at>,
	Li Zefan <lizefan@huawei.com>,
	Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org, Sheng Yong <shengyong1@huawei.com>
Subject: Current linux-next status of UBI/UBIFS? Re: new UBI co-maintainer
Date: Wed, 28 Jan 2015 10:43:14 +0800	[thread overview]
Message-ID: <54C84CC2.6060708@huawei.com> (raw)
In-Reply-To: <1421918762.8637.162.camel@sauron.fi.intel.com>

On 2015/1/22 17:26, Artem Bityutskiy wrote:
> Hi,
> 
> I'd like to give Richard Weinberger UBI tree push rights, so that he
> could help us improving the QoS.
> 
> If no one objects, lets make it effective.
> 

Hi Artem,

First, thank Richard for his contributions to UBI/UBIFS.


I regret to say the updating of UBI/UBIFS was blocked about 2 months.
So Richard could help us maintaining the improvement of UBIFS next?

I've sent some patches to MTD list these days, what's the opinion of
you and Richard about these pacthes?

   [PATCH] UBI: add ubi_err() to report the failure of leb read
   [PATCH RFC 1/2] UBIFS: fix empty log leb error
   [PATCH] UBI: fix soft lockup in ubi_check_volume()

   and ubidump v6

The patch "UBI: fix soft lockup in ubi_check_volume()" solves a really
important problem, I wish it could be merged into stable soon.

I've discussed with Richard about the recovery of an corrupted UBIFS
image, for example, ECC error. And actually my colleagues and I had
worked out some features to improve the reliability of UBIFS. We are
happy to share our design and greatly aspire the help from community.

Also, I think we could start to add more functions to my ubidump to
make it a useful tool.

I think the updating of UBI/UBIFS will re-start soon, am I right?

BR,
Hu

  parent reply	other threads:[~2015-01-28  2:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  9:26 new UBI co-maintainer Artem Bityutskiy
2015-01-22 21:57 ` Brian Norris
2015-01-28  2:43 ` hujianyang [this message]
2015-01-28 15:47   ` Current linux-next status of UBI/UBIFS? " Richard Weinberger
2015-01-29  3:28     ` hujianyang
2015-01-29  9:08       ` Richard Weinberger

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=54C84CC2.6060708@huawei.com \
    --to=hujianyang@huawei.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lizefan@huawei.com \
    --cc=richard@nod.at \
    --cc=shengyong1@huawei.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 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.