ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Maintainer's Summit Agenda Planning
Date: Fri, 6 Oct 2017 22:11:46 +0200	[thread overview]
Message-ID: <CACRpkda8gy181QKh9dnTOXXsdO8NAXORLangtJb1syYHATOBWQ@mail.gmail.com> (raw)
In-Reply-To: <20171006103259.78ab2508@lwn.net>

On Fri, Oct 6, 2017 at 6:32 PM, Jonathan Corbet <corbet@lwn.net> wrote:

> The tricky part, of course, is finding a way to document the consensus on
> best practices without trying to "drive" it too hard.

I put some two very technical, not too subjective design
patterns in
Documentation/driver-model/design-patterns.txt

I have found myself on the verge of sending a patch adding
Rusty Russell's API design manifesto somewhere there
http://sweng.the-davies.net/Home/rustys-api-design-manifesto

The problem is mostly that I don't always feel what the
consensus is. With some subsystem maintainers happily
agree to disagree on so many things like inverse-christmas
tree includes or u_int8_t vs u8 it's easy to be discouraged.

I guess we should just be more bold? Who knows, maybe
noone even gets upset.

Apart from that I guess Documentation/process/* need to
be updated with best practices? Maybe that was the actual
initial question. I especially like management-style.rst,
that doc kicks ass.

Yours,
Linus Walleij

  parent reply	other threads:[~2017-10-06 20:11 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 [this message]
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
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=CACRpkda8gy181QKh9dnTOXXsdO8NAXORLangtJb1syYHATOBWQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=corbet@lwn.net \
    --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