From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: mark.rutland@arm.com, irogers@google.com, peterz@infradead.org,
kjain@linux.ibm.com, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, alexander.shishkin@linux.intel.com,
yao.jin@linux.intel.com, mingo@redhat.com,
linux-arm-kernel@lists.infradead.org, namhyung@kernel.org,
Jiri Olsa <jolsa@redhat.com>,
yeyunfeng@huawei.com
Subject: Re: [PATCH] perf jevents: Fix event code for events referencing std arch events
Date: Thu, 15 Oct 2020 09:25:22 -0300 [thread overview]
Message-ID: <20201015122522.GA2896742@kernel.org> (raw)
In-Reply-To: <fa6351ab-4d2d-8de7-96e1-102d6fa0dd50@huawei.com>
Em Wed, Oct 14, 2020 at 06:46:12PM +0100, John Garry escreveu:
> On 14/10/2020 17:49, Arnaldo Carvalho de Melo wrote:
> > Ok, applied,
>
> Thanks
>
> > please consider adding a Fixes tag next time.
> >
>
> Can do if it helps, but I only thought it appropriate when fixing something
> merged to mainline.
Please do, I think it appropriate in all cases, people doing backports
may decide to pick something and if it has some subtle issue this can be
automatically checked for by looking at any later Fixes for that
specific cset.
I decided not to do any rebase on perf/core, so those Fixes will remain
valid.
- Arnaldo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-15 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1602170368-11892-1-git-send-email-john.garry@huawei.com>
[not found] ` <a7cbb1f7-1f7f-6bf9-6acf-fd5455aadd82@linux.ibm.com>
2020-10-09 11:38 ` [PATCH] perf jevents: Fix event code for events referencing std arch events John Garry
[not found] ` <20201012105430.GH1099489@krava>
[not found] ` <5b0aefe2-e0d5-b5ff-654c-4e93c427050f@huawei.com>
[not found] ` <20201012112419.GJ1099489@krava>
2020-10-13 8:41 ` John Garry
[not found] ` <20201014164905.GN3100363@kernel.org>
[not found] ` <fa6351ab-4d2d-8de7-96e1-102d6fa0dd50@huawei.com>
2020-10-15 12:25 ` Arnaldo Carvalho de Melo [this message]
2020-10-15 15:42 ` John Garry
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=20201015122522.GA2896742@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=kjain@linux.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.com \
--cc=yeyunfeng@huawei.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;
as well as URLs for NNTP newsgroup(s).