From: Joe Perches <joe@perches.com>
To: Artem Bityutskiy <dedekind1@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn
Date: Wed, 02 Mar 2016 10:19:12 -0800 [thread overview]
Message-ID: <1456942752.4044.22.camel@perches.com> (raw)
In-Reply-To: <6f81fc68890afcdf53defe70df9b182be9f26df8.1456258476.git.joe@perches.com>
On Tue, 2016-02-23 at 12:21 -0800, Joe Perches wrote:
> The existing logging macros are fairly large and converting the
> macros to functions make the object code smaller.
Artem and Adrian are the nominal maintainers for ubifs.
Artem last had a sign-off on a ubifs patch 6 months ago and
Adrian's
last one was over 3 years ago.
Is there an expected ack/nack/applied handling time for a
ubifs patch like this?
Should this patch go to someone else?
Should the MAINTAINERS entry for ubifs be changed to orphan?
next prev parent reply other threads:[~2016-03-02 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 20:21 [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn Joe Perches
2016-03-02 18:19 ` Joe Perches [this message]
[not found] <1456944509.4044.27.camel@nod.at>
2016-03-02 18:58 ` 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
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=1456942752.4044.22.camel@perches.com \
--to=joe@perches.com \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.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 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.