From: Todd Brandt <todd.e.brandt@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
todd.e.brandt@intel.com
Subject: Re: [PATCH 0/5] scripts: AnalyzeSuspend v4.2
Date: Thu, 14 Jul 2016 14:33:18 -0700 [thread overview]
Message-ID: <1468531998.15887.4.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0gSrwcBC-A-g6Pf_eMJ904zZdRkB591w844bwU6pL8qEQ@mail.gmail.com>
On Thu, 2016-07-14 at 23:22 +0200, Rafael J. Wysocki wrote:
> On Thu, Jul 14, 2016 at 11:09 PM, Todd Brandt
> <todd.e.brandt@linux.intel.com> wrote:
> > AnalyzeSuspend v4.2
> >
> > kprobe support for function tracing
> > config file support in lieu of command line options
> > advanced callgraph support for function debug
> > dev mode for monitoring common sources of delay, e.g. msleep, udelay
> > many bug fixes and formatting upgrades
> >
> > Todd Brandt (5):
> > AnalyzeSuspend v4.2 part1
> > AnalyzeSuspend v4.2 part2
> > AnalyzeSuspend v4.2 part3
> > AnalyzeSuspend v4.2 part4
> > AnalyzeSuspend v4.2 part5
> >
> > scripts/analyze_suspend.py | 3641 ++++++++++++++++++++++++++++++--------------
> > 1 file changed, 2474 insertions(+), 1167 deletions(-)
> >
> > --
>
> Can you please tell me what specifically goes into each of the patches?
It's just a 5 way splitdiff on the original patch, it seems it was too
large to be accepted on the mailing list as a single patch, so I broke
it into 5 ~1000 line pieces. The patch is just meant to upgrade the
kernel analyze_suspend version from 3.0 to 4.2.
Someone suggested that I do a pull request, but I don't want the
analyze_suspend git log included in the kernel git log, so I'm just
describing the changes by version number in the kernel git log.
When you include the patch just set it to be a single commit message.
>
> Thanks,
> Rafael
next prev parent reply other threads:[~2016-07-14 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 21:09 [PATCH 0/5] scripts: AnalyzeSuspend v4.2 Todd Brandt
2016-07-14 21:09 ` [PATCH 1/5] scripts: AnalyzeSuspend v4.2 part1 Todd Brandt
2016-07-14 21:09 ` [PATCH 2/5] scripts: AnalyzeSuspend v4.2 part2 Todd Brandt
2016-07-14 21:09 ` [PATCH 3/5] scripts: AnalyzeSuspend v4.2 part3 Todd Brandt
2016-07-14 21:09 ` [PATCH 4/5] scripts: AnalyzeSuspend v4.2 part4 Todd Brandt
2016-07-14 21:09 ` [PATCH 5/5] scripts: AnalyzeSuspend v4.2 part5 Todd Brandt
2016-07-14 21:22 ` [PATCH 0/5] scripts: AnalyzeSuspend v4.2 Rafael J. Wysocki
2016-07-14 21:33 ` Todd Brandt [this message]
2016-07-14 21:37 ` 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=1468531998.15887.4.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.