[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMgE1-EuNBmYVfLoBwjohcxt5tio6wtZn=TYvDAgQgh9cw@mail.gmail.com>
Date: Thu, 21 Jan 2016 20:40:53 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: Faisal Latif <faisal.latif@...el.com>
Cc: Or Gerlitz <ogerlitz@...lanox.com>,
Steve Wise <swise@...ngridcomputing.com>,
Doug Ledford <dledford@...hat.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
Linux Netdev List <netdev@...r.kernel.org>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
e1000-rdma@...ts.sourceforge.net
Subject: Re: [PATCH v3 00/16] add Intel X722 iWARP driver
On Thu, Jan 21, 2016 at 8:24 PM, Faisal Latif <faisal.latif@...el.com> wrote:
> We can certainly take up the discussion on improving the current port mapper design/implementation. But
> that would be more appropriate in a separate thread.
If we observe a kernel API / mechanism which could be wrongly
duplicated between two drivers, and now a new driver comes to town
with C&P-ing this -- why not stopping and thinking before rushing to
get the 3rd duplication upstream?
Powered by blists - more mailing lists