From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
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 17:15:15 -0300 [thread overview]
Message-ID: <Y6NpUyLRR0f9sQ9C@kernel.org> (raw)
In-Reply-To: <98978f82-eb78-4fa7-901e-76c3070362e3@app.fastmail.com>
Em Fri, Nov 25, 2022 at 02:56:31PM +0100, Arnd Bergmann escreveu:
> On Fri, Nov 25, 2022, at 13:54, Leo Yan wrote:
> > On Fri, Nov 25, 2022 at 12:53:10PM +0100, Vincent Whitchurch wrote:
>
> >> It looks like this patch was never applied? AFAICS it is still needed
> >> on current HEAD and it still applies cleanly.
> >
> > Thanks a lot for bringing up this.
> >
> > Before there have a discussion [1] for refactoring Arm64 system call
> > table but it didn't really happen.
>
> I actually worked on this last week and did a new series to convert
> the old asm-generic/unistd.h header into the syscall.tbl format,
> and change arm64 to use that.
>
> You can find my work in the 'syscall-tbl' branch of my asm-generic
> tree [1]. This has only seen light build testing so far, and is
> probably still buggy, but most of the work is there. The missing
> bits are the Makefiles for the other seven architectures using
> asm-generic/unistd.h, and checking the output to ensure the
> contents are still the same.
>
> > 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?
- Arnaldo
> Arnd
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git/
next prev parent reply other threads:[~2022-12-21 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 2:39 [PATCH] perf arm64: Fix mksyscalltbl, don't lose syscalls due to sort -nu 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 [this message]
2022-12-21 20:21 ` Arnd Bergmann
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=Y6NpUyLRR0f9sQ9C@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnd@arndb.de \
--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;
as well as URLs for NNTP newsgroup(s).