[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZOPZL05TY6qSdBDoS6aCj=_uepkZTX5+fVvnHTsCsKKMqgSQ@mail.gmail.com>
Date: Wed, 5 Mar 2014 21:39:20 +0200
From: Or Gerlitz <or.gerlitz@...il.com>
To: Casey Leedom <leedom@...lsio.com>
Cc: Hariprasad S <hariprasad@...lsio.com>,
David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
linux-rdma <linux-rdma@...r.kernel.org>,
Roland Dreier <roland@...estorage.com>, kumaras@...lsio.com,
dm@...lsio.com, Steve Wise <swise@...ngridcomputing.com>,
santosh@...lsio.com, nirranjan@...lsio.com
Subject: Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4
On Wed, Mar 5, 2014 at 9:15 PM, Casey Leedom <leedom@...lsio.com> wrote:
> Yes, thanks mightily for your help and advice and sorry for the size of the updates. Hari has taken on the very difficult task of synchronizing our out-of-kernel development branch with the in-kernel code. These two code bases have drifted apart quite a bit because of the difficulty of translating our out-of-kernel changes into the in-kernel driver which uses completely different symbolic register constants.
Can you explain this in a little bit more details? what's the source
of the need to use two different sets of symbolic register constants?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists