From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Pierre-Hugues Husson <phh@phh.me>, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2 2/3] perf/amlogic: resolve conflict between canvas & pmu
Date: Tue, 28 Mar 2023 13:56:30 +0200 [thread overview]
Message-ID: <02ce8478-6586-e080-c82d-8e709ec9d9d5@free.fr> (raw)
In-Reply-To: <09fbe342-7bf2-fd51-f401-d88e787078a4@linaro.org>
On 27/03/2023 16:12, Neil Armstrong wrote:
> On 27/03/2023 14:09, Marc Gonzalez wrote:
>
> I'll fixup the commit message while applying.
Neil,
I just noticed that patch 3/3 also has the wrong prefix
("perf/amlogic:" in the commit message).
I don't know if that matters?
Regards.
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-03-28 11:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 12:09 [PATCH v2 0/3] Fix G12 PMU conflict Marc Gonzalez
2023-03-27 12:09 ` [PATCH v2 1/3] arm64: dts: meson-g12-common: specify full DMC range Marc Gonzalez
2023-03-27 12:09 ` [PATCH v2 2/3] perf/amlogic: resolve conflict between canvas & pmu Marc Gonzalez
2023-03-27 12:44 ` Marc Gonzalez
2023-03-27 14:12 ` Neil Armstrong
2023-03-28 11:56 ` Marc Gonzalez [this message]
2023-03-27 12:09 ` [PATCH v2 3/3] perf/amlogic: adjust register offsets Marc Gonzalez
2023-03-27 14:17 ` Neil Armstrong
2023-03-27 15:12 ` Will Deacon
2023-03-27 15:27 ` Neil Armstrong
2023-03-27 14:15 ` (subset) [PATCH v2 0/3] Fix G12 PMU conflict Neil Armstrong
2023-03-27 15:25 ` Marc Gonzalez
2023-03-27 15:36 ` Marc Gonzalez
2023-03-27 15:52 ` Marc Gonzalez
2023-03-29 0:01 ` Marc Gonzalez
2023-03-27 15:31 ` (subset) " Neil Armstrong
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=02ce8478-6586-e080-c82d-8e709ec9d9d5@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=phh@phh.me \
/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).