From: Ionela Voinescu <ionela.voinescu@arm.com>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Vladimir Murzin <vladimir.murzin@arm.com>,
catalin.marinas@arm.com, kbuild-all@01.org, will@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: s/AMEVTYPE/AMEVTYPER
Date: Tue, 21 Jul 2020 15:31:15 +0100 [thread overview]
Message-ID: <20200721143115.GA26722@arm.com> (raw)
In-Reply-To: <jhjsgdlhvyq.mognet@arm.com>
Hi Vladimir,
On Tuesday 21 Jul 2020 at 13:51:57 (+0100), Valentin Schneider wrote:
>
> On 21/07/20 13:28, Mark Rutland wrote:
> > [adding folk to Cc]
> >
> > On Tue, Jul 21, 2020 at 10:12:59AM +0100, Vladimir Murzin wrote:
> >> Activity Monitor Event Type Registers are named as AMEVTYPER{0,1}<n>
> >>
> >> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
> >
> > This matches the ARM ARM, and looks sound to me, so FWIW:
> >
> > Acked-by: Mark Rutland <mark.rutland@arm.com>
> >
>
> That looks fine to me as well.
It looks good to me as well, thank you for correcting this!
Regards,
Ionela.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Ionela Voinescu <ionela.voinescu@arm.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] arm64: s/AMEVTYPE/AMEVTYPER
Date: Tue, 21 Jul 2020 15:31:15 +0100 [thread overview]
Message-ID: <20200721143115.GA26722@arm.com> (raw)
In-Reply-To: <jhjsgdlhvyq.mognet@arm.com>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Hi Vladimir,
On Tuesday 21 Jul 2020 at 13:51:57 (+0100), Valentin Schneider wrote:
>
> On 21/07/20 13:28, Mark Rutland wrote:
> > [adding folk to Cc]
> >
> > On Tue, Jul 21, 2020 at 10:12:59AM +0100, Vladimir Murzin wrote:
> >> Activity Monitor Event Type Registers are named as AMEVTYPER{0,1}<n>
> >>
> >> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
> >
> > This matches the ARM ARM, and looks sound to me, so FWIW:
> >
> > Acked-by: Mark Rutland <mark.rutland@arm.com>
> >
>
> That looks fine to me as well.
It looks good to me as well, thank you for correcting this!
Regards,
Ionela.
next prev parent reply other threads:[~2020-07-21 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 9:12 [PATCH] arm64: s/AMEVTYPE/AMEVTYPER Vladimir Murzin
2020-07-21 9:12 ` Vladimir Murzin
2020-07-21 12:28 ` Mark Rutland
2020-07-21 12:28 ` Mark Rutland
2020-07-21 12:51 ` Valentin Schneider
2020-07-21 12:51 ` Valentin Schneider
2020-07-21 14:31 ` Ionela Voinescu [this message]
2020-07-21 14:31 ` Ionela Voinescu
2020-07-22 17:29 ` Catalin Marinas
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=20200721143115.GA26722@arm.com \
--to=ionela.voinescu@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=valentin.schneider@arm.com \
--cc=vladimir.murzin@arm.com \
--cc=will@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 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.