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-prev] [day] [month] [year] [list]

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

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?