From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Tanya Brokhman <tlinder@codeaurora.org>,
Richard Weinberger <richard@nod.at>,
open list <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH V6] UBI: Extend UBI layer debug/messaging capabilities
Date: Tue, 11 Nov 2014 13:44:04 +0200 [thread overview]
Message-ID: <1415706244.22887.156.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1415642273.8868.8.camel@perches.com>
On Mon, 2014-11-10 at 09:57 -0800, Joe Perches wrote:
> On Mon, 2014-11-10 at 18:37 +0100, Richard Weinberger wrote:
> > Am 03.11.2014 um 14:58 schrieb Tanya Brokhman:
> > > 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.
>
> Adding "error" and "warning" to the message logs is
> duplicative to the KERN_<LEVEL> logging information.
>
> > > Changes from V5:
> > > - Added ptr verification @ ubi_err/ubi_msg/ubi_warn
> > > Removed extra printing of ubi number
> > > Removed new messages.
>
> Did you all ever look at what I posted?
>
> https://lkml.org/lkml/2014/10/14/280
>
> smaller code, consistent prefixing, consistent with
> typical kernel style, etc.
No, I did not, because Tanya is someone who actually using and
developing that stuff, and you are more of being on the watch for the
kernel in general. So naturally, I use my limited time to first check
her stuff. Sorry for this.
But Let me change small things in Tanya's patch first. The if you'd be
kind enough to implement your changes on top of that, that'd be perfect.
Artem.
next prev parent reply other threads:[~2014-11-11 11:44 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
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 [this message]
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=1415706244.22887.156.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=joe@perches.com \
--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;
as well as URLs for NNTP newsgroup(s).