linux-kernel - Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg, ubifs_err and ubifs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1456945122.4044.35.camel@perches.com>
Date:	Wed, 02 Mar 2016 10:58:42 -0800
From:	Joe Perches <joe@...ches.com>
To:	Richard Weinberger <richard@....at>
Cc:	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Adrian Hunter <adrian.hunter@...el.com>,
	Artem Bityutskiy <dedekind1@...il.com>
Subject: Re: [PATCH V2] ubifs: Add logging functions for ubifs_msg,
 ubifs_err and ubifs_warn

On Wed, 2016-03-02 at 19:46 +0100, Richard Weinberger wrote:
> Am 02.03.2016 7:19 nachm. schrieb Joe Perches <joe@...ches.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@...il.com>
-M:	Adrian Hunter <adrian.hunter@...el.com>
+M:	Richard Weinberger <richard@....at>
 L:	linux-mtd@...ts.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@...il.com>
 M:	Richard Weinberger <richard@....at>
 W:	http://www.linux-mtd.infradead.org/
 L:	linux-mtd@...ts.infradead.org