[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdZbHwTFbi__5gobypc43OzvgpJ3qL5c9=xLq8KEbVQqdw@mail.gmail.com>
Date: Tue, 25 Sep 2018 21:16:09 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: sdasari@...com
Cc: Joel Stanley <joel@....id.au>, taoren@...com, cov@...com,
Andrew Jeffery <andrew@...id.au>,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] clocksource/drivers/fttmr010: fix set_next_event handler
On Tue, Sep 25, 2018 at 7:13 PM Sai Dasari <sdasari@...com> wrote:
> 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.
tools/time in the kernel tree?
Uh oh there is something familiar there already:
ls tools/time
udelay_test.sh
Yours,
Linus Walleij
Powered by blists - more mailing lists