From: Richard Weinberger <richard@nod.at>
To: Joe Perches <joe@perches.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs_warn
Date: Wed, 2 Mar 2016 22:24:47 +0100 [thread overview]
Message-ID: <56D75A1F.5070304@nod.at> (raw)
In-Reply-To: <1456945122.4044.35.camel@perches.com>
Joe,
Am 02.03.2016 um 19:58 schrieb Joe Perches:
> On Wed, 2016-03-02 at 19:46 +0100, Richard Weinberger wrote:
>> Am 02.03.2016 7:19 nachm. schrieb Joe Perches <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?
>> No need to panic. I take care of the patch. :)
>
> No worries, I'm calm. But if you're taking care of the patch
> and not the nominal maintainers, likely the MAINTAINERS entry
> should be updated.
>
> Presumably the equivalent ubi patch will be handled in the
> same fashion,
>
> For drivers/mtd/ubi, Artem is also a nominal maintainer, but
> last signed a patch in 2014.
>
> Likely the MAINTAINERS entry for UBI should be updated too.
>
> Maybe something like:
> ---
> MAINTAINERS | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 81302e4..927557c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11266,8 +11266,7 @@ S: Maintained
> F: drivers/scsi/u14-34f.c
>
> UBI FILE SYSTEM (UBIFS)
> -M: Artem Bityutskiy <dedekind1@gmail.com>
> -M: Adrian Hunter <adrian.hunter@intel.com>
> +M: Richard Weinberger <richard@nod.at>
I can be the official patch monkey for UBIFS.
Especial as the git tree is the same as for UBI.
But I definitely want to keep Artem.
He gives very valuable input and knows UBIFS much better than I do.
> L: linux-mtd@lists.infradead.org
> T: git git://git.infradead.org/ubifs-2.6.git
> W: http://www.linux-mtd.infradead.org/doc/ubifs.html
> @@ -11350,7 +11349,6 @@ F: Documentation/scsi/ufs.txt
> F: drivers/scsi/ufs/
>
> UNSORTED BLOCK IMAGES (UBI)
> -M: Artem Bityutskiy <dedekind1@gmail.com>
> M: Richard Weinberger <richard@nod.at>
> W: http://www.linux-mtd.infradead.org/
> L: linux-mtd@lists.infradead.org
Same here. Artem has to stay.
Thanks,
//richard
next prev parent reply other threads:[~2016-03-02 21:24 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 [this message]
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
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=56D75A1F.5070304@nod.at \
--to=richard@nod.at \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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