linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tanya Brokhman <tlinder@codeaurora.org>
To: hujianyang <hujianyang@huawei.com>, dedekind1@gmail.com
Cc: linux-arm-msm@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>,
	linux-mtd@lists.infradead.org,
	Richard Weinberger <richard@nod.at>,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH V6] UBI: Extend UBI layer debug/messaging capabilities
Date: Fri, 07 Nov 2014 14:32:34 +0200	[thread overview]
Message-ID: <545CBBE2.7000205@codeaurora.org> (raw)
In-Reply-To: <545C9A1B.6020905@huawei.com>

On 11/7/2014 12:08 PM, hujianyang wrote:
> On 2014/11/5 23:35, Artem Bityutskiy wrote:
>> On Mon, 2014-11-03 at 15:58 +0200, 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>
>>
>> Oh, the entire patch-set again... this means we need to review it again!
>> Please, have a mercy! :-) It is huge! Please, send a small patch against
>> the one which I pushed already. Thanks!
>>

Oh :( and I did that on purpose.... For some reason I thought you would 
revert that one and push a new and updated one.
Ok, I'll upload a short version.

>
> That means I can't add a Reviewed-by on this huge one...

... and then you can add Reviewed-by! :)
>
> What a pity~! ^.^
>
>
>> Artem.
>>
>>
>> ______________________________________________________
>> Linux MTD discussion mailing list
>> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>>
>>
>
>


Thanks,
Tanya Brokhman
-- 
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2014-11-07 12:33 UTC|newest]

Thread overview: 21+ 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 [this message]
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  9:53           ` Tanya Brokhman
2014-11-11 11:35             ` Artem Bityutskiy
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
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=545CBBE2.7000205@codeaurora.org \
    --to=tlinder@codeaurora.org \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=hujianyang@huawei.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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;
as well as URLs for NNTP newsgroup(s).