ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Li Zefan <lizefan@huawei.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] stable issues
Date: Wed, 07 May 2014 12:31:34 +0900	[thread overview]
Message-ID: <5369A916.4000206@hitachi.com> (raw)
In-Reply-To: <5369A311.2030001@huawei.com>

(2014/05/07 12:05), Li Zefan wrote:
> On 2014/5/7 10:49, Masami Hiramatsu wrote:
>> (2014/05/04 20:19), Li Zefan wrote:
>>> - Testing stable kernels
>>>
>>> The testing of stable kernels when a new version is under review seems
>>> quite limited. We have Dave's Trinity and Fengguang's 0day, but they
>>> are run on mainline/for-next only. Would be useful to also have them
>>> run on stable kernels?
>>
>> This might be a kind of off-topic, but I'm interested in the testing
>> on the linux kernel, especially standard framework of unit-tests
>> for each feature.
>>
>> I see the Trinity and Fengguang's 0day test are useful. But for newer
>> introduced features/bugfixes, would we have a standard tests?
>> (for some subsystems have own selftests, but not unified.)
>>
> 
> I kind of remember Andrew once suggested a new feature can't be accepted
> unless it comes with test cases?

Yeah, that's a good suggestion :)

And I think we should have a unified test framework which can drive
such test cases, and document how to add a test case within
a series of patches. It would be great if we can point out
which feature/commit is broken because of a test-case failure. :)

Thank you,

-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com

  reply	other threads:[~2014-05-07  3:31 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 11:19 Li Zefan
2014-05-04 12:04 ` Guenter Roeck
2014-05-04 12:54 ` Josh Boyer
2014-05-04 14:26   ` Guenter Roeck
2014-05-05  0:37     ` Josh Boyer
2014-05-05  3:09       ` Li Zefan
2014-05-05  3:47       ` Guenter Roeck
2014-05-05 11:31         ` Jason Cooper
2014-05-05 13:40           ` Guenter Roeck
2014-05-05  6:10       ` Michal Simek
2014-05-05  2:47   ` Li Zefan
2014-05-05 13:41     ` Theodore Ts'o
2014-05-05 15:23       ` Takashi Iwai
2014-05-05 15:39         ` Jan Kara
2014-05-05 16:02           ` Takashi Iwai
2014-05-05 16:07             ` Jason Cooper
2014-05-05 16:17               ` Takashi Iwai
2014-05-05 22:33       ` Greg KH
2014-05-06  3:20         ` Steven Rostedt
2014-05-06  4:04           ` Guenter Roeck
2014-05-06 10:49             ` Steven Rostedt
2014-05-05  3:22   ` Greg KH
2014-05-04 15:35 ` Ben Hutchings
2014-05-04 15:45   ` Guenter Roeck
2014-05-05  3:00   ` Li Zefan
2014-05-05  1:03 ` Olof Johansson
2014-05-07  2:49 ` Masami Hiramatsu
2014-05-07  2:58   ` Davidlohr Bueso
2014-05-07  8:27     ` Masami Hiramatsu
2014-05-07  8:39       ` Matt Fleming
2014-05-07 11:45         ` Masami Hiramatsu
2014-05-07 12:45           ` Daniel Vetter
2014-05-08  3:20             ` Masami Hiramatsu
2014-05-09 12:32               ` Daniel Vetter
2014-05-12  6:55                 ` Masami Hiramatsu
2014-05-13 20:36                   ` Steven Rostedt
2014-05-13 20:40                     ` Davidlohr Bueso
2014-05-14  1:30                     ` Masami Hiramatsu
2014-05-07 18:40       ` Davidlohr Bueso
2014-05-07  9:06     ` Dan Carpenter
2014-05-07 14:15       ` Jan Kara
2014-05-08  3:38         ` Li Zefan
2014-05-08  9:41           ` Jan Kara
2014-05-08 20:35             ` Andy Lutomirski
2014-05-09  4:11               ` Greg KH
2014-05-09  5:33                 ` Masami Hiramatsu
2014-05-09  5:41                   ` Greg KH
2014-05-07  3:05   ` Li Zefan
2014-05-07  3:31     ` Masami Hiramatsu [this message]
2014-05-07  7:20     ` Laurent Pinchart
2014-05-13 20:46     ` Steven Rostedt

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=5369A916.4000206@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=lizefan@huawei.com \
    /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