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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 5 Mar 2014 11:15:33 -0800
From:	Casey Leedom <leedom@...lsio.com>
To:	Hariprasad S <hariprasad@...lsio.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-rdma@...r.kernel.org, roland@...estorage.com,
	kumaras@...lsio.com, dm@...lsio.com, swise@...ngridcomputing.com,
	santosh@...lsio.com, nirranjan@...lsio.com
Subject: Re: [PATCHv3 net-next 00/31] Misc. fixes for cxgb4 and iw_cxgb4 

  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.  This has led many of us to defer propagating our out-of-kernel work into the in-kernel driver — partly because of the difficulty and party because of the error prone nature of the effort: there are many symbolic register constants which have the exact same name but have completely different values which has tripped us up at least twice, introducing bugs into the kernel.org driver.  If there’s ever an opportunity to revisit the decision to have us use these different constants we would be Very Excited … :-)

Casey

On Mar 4, 2014, at 9:30 PM, Hariprasad S <hariprasad@...lsio.com> wrote:

> 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 keep your future submissions sizes more reasonable,
>> perhaps ~10 patches or so at most.
>> 
>> Thanks.
> 
> Sure, thanks for the suggestion.
> I will just re-post the revert patch on cxgb4 now, part of this series, which is 
> causing regression.
> And, I will split the rest of patch-series into 8-10 patches and re-submit.
> 
> 
> Thanks for the review comments!
> -Hari.

--
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