From: Linus Walleij <linus.walleij@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Dan Williams <dan.j.williams@intel.com>, ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Between a rock and a hard place, managing expectations...
Date: Tue, 22 Aug 2023 15:37:21 +0200 [thread overview]
Message-ID: <CACRpkdZWoyGfDdG=6aULDhvwYDF829yqK-u9wp563R+E+SWOtw@mail.gmail.com> (raw)
In-Reply-To: <2023082250-replace-rectangle-1d47@gregkh>
Dan wrote:
> Standardization helps, but there is often a "system-software
> implementation-specific" gap that a standard leaves for an operating
> system to resolve. Linux is nowadays a first mover, and a primary
> deployment target.
When we designed pin control, I first made an iteration which we had
to throw away, keeping the old quote from "the mythical man-month"
in mind, "always count on throwing one version away". The same
happened with the GPIO character device. v2 looks good. We need
to realize at least from what I've seen, that Fred Brooks was right
about this.
Always having to throw the first version away is the most obvious
pattern that we should always expect, yet fail repeatedly to account
for and always get annoyed at. Why? It is expected.
Greg wrote:
Why not have the community "fight it out" among themselves first, before
> we have to worry about it?
We can be a bit proactive with this, but it's more of elusive
entrepreneurship or magical coincidence when we do, and the
work happens seemingly unorganized.
The v2 pin control was designed in a conference room at the Embedded
Linux Conference in San Diego 2012 I think. nVidia, Texas Instruments and
Renesas were there, possibly more. We had a whiteboard. That
ended up with with the lines hooking it up in drivers/base/dd.c and that
is still the core behaviour.
It wasn't a fight, more like a good version of committee work, like a
committee without any prestige.
Collect the key people in the same geographical location and talk
it over, magic happens. Sometimes, at least. It's worth a try.
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-08-22 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 0:43 Dan Williams
2023-08-22 8:55 ` Greg KH
2023-08-22 13:37 ` Linus Walleij [this message]
2023-08-22 14:29 ` Laurent Pinchart
2023-08-24 0:46 ` Jason Gunthorpe
2023-08-24 8:16 ` Linus Walleij
2023-08-24 14:19 ` Jason Gunthorpe
2023-08-24 17:12 ` Mark Brown
2023-08-24 17:20 ` Bird, Tim
2023-08-24 19:29 ` Bart Van Assche
2023-08-24 19:58 ` Mark Brown
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='CACRpkdZWoyGfDdG=6aULDhvwYDF829yqK-u9wp563R+E+SWOtw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
/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