<?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>d0b2dbfa - Remove $FreeBSD$: one-line sh pattern</title>
        <link>http://172.16.0.5:8080/history/freebsd-14.2/lib/libkvm/tests/Makefile#d0b2dbfa</link>
        <description>Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/

            List of files:
            /freebsd-14.2/lib/libkvm/tests/Makefile</description>
        <pubDate>Wed, 16 Aug 2023 17:55:03 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>7cc42f6d - Do a sweep and remove most WARNS=6 settings</title>
        <link>http://172.16.0.5:8080/history/freebsd-14.2/lib/libkvm/tests/Makefile#7cc42f6d</link>
        <description>Do a sweep and remove most WARNS=6 settingsRepeating the default WARNS here makes it slightly more difficult toexperiment with default WARNS changes, e.g. if we did something absolutelybananas and introduced a WARNS=7 and wanted to try lifting the default tothat.Drop most of them; there is one in the blake2 kernel module, but I suspectit should be dropped -- the default WARNS in the rest of the build doesn&apos;tcurrently apply to kernel modules, and I haven&apos;t put too much thought intowhether it makes sense to make it so.

            List of files:
            /freebsd-14.2/lib/libkvm/tests/Makefile</description>
        <pubDate>Thu, 01 Oct 2020 01:10:51 +0000</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>537976d1 - test: add libkvm read test</title>
        <link>http://172.16.0.5:8080/history/freebsd-14.2/lib/libkvm/tests/Makefile#537976d1</link>
        <description>test: add libkvm read testThis test checks if value received from kvm_read is sane, based onvalue returned by sysctl interface.This should catch regression on bug fixed by r359160Reviewed by:	jhbApproved by:	jhibbits (mentor)MFC after:	1 weekSponsored by:	Eldorado Research Institute (eldorado.org.br)Differential Revision:	https://reviews.freebsd.org/D23783

            List of files:
            /freebsd-14.2/lib/libkvm/tests/Makefile</description>
        <pubDate>Wed, 08 Jul 2020 18:58:44 +0000</pubDate>
        <dc:creator>Alfredo Dal&apos;Ava Junior &lt;alfredo@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>10f81a9b - lib/libkvm: start adding basic tests for kvm(3)</title>
        <link>http://172.16.0.5:8080/history/freebsd-14.2/lib/libkvm/tests/Makefile#10f81a9b</link>
        <description>lib/libkvm: start adding basic tests for kvm(3)- kvm_close: add a testcase to verify support for errno = EINVAL / -1  (see D10065) when kd == NULL is provided to the libcall.- kvm_geterr:-- Add a negative testcase for kd == NULL returning &quot;&quot; (see D10022).-- Add two positive testcases:--- test the error case using kvm_write on a O_RDONLY descriptor.--- test the &quot;no error&quot; case using kvm_read(3) and kvm_nlist(3) as    helper routines and by injecting a bogus error message via    _kvm_err (an internal API) _kvm_err was used as there isn&apos;t a    formalized way to clear the error output, and because    kvm_nlist always returns ENOENT with the NULL terminator today.- kvm_open, kvm_open2:-- Add some basic negative tests for kvm_open(3) and kvm_open2(3).   Testing positive cases with a specific   `corefile`/`execfile`/`resolver` requires more work and would require   user intervention today in order to reliably test this out.Reviewed by:	markjMFC after:	2 monthsSponsored by:	Dell EMC IsilonDifferential Revision:	D10024

            List of files:
            /freebsd-14.2/lib/libkvm/tests/Makefile</description>
        <pubDate>Tue, 28 Mar 2017 17:37:49 +0000</pubDate>
        <dc:creator>Enji Cooper &lt;ngie@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
