From: Andrew Morton <akpm@linux-foundation.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Hunter Adrian <adrian.hunter@nokia.com>,
Chris Ball <cjb@laptop.org>,
Andy Shevchenko <ext-andriy.shevchenko@nokia.com>
Subject: Re: [PATCHv6 3/3] mmc_test: collect data and show it via sysfs by demand
Date: Wed, 8 Sep 2010 12:50:17 -0700 [thread overview]
Message-ID: <20100908125017.686ebebd.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTikV4TvwtwQHnb_p9HBsJTV4hVmbpvjKs6MvbYo=@mail.gmail.com>
On Wed, 8 Sep 2010 12:08:58 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Wed, Sep 8, 2010 at 1:27 AM, Andrew Morton <akpm@linux-foundation.org> wrote:
> >> Here is a patch which brings possibility to get test results via sysfs. It
> >> helps to do tests non-interactively.
> >>
> >> We have the file created under sysfs already and we could use it to out test
> >> results.
> >
> > So what we end up with is extremely thin. __Something about adding
> > something to sysfs.
> Yeah, agree with you. How to proceed with commit messages?
> Should I make newer version of this certain patch with updated commit message?
>
I used the words which Chris sent:
: Make it possibile to get test results via sysfs. It helps to do tests
: non-interactively.
:
: We have the file created under sysfs already and we could use it to out test
: results.
:
: Prior to this patch, the "test" file under each card's sysfs node was
: write-only, and results were obtained by looking at dmesg. This patch
: improves programmatic access to the test results, making them available by
: reading back from the same "test" file:
:
: [root@host mmc0:e624]# echo 6 > test
: [root@host mmc0:e624]# cat test
: Test 6: 2
:
: [cjb@laptop.org: changelog improvements]
: Signed-off-by: Andy Shevchenko <ext-andriy.shevchenko@nokia.com>
: Cc: Chris Ball <cjb@laptop.org>
: Cc: <linux-mmc@vger.kernel.org>
which is good enough. You can send me replacement changelog text any
old time - it's not problem. I'm forever editing changelogs, mainly
adding acked-by's etc.
next prev parent reply other threads:[~2010-09-08 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 12:35 [PATCHv6 1/3] mmc_test: use API to check card type Andy Shevchenko
2010-09-07 12:35 ` [PATCHv6 2/3] mmc_test: change simple_strtol() to strict_strtol() Andy Shevchenko
2010-09-07 12:35 ` [PATCHv6 3/3] mmc_test: collect data and show it via sysfs by demand Andy Shevchenko
2010-09-07 22:27 ` Andrew Morton
2010-09-07 22:58 ` Chris Ball
2010-09-08 9:14 ` Andy Shevchenko
2010-09-09 3:59 ` Greg KH
2010-09-09 5:51 ` Andy Shevchenko
2010-09-08 9:08 ` Andy Shevchenko
2010-09-08 19:50 ` Andrew Morton [this message]
2010-09-08 14:44 ` hong zhang
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=20100908125017.686ebebd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adrian.hunter@nokia.com \
--cc=andy.shevchenko@gmail.com \
--cc=cjb@laptop.org \
--cc=ext-andriy.shevchenko@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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