[dpdk-dev] thoughts on DPDK after a few days of reading sources

Wiles, Keith keith.wiles at intel.com
Thu Feb 11 17:29:20 CET 2016


>2016-02-11 11:13, Dave Neary:
>> Hi,
>> 
>> On 02/11/2016 02:58 AM, Thomas Monjalon wrote:
>> > 2016-02-10 19:05, Seth Arnold:
>> > [...]
>> >>   It's nearly impossible to solve issues without error reporting. Good
>> >>   error reporting saves admins time and money.
>> > 
>> > Until now, the errors were reported on the list and most often fixed quickly.
>> > While I agree we need a more formal process (a bug tracker), I think we must
>> > be noticed of new bugs on the mailing list.
>> > Since nobody was against the bugzilla proposal, a deployment will be planned.
>> > 	http://dpdk.org/ml/archives/dev/2015-August/023012.html
>> 
>> I may have misunderstood Seth's comment, but it looked like he was
>> talking about checking errno after fopen and reporting the error with
>> perror or strerror in the event of a non-zero return.
>
>Maybe I misunderstood his comments.
>Anyway, after looking at his list of bugs, it appears that a bug tracker
>would be useful :)

+1 for a bug tracker

I think some of these are reported by Coverity, correct?
>
>
>


Regards,
Keith






More information about the dev mailing list