From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Between a rock and a hard place, managing expectations...
Date: Tue, 22 Aug 2023 10:55:13 +0200 [thread overview]
Message-ID: <2023082250-replace-rectangle-1d47@gregkh> (raw)
In-Reply-To: <64e404a979f54_4c1f3294d3@dwillia2-mobl3.amr.corp.intel.com.notmuch>
On Mon, Aug 21, 2023 at 05:43:21PM -0700, Dan Williams wrote:
> - When do vendors need to share a common ABI?
When they do the "same type of thing" :)
> - How well is our "community consensus" protocol working to give
> contributors actionable feedback?
> - Is there more we can do to enable contributors to steer the right path
> out of the expediency vs maintainability trap?
>
> "Confidential Computing" is an example of an area with several
> cross-silicon-vendor implementations that continue to add features with
> a steady stream of upstream design decisions that cross multiple
> subsystems.
And the normal "you all need to get together and agree on an api
yourself, otherwise we can't take any of this" should work here, right?
Well, except for the groups that snuck stuff in before we realized what
it really was, I guess we are stuck with them.
Why not have the community "fight it out" among themselves first, before
we have to worry about it?
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-22 8:55 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 [this message]
2023-08-22 13:37 ` Linus Walleij
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=2023082250-replace-rectangle-1d47@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.j.williams@intel.com \
--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