From: "Arnd Bergmann" <arnd@arndb.de>
To: "Arnaldo Carvalho de Melo" <acme@kernel.org>
Cc: "Leo Yan" <leo.yan@linaro.org>,
"Vincent Whitchurch" <vincent.whitchurch@axis.com>,
"Hans-Peter Nilsson" <hp@axis.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"John Garry" <john.garry@huawei.com>,
"Will Deacon" <will@kernel.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Kim Phillips" <kim.phillips@arm.com>
Subject: Re: [PATCH] perf arm64: Fix mksyscalltbl, don't lose syscalls due to sort -nu
Date: Wed, 21 Dec 2022 21:21:28 +0100 [thread overview]
Message-ID: <50c4ad07-e18f-46ef-a0e4-1bc6a5c2d632@app.fastmail.com> (raw)
In-Reply-To: <Y6NpUyLRR0f9sQ9C@kernel.org>
On Wed, Dec 21, 2022, at 21:15, Arnaldo Carvalho de Melo wrote:
> Em Fri, Nov 25, 2022 at 02:56:31PM +0100, Arnd Bergmann escreveu:
>> On Fri, Nov 25, 2022, at 13:54, Leo Yan wrote:
>> > I think it's the right thing to merge
>> > this patch, @Arnaldo, could you pick up this patch?
>
> So I'm adding the provided:
>
> Reviewed-by: Leo Yan <leo.yan@linaro.org>
> Tested-by: Leo Yan <leo.yan@linaro.org>
>
>
>> That sounds fine to me.
>
> And taking this as an:
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> ok?
Yes, sounds good.
Arnd
prev parent reply other threads:[~2022-12-21 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 2:39 Hans-Peter Nilsson
2020-12-29 3:09 ` Leo Yan
2022-11-25 11:53 ` Vincent Whitchurch
2022-11-25 12:54 ` Leo Yan
2022-11-25 13:56 ` Arnd Bergmann
2022-12-02 18:39 ` Arnaldo Carvalho de Melo
2022-12-12 10:52 ` Leo Yan
2022-12-12 13:42 ` Arnd Bergmann
2022-12-21 20:15 ` Arnaldo Carvalho de Melo
2022-12-21 20:21 ` Arnd Bergmann [this message]
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=50c4ad07-e18f-46ef-a0e4-1bc6a5c2d632@app.fastmail.com \
--to=arnd@arndb.de \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=hp@axis.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=vincent.whitchurch@axis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®