From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Lukasz Majewski <l.majewski@samsung.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Thomas Abraham <ta.omasab@gmail.com>,
"thomas.ab@samsung.com" <thomas.ab@samsung.com>,
Lukasz Majewski <l.majewski@majess.pl>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Tomasz Figa <t.figa@samsung.com>,
Sachin Kamat <spk.linux@gmail.com>
Subject: Re: [PATCH v2] cpufreq: tests: Providing cpufreq regression test
Date: Thu, 07 Aug 2014 00:50:23 +0200 [thread overview]
Message-ID: <3078797.FIBUCqEiQa@vostro.rjw.lan> (raw)
In-Reply-To: <20140724090402.1f981470@amdc2363>
On Thursday, July 24, 2014 09:04:02 AM Lukasz Majewski wrote:
> Hi Rafael,
>
> > On Monday, July 21, 2014 09:02:34 AM Lukasz Majewski wrote:
> > > This commit adds first regression test "cpufreq_freq_test.sh" for
> > > the cpufreq subsystem.
> >
> > First of all, I'm not seeing any explanation why this script should be
> > shipped with the kernel.
>
> OK.
>
> >
> > What regressions it tests against in particular and
>
> Do you require SHA's/commit messages of commits which were developed to
> fix issues spotted with this test script?
No. I want information about what kind of bugs can be catched with the
help of this script.
> > how it does that.
>
> Is this information required in the commit message or can it stay in
> the README file created in the same commit?
There should be *some* information in the changelog too.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2014-08-06 22:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 10:23 [PATCH] cpufreq: tests: Providing cpufreq regression test Lukasz Majewski
2014-07-18 11:28 ` Sachin Kamat
2014-07-18 11:59 ` Lukasz Majewski
2014-07-22 4:13 ` Sachin Kamat
2014-07-18 11:42 ` Rafael J. Wysocki
2014-07-18 12:00 ` Lukasz Majewski
2014-07-21 7:02 ` [PATCH v2] " Lukasz Majewski
2014-07-23 5:06 ` Viresh Kumar
2014-07-23 7:38 ` Lukasz Majewski
2014-07-23 8:49 ` Viresh Kumar
2014-07-23 10:10 ` Lukasz Majewski
2014-07-23 10:48 ` Viresh Kumar
2014-07-24 10:05 ` Javi Merino
2014-07-23 11:58 ` Rafael J. Wysocki
2014-07-23 15:02 ` Andrew Lunn
2014-07-23 23:58 ` Rafael J. Wysocki
2014-07-24 7:04 ` Lukasz Majewski
2014-08-06 22:50 ` Rafael J. Wysocki [this message]
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=3078797.FIBUCqEiQa@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=cpufreq@vger.kernel.org \
--cc=l.majewski@majess.pl \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=spk.linux@gmail.com \
--cc=t.figa@samsung.com \
--cc=ta.omasab@gmail.com \
--cc=thomas.ab@samsung.com \
--cc=viresh.kumar@linaro.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).