<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>355312bfcd3751f9af17fbefc90373fb8a269614 - so_ver: increase all major versions after SPDK 24.01</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/spdk/lib/ut/Makefile#355312bfcd3751f9af17fbefc90373fb8a269614</link>
        <description>so_ver: increase all major versions after SPDK 24.01To allow SO_MINOR updates on LTS for the whole year it is supported,the major version for all components needs to be increased.This is to prevent scenario where two versions exists with matchingversions, but conflicting ABI.Ex. Next SPDK release adds an API call increasing the minor version,then LTS needs just a subset of those additions.Increasing major so version after LTS, allows the future releasesto update versions as needed. Yet allowing LTS to increase minorversion separately.This patch:- increases SO_VER by 1 for all components- resets SO_MINOR to 0 for all componentsDue to patch below being introduced after v24.01 code freeze,bdev lib version should not be increased:61623c5ca9 bdev: add spdk_bdev_io padding in place of io_submit_chShort reference to how the versions were changed:MAX=$(git grep &quot;SO_VER := &quot; | cut -d&quot; &quot; -f 3 | sort -ubnr | head -1)for((i=$MAX;i&gt;0;i-=1)); do find . -name &quot;Makefile&quot; -exec \	sed -i -e &quot;s/SO_VER := $i\$/SO_VER := $(($i+1))/g&quot; {} +;  donefind . -name &quot;Makefile&quot; -exec \	sed -i -e &quot;s/SO_MINOR := .*/SO_MINOR := 0/g&quot; {} +Signed-off-by: Tomasz Zawadzki &lt;tomasz.zawadzki@intel.com&gt;Change-Id: I0166d6be6c17bbbf985d48b5dfcb36f1d4af1b48Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/21582Reviewed-by: Konrad Sztyber &lt;konrad.sztyber@intel.com&gt;Tested-by: SPDK CI Jenkins &lt;sys_sgci@intel.com&gt;

            List of files:
            /spdk/lib/ut/Makefile</description>
        <pubDate>Fri, 26 Jan 2024 11:19:16 +0000</pubDate>
        <dc:creator>Tomasz Zawadzki &lt;tomasz.zawadzki@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>3c6897d0c303da6539e2cfe17620553aa22167cf - lib: add ut library</title>
        <link>http://src.rcs.uwaterloo.ca:8080/history/spdk/lib/ut/Makefile#3c6897d0c303da6539e2cfe17620553aa22167cf</link>
        <description>lib: add ut libraryThe purpose of this new library is to provide helpers functions forcommon unit test tasks.  In the first iteration, it&apos;ll provide aninterface for running the tests based on the command-line parameters.To use it, the calls to CU_basic_run_tests() need to be replaced withspdk_ut_run_tests().When working on a feature, it&apos;s often useful to run a single test case,as it makes easier to read the logs.  So, the command-line interfaceprovides parameters to select the test case (-t, --test) or test suite(-s, --suite) to execute.  By default, if no arguments are specified,all tests in all test suites are executed.  If there&apos;s only a singletest suite registered (like in most unit tests), users can omit the testsuite argument.Signed-off-by: Konrad Sztyber &lt;konrad.sztyber@intel.com&gt;Change-Id: Ia8fd4bc047e7c6adf21a71215a0fd3d4f06bc834Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/19285Tested-by: SPDK CI Jenkins &lt;sys_sgci@intel.com&gt;Reviewed-by: Aleksey Marchuk &lt;alexeymar@nvidia.com&gt;Reviewed-by: Tomasz Zawadzki &lt;tomasz.zawadzki@intel.com&gt;Community-CI: Mellanox Build Bot

            List of files:
            /spdk/lib/ut/Makefile</description>
        <pubDate>Fri, 28 Jul 2023 08:54:12 +0000</pubDate>
        <dc:creator>Konrad Sztyber &lt;konrad.sztyber@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
