linux-kernel - Re: [PATCH 1/2] Documentation/development-process: add info on maintainers

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

Date:	Tue, 6 Apr 2010 17:26:36 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] Documentation/development-process: add info on
 maintainers

On Tue, 6 Apr 2010 16:17:05 -0700
Randy Dunlap <randy.dunlap@...cle.com> wrote:

> +-  Please note that most maintainers also have day jobs, so merging
> +   your patch may not be their highest priority.  If your patch is
> +   getting feedback about changes that are needed, you should either
> +   make those changes or justify why they should not be made.  If your
> +   patch has no review complaints but is not being merged by its
> +   appropriate subsystem or driver maintainer, you should be persistent
> +   in updating the patch to the current kernel so that it applies cleanly
> +   and keep sending it for review & merging.

I'd prefer to spell out "and" in that last line, being the sort of
person that I am.  Either way:

Acked-by: Jonathan Corbet <corbet@....net>

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/