[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaF4UXuiH_4StWZLwhrC8H7Le9rbnRtHYaRLrJ+fQT2_g@mail.gmail.com>
Date: Mon, 18 Jul 2022 11:09:18 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Li Huafei <lihuafei1@...wei.com>
Cc: linux@...linux.org.uk, rmk+kernel@...linux.org.uk, ardb@...nel.org,
will@...nel.org, mark.rutland@....com, broonie@...nel.org,
peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
namhyung@...nel.org, arnd@...db.de, rostedt@...dmis.org,
nick.hawkins@....com, john@...ozen.org, mhiramat@...nel.org,
ast@...nel.org, linyujun809@...wei.com, ndesaulniers@...gle.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH 4/5] ARM: stacktrace: Make stack walk callback consistent
with generic code
On Tue, Jul 12, 2022 at 4:19 AM Li Huafei <lihuafei1@...wei.com> wrote:
> In order to use generic arch_stack_walk() code, make stack walk callback
> consistent with it.
>
> Signed-off-by: Li Huafei <lihuafei1@...wei.com>
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
Yours,
Linus Walleij
Powered by blists - more mailing lists