All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: check.kernel@gmail.com
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Len Brown <len.brown@intel.com>, Ethan du <duhui@xiaomi.com>,
	Linghua Gu <gulinghua@xiaomi.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	yangdongdong <yangdongdong@xiaomi.com>
Subject: Re: [PATCH] power: align wakeup_sources format
Date: Tue, 15 Sep 2015 13:19:15 +0200	[thread overview]
Message-ID: <20150915111915.GB32689@amd> (raw)
In-Reply-To: <1439542767-689-1-git-send-email-check.kernel@gmail.com>

On Fri 2015-08-14 16:59:27, check.kernel@gmail.com wrote:
> From: yangdongdong <yangdongdong@xiaomi.com>
> 
> This aligns every column of elements in wakeup_sources to
> conveniently check any specific column for suspicious power
> consumption wakeup source or for other easily readable purpose.
> 
> Signed-off-by: Dongdong Yang <yangdongdong@xiaomi.com>
> Signed-off-by: Linghua Gu <gulinghua@xiaomi.com>
> ---
>  drivers/base/power/wakeup.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Its debugfs, so format update should be ok.

Acked-by: Pavel Machek <pavel@ucw.cz>

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-09-15 11:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14  8:59 [PATCH] power: align wakeup_sources format check.kernel
2015-09-15 11:19 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-13  2:24 check.kernel
2015-08-14  8:59 ` Rafael J. Wysocki
2015-08-14  8:41   ` 杜慧
2015-08-14  8:41     ` 杜慧
2015-08-12  6:12 check.kernel
2015-08-12 16:20 ` Greg Kroah-Hartman
2015-08-12  4:31 check.kernel
2015-08-12  4:59 ` Greg Kroah-Hartman

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=20150915111915.GB32689@amd \
    --to=pavel@ucw.cz \
    --cc=check.kernel@gmail.com \
    --cc=duhui@xiaomi.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gulinghua@xiaomi.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=yangdongdong@xiaomi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.