From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: vendor extension moratorium?
Date: Wed, 17 Feb 2016 00:55:08 -0800 [thread overview]
Message-ID: <20160217085508.GA3578@infradead.org> (raw)
While doing heavy lifting in the RDMA stack I keep running into
badly designed vendor extensions over and over.
Is there any support for requiring that we'll only add features that
actually are peer reviewed and standardized before keeping on piling
up crap? It seems like at least vendors seems to be fighting for death
by features unfortunately.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-02-17 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:55 Christoph Hellwig [this message]
[not found] ` <20160217085508.GA3578-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-02-17 10:02 ` vendor extension moratorium? Leon Romanovsky
[not found] ` <20160217100207.GB30450-2ukJVAZIZ/Y@public.gmane.org>
2016-02-17 15:05 ` Christoph Hellwig
[not found] ` <20160217150500.GA8164-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-02-17 19:18 ` Leon Romanovsky
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=20160217085508.GA3578@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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