From: Artem Bityutskiy <dedekind1@gmail.com>
To: Tanya Brokhman <tlinder@codeaurora.org>
Cc: Richard Weinberger <richard@nod.at>,
linux-arm-msm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: ubi: Extend UBI layer debug/messaging capabilities
Date: Sun, 28 Sep 2014 15:15:56 +0300 [thread overview]
Message-ID: <1411906556.11836.26.camel@karhu> (raw)
In-Reply-To: <5427C5C4.40508@codeaurora.org>
On Sun, 2014-09-28 at 11:24 +0300, Tanya Brokhman wrote:
> This is how I first implemented this patch. But then I cam across
> some
> ubi_err prints during the init process (in build.c ubi_init()) when
> we
> still don't have the ubi structure, so we need to pass some number to
> the message. I overcame this by using UBI_MAX_DEVICES.
Well, may be having two sets of wrappers would make sense then?
Or if there are few of those, just using 'printk()' would be a solution?
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-09-28 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 6:36 [PATCH] mtd: ubi: Extend UBI layer debug/messaging capabilities Tanya Brokhman
2014-09-28 8:01 ` Richard Weinberger
2014-09-28 8:24 ` Tanya Brokhman
2014-09-28 12:15 ` Artem Bityutskiy [this message]
2014-09-28 12:14 ` Artem Bityutskiy
2014-09-28 12:01 ` Artem Bityutskiy
2014-09-30 8:02 ` Tanya Brokhman
2014-09-29 10:50 ` Kiran Padwal
2014-09-29 12:01 ` Richard Weinberger
2014-09-29 12:32 ` Kiran Padwal
2014-09-29 12:37 ` Richard Weinberger
2014-09-30 7:30 ` Tanya Brokhman
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=1411906556.11836.26.camel@karhu \
--to=dedekind1@gmail.com \
--cc=computersforpeace@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