From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <keescook@google.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 9FCB6C07
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Tue, 24 Oct 2017 23:03:05 +0000 (UTC)
Received: from mail-it0-f68.google.com (mail-it0-f68.google.com
	[209.85.214.68])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2BA49180
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Tue, 24 Oct 2017 23:03:05 +0000 (UTC)
Received: by mail-it0-f68.google.com with SMTP id l196so11989234itl.4
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Tue, 24 Oct 2017 16:03:05 -0700 (PDT)
MIME-Version: 1.0
Sender: keescook@google.com
In-Reply-To: <1507303665.3104.13.camel@HansenPartnership.com>
References: <20171005192002.hxbjjdjhrfa4oa37@thunk.org>
	<1507303665.3104.13.camel@HansenPartnership.com>
From: Kees Cook <keescook@chromium.org>
Date: Tue, 24 Oct 2017 16:03:03 -0700
Message-ID: <CAGXu5jJAUbhEZPFYSU1ExON49LqQMTgjmRSszp6eMuaDuSimsA@mail.gmail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Content-Type: text/plain; charset="UTF-8"
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Maintainer's Summit Agenda Planning
List-Id: <ksummit-discuss.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/ksummit-discuss/>
List-Post: <mailto:ksummit-discuss@lists.linuxfoundation.org>
List-Help: <mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=subscribe>

On Fri, Oct 6, 2017 at 8:27 AM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> On Thu, 2017-10-05 at 15:20 -0400, Theodore Ts'o wrote:
>> Appendix: Other topics that were brought up
>> [...]
>> Developing across multiple areas of the kernel
>
> I've got a couple of extra possibilities
> [...]
> 2) Trivial patches (again).

Given that the "trivial patches" topic's discussion ended up boiling
down to a discussion about developing across multiple areas of the
kernel, maybe we should make space for a "tree-wide changes"
discussion? Even after the earlier thread about it, I tripped all over
this in the last couple months while doing timer conversions, so I
would at least have some more strong opinions on the subject. ;)

-Kees

-- 
Kees Cook
Pixel Security