public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hujianyang <hujianyang@huawei.com>
To: Tanya Brokhman <tlinder@codeaurora.org>
Cc: <dedekind1@gmail.com>, <linux-arm-msm@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Richard Weinberger <richard@nod.at>,
	<linux-mtd@lists.infradead.org>,
	Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH V6] UBI: Extend UBI layer debug/messaging capabilities
Date: Mon, 29 Dec 2014 11:14:21 +0800	[thread overview]
Message-ID: <54A0C70D.7040706@huawei.com> (raw)
In-Reply-To: <1415023112-21704-1-git-send-email-tlinder@codeaurora.org>

On 2014/11/3 21:58, Tanya Brokhman wrote:
> If there is more then one UBI device mounted, there is no way to
> distinguish between messages from different UBI devices.
> Add device number to all ubi layer message types.
> 
> The R/O block driver messages were replaced by pr_* since
> ubi_device structure is not used by it.
> 
> Amended a bit by Artem.
> 
> Signed-off-by: Tanya Brokhman <tlinder@codeaurora.org>
> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> ---
> Changes from V1:


Hi Artem and Tanya,

Do you think the similar effort is worth to be done on ubifs-level?

We could have several ubifs partition mounted on a host.

Thanks,
Hu



  parent reply	other threads:[~2014-12-29  3:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 13:58 [PATCH V6] UBI: Extend UBI layer debug/messaging capabilities Tanya Brokhman
2014-11-05 15:35 ` Artem Bityutskiy
2014-11-07 10:08   ` hujianyang
2014-11-07 12:32     ` Tanya Brokhman
2014-11-10 17:37 ` Richard Weinberger
2014-11-10 17:57   ` Joe Perches
2014-11-11  8:24     ` Tanya Brokhman
2014-11-11  8:34       ` Joe Perches
2014-11-11  8:56         ` Richard Weinberger
2014-11-11 11:44     ` Artem Bityutskiy
2014-11-11  8:15   ` Richard Weinberger
2014-11-11 12:03     ` Artem Bityutskiy
2014-11-11 12:25       ` Richard Weinberger
2014-11-11 13:27         ` Artem Bityutskiy
2014-11-11 19:49           ` Richard Weinberger
2014-11-12 12:32             ` Artem Bityutskiy
2014-12-29  3:14 ` hujianyang [this message]
2014-12-29 14:15   ` Tanya Brokhman
2014-12-30  1:27     ` hujianyang

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=54A0C70D.7040706@huawei.com \
    --to=hujianyang@huawei.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=tlinder@codeaurora.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