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: <20130820152456.c12dd8f543e2735b6952ae13@linux-foundation.org>
Date:	Tue, 20 Aug 2013 15:24:56 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Joe Perches <joe@...ches.com>
Cc:	Rob Landley <rob@...dley.net>, Jiri Kosina <jkosina@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>,
	kernel-janitors <kernel-janitors@...r.kernel.org>
Subject: Re: rfc: trivial patches and slow deaths?

On Tue, 20 Aug 2013 15:11:18 -0700 Joe Perches <joe@...ches.com> wrote:

> Andrew?  Do you want to handle patches for defects that
> are both obvious _and_ trivial?

I look at everything!  If I like it and see that Jiri was cc'ed I try
to remember to cc him on the commit.

> > If it's trivial it's not time critical. If it's time critical it's not  
> > trivial.
> 
> We disagree on the definition of trivial.
> Trivial can also mean simple and immediately evident.

I find that I often remove "trivial" from changelogs and titles.  Patches
which are marked thus are often non-trivial and merit a bit of thought.

For example, I somewhat disagree that even
https://patchwork.kernel.org/patch/2833648/ was trivial.  It changes
the format of kernel logs and might have implications for people who
are parsing those logs.  Unlikely, but one needs to read each and every
conversion and decide on the risk factor.

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