From: Andi Kleen <ak@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: Please pull Intel JSON event files updates
Date: Thu, 30 Mar 2017 13:21:30 -0700 [thread overview]
Message-ID: <20170330202130.GD4543@tassilo.jf.intel.com> (raw)
In-Reply-To: <20170330114948.GA17009@kernel.org>
> commit b0ad8ea66445d64a469df0c710947f4cdb8ef16b
> Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> Date: Mon Mar 27 11:47:20 2017 -0300
>
> perf tools: Remove unused 'prefix' from builtin functions
>
> Has:
>
> Link: http://lkml.kernel.org/n/tip-uw5swz05vol0qpr32c5lpvus@git.kernel.org
>
> Which works.
The link is the git commit id? I don't see how I can put that into
the commit log, because changing the commit log changes the commit
id too.
I added all the other suggestions.
-Andi
prev parent reply other threads:[~2017-03-30 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 0:43 Please pull Intel JSON event files updates Andi Kleen
2017-03-30 11:49 ` Arnaldo Carvalho de Melo
2017-03-30 20:21 ` Andi Kleen [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=20170330202130.GD4543@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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