From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Maintainer's Summit Agenda Planning
Date: Tue, 24 Oct 2017 16:41:48 -0700 [thread overview]
Message-ID: <1508888508.1955.16.camel@perches.com> (raw)
In-Reply-To: <CAGXu5jJAUbhEZPFYSU1ExON49LqQMTgjmRSszp6eMuaDuSimsA@mail.gmail.com>
On Tue, 2017-10-24 at 16:03 -0700, Kees Cook wrote:
> 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. ;)
It's a ripe area (like months old limburger cheese) for discussion.
There's currently no good way to do tree-wide changes.
next prev parent reply other threads:[~2017-10-24 23:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 19:20 Theodore Ts'o
2017-10-05 20:13 ` Rafael J. Wysocki
2017-10-05 21:55 ` Jiri Kosina
2017-10-06 14:59 ` Takashi Iwai
2017-10-06 15:27 ` James Bottomley
2017-10-06 16:26 ` Josh Poimboeuf
2017-10-06 16:32 ` Jonathan Corbet
2017-10-06 16:51 ` Josh Poimboeuf
2017-10-06 16:56 ` James Bottomley
2017-10-06 17:16 ` Josh Poimboeuf
2017-10-06 20:11 ` Linus Walleij
2017-10-09 8:13 ` Mark Brown
2017-10-09 15:54 ` Jiri Kosina
2017-10-09 16:37 ` James Bottomley
2017-10-09 16:47 ` Joe Perches
2017-10-09 16:49 ` Julia Lawall
2017-10-09 16:56 ` James Bottomley
2017-10-09 17:04 ` Joe Perches
2017-10-11 18:51 ` Jani Nikula
2017-10-12 10:03 ` Daniel Vetter
2017-10-16 14:12 ` James Bottomley
2017-10-16 14:25 ` Jani Nikula
2017-10-16 16:07 ` Joe Perches
2017-10-17 8:34 ` Jani Nikula
2017-10-18 1:27 ` Joe Perches
2017-10-18 10:41 ` Jani Nikula
2017-10-16 18:52 ` Mark Brown
2017-10-10 8:53 ` Jiri Kosina
2017-10-24 23:03 ` Kees Cook
2017-10-24 23:41 ` Joe Perches [this message]
2017-10-25 0:54 ` Kees Cook
2017-10-25 4:21 ` Julia Lawall
2017-10-25 4:29 ` Joe Perches
2017-10-25 4:36 ` Julia Lawall
2017-10-25 6:05 ` Martin K. Petersen
2017-10-25 6:55 ` Kees Cook
2017-10-25 7:34 ` Martin K. Petersen
2017-10-25 6:45 ` Frank Rowand
2017-10-25 7:56 ` Mark Brown
2017-10-25 9:39 ` Laurent Pinchart
2017-10-31 19:19 ` Rob Herring
2017-10-31 19:28 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1508888508.1955.16.camel@perches.com \
--to=joe@perches.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=keescook@chromium.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox