linux-kernel - Re: [PATCH] clocksource/drivers/fttmr010: fix set_next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <571BD9E6-5A5B-4B66-AFAB-EC4E97B0A0D7@fb.com>
Date:   Tue, 25 Sep 2018 17:13:01 +0000
From:   Sai Dasari <sdasari@...com>
To:     Joel Stanley <joel@....id.au>, Tao Ren <taoren@...com>
CC:     Christopher Covington <cov@...com>,
        Andrew Jeffery <andrew@...id.au>,
        OpenBMC Maillist <openbmc@...ts.ozlabs.org>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        "Linus Walleij" <linus.walleij@...aro.org>
Subject: Re: [PATCH] clocksource/drivers/fttmr010: fix set_next_event handler


On 9/24/18, 4:21 PM, "openbmc on behalf of Joel Stanley" <openbmc-bounces+sdasari=fb.com@...ts.ozlabs.org on behalf of joel@....id.au> wrote:

    I will then add it to the set of tests I run when testing aspeed
    kernels.
    
Thanks Joel! Curious to know what would be the best place to keep these kind of Kernel test cases for sake of review and/or adding new test cases as needed.