From: Todd Brandt <todd.e.brandt@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
todd.e.brandt@intel.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Rafael Wysocki <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v3 0/4] AnalyzeSuspend v4.5
Date: Fri, 10 Feb 2017 16:06:03 -0800 [thread overview]
Message-ID: <1486771563.13784.1.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0hPYRWwjwR=pRcLL1oazvxv40iF6GztGY9kApUBkxGJJQ@mail.gmail.com>
On Thu, 2017-02-09 at 22:42 +0100, Rafael J. Wysocki wrote:
> On Thu, Feb 9, 2017 at 10:27 PM, Todd Brandt
> <todd.e.brandt@linux.intel.com> wrote:
> > This patch series updates the tool from v4.2 to v4.5. The patches
> > can be combined into a single commit for brevity.
> >
> > Todd Brandt (4):
> > AnalyzeSuspend v4.3
> > AnalyzeSuspend v4.4
> > AnalyzeSuspend v4.5
> > AnalyzeSuspend v4.5: fix drag and zoom bug in javascript
> >
> > v2 changes:
> > - added v4.5 fixes since initial upstream attempt
> > v3 changes:
> > - resubmit with fixes to v2 submit errors
> >
> > scripts/analyze_suspend.py | 1933 ++++++++++++++++++++++++++------------------
> > 1 file changed, 1135 insertions(+), 798 deletions(-)
> >
> > --
>
> I applied the previous iteration.
>
> Have patches [1-3/4] changed since then?
Ahh ok, then ignore this then. Nothing changed in patches 1-3/4, there's
just the small addition in 4/4. Thanks.
>
> Thanks,
> Rafael
next prev parent reply other threads:[~2017-02-11 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 21:27 [PATCH v3 0/4] AnalyzeSuspend v4.5 Todd Brandt
2017-02-09 21:27 ` [PATCH v3 1/4] AnalyzeSuspend v4.3 Todd Brandt
2017-02-09 21:27 ` [PATCH v3 2/4] AnalyzeSuspend v4.4 Todd Brandt
2017-02-09 21:27 ` [PATCH v3 3/4] AnalyzeSuspend v4.5 Todd Brandt
2017-02-09 21:27 ` [PATCH v3 4/4] AnalyzeSuspend v4.5: fix drag and zoom bug in javascript Todd Brandt
2017-02-09 21:42 ` [PATCH v3 0/4] AnalyzeSuspend v4.5 Rafael J. Wysocki
2017-02-11 0:06 ` Todd Brandt [this message]
2017-02-13 11:52 ` Rafael J. Wysocki
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=1486771563.13784.1.camel@linux.intel.com \
--to=todd.e.brandt@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=todd.e.brandt@intel.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.