<?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>5ac79730 - platform: Add test managed platform_device/driver APIs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#5ac79730</link>
        <description>platform: Add test managed platform_device/driver APIsIntroduce KUnit resource wrappers around platform_driver_register(),platform_device_alloc(), and platform_device_add() so that test authorscan register platform drivers/devices from their tests and have thedrivers/devices automatically be unregistered when the test is done.This makes test setup code simpler when a platform driver or platformdevice is needed. Add a few test cases at the same time to make sure theAPIs work as intended.Cc: Brendan Higgins &lt;brendan.higgins@linux.dev&gt;Reviewed-by: David Gow &lt;davidgow@google.com&gt;Cc: Rae Moar &lt;rmoar@google.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Cc: &quot;Rafael J. Wysocki&quot; &lt;rafael@kernel.org&gt;Signed-off-by: Stephen Boyd &lt;sboyd@kernel.org&gt;Link: https://lore.kernel.org/r/20240718210513.3801024-6-sboyd@kernel.org

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Thu, 18 Jul 2024 21:05:04 +0000</pubDate>
        <dc:creator>Stephen Boyd &lt;sboyd@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>51104c19 - kunit: test: Add vm_mmap() allocation resource manager</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#51104c19</link>
        <description>kunit: test: Add vm_mmap() allocation resource managerFor tests that need to allocate using vm_mmap() (e.g. usercopy andexecve), provide the interface to have the allocation tracked by KUnititself. This requires bringing up a placeholder userspace mm.This combines my earlier attempt at this with Mark Rutland&apos;s version[1].Normally alloc_mm() and arch_pick_mmap_layout() aren&apos;t exported formodules, so export these only for KUnit testing.Link: https://lore.kernel.org/lkml/20230321122514.1743889-2-mark.rutland@arm.com/ [1]Co-developed-by: Mark Rutland &lt;mark.rutland@arm.com&gt;Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt;Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Kees Cook &lt;kees@kernel.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Wed, 12 Jun 2024 19:59:18 +0000</pubDate>
        <dc:creator>Kees Cook &lt;kees@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>2c7afc2a - kunit: Cover &apos;assert.c&apos; with tests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#2c7afc2a</link>
        <description>kunit: Cover &apos;assert.c&apos; with testsThere are multiple assertion formatting functions in the `assert.c`file, which are not covered with tests yet. Implement the KUnit testfor these functions.The test consists of 11 test cases for the following functions:1) &apos;is_literal&apos;2) &apos;is_str_literal&apos;3) &apos;kunit_assert_prologue&apos;, test case for multiple assert types4) &apos;kunit_assert_print_msg&apos;5) &apos;kunit_unary_assert_format&apos;6) &apos;kunit_ptr_not_err_assert_format&apos;7) &apos;kunit_binary_assert_format&apos;8) &apos;kunit_binary_ptr_assert_format&apos;9) &apos;kunit_binary_str_assert_format&apos;10) &apos;kunit_assert_hexdump&apos;11) &apos;kunit_mem_assert_format&apos;The test aims at maximizing the branch coverage for the assertionformatting functions.As you can see, it covers some of the static helper functions aswell, so mark the static functions in `assert.c` as &apos;VISIBLE_IF_KUNIT&apos;and conditionally export them with EXPORT_SYMBOL_IF_KUNIT. Add thecorresponding definitions to `assert.h`.Build the assert test when CONFIG_KUNIT_TEST is enabled, similar tohow it is done for the string stream test.Signed-off-by: Ivan Orlov &lt;ivan.orlov0322@gmail.com&gt;Reviewed-by: Rae Moar &lt;rmoar@google.com&gt;Acked-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Thu, 16 May 2024 21:17:31 +0000</pubDate>
        <dc:creator>Ivan Orlov &lt;ivan.orlov0322@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d03c720e - kunit: Add APIs for managing devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#d03c720e</link>
        <description>kunit: Add APIs for managing devicesTests for drivers often require a struct device to pass to otherfunctions. While it&apos;s possible to create these withroot_device_register(), or to use something like a platform device, thisis both a misuse of those APIs, and can be difficult to clean up after,for example, a failed assertion.Add some KUnit-specific functions for registering and unregistering astruct device:- kunit_device_register()- kunit_device_register_with_driver()- kunit_device_unregister()These helpers allocate a on a &apos;kunit&apos; bus which will either probe thedriver passed in (kunit_device_register_with_driver), or will create astub driver (kunit_device_register) which is cleaned up on test shutdown.Devices are automatically unregistered on test shutdown, but can bemanually unregistered earlier with kunit_device_unregister() in orderto, for example, test device release code.Reviewed-by: Matti Vaittinen &lt;mazziesaccount@gmail.com&gt;Reviewed-by: Maxime Ripard &lt;mripard@kernel.org&gt;Signed-off-by: David Gow &lt;davidgow@google.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Fri, 15 Dec 2023 07:39:08 +0000</pubDate>
        <dc:creator>davidgow@google.com &lt;davidgow@google.com&gt;</dc:creator>
    </item>
<item>
        <title>39e92cb1 - kunit: Add test attributes API structure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#39e92cb1</link>
        <description>kunit: Add test attributes API structureAdd the basic structure of the test attribute API to KUnit, which can beused to save and access test associated data.Add attributes.c and attributes.h to hold associated structs and functionsfor the API.Create a struct that holds a variety of associated helper functions foreach test attribute. These helper functions will be used to get theattribute value, convert the value to a string, and filter based on thevalue. This struct is flexible by design to allow for attributes ofnumerous types and contexts.Add a method to print test attributes in the format of &quot;# [&lt;test_name ifnot suite&gt;.]&lt;attribute_name&gt;: &lt;attribute_value&gt;&quot;.Example for a suite: &quot;# speed: slow&quot;Example for a test case: &quot;# test_case.speed: very_slow&quot;Use this method to report attributes in the KTAP output (KTAP spec:https://docs.kernel.org/dev-tools/ktap.html) and _list_tests output whenkernel&apos;s new kunit.action=list_attr option is used. Note this is derivativeof the kunit.action=list option.In test.h, add fields and associated helper functions to test cases andsuites to hold user-inputted test attributes.Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Rae Moar &lt;rmoar@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Tue, 25 Jul 2023 21:25:12 +0000</pubDate>
        <dc:creator>Rae Moar &lt;rmoar@google.com&gt;</dc:creator>
    </item>
<item>
        <title>32ff6831 - kunit: Fix &apos;hooks.o&apos; build by recursing into kunit</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#32ff6831</link>
        <description>kunit: Fix &apos;hooks.o&apos; build by recursing into kunitKUnit&apos;s &apos;hooks.o&apos; file need to be built-in whenever KUnit is enabled(even if CONFIG_KUNIT=m).  We&apos;d previously attemtped to do this byadding &apos;kunit/hooks.o&apos; to obj-y in lib/Makefile, but this caused hooks.cto be rebuilt even when it was unchanged.Instead, always recurse into lib/kunit using obj-y when KUnit isenabled, and add the hooks there.Fixes: 7170b7ed6acb (&quot;kunit: Add &quot;hooks&quot; to call into KUnit when it&apos;s built as a module&quot;).Reported-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Link: https://lore.kernel.org/linux-kselftest/CAHk-=wiEf7irTKwPJ0jTMOF3CS-13UXmF6Fns3wuWpOZ_wGyZQ@mail.gmail.com/Signed-off-by: David Gow &lt;davidgow@google.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Sat, 25 Feb 2023 01:45:30 +0000</pubDate>
        <dc:creator>David Gow &lt;davidgow@google.com&gt;</dc:creator>
    </item>
<item>
        <title>e047c5ea - kunit: Expose &apos;static stub&apos; API to redirect functions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#e047c5ea</link>
        <description>kunit: Expose &apos;static stub&apos; API to redirect functionsAdd a simple way of redirecting calls to functions by including aspecial prologue in the &quot;real&quot; function which checks to see if thereplacement function should be called (and, if so, calls it).To redirect calls to a function, make the first (non-declaration) lineof the function:	KUNIT_STATIC_STUB_REDIRECT(function_name, [function arguments]);(This will compile away to nothing if KUnit is not enabled, otherwise itwill check if a redirection is active, call the replacement function,and return. This check is protected by a static branch, so has verylittle overhead when there are no KUnit tests running.)Calls to the real function can be redirected to a replacement using:	kunit_activate_static_stub(test, real_fn, replacement_fn);The redirection will only affect calls made from within the kthread ofthe current test, and will be automatically disabled when the testcompletes. It can also be manually disabled withkunit_deactivate_static_stub().The &apos;example&apos; KUnit test suite has a more complete example.Co-developed-by: Daniel Latypov &lt;dlatypov@google.com&gt;Signed-off-by: Daniel Latypov &lt;dlatypov@google.com&gt;Signed-off-by: David Gow &lt;davidgow@google.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Tue, 31 Jan 2023 06:46:40 +0000</pubDate>
        <dc:creator>David Gow &lt;davidgow@google.com&gt;</dc:creator>
    </item>
<item>
        <title>7170b7ed - kunit: Add &quot;hooks&quot; to call into KUnit when it&apos;s built as a module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#7170b7ed</link>
        <description>kunit: Add &quot;hooks&quot; to call into KUnit when it&apos;s built as a moduleKUnit has several macros and functions intended for use from non-testcode. These hooks, currently the kunit_get_current_test() andkunit_fail_current_test() macros, didn&apos;t work when CONFIG_KUNIT=m.In order to support this case, the required functions and static dataneed to be available unconditionally, even when KUnit itself is notbuilt-in. The new &apos;hooks.c&apos; file is therefore always included, and hasboth the static key required for kunit_get_current_test(), and a tableof function pointers in struct kunit_hooks_table. This is filled in withthe real implementations by kunit_install_hooks(), which is kept inhooks-impl.h and called when the kunit module is loaded.This can  be extended for future features which require similar&quot;hook&quot; behaviour, such as static stubs, by simply adding new entries tothe struct, and the appropriate code to set them.Fixed white-space errors during commit:Shuah Khan &lt;skhan@linuxfoundation.org&gt;Resolved merge conflicts with:db105c37a4d6 (&quot;kunit: Export kunit_running()&quot;)This patch supersedes the above.Shuah Khan &lt;skhan@linuxfoundation.org&gt;Signed-off-by: David Gow &lt;davidgow@google.com&gt;Reviewed-by: Rae Moar &lt;rmoar@google.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Sat, 28 Jan 2023 07:10:07 +0000</pubDate>
        <dc:creator>David Gow &lt;davidgow@google.com&gt;</dc:creator>
    </item>
<item>
        <title>cdebea69 - kunit: split resource API impl from test.c into new resource.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#cdebea69</link>
        <description>kunit: split resource API impl from test.c into new resource.cWe&apos;ve split out the declarations from include/kunit/test.h intoresource.h.This patch splits out the definitions as well for consistency.A side effect of this is git blame won&apos;t properly track history bydefault, users need to run$ git blame -L ,1 -C13 lib/kunit/resource.cSigned-off-by: Daniel Latypov &lt;dlatypov@google.com&gt;Reviewed-by: David Gow &lt;davidgow@google.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Mon, 28 Mar 2022 17:41:43 +0000</pubDate>
        <dc:creator>Daniel Latypov &lt;dlatypov@google.com&gt;</dc:creator>
    </item>
<item>
        <title>aac35468 - kunit: test: create a single centralized executor for all tests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#aac35468</link>
        <description>kunit: test: create a single centralized executor for all testsAdd a centralized executor to dispatch tests rather than relying onlate_initcall to schedule each test suite separately. Centralizedexecution is for built-in tests only; modules will execute tests whenloaded.Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Co-developed-by: Iurii Zaikin &lt;yzaikin@google.com&gt;Signed-off-by: Iurii Zaikin &lt;yzaikin@google.com&gt;Co-developed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Stephen Boyd &lt;sboyd@kernel.org&gt;Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Tue, 04 Aug 2020 20:47:42 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>b16838c6 - kbuild: trace functions in subdirectories of lib/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#b16838c6</link>
        <description>kbuild: trace functions in subdirectories of lib/ccflags-remove-$(CONFIG_FUNCTION_TRACER) += $(CC_FLAGS_FTRACE)exists here in sub-directories of lib/ to keep the behavior ofcommit 2464a609ded0 (&quot;ftrace: do not trace library functions&quot;).Since that commit, not only the objects in lib/ but also the ones inthe sub-directories are excluded from ftrace (although the commitdescription did not explicitly mention this).However, most of library functions in sub-directories are not so hot.Re-add them to ftrace.Going forward, only the objects right under lib/ will be excluded.Cc: Ingo Molnar &lt;mingo@kernel.org&gt;Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Acked-by: Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Tue, 07 Jul 2020 09:21:17 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>15d5761a - kbuild: introduce ccflags-remove-y and asflags-remove-y</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#15d5761a</link>
        <description>kbuild: introduce ccflags-remove-y and asflags-remove-yCFLAGS_REMOVE_&lt;file&gt;.o filters out flags when compiling a particularobject, but there is no convenient way to do that for every object ina directory.Add ccflags-remove-y and asflags-remove-y to make it easily.Use ccflags-remove-y to clean up some Makefiles.The add/remove order works as follows: [1] KBUILD_CFLAGS specifies compiler flags used globally [2] ccflags-y adds compiler flags for all objects in the     current Makefile [3] ccflags-remove-y removes compiler flags for all objects in the     current Makefile (New feature) [4] CFLAGS_&lt;file&gt; adds compiler flags per file. [5] CFLAGS_REMOVE_&lt;file&gt; removes compiler flags per file.Having [3] before [4] allows us to remove flags from most (but not all)objects in the current Makefile.For example, kernel/trace/Makefile removes $(CC_FLAGS_FTRACE)from all objects in the directory, then adds it back totrace_selftest_dynamic.o and CFLAGS_trace_kprobe_selftest.oThe same applies to lib/livepatch/Makefile.Please note ccflags-remove-y has no effect to the sub-directories.In contrast, the previous notation got rid of compiler flags also fromall the sub-directories.The following are not affected because they have no sub-directories:  arch/arm/boot/compressed/  arch/powerpc/xmon/  arch/sh/  kernel/trace/However, lib/ has several sub-directories.To keep the behavior, I added ccflags-remove-y to all Makefilesin subdirectories of lib/, except the following:  lib/vdso/Makefile        - Kbuild does not descend into this Makefile  lib/raid/test/Makefile   - This is not used for the kernel buildI think commit 2464a609ded0 (&quot;ftrace: do not trace library functions&quot;)excluded too much. In the next commit, I will remove ccflags-remove-yfrom the sub-directories of lib/.Suggested-by: Sami Tolvanen &lt;samitolvanen@google.com&gt;Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Acked-by: Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;Acked-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt; (powerpc)Acked-by: Brendan Higgins &lt;brendanhiggins@google.com&gt; (KUnit)Tested-by: Anders Roxell &lt;anders.roxell@linaro.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Tue, 07 Jul 2020 09:21:16 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>e2219db2 - kunit: add debugfs /sys/kernel/debug/kunit/&lt;suite&gt;/results display</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#e2219db2</link>
        <description>kunit: add debugfs /sys/kernel/debug/kunit/&lt;suite&gt;/results displayadd debugfs support for displaying kunit test suite results; this isespecially useful for module-loaded tests to allow disentangling oftest result display from other dmesg events.  debugfs support isprovided if CONFIG_KUNIT_DEBUGFS=y.As well as printk()ing messages, we append them to a per-test log.Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Frank Rowand &lt;frank.rowand@sony.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Thu, 26 Mar 2020 14:25:07 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>9fe124bf - kunit: allow kunit to be loaded as a module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#9fe124bf</link>
        <description>kunit: allow kunit to be loaded as a moduleMaking kunit itself buildable as a module allows for &quot;always-on&quot;kunit configuration; specifying CONFIG_KUNIT=m means the moduleis built but only used when loaded.  Kunit test modules will loadkunit.ko as an implicit dependency, so simply running&quot;modprobe my-kunit-tests&quot; will load the tests along with the kunitmodule and run them.Co-developed-by: Knut Omang &lt;knut.omang@oracle.com&gt;Signed-off-by: Knut Omang &lt;knut.omang@oracle.com&gt;Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Mon, 06 Jan 2020 22:28:22 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>c475c77d - kunit: allow kunit tests to be loaded as a module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#c475c77d</link>
        <description>kunit: allow kunit tests to be loaded as a moduleAs tests are added to kunit, it will become less feasible to executeall built tests together.  By supporting modular tests we providea simple way to do selective execution on a running system; specifyingCONFIG_KUNIT=yCONFIG_KUNIT_EXAMPLE_TEST=m...means we can simply &quot;insmod example-test.ko&quot; to run the tests.To achieve this we need to do the following:o export the required symbols in kunito string-stream tests utilize non-exported symbols so for now we skip  building them when CONFIG_KUNIT_TEST=m.o drivers/base/power/qos-test.c contains a few unexported interface  references, namely freq_qos_read_value() and freq_constraints_init().  Both of these could be potentially defined as static inline functions  in include/linux/pm_qos.h, but for now we simply avoid supporting  module build for that test suite.o support a new way of declaring test suites.  Because a module cannot  do multiple late_initcall()s, we provide a kunit_test_suites() macro  to declare multiple suites within the same module at once.o some test module names would have been too general (&quot;test-test&quot;  and &quot;example-test&quot; for kunit tests, &quot;inode-test&quot; for ext4 tests);  rename these as appropriate (&quot;kunit-test&quot;, &quot;kunit-example-test&quot;  and &quot;ext4-inode-test&quot; respectively).Also define kunit_test_suite() via kunit_test_suites()as callers in other trees may need the old definition.Co-developed-by: Knut Omang &lt;knut.omang@oracle.com&gt;Signed-off-by: Knut Omang &lt;knut.omang@oracle.com&gt;Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Acked-by: Theodore Ts&apos;o &lt;tytso@mit.edu&gt; # for ext4 bitsAcked-by: David Gow &lt;davidgow@google.com&gt; # For list-testReported-by: kbuild test robot &lt;lkp@intel.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Mon, 06 Jan 2020 22:28:20 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>e4eb117f - kunit: test: add tests for kunit test abort</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#e4eb117f</link>
        <description>kunit: test: add tests for kunit test abortAdd KUnit tests for the KUnit test abort mechanism (see precedingcommit). Add tests both for general try catch mechanism as well asnon-architecture specific mechanism.Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;Reviewed-by: Stephen Boyd &lt;sboyd@kernel.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Mon, 23 Sep 2019 09:02:40 +0000</pubDate>
        <dc:creator>Brendan Higgins &lt;brendanhiggins@google.com&gt;</dc:creator>
    </item>
<item>
        <title>5f3e0620 - kunit: test: add support for test abort</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#5f3e0620</link>
        <description>kunit: test: add support for test abortAdd support for aborting/bailing out of test cases, which is needed forimplementing assertions.An assertion is like an expectation, but bails out of the test caseearly if the assertion is not met. The idea with assertions is that youuse them to state all the preconditions for your test. Logicallyspeaking, these are the premises of the test case, so if a premise isn&apos;ttrue, there is no point in continuing the test case because there are noconclusions that can be drawn without the premises. Whereas, theexpectation is the thing you are trying to prove.Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;Reviewed-by: Stephen Boyd &lt;sboyd@kernel.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Mon, 23 Sep 2019 09:02:39 +0000</pubDate>
        <dc:creator>Brendan Higgins &lt;brendanhiggins@google.com&gt;</dc:creator>
    </item>
<item>
        <title>d8e2a76b - kunit: test: add initial tests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#d8e2a76b</link>
        <description>kunit: test: add initial testsAdd a test for string stream along with a simpler example.Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;Reviewed-by: Stephen Boyd &lt;sboyd@kernel.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Mon, 23 Sep 2019 09:02:37 +0000</pubDate>
        <dc:creator>Brendan Higgins &lt;brendanhiggins@google.com&gt;</dc:creator>
    </item>
<item>
        <title>6b229e59 - kunit: test: add assertion printing library</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#6b229e59</link>
        <description>kunit: test: add assertion printing libraryAdd `struct kunit_assert` and friends which provide a structured way tocapture data from an expectation or an assertion (introduced later inthe series) so that it may be printed out in the event of a failure.Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Stephen Boyd &lt;sboyd@kernel.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Mon, 23 Sep 2019 09:02:34 +0000</pubDate>
        <dc:creator>Brendan Higgins &lt;brendanhiggins@google.com&gt;</dc:creator>
    </item>
<item>
        <title>d1fadef1 - kunit: test: add string_stream a std::stream like string builder</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Makefile#d1fadef1</link>
        <description>kunit: test: add string_stream a std::stream like string builderA number of test features need to do pretty complicated string printingwhere it may not be possible to rely on a single preallocated stringwith parameters.So provide a library for constructing the string as you go similar toC++&apos;s std::string. string_stream is really just a string builder,nothing more.Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;Reviewed-by: Stephen Boyd &lt;swboyd@chromium.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Makefile</description>
        <pubDate>Mon, 23 Sep 2019 09:02:33 +0000</pubDate>
        <dc:creator>Brendan Higgins &lt;brendanhiggins@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
