From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joe Perches <joe@perches.com>, Richard Weinberger <richard@nod.at>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn
Date: Fri, 04 Mar 2016 13:03:08 +0200 [thread overview]
Message-ID: <1457089388.1917.5.camel@gmail.com> (raw)
In-Reply-To: <1457007958.4044.111.camel@perches.com>
On Thu, 2016-03-03 at 04:25 -0800, Joe Perches wrote:
> My suggestion would be to add him and designate you and Adrian
> as R: reviewers instead of M: maintainers like below.
I think it is a little bit too early.
next prev parent reply other threads:[~2016-03-04 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1456944509.4044.27.camel@nod.at>
2016-03-02 18:58 ` [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn Joe Perches
2016-03-02 21:24 ` Richard Weinberger
2016-03-02 21:30 ` Joe Perches
2016-03-03 8:39 ` Artem Bityutskiy
2016-03-03 12:25 ` Joe Perches
2016-03-04 11:03 ` Artem Bityutskiy [this message]
2016-02-23 20:21 Joe Perches
2016-03-02 18:19 ` Joe Perches
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=1457089388.1917.5.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=joe@perches.com \
--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).