linux-kernel - Re: Maintainer abuse

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, 16 Dec 2014 19:06:24 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Maintainer abuse

On Sat, 2014-12-13 at 00:24 +0100, Thomas Gleixner wrote:
> I'm really starting to get seriously grumpy about this.
> 
> Everyone is aware that we are in the middle of the merge window. So
> this is definetely NOT the time to send anything else than urgent
> bugfixes or the usual question/reply on something which was discussed
> before.
> 
> I really consider it to be maintainer abuse to have

 ../..

Picking up that thread late ... 

I might have myself been the culprit of that and I don't enforce such
policies on devs on powerpc either, as long as they don't have an
expectation of that stuff being merged before at best the next merge
window.

Especially RFC stuff. People are seeking comments about something or
some approach to a problem, this is clearly not intended for merging and
the comments might not necessarily have to come all from the maintainer,
so I don't see why posting to the list should adhere to a specific
rhythm.

I've certainly myself never taken much attention about when I was
sending a patch, only knew what to expect about when it might end up
being reviewed / merged.

Cheers,
Ben.

--
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/