Revision tags: v24.05, v24.09-pre, v24.05-rc1, LTS, v24.01, v24.05-pre, v24.01-rc1, v23.09, v24.01-pre, v23.09-rc1, v23.05, v23.09-pre, v23.01.1, v23.01, v23.05-pre, v23.01-rc1, v22.01.2 |
|
#
a6dbe372 |
| 01-Nov-2022 |
paul luse <paul.e.luse@intel.com> |
update Intel copyright notices
per Intel policy to include file commit date using git cmd below. The policy does not apply to non-Intel (C) notices.
git log --follow -C90% --format=%ad --date defa
update Intel copyright notices
per Intel policy to include file commit date using git cmd below. The policy does not apply to non-Intel (C) notices.
git log --follow -C90% --format=%ad --date default <file> | tail -1
and then pull just the 4 digit year from the result.
Intel copyrights were not added to files where Intel either had no contribution ot the contribution lacked substance (ie license header updates, formatting changes, etc). Contribution date used "--follow -C95%" to get the most accurate date.
Note that several files in this patch didn't end the license/(c) block with a blank comment line so these were added as the vast majority of files do have this last blank line. Simply there for consistency.
Signed-off-by: paul luse <paul.e.luse@intel.com> Change-Id: Id5b7ce4f658fe87132f14139ead58d6e285c04d4 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15192 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Community-CI: Mellanox Build Bot
show more ...
|
Revision tags: v22.09, v23.01-pre, v22.09-rc1 |
|
#
488570eb |
| 03-Jun-2022 |
Jim Harris <james.r.harris@intel.com> |
Replace most BSD 3-clause license text with SPDX identifier.
Many open source projects have moved to using SPDX identifiers to specify license information, reducing the amount of boilerplate code in
Replace most BSD 3-clause license text with SPDX identifier.
Many open source projects have moved to using SPDX identifiers to specify license information, reducing the amount of boilerplate code in every source file. This patch replaces the bulk of SPDK .c, .cpp and Makefiles with the BSD-3-Clause identifier.
Almost all of these files share the exact same license text, and this patch only modifies the files that contain the most common license text. There can be slight variations because the third clause contains company names - most say "Intel Corporation", but there are instances for Nvidia, Samsung, Eideticom and even "the copyright holder".
Used a bash script to automate replacement of the license text with SPDX identifier which is checked into scripts/spdx.sh.
Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Iaa88ab5e92ea471691dc298cfe41ebfb5d169780 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12904 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Dong Yi <dongx.yi@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: <qun.wan@intel.com>
show more ...
|
Revision tags: v22.05, v22.09-pre, v22.05-rc1, v22.01.1, v22.01, v22.01-rc1, v21.10, v21.10-rc1, v21.07, v21.07-rc1, v21.04, v21.04-rc1, v21.01.1, v21.01, v21.01-rc1, v20.10, v20.10-rc1, v20.07, v20.07-rc1, v20.04.1, v20.01.2, v20.04, v20.04-rc1, v20.01.1, v20.01, v20.01-rc1, v19.10.1, v19.10, v19.10-rc1, v19.07.1, v19.07, v19.04.1, v19.04, v18.10.2, v19.01.1, v19.01, v18.10.1, v18.10, v18.07.1, v18.07, v18.04.1, v18.04, v18.01.1, v18.01 |
|
#
7d716668 |
| 31-Jan-2018 |
Daniel Verkamp <daniel.verkamp@intel.com> |
utf.h: remove #include "spdk/json.h"
After the renaming of json_internal.h to utf.h, it doesn't make sense for utf.h to include spdk/json.h.
Move the #include "spdk/json.h" to the JSON library impl
utf.h: remove #include "spdk/json.h"
After the renaming of json_internal.h to utf.h, it doesn't make sense for utf.h to include spdk/json.h.
Move the #include "spdk/json.h" to the JSON library implementation files and remove it from utf.h.
Change-Id: I36092524c9b982fd2e931faf1b7c5d1d6a6c80c0 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/397603 Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: <shuhei.matsumoto.xt@hitachi.com>
show more ...
|
#
0a97bd14 |
| 09-Jan-2018 |
Seth Howell <seth.howell@intel.com> |
json_internal.h: rename to utf.h and place in spdk_internal
Change-Id: I1b1f3a6c10b97c6323e52b58537293f6a6c5c56b Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrit
json_internal.h: rename to utf.h and place in spdk_internal
Change-Id: I1b1f3a6c10b97c6323e52b58537293f6a6c5c56b Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/394117 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
show more ...
|
#
59970a89 |
| 07-Dec-2017 |
Daniel Verkamp <daniel.verkamp@intel.com> |
astyle: enforce braces around single-line statements
Require braces around all conditional statements, e.g.:
if (cond) statement();
becomes:
if (cond) { statement(); }
astyle: enforce braces around single-line statements
Require braces around all conditional statements, e.g.:
if (cond) statement();
becomes:
if (cond) { statement(); }
This is the style used through most of the SPDK code, but several exceptions crept in over time. Add the astyle option to make sure we are consistent.
Change-Id: I5a71980147fe8dfb471ff42e8bc06db2124a1a7f Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/390914 Reviewed-by: <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
show more ...
|
Revision tags: v17.10.1, v17.10, v17.07.1, v17.07, v17.03 |
|
#
d6fd64cd |
| 03-Jan-2017 |
Daniel Verkamp <daniel.verkamp@intel.com> |
json: make sure parse always sets *end
Funnel all of the return paths in the main parsing routine through the code that sets the *end pointer so that all error cases set it.
Change-Id: I0565913f7b9
json: make sure parse always sets *end
Funnel all of the return paths in the main parsing routine through the code that sets the *end pointer so that all error cases set it.
Change-Id: I0565913f7b9488470ede79dc1af84eb4b9a03225 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
show more ...
|
Revision tags: v16.12 |
|
#
38c09e5e |
| 19-Dec-2016 |
Daniel Verkamp <daniel.verkamp@intel.com> |
json/parse: rewrite and simplify number parsing
Convert the number parsing function into a linear sequence with a goto label for each state, rather than a single loop with a state variable.
This ma
json/parse: rewrite and simplify number parsing
Convert the number parsing function into a linear sequence with a goto label for each state, rather than a single loop with a state variable.
This makes the code easier to read and also improves speed (better branch prediction and smaller inner loops for the common case).
On my test system, jsoncat citylots.json > /dev/null improves from ~1.7s to ~1.2s.
This changes behavior of some number parsing test cases: inputs matching the number grammar as defined by JSON will be returned even if there is trailing garbage, consistent with the rest of the parser. For example, the input 01 will be parsed as a valid number 0 followed by trailing 1. This only makes any difference when the full input is a single number value, since if the value was nested in an object or array, the trailing garbage will not match the expected syntax and the whole parse will fail with SPDK_JSON_PARSE_INVALID (e.g. [00 will parse the first 0 as a number and then fail on the second 0, since only a comma or right square bracket would be accepted).
Change-Id: Ifabfaed611219b3e0a06c8677190a28b87e8a13b Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
show more ...
|
#
69c7ff06 |
| 17-Aug-2016 |
Daniel Verkamp <daniel.verkamp@intel.com> |
json: allow decoding of non-standard comments
Comments are not allowed in the JSON RFC, but some JSON libraries accept JavaScript-style comments.
Add a flag that enables non-spec-compliant comment
json: allow decoding of non-standard comments
Comments are not allowed in the JSON RFC, but some JSON libraries accept JavaScript-style comments.
Add a flag that enables non-spec-compliant comment parsing.
Change-Id: I9dfb66bb46ecff1a22d8af5a9c50620686a4707c Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
show more ...
|
Revision tags: v16.08, v16.06 |
|
#
f9193f4c |
| 09-May-2016 |
Daniel Verkamp <daniel.verkamp@intel.com> |
json: add JSON parser and encoder libraries
Change-Id: Id73fb7e300d66d31a7c3986c0334b6f56e284905 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
|