From: John Stultz <john.stultz@linaro.org>
To: Ruchi Kandoi <kandoiruchi@google.com>,
inux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Cc: rjw@rjwysocki.net, ghackmann@google.com, toddpoynor@google.com
Subject: Re: [PATCH v2] power: add an API to log wakeup reasons
Date: Tue, 11 Mar 2014 20:24:52 -0700 [thread overview]
Message-ID: <531FD384.1020700@linaro.org> (raw)
In-Reply-To: <1394589767-16829-1-git-send-email-kandoiruchi@google.com>
On 03/11/2014 07:02 PM, Ruchi Kandoi wrote:
> Add API log_wakeup_reason() and expose it to userspace via sysfs path
> /sys/kernel/wakeup_reasons/last_resume_reason
> This is useful for power management diagnostic purposes.
Thanks for re-submitting!
This commit message is still really too brief, focusing only on what
you're doing and not *why*. You should include some of the rational you
provided in in your earlier reply.
The following template is usually good to follow:
1) The Why: Explanation of a problem (and how it came to be) or
problematic use case to be overcome.
2) The What: Your approach or design to solving the problem, with
details on any tradeoffs, or particular benefits of your solution that
should be noted.
I know it can seem terribly verbose for small patches, but it helps
maintainers and other reviewers get into the right context in order to
understand what your patch does before they look at the code.
thanks
-john
prev parent reply other threads:[~2014-03-12 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 2:02 [PATCH v2] power: add an API to log wakeup reasons Ruchi Kandoi
2014-03-12 3:24 ` John Stultz [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=531FD384.1020700@linaro.org \
--to=john.stultz@linaro.org \
--cc=ghackmann@google.com \
--cc=inux-kernel@vger.kernel.org \
--cc=kandoiruchi@google.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=toddpoynor@google.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;
as well as URLs for NNTP newsgroup(s).