From: Jason Gunthorpe <jgg@mellanox.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"dledford@redhat.com" <dledford@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"nhorman@redhat.com" <nhorman@redhat.com>,
"sassmann@redhat.com" <sassmann@redhat.com>,
"mustafa.ismail@intel.com" <mustafa.ismail@intel.com>,
"shiraz.saleem@intel.com" <shiraz.saleem@intel.com>,
"david.m.ertman@intel.com" <david.m.ertman@intel.com>
Subject: Re: [net-next 0/3][pull request] Intel Wired LAN ver Updates 2019-07-03
Date: Thu, 4 Jul 2019 12:15:04 +0000 [thread overview]
Message-ID: <20190704121459.GA3401@mellanox.com> (raw)
In-Reply-To: <20190704021252.15534-1-jeffrey.t.kirsher@intel.com>
On Wed, Jul 03, 2019 at 07:12:49PM -0700, Jeff Kirsher wrote:
> This series contains updates to i40e an ice drivers only and is required
> for a series of changes being submitted to the RDMA maintainer/tree.
> Vice Versa, the Intel RDMA driver patches could not be applied to
> net-next due to dependencies to the changes currently in the for-next
> branch of the rdma git tree.
RDMA driver code is not to be applied to the net-next tree. We've
learned this causes too many work flow problems.
You must co-ordinate your driver with a shared git tree as Mellanox is
doing, or wait for alternating kernel releases.
I'm not sure what to do with this PR, it is far too late in the cycle
to submit a new driver so most likely net should not go ahead with
this prep work until this new driver model scheme is properly
reviewed.
> The following are changes since commit a51df9f8da43e8bf9e508143630849b7d696e053:
> gve: fix -ENOMEM null check on a page allocation
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 100GbE
And if you expect anything to be shared with rdma you need to produce
pull requests that are based on some sensible -rc tag.
Jason
next parent reply other threads:[~2019-07-04 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190704021252.15534-1-jeffrey.t.kirsher@intel.com>
2019-07-04 12:15 ` Jason Gunthorpe [this message]
[not found] ` <20190704021252.15534-2-jeffrey.t.kirsher@intel.com>
2019-07-04 12:16 ` [net-next 1/3] ice: Initialize and register platform device to provide RDMA Jason Gunthorpe
2019-07-04 12:29 ` Greg KH
2019-07-04 12:37 ` Jason Gunthorpe
2019-07-04 12:42 ` Greg KH
2019-07-04 12:48 ` Jason Gunthorpe
2019-07-04 13:46 ` Greg KH
2019-07-04 13:53 ` Jason Gunthorpe
2019-07-05 16:33 ` Saleem, Shiraz
2019-07-06 8:25 ` Greg KH
2019-07-06 16:03 ` Saleem, Shiraz
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=20190704121459.GA3401@mellanox.com \
--to=jgg@mellanox.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=dledford@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
--cc=shiraz.saleem@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