Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-06 Thread Hariprasad S
On Wed, Mar 05, 2014 at 17:58:19 -0600, Steve Wise wrote: > > > BTW, if you're frustrated from having to send these patches so many > > > times because of changes being requested, this is the main reason > > > why you shouldn't queue up such enormous numbers of patches at one > > > time. > > > > >

RE: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-05 Thread Steve Wise
> > BTW, if you're frustrated from having to send these patches so many > > times because of changes being requested, this is the main reason > > why you shouldn't queue up such enormous numbers of patches at one > > time. > > > > Please try to keep your future submissions sizes more reasonable, >

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-05 Thread Casey Leedom
On Mar 5, 2014, at 11:59 AM, Casey Leedom wrote: > > On Mar 5, 2014, at 11:52 AM, Or Gerlitz wrote: > >> On Wed, Mar 5, 2014 at 9:46 PM, Casey Leedom wrote: >> >> are you referring to constants defined in >> drivers/net/ethernet/chelsio/cxgb4/t4_hw.h or other/more headers? > > t4_regs.h.

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-05 Thread Casey Leedom
On Mar 5, 2014, at 11:52 AM, Or Gerlitz wrote: > On Wed, Mar 5, 2014 at 9:46 PM, Casey Leedom wrote: >> On Mar 5, 2014, at 11:39 AM, Or Gerlitz wrote: >>> On Wed, Mar 5, 2014 at 9:15 PM, Casey Leedom wrote: Yes, thanks mightily for your help and advice and sorry for the size of the

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-05 Thread Or Gerlitz
On Wed, Mar 5, 2014 at 9:46 PM, Casey Leedom wrote: > On Mar 5, 2014, at 11:39 AM, Or Gerlitz wrote: >> On Wed, Mar 5, 2014 at 9:15 PM, Casey Leedom 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

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-05 Thread Casey Leedom
On Mar 5, 2014, at 11:39 AM, Or Gerlitz wrote: > On Wed, Mar 5, 2014 at 9:15 PM, Casey Leedom 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

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-05 Thread Or Gerlitz
On Wed, Mar 5, 2014 at 9:15 PM, Casey Leedom 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

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-05 Thread Casey Leedom
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 trans

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-05 Thread Or Gerlitz
On 04/03/2014 14:41, Hariprasad Shenai wrote: Hariprasad Shenai (1): Revert "cxgb4: Don't assume LSO only uses SGL path in t4_eth_xmit()" Kumar Sanghvi (5): cxgb4: Fix some small bugs in t4_sge_init_soft() when our Page Size is 64KB cxgb4: Add code to dump SGE registers when hittin

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-04 Thread Hariprasad S
On Tue, Mar 04, 2014 at 13:22:26 -0500, David Miller wrote: > > BTW, if you're frustrated from having to send these patches so many > times because of changes being requested, this is the main reason > why you shouldn't queue up such enormous numbers of patches at one > time. > > Please try to ke

Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4

2014-03-04 Thread David Miller
BTW, if you're frustrated from having to send these patches so many times because of changes being requested, this is the main reason why you shouldn't queue up such enormous numbers of patches at one time. Please try to keep your future submissions sizes more reasonable, perhaps ~10 patches or s