linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sai Dasari <sdasari@fb.com>
To: Joel Stanley <joel@jms.id.au>, Tao Ren <taoren@fb.com>
Cc: Christopher Covington <cov@fb.com>,
	Andrew Jeffery <andrew@aj.id.au>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [PATCH] clocksource/drivers/fttmr010: fix set_next_event handler
Date: Tue, 25 Sep 2018 17:13:01 +0000	[thread overview]
Message-ID: <571BD9E6-5A5B-4B66-AFAB-EC4E97B0A0D7@fb.com> (raw)
In-Reply-To: <CACPK8Xd03w51FM8iJsFNhWkpRFMhy97XZpxOhbRwbD3ytQcRbg@mail.gmail.com>


On 9/24/18, 4:21 PM, "openbmc on behalf of Joel Stanley" <openbmc-bounces+sdasari=fb.com@lists.ozlabs.org on behalf of joel@jms.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.     


  parent reply	other threads:[~2018-09-25 17:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 22:13 [PATCH] clocksource/drivers/fttmr010: fix set_next_event handler Tao Ren
2018-09-19 23:16 ` Daniel Lezcano
2018-09-20 15:45 ` Linus Walleij
2018-09-20 21:09   ` Tao Ren
2018-09-21  3:32     ` Joel Stanley
2018-09-21  6:22       ` Lei YU
2018-09-21 18:11         ` Tao Ren
2018-09-21 18:11       ` Tao Ren
2018-09-24 23:20         ` Joel Stanley
2018-09-25  0:40           ` Tao Ren
2018-09-25 17:13           ` Sai Dasari [this message]
2018-09-25 19:16             ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=571BD9E6-5A5B-4B66-AFAB-EC4E97B0A0D7@fb.com \
    --to=sdasari@fb.com \
    --cc=andrew@aj.id.au \
    --cc=cov@fb.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=joel@jms.id.au \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=taoren@fb.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).