Re: [lng-odp] [PATCH] [API-NEXT PATCH v5] api: hash: Added crc32 and crc32c hash functions

2015-10-23 Thread Maxim Uvarov
Somehow that email inside previous version thread it's hard to follow it. I have few notes: 1. version should be remove from long log and put under "---" in email. 2. doxygen: /opt/Linaro/odp2.git/include/odp/api/hash.h:73: warning: argument 'crc_param' of command @param is not found in the

Re: [lng-odp] [PATCH] [API-NEXT PATCH v5] api: hash: Added crc32 and crc32c hash functions

2015-10-23 Thread Savolainen, Petri (Nokia - FI/Espoo)
Ping. Why this has not been merged yet. > -Original Message- > From: Savolainen, Petri (Nokia - FI/Espoo) > Sent: Thursday, October 15, 2015 11:08 AM > To: 'EXT Peng'; lng-odp@lists.linaro.org > Cc: Peng > Subject: RE: [PATCH] [API-NEXT PATCH v5] api: hash: Added crc32 and crc32c > hash

Re: [lng-odp] [PATCH] [API-NEXT PATCH v5] api: hash: Added crc32 and crc32c hash functions

2015-10-23 Thread HePeng
Hi, Maxim > 在 2015年10月23日，下午11:40，Maxim Uvarov 写道： > > Somehow that email inside previous version thread it's hard to follow it. I am having troubles in using git send-email to reply to specific emails, even I’ve tried using —reply-to message-id, the email is sent as

[lng-odp] [PATCH] [API-NEXT PATCH v5] api: hash: Added crc32 and crc32c hash functions

2015-10-15 Thread Peng
From: Peng v2: Add copyright license. v3: APIs: crc32c, crc32 and generic CRC hash impl linux-generic: add impl for crc32c. v4: linux-generic: change odp_crc32c_1word to crc32c_u32, change odp_crc32c_2words to crc32c_u64, drop inline decorator for

Re: [lng-odp] [PATCH] [API-NEXT PATCH v5] api: hash: Added crc32 and crc32c hash functions

2015-10-15 Thread Savolainen, Petri (Nokia - FI/Espoo)
Reviewed-by: Petri Savolainen > -Original Message- > From: EXT Peng [mailto:xnhp0...@icloud.com] > Sent: Thursday, October 15, 2015 10:51 AM > To: lng-odp@lists.linaro.org > Cc: Savolainen, Petri (Nokia - FI/Espoo); Peng > Subject: [PATCH] [API-NEXT PATCH