From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sihyeon Jang <uneedsihyeon@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH 1/6] perf inject: Document missing options
Date: Thu, 16 Nov 2017 11:35:12 -0300 [thread overview]
Message-ID: <20171116143512.GA12426@kernel.org> (raw)
In-Reply-To: <1510842367-11011-1-git-send-email-uneedsihyeon@gmail.com>
Em Thu, Nov 16, 2017 at 11:26:02PM +0900, Sihyeon Jang escreveu:
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Sihyeon Jang <uneedsihyeon@gmail.com>
Applied 1-6
- Arnaldo
next prev parent reply other threads:[~2017-11-16 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 14:26 [PATCH 1/6] perf inject: Document missing options Sihyeon Jang
2017-11-16 14:26 ` [PATCH 2/6] perf trace: Document missing option, colons Sihyeon Jang
2017-11-18 8:37 ` [tip:perf/core] " tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 3/6] perf timechart: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf timechart: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 4/6] perf sched: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf sched: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 5/6] perf evlist: Document missing option Sihyeon Jang
2017-11-18 8:38 ` [tip:perf/core] perf evlist: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:26 ` [PATCH 6/6] perf buildid-cache: Document missing option Sihyeon Jang
2017-11-18 8:39 ` [tip:perf/core] perf buildid-cache: Document missing --force option tip-bot for Sihyeon Jang
2017-11-16 14:35 ` Arnaldo Carvalho de Melo [this message]
2017-11-18 8:37 ` [tip:perf/core] perf inject: Document missing options tip-bot for Sihyeon Jang
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=20171116143512.GA12426@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=uneedsihyeon@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox