From: Jason Gunthorpe <jgg@ziepe.ca>
To: Andrew Boyer <aboyer@pensando.io>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: linux-rdma@vger.kernel.org, Allen Hubbe <allenbh@pensando.io>,
Leon Romanovsky <leonro@mellanox.com>,
Doug Ledford <dledford@redhat.com>
Subject: Re: Which print functions to use during early device create?
Date: Fri, 14 Feb 2020 20:11:30 -0400 [thread overview]
Message-ID: <20200215001130.GB31668@ziepe.ca> (raw)
In-Reply-To: <7A6D8934-9D25-4BDF-BCBA-B37CAA064677@pensando.io>
On Fri, Feb 14, 2020 at 05:23:29PM -0500, Andrew Boyer wrote:
> When we get a NETDEV_REGISTER event, we get a pointer to the
> existing struct netdev. If all goes well, we end up creating an
> associated struct ib_device.
New rdma drivers cannot use the hacky NETDEV_REGISTER to bind to
netdevs.
Jeff & co are working on 'virtual bus' to provide the right kind of
binding for multi-function PCI devices:
https://patchwork.kernel.org/project/linux-rdma/list/?series=240585
You should probably strike a deal to review their driver if they
review yours :)
Jason
prev parent reply other threads:[~2020-02-15 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 22:23 Which print functions to use during early device create? Andrew Boyer
2020-02-15 0:11 ` 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=20200215001130.GB31668@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=aboyer@pensando.io \
--cc=allenbh@pensando.io \
--cc=dledford@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).