From: Tanya Brokhman <tlinder@codeaurora.org>
To: dedekind1@gmail.com,
Ezequiel Garcia <ezequiel.garcia@free-electrons.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 v3] mtd: ubi: Extend UBI layer debug/messaging capabilities
Date: Tue, 14 Oct 2014 15:14:48 +0300 [thread overview]
Message-ID: <543D13B8.6010006@codeaurora.org> (raw)
In-Reply-To: <1413215953.7906.63.camel@sauron.fi.intel.com>
On 10/13/2014 6:59 PM, Artem Bityutskiy wrote:
> On Mon, 2014-10-13 at 18:37 +0300, Artem Bityutskiy wrote:
>> On Mon, 2014-10-06 at 14:01 +0300, 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.
>>
>> Looks good to me, pushed to the master branch of the linux-ubifs.git
>> tree. Later, when the merge window is closed, I'll merge this patch to
>> the linux-next branch too.
>
> Tanya,
>
> sorry, I was not careful enough, I merged it and tested against the
> Linuses head, it is fine.
>
> But it does not apply the the linux-ubifs.git tree. There are conflicts.
>
> But more importantly, you did not get the 'block.c' right. There we use
> the same printing macros, but we do not have 'struct ubi_info' there at
> all.
>
> Please, enable the R/O block layer feature and try to compile, it'll
> fail.
>
> The block driver is in 'drivers/mtd/ubi', but it is kind of a separate
> driver - it does not access the internal UBI data structures.
>
> I guess the solution would be to just use pr_* functions there instead.
>
> CCing Ezequiel.
>
> Please, submit a patch against the 'linux-next' branch of this tree:
>
> git://git.infradead.org/linux-ubifs.git
>
>
> Artem.
>
Ok, will do ASAP.
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
prev parent reply other threads:[~2014-10-14 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 11:01 [PATCH v3] mtd: ubi: Extend UBI layer debug/messaging capabilities Tanya Brokhman
2014-10-06 11:01 ` Tanya Brokhman
2014-10-06 11:01 ` Tanya Brokhman
2014-10-13 15:37 ` Artem Bityutskiy
2014-10-13 15:37 ` Artem Bityutskiy
2014-10-13 15:59 ` Artem Bityutskiy
2014-10-14 12:14 ` Tanya Brokhman [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=543D13B8.6010006@codeaurora.org \
--to=tlinder@codeaurora.org \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.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 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.