From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] perf script python: Database export fixes
Date: Tue, 25 Sep 2018 11:36:53 -0300 [thread overview]
Message-ID: <20180925143653.GA3541@kernel.org> (raw)
In-Reply-To: <b7a7a61a-9b2b-5f93-9d12-01b52d6034e4@intel.com>
Em Tue, Sep 25, 2018 at 02:08:06PM +0300, Adrian Hunter escreveu:
> On 11/09/18 14:45, Adrian Hunter wrote:
> > Hi
> >
> > Here are a couple of database export fixes.
> >
> >
> > Adrian Hunter (2):
> > perf script python: Fix export-to-postgresql.py occasional failure
> > perf script python: Fix export-to-sqlite.py sample columns
> >
> > tools/perf/scripts/python/export-to-postgresql.py | 9 +++++++++
> > tools/perf/scripts/python/export-to-sqlite.py | 6 +++++-
> > 2 files changed, 14 insertions(+), 1 deletion(-)
>
> Please consider these
Applied to perf/urgent, please consider using the Fixes: tag, so that
the stable guys have a easier time (automatically even) figuring out how
far back the patch should be applied.
Thanks!
- Arnaldo
prev parent reply other threads:[~2018-09-25 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 11:45 [PATCH 0/2] perf script python: Database export fixes Adrian Hunter
2018-09-11 11:45 ` [PATCH 1/2] perf script python: Fix export-to-postgresql.py occasional failure Adrian Hunter
2018-10-05 16:18 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-09-11 11:45 ` [PATCH 2/2] perf script python: Fix export-to-sqlite.py sample columns Adrian Hunter
2018-10-05 16:19 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-09-25 11:08 ` [PATCH 0/2] perf script python: Database export fixes Adrian Hunter
2018-09-25 14:36 ` Arnaldo Carvalho de Melo [this message]
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=20180925143653.GA3541@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.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