From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Doug Ledford <dledford@redhat.com>,
Tadeusz Struk <tadeusz.struk@intel.com>,
linux-rdma@vger.kernel.org, linux-pci@vger.kernel.org,
dennis.dalessandro@intel.com, ira.weiny@intel.com
Subject: Re: [PATCH] [RFC] IB/hfi1: Fix port ordering issue in a multiport device
Date: Sun, 22 Jan 2017 10:16:40 +0200 [thread overview]
Message-ID: <20170122081640.GG28570@mtr-leonro.local> (raw)
In-Reply-To: <20170119175802.GB8109@obsidianresearch.com>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Thu, Jan 19, 2017 at 10:58:02AM -0700, Jason Gunthorpe wrote:
> On Wed, Jan 18, 2017 at 07:16:29PM -0500, Doug Ledford wrote:
>
>
> > No, mlx5 could have easily hit this too as their ports are separate
> > PCI functions.
>
> Sound like intel and mellanox should collaborate on getting udev
> stable naming working right for RDMA... They are eventually going to
> get burned.
Send patches and we will be happy to review and test them.
Thanks
>
> Jason
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-01-22 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 23:57 [PATCH] [RFC] IB/hfi1: Fix port ordering issue in a multiport device Tadeusz Struk
2017-01-11 7:12 ` Leon Romanovsky
2017-01-11 17:20 ` Tadeusz Struk
2017-01-11 17:59 ` Leon Romanovsky
2017-01-11 18:10 ` Jason Gunthorpe
2017-01-18 21:01 ` Doug Ledford
2017-01-18 21:08 ` Jason Gunthorpe
2017-01-18 22:03 ` Tadeusz Struk
2017-01-19 0:17 ` Doug Ledford
2017-01-19 16:51 ` Tadeusz Struk
2017-01-19 0:16 ` Doug Ledford
2017-01-19 17:58 ` Jason Gunthorpe
2017-01-22 8:16 ` Leon Romanovsky [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=20170122081640.GG28570@mtr-leonro.local \
--to=leon@kernel.org \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tadeusz.struk@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).