public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Tadeusz Struk <tadeusz.struk@intel.com>,
	gregkh@linuxfoundation.org, linux-rdma@vger.kernel.org,
	dennis.dalessandro@intel.com, linux-kernel@vger.kernel.org,
	grant.likely@secretlab.ca, dledford@redhat.com,
	ira.weiny@intel.com
Subject: Re: [PATCH RFC 2/2] IB/hfi1: Fix port ordering issue in a multiport device
Date: Mon, 6 Feb 2017 13:04:25 -0800	[thread overview]
Message-ID: <20170206210425.GA2062@infradead.org> (raw)
In-Reply-To: <20170206192642.GA22482@obsidianresearch.com>

On Mon, Feb 06, 2017 at 12:26:42PM -0700, Jason Gunthorpe wrote:
> Still no on this from me, this is a horrible abuse of the device core.

Seconded.  Netdevice (and thus RDMA) devices names generated by the
kernel are not stable, period.  Use udev and the MAC / port GUID or
whatever the OFI equivalent is to generate stable device names.

  reply	other threads:[~2017-02-06 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 19:15 [PATCH RFC 1/2] driver core: allow EPROBE_DEFER after boot Tadeusz Struk
2017-02-06 19:15 ` [PATCH RFC 2/2] IB/hfi1: Fix port ordering issue in a multiport device Tadeusz Struk
     [not found]   ` <148640853387.13713.5705865367460168894.stgit-mEAvsCHCuLl9qtVHHdszJa2pdiUAq4bhAL8bYrjMMd8@public.gmane.org>
2017-02-06 19:26     ` Jason Gunthorpe
2017-02-06 21:04       ` Christoph Hellwig [this message]
     [not found]         ` <20170206210425.GA2062-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-02-07  9:13           ` Greg KH

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=20170206210425.GA2062@infradead.org \
    --to=hch@infradead.org \
    --cc=dennis.dalessandro@intel.com \
    --cc=dledford@redhat.com \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=ira.weiny@intel.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-kernel@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