From: Christoph Hellwig <hch@infradead.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Jason Gunthorpe <jgg@mellanox.com>,
davem@davemloft.net, dledford@redhat.com,
Sindhu Devale <sindhu.devale@intel.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
nhorman@redhat.com, sassmann@redhat.com, jogreene@redhat.com,
Shiraz Saleem <shiraz.saleem@intel.com>
Subject: Re: [net-next] i40iw/i40e: Remove link dependency on i40e
Date: Tue, 22 May 2018 23:19:22 -0700 [thread overview]
Message-ID: <20180523061922.GA4753@infradead.org> (raw)
In-Reply-To: <079ceee3bc8cd0ea50dd7ddc12b27512ca5ac49e.camel@intel.com>
On Tue, May 22, 2018 at 02:04:06PM -0700, Jeff Kirsher wrote:
> > Why would you want to do this? The rdma driver is non-functional
> > without the ethernet driver, so why on earth would we want to defeat
> > the module dependency mechanism?
>
> This change is driven by the OSV's like Red Hat, where customer's were
> updating the i40e driver, which in turn broke i40iw.
Doctor it hurts when I do this..
There is no reason to make a mess of our drivers because people are
doing things they should haver never done and that aren't supported
in Linux.
If Intel didn;t offer any out of tree drivers I'm pretty sure no
customer would even attempt this. So fix this where the problem is.
next prev parent reply other threads:[~2018-05-23 6:19 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 [this message]
2018-05-23 15:03 ` Alexander Duyck
2018-05-23 15:18 ` Jason Gunthorpe
2018-05-23 19:00 ` David Miller
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=20180523061922.GA4753@infradead.org \
--to=hch@infradead.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.