From: "Arnd Bergmann" <arnd@arndb•de>
To: "Will Deacon" <will@kernel•org>,
"Stephen Rothwell" <sfr@canb•auug.org.au>
Cc: "Olof Johansson" <olof@lixom•net>,
ARM <linux-arm-kernel@lists•infradead.org>,
"Anshuman Khandual" <anshuman.khandual@arm•com>,
"Linus Walleij" <linus.walleij@linaro•org>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
linux-next <linux-next@vger•kernel.org>
Subject: Re: linux-next: manual merge of the arm-soc tree with the arm-perf tree
Date: Wed, 03 Jan 2024 18:38:55 +0100 [thread overview]
Message-ID: <5a6d441a-54bb-42ed-9ab7-3a7f24c8a14b@app.fastmail.com> (raw)
In-Reply-To: <20240103173018.GD5954@willie-the-truck>
On Wed, Jan 3, 2024, at 18:30, Will Deacon wrote:
> On Wed, Jan 03, 2024 at 10:03:24AM +1100, Stephen Rothwell wrote:
>> static int armv6_map_event(struct perf_event *event)
>> {
>> return armpmu_map_event(event, &armv6_perf_map,
>
> Thanks, this looks fine to me (just remove all the 11MPCore code).
>
> Arnd -- anything you need me to do in the perf tree here other than mention
> this in my pull request?
No, I think we're good here as far as I can tell.
Arnd
next prev parent reply other threads:[~2024-01-03 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 23:03 linux-next: manual merge of the arm-soc tree with the arm-perf tree Stephen Rothwell
2024-01-03 17:30 ` Will Deacon
2024-01-03 17:38 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-23 0:33 Stephen Rothwell
2015-03-23 14:41 ` Abhilash Kesavan
2015-03-23 15:13 ` Suzuki K. Poulose
2015-03-23 21:16 ` Stephen Rothwell
2015-03-24 14:59 ` Suzuki K. Poulose
2014-02-21 0:58 Stephen Rothwell
2014-02-21 1:02 ` Olof Johansson
2014-02-21 11:09 ` Will Deacon
2014-02-22 0:46 ` Olof Johansson
2014-02-21 1:02 ` Stephen Boyd
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=5a6d441a-54bb-42ed-9ab7-3a7f24c8a14b@app.fastmail.com \
--to=arnd@arndb$(echo .)de \
--cc=anshuman.khandual@arm$(echo .)com \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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