From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Majd Dibbiny <majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH for-next 0/5] Add scatter FCS support
Date: Fri, 13 May 2016 17:18:56 -0600 [thread overview]
Message-ID: <20160513231856.GA18260@obsidianresearch.com> (raw)
In-Reply-To: <92e9a494-c363-db42-894c-17d67fe96ecc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Fri, May 13, 2016 at 04:39:23PM -0400, Doug Ledford wrote:
> This patchset is a uAPI extending patchset. Recently, there has been
> talk of requiring a higher level of review and acknowledgment from
> various vendors for such patches. However, in this case, it extends the
> QP creation code, which is already an extended function, and it extends
> it in a manner consistent with the original extension mechanism.
You've missed the point - the extension mechanism is explicitly not
for vendor-specific stuff, the question to ask is this FCS thing
driver specific, is it sufficiently general, and can other vendors
implement it.
I'd say yes to those questions, what it does seems well defined and
generic.
Jason
--
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
prev parent reply other threads:[~2016-05-13 23:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 14:19 [PATCH for-next 0/5] Add scatter FCS support Matan Barak
[not found] ` <1460902778-5977-1-git-send-email-matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-04-17 14:19 ` [PATCH for-next 1/5] IB/core: Add extended device capability flags Matan Barak
2016-04-17 14:19 ` [PATCH for-next 2/5] IB/core: Add Raw Scatter FCS device capability Matan Barak
2016-04-17 14:19 ` [PATCH for-next 3/5] IB/core: Add Scatter FCS create flag Matan Barak
2016-04-17 14:19 ` [PATCH for-next 4/5] IB/mlx5: Add Scatter FCS support for Raw Packet QP Matan Barak
[not found] ` <1460902778-5977-5-git-send-email-matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-04-17 15:10 ` kbuild test robot
2016-04-17 15:32 ` kbuild test robot
2016-04-17 15:44 ` kbuild test robot
2016-04-17 14:19 ` [PATCH for-next 5/5] IB/mlx5: Report Scatter FCS device capability when supported Matan Barak
[not found] ` <1460902778-5977-6-git-send-email-matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-04-17 15:15 ` kbuild test robot
2016-04-17 15:44 ` kbuild test robot
[not found] ` <201604172352.60qppaot%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-21 1:24 ` ira.weiny
[not found] ` <20160421012442.GA30527-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2016-04-21 7:07 ` Leon Romanovsky
2016-05-13 20:39 ` [PATCH for-next 0/5] Add scatter FCS support Doug Ledford
[not found] ` <92e9a494-c363-db42-894c-17d67fe96ecc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-13 23:18 ` Jason Gunthorpe [this message]
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=20160513231856.GA18260@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=matanb-VPRAkNaXOzVWk0Htik3J/w@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