From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: dledford@redhat.com, jgg@mellanox.com, sindhu.devale@intel.com,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
nhorman@redhat.com, sassmann@redhat.com, jogreene@redhat.com,
shiraz.saleem@intel.com
Subject: Re: [net-next] i40iw/i40e: Remove link dependency on i40e
Date: Wed, 23 May 2018 15:00:10 -0400 (EDT) [thread overview]
Message-ID: <20180523.150010.1920539704834947370.davem@davemloft.net> (raw)
In-Reply-To: <20180522203831.20624-1-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Tue, 22 May 2018 13:38:31 -0700
> From: Sindhu Devale <sindhu.devale@intel.com>
>
> Currently i40iw is dependent on i40e symbols
> i40e_register_client and i40e_unregister_client due to
> which i40iw cannot be loaded without i40e being loaded.
>
> This patch allows RDMA driver to build and load without
> linking to LAN driver and without LAN driver being loaded
> first. Once the LAN driver is loaded, the RDMA driver
> is notified through the netdevice notifiers to register
> as client to the LAN driver. Add function pointers to IDC
> register/unregister in the private VSI structure. This
> allows a RDMA driver to build without linking to i40e.
>
> Signed-off-by: Sindhu Devale <sindhu.devale@intel.com>
> Signed-off-by: Shiraz Saleem <shiraz.saleem@intel.com>
> Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
If two drivers depend upon eachother, and a change to one can create
an incompatibility with the other, by definition they must be upgraded
together.
This doesn't even get into recompiling or anything like that, it's a
simple fact of life.
I'm not applying this sorry.
prev parent reply other threads:[~2018-05-23 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 20:38 [net-next] i40iw/i40e: Remove link dependency on i40e Jeff Kirsher
2018-05-22 20:56 ` Jason Gunthorpe
2018-05-22 21:04 ` Jeff Kirsher
2018-05-22 21:33 ` Jason Gunthorpe
2018-05-22 21:50 ` Jeff Kirsher
2018-05-22 21:54 ` Jason Gunthorpe
2018-05-23 6:20 ` Christoph Hellwig
2018-05-23 6:19 ` Christoph Hellwig
2018-05-23 15:03 ` Alexander Duyck
2018-05-23 15:18 ` Jason Gunthorpe
2018-05-23 19:00 ` David Miller [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=20180523.150010.1920539704834947370.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jgg@mellanox.com \
--cc=jogreene@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
--cc=shiraz.saleem@intel.com \
--cc=sindhu.devale@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).