From: Torsten Duwe <duwe@lst.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
linuxppc-dev@ozlabs.org, bsingharora@gmail.com,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
kamalesh@linux.vnet.ibm.com, pmladek@suse.com, jeyu@redhat.com,
live-patching@vger.kernel.org
Subject: Re: [PATCH 0/5] Live patching for powerpc
Date: Thu, 14 Apr 2016 14:57:35 +0200 [thread overview]
Message-ID: <20160414125735.GA20296@lst.de> (raw)
In-Reply-To: <1460616590.2754.6.camel@ellerman.id.au>
On Thu, Apr 14, 2016 at 04:49:50PM +1000, Michael Ellerman wrote:
> On Wed, 2016-04-13 at 15:22 +0200, Jiri Kosina wrote:
> > On Wed, 13 Apr 2016, Miroslav Benes wrote:
> > > > This series adds live patching support for powerpc (ppc64le only ATM).
> > > >
> > > > It's unchanged since the version I posted on March 24, with the exception that
> > > > I've dropped the first patch, which was a testing-only patch.
Confirmed. And it still works on top of 4.6-rc3, even with the additional testing.
> > > > If there's no further comments I'll put this in a topic branch in the next day
> > > > or two and Jiri & I will both merge that into next.
"Go" from my side.
FTR: then I still have a few ppc64 hunks floating around to support certain consistency
models...
Torsten
next prev parent reply other threads:[~2016-04-14 12:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 12:53 [PATCH 0/5] Live patching for powerpc Michael Ellerman
2016-04-13 12:53 ` [PATCH 1/5] ftrace: Make ftrace_location_range() global Michael Ellerman
2016-04-19 10:16 ` [1/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 2/5] livepatch: Allow architectures to specify an alternate ftrace location Michael Ellerman
2016-04-14 12:01 ` Miroslav Benes
2016-04-14 13:06 ` Michael Ellerman
2016-04-14 14:06 ` Miroslav Benes
2016-04-19 10:16 ` [2/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 3/5] powerpc/livepatch: Add livepatch header Michael Ellerman
2016-04-14 12:18 ` Miroslav Benes
2016-04-14 12:23 ` Miroslav Benes
2016-04-14 13:12 ` Michael Ellerman
2016-04-19 10:16 ` [3/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 4/5] powerpc/livepatch: Add livepatch stack to struct thread_info Michael Ellerman
2016-04-19 10:16 ` [4/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 5/5] powerpc/livepatch: Add live patching support on ppc64le Michael Ellerman
2016-04-19 10:16 ` [5/5] " Michael Ellerman
2016-04-13 13:01 ` [PATCH 0/5] Live patching for powerpc Miroslav Benes
2016-04-13 13:22 ` Jiri Kosina
2016-04-14 6:49 ` Michael Ellerman
2016-04-14 12:57 ` Torsten Duwe [this message]
2016-04-14 13:08 ` Michael Ellerman
2016-04-14 15:20 ` Torsten Duwe
2016-04-14 16:41 ` Josh Poimboeuf
2016-04-15 11:22 ` Michael Ellerman
2016-04-15 12:59 ` Josh Poimboeuf
2016-04-15 13:21 ` Michael Ellerman
2016-04-14 14:34 ` Jiri Kosina
2016-04-15 12:24 ` Michael Ellerman
2016-04-15 15:07 ` Jiri Kosina
2016-04-19 21:42 ` Balbir Singh
2016-04-19 21:52 ` Jiri Kosina
2016-04-13 18:22 ` Jessica Yu
2016-04-14 13:28 ` Miroslav Benes
2016-04-14 19:20 ` Jessica Yu
2016-04-15 8:28 ` Miroslav Benes
2016-04-15 10:01 ` Michael Ellerman
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=20160414125735.GA20296@lst.de \
--to=duwe@lst.de \
--cc=bsingharora@gmail.com \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=pmladek@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).