mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Jiri Kosina <jikos@kernel.org>, Torsten Duwe <duwe@lst.de>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: Denis Kirjanov <kda@linux-powerpc.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	live-patching@vger.kernel.org
Subject: Re: [PATCH v4 2/9] ppc64le FTRACE_WITH_REGS implementation
Date: Tue, 19 Jan 2016 10:29:02 +1100	[thread overview]
Message-ID: <1453159742.24878.0.camel@ellerman.id.au> (raw)
In-Reply-To: <alpine.LNX.2.00.1601182321230.21446@cbobk.fhfr.pm>

On Mon, 2016-01-18 at 23:22 +0100, Jiri Kosina wrote:
> On Tue, 5 Jan 2016, Torsten Duwe wrote:
> 
> > > I (still) haven't had a chance to have a good look at it, but I won't this week
> > > anyway. So post v5 and hopefully I can review that and it will be perfect :)
> > 
> > The perfect v5 is there now, for 4 weeks minus the holiday season, and 
> > no further problems arose. Independently verified by Petr Mladek -- 
> > don't forget his high-level fix.
> 
> Hi everybody,
> 
> so what are the current plans with this one, please? Is this going through 
> ppc tree, ftrace tree, or does it have issues that need to be worked on 
> before merging?

Anton and I need to review it and then it will be merged via the powerpc tree.
We just haven't had the spare cycles to do it.

cheers

  reply	other threads:[~2016-01-18 23:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 16:53 [PATCH v4 0/9] ftrace with regs + live patching for ppc64 LE (ABI v2) Torsten Duwe
2015-11-25 16:23 ` [PATCH v4 1/9] ppc64 (le): prepare for -mprofile-kernel Torsten Duwe
2015-11-26 10:12   ` Denis Kirjanov
2015-11-26 12:57     ` Torsten Duwe
2015-11-25 16:34 ` [PATCH v4 2/9] ppc64le FTRACE_WITH_REGS implementation Torsten Duwe
2015-11-26 10:04   ` Denis Kirjanov
2015-11-26 12:59     ` Torsten Duwe
2015-12-01 17:29     ` Torsten Duwe
2015-12-01 22:18       ` Michael Ellerman
2016-01-05 15:58         ` Torsten Duwe
2016-01-18 22:22           ` Jiri Kosina
2016-01-18 23:29             ` Michael Ellerman [this message]
2015-11-25 16:35 ` [PATCH v4 3/9] ppc use ftrace_modify_all_code default Torsten Duwe
2015-11-25 16:37 ` [PATCH v4 4/9] ppc64 ftrace_with_regs configuration variables Torsten Duwe
2015-12-03 16:20   ` Petr Mladek
2015-12-04  9:01     ` Torsten Duwe
2015-11-25 16:39 ` [PATCH v4 5/9] ppc64 ftrace_with_regs: spare early boot and low level Torsten Duwe
2015-11-25 16:41 ` [PATCH v4 6/9] ppc64 ftrace: disable profiling for some functions Torsten Duwe
2015-11-25 16:42 ` [PATCH v4 7/9] ppc64 ftrace: disable profiling for some files Torsten Duwe
2015-11-25 16:48 ` [PATCH v4 8/9] Implement kernel live patching for ppc64le (ABIv2) Torsten Duwe
2015-12-03 16:24   ` Petr Mladek
2015-12-04  9:06     ` Torsten Duwe
2015-11-25 16:49 ` [PATCH v4 9/9] Enable LIVEPATCH to be configured on ppc64le and add livepatch.o if it is selected Torsten Duwe
2015-12-03 16:00 ` [PATCH v4 0/9] ftrace with regs + live patching for ppc64 LE (ABI v2) Petr Mladek

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=1453159742.24878.0.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=duwe@lst.de \
    --cc=jikos@kernel.org \
    --cc=kda@linux-powerpc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=live-patching@vger.kernel.org \
    --cc=rostedt@goodmis.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

Powered by JetHome