All of lore.kernel.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 7/7] arm64/perf: Add Broadcom Vulcan PMU support
Date: Thu, 21 Apr 2016 14:54:50 +0100	[thread overview]
Message-ID: <20160421135450.GO6879@leverpostej> (raw)
In-Reply-To: <1461243525-13603-8-git-send-email-ashoks@broadcom.com>

On Thu, Apr 21, 2016 at 05:58:45AM -0700, Ashok Kumar wrote:
> +static int armv8_vulcan_pmu_init(struct arm_pmu *cpu_pmu)
> +{
> +	armv8_pmu_init(cpu_pmu);
> +	cpu_pmu->name			= "armv8_brcm_vulcan";

Are we happy with "brcm" being the exposed userspace name? It might be
better to have this as "armv8_broadcom_vulcan".

I'll leave that to you and Will. Either way:

Acked-by: Mark Rutland <mark.rutland@arm.com>

Thanks,
Mark.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Ashok Kumar <ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	will.deacon-5wv7dgnIgG8@public.gmane.org,
	Suzuki.Poulose-5wv7dgnIgG8@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	catalin.marinas-5wv7dgnIgG8@public.gmane.org,
	jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
	jglauber-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH v6 7/7] arm64/perf: Add Broadcom Vulcan PMU support
Date: Thu, 21 Apr 2016 14:54:50 +0100	[thread overview]
Message-ID: <20160421135450.GO6879@leverpostej> (raw)
In-Reply-To: <1461243525-13603-8-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>

On Thu, Apr 21, 2016 at 05:58:45AM -0700, Ashok Kumar wrote:
> +static int armv8_vulcan_pmu_init(struct arm_pmu *cpu_pmu)
> +{
> +	armv8_pmu_init(cpu_pmu);
> +	cpu_pmu->name			= "armv8_brcm_vulcan";

Are we happy with "brcm" being the exposed userspace name? It might be
better to have this as "armv8_broadcom_vulcan".

I'll leave that to you and Will. Either way:

Acked-by: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>

Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-04-21 13:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 12:58 [PATCH v6 0/7] arm64: perf: Broadcom Vulcan PMU support Ashok Kumar
2016-04-21 12:58 ` Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 1/7] Documentation: arm64: pmu: Add Broadcom Vulcan PMU binding Ashok Kumar
2016-04-21 12:58   ` Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 2/7] arm64: dts: Add Broadcom Vulcan PMU in dts Ashok Kumar
2016-04-21 12:58   ` Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 3/7] arm64/perf: Changed events naming as per the ARM ARM Ashok Kumar
2016-04-21 12:58   ` Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 4/7] arm64/perf: Define complete ARMv8 recommended implementation defined events Ashok Kumar
2016-04-21 12:58   ` Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 5/7] arm64/perf: Access pmu register using <read/write>_sys_reg Ashok Kumar
2016-04-21 12:58   ` Ashok Kumar
2016-04-25 13:06   ` Will Deacon
2016-04-25 13:06     ` Will Deacon
2016-04-25 13:12     ` Will Deacon
2016-04-25 13:12       ` Will Deacon
2016-04-21 12:58 ` [PATCH v6 6/7] arm64/perf: Filter common events based on PMCEIDn_EL0 Ashok Kumar
2016-04-21 12:58   ` Ashok Kumar
2016-04-21 13:49   ` Mark Rutland
2016-04-21 13:49     ` Mark Rutland
2016-04-21 12:58 ` [PATCH v6 7/7] arm64/perf: Add Broadcom Vulcan PMU support Ashok Kumar
2016-04-21 12:58   ` Ashok Kumar
2016-04-21 13:54   ` Mark Rutland [this message]
2016-04-21 13:54     ` Mark Rutland
2016-04-22 11:19     ` Jayachandran C
2016-04-22 11:19       ` Jayachandran C

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=20160421135450.GO6879@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.