linux-kernel - Re: rfc: trivial patches and slow deaths?

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]

Message-ID: <1376947637.2016.39.camel@joe-AO722>
Date:	Mon, 19 Aug 2013 14:27:17 -0700
From:	Joe Perches <joe@...ches.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	kernel-janitors <kernel-janitors@...r.kernel.org>
Subject: Re: rfc: trivial patches and slow deaths?

On Mon, 2013-08-19 at 23:22 +0200, Jiri Kosina wrote:
> On Mon, 19 Aug 2013, Joe Perches wrote:
> 
> > This is a 7 line patch that corrects logging defects that has had no 
> > reply from you for the last month.
> > 
> > https://patchwork.kernel.org/patch/2833648/
> 
> This hasn't missed any Linus' major release, as it has been submitted post 
> 3.11 merge, right? (hint, that was Jul 4th).
> 
> If this would miss *next* major Linus' release, I would accept your 
> complaints. But this is definitely not the case.

You're suggesting this patch, which corrects obvious
defects, should miss 3.12 and go into 3.13?

I think that's wrong.

I think it should be in -next now.  It's not.

What should any patch submitter expect about
visibility and/or knowledge of the applicability
of this sort of patch from trivial?


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