From: Brian Norris <briannorris@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org,
Doug Anderson <dianders@chromium.org>,
Brian Norris <computersforpeace@gmail.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
linux-pm@vger.kernel.org,
Chuansheng Liu <chuansheng.liu@intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 2/2] PM / sleep: don't suspend parent when async child suspend_{noirq,early} fails
Date: Thu, 27 Oct 2016 09:03:07 -0700 [thread overview]
Message-ID: <20161027160306.GA39629@google.com> (raw)
In-Reply-To: <20161027153406.GA3208@kroah.com>
On Thu, Oct 27, 2016 at 05:34:06PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Oct 19, 2016 at 05:46:11PM -0700, Brian Norris wrote:
> > Ugh, as I hope the patch context makes clear, the subject should be
> >
> > s/early/late/
> >
> > as should the body of the commit message.
[...]
> > If the patch is otherwise acceptable, feel free to make the above edits.
> > Or I can fix them up if I send v2.
>
> Please fix up, we should never have to hand-edit a changelog text...
Sorry, I figured it was possible to get review without spamming
everyone. If I was going to need a v2 anyway, for example, then why
bother for a trivial change.
I'll send v2 (of just this patch) shortly.
Thanks,
Brian
next prev parent reply other threads:[~2016-10-27 16:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 0:26 [RESEND PATCH 1/2] PM / sleep: print function name of callbacks Brian Norris
2016-10-20 0:26 ` [PATCH 2/2] PM / sleep: don't suspend parent when async child suspend_{noirq,early} fails Brian Norris
2016-10-20 0:46 ` Brian Norris
2016-10-27 15:34 ` Greg Kroah-Hartman
2016-10-27 16:03 ` Brian Norris [this message]
2016-10-20 0:56 ` Dmitry Torokhov
2016-10-27 16:05 ` [PATCH v2 2/2] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails Brian Norris
2016-11-01 4:25 ` Rafael J. Wysocki
2016-11-01 5:22 ` Brian Norris
2016-11-01 6:04 ` Dmitry Torokhov
2016-11-02 3:51 ` Rafael J. Wysocki
2016-11-02 5:07 ` Brian Norris
2016-11-10 0:08 ` Rafael J. Wysocki
2016-11-10 0:18 ` Brian Norris
2016-11-10 1:21 ` [PATCH v3] " Brian Norris
2016-11-10 1:53 ` Rafael J. Wysocki
2016-11-10 2:00 ` Brian Norris
2016-11-11 1:42 ` Rafael J. Wysocki
2016-10-20 0:52 ` [RESEND PATCH 1/2] PM / sleep: print function name of callbacks Dmitry Torokhov
2016-11-01 4:27 ` Rafael J. Wysocki
2016-11-02 21:02 ` Brian Norris
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=20161027160306.GA39629@google.com \
--to=briannorris@chromium.org \
--cc=chuansheng.liu@intel.com \
--cc=computersforpeace@gmail.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffy.chen@rock-chips.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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).