linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Torsten Duwe <duwe@lst.de>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Julien Thierry <julien.thierry@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Will Deacon <will.deacon@arm.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Ingo Molnar <mingo@redhat.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	live-patching@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/5] arm64: ftrace with regs
Date: Mon, 8 Apr 2019 16:36:28 +0100	[thread overview]
Message-ID: <20190408153628.GL6139@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20190311114945.GA5625@lst.de>

On Mon, Mar 11, 2019 at 12:49:46PM +0100, Torsten Duwe wrote:
> On Wed, Feb 13, 2019 at 11:11:04AM +0000, Julien Thierry wrote:
> > Hi Torsten,
> > 
> > On 08/02/2019 15:08, Torsten Duwe wrote:
> > > Patch series v8, as discussed.
> > > The whole series applies cleanly on 5.0-rc5
> 
> So what's the status now? Besides debatable minor style
> issues there were no more objections to v8. Would this
> go through the ARM repo or via the ftrace repo?

Sorry agains for the delay on this. I'm now back in the office and in
front of a computer daily, so I can spend a bit more time on this.

Regardless of anything else, I think that we should queue the first
three patches now. I've poked the relevant maintainers for their acks so
that those can be taken via the arm64 tree.

I'm happy to do the trivial cleanups on the last couple of patches (e.g.
s/lr/x30), and I'm actively looking at the API rework I requested.

Thanks,
Mark.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-04-08 15:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 15:08 [PATCH v8 0/5] arm64: ftrace with regs Torsten Duwe
2019-02-08 15:10 ` [PATCH v8 1/5] arm64: replace -pg with CC_FLAGS_FTRACE in arm64 Makefiles Torsten Duwe
2019-02-11 11:53   ` Mark Rutland
2019-02-08 15:10 ` [PATCH v8 2/5] arm64: replace -pg with CC_FLAGS_FTRACE in efi Makefiles Torsten Duwe
2019-02-11 11:59   ` Mark Rutland
2019-04-08 15:23   ` Mark Rutland
2019-04-08 20:49     ` Ard Biesheuvel
2019-02-08 15:10 ` [PATCH v8 3/5] arm64: replace -pg with CC_FLAGS_FTRACE in mm/kasan Makefile Torsten Duwe
2019-02-11 11:55   ` Mark Rutland
2019-02-11 11:56   ` Mark Rutland
2019-04-08 15:25   ` Mark Rutland
2019-04-08 15:35   ` Andrey Ryabinin
2019-02-08 15:10 ` [PATCH v8 4/5] arm64: implement ftrace with regs Torsten Duwe
2019-02-13 10:30   ` Julien Thierry
2019-02-08 15:10 ` [PATCH v8 5/5] arm64: use -fpatchable-function-entry if available Torsten Duwe
2019-02-13 11:11 ` [PATCH v8 0/5] arm64: ftrace with regs Julien Thierry
2019-03-11 11:49   ` Torsten Duwe
2019-03-11 12:18     ` Mark Rutland
2019-03-29 10:18       ` Torsten Duwe
2019-04-08 15:36     ` Mark Rutland [this message]
2019-04-09 17:52       ` Will Deacon
2019-07-10 12:27         ` Ruslan Bilovol
2019-07-24 16:15           ` Mark Rutland
2019-10-16 11:42             ` Jiri Kosina
2019-10-16 17:58               ` Mark Rutland
2019-10-18 17:41                 ` Mark Rutland
2019-10-19 11:01                   ` Torsten Duwe
2019-10-21 11:37                     ` Mark Rutland
2019-10-21 13:20                     ` Josh Poimboeuf

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=20190408153628.GL6139@lakrids.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=amit.kachhap@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=duwe@lst.de \
    --cc=jpoimboe@redhat.com \
    --cc=julien.thierry@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=will.deacon@arm.com \
    /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).