[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191101090801.GB3508@blommer>
Date: Fri, 1 Nov 2019 09:08:01 +0000
From: Mark Rutland <mark.rutland@....com>
To: Torsten Duwe <duwe@...e.de>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
amit.kachhap@....com, catalin.marinas@....com, deller@....de,
James.Bottomley@...senpartnership.com, james.morse@....com,
jeyu@...nel.org, jpoimboe@...hat.com, jthierry@...hat.com,
linux-parisc@...r.kernel.org, mingo@...hat.com,
peterz@...radead.org, rostedt@...dmis.org, svens@...ckframe.org,
takahiro.akashi@...aro.org, will@...nel.org
Subject: Re: [PATCHv2 0/8] arm64: ftrace cleanup + FTRACE_WITH_REGS
On Thu, Oct 31, 2019 at 06:16:41PM +0100, Torsten Duwe wrote:
> After yesterday's testing, now
>
> Reviewed-by: Torsten Duwe <duwe@...e.de>
>
> for the series.
Thanks! I've folded that in and pushed out the updated branch.
Since the only change this time around was only a trivial change in the linker
script, I'll hold off sending a v3. I'm hoping I can get acks for the ftrace,
module, and parisc bits soon...
> Executive summary: where I used x28 as scratch register in ftrace_regs_caller
> which I had to save for that reason, you switched to x10, which is so obvious
> that I failed to see it. Then the PLT initialisation on module load, and
> finally the ftrace_init_nop() hook that got you started initially. The rest
> I'd call more or less cosmetic deviations from my v8. IOW: fine with me.
Yup, that sounds about right. The other thing I did was expand the comments on
the ABI details, as that can be quite subtle, but I guess that's arguably
cosmetic, too.
Thanks for working on this, and for bearing with me on this rework -- I hadn't
intended that to drag on for so long.
Thanks,
Mark.
Powered by blists - more mailing lists