From: Greg KH <gregkh@linuxfoundation.org>
To: Zichar Zhang <zichar.zhang@linaro.org>
Cc: john.stultz@linaro.org, krossmo@google.com, lee.jones@linaro.org,
len.brown@intel.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, nayakvij@google.com, pavel@ucw.cz,
rafael@kernel.org, sumit.semwal@linaro.org,
amit.pundir@linaro.org, kernel-team@android.com
Subject: Re: [PATCH 1/1] [RFC] wakeup_reason: Add infrastructure to log and report why the system resumed from suspend.
Date: Fri, 28 Jan 2022 08:01:33 +0100 [thread overview]
Message-ID: <YfOUzZ4scTZAWnxl@kroah.com> (raw)
In-Reply-To: <20220128045522.3505336-1-zichar.zhang@linaro.org>
On Fri, Jan 28, 2022 at 12:55:22PM +0800, Zichar Zhang wrote:
>
> Signed-off-by: Zichar Zhang <zichar.zhang@linaro.org>
> Change-Id: Id70f3cbec15f24ea999d7f643e9589be9c047f2b
Please always run checkpatch.pl on your submissions so that you do not
get people asking you to run checkpatch.pl on your submissions.
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-28 7:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:49 [RFC] PM: suspend: Upstreaming wakeup reason capture support Kelly Rossmoyer
2022-01-24 17:37 ` John Stultz
2022-01-26 5:09 ` Zichar Zhang
2022-01-28 4:55 ` [PATCH 1/1] [RFC] wakeup_reason: Add infrastructure to log and report why the system resumed from suspend Zichar Zhang
2022-01-28 7:01 ` Greg KH [this message]
2022-01-28 8:43 ` Zichar Zhang
2022-01-28 9:32 ` Lee Jones
2022-01-29 7:52 ` [RFC] PM: suspend: Upstreaming wakeup reason capture support Kelly Rossmoyer
2022-01-27 19:54 ` Rafael J. Wysocki
2022-01-27 20:10 ` Rafael J. Wysocki
2022-01-29 8:26 ` Kelly Rossmoyer
2022-01-30 14:46 ` Rafael J. Wysocki
2022-02-02 7:59 ` Kelly Rossmoyer
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=YfOUzZ4scTZAWnxl@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=krossmo@google.com \
--cc=lee.jones@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nayakvij@google.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=zichar.zhang@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
Powered by JetHome