Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760750AbcDMNWX (ORCPT ); Wed, 13 Apr 2016 09:22:23 -0400 Received: from mx2.suse.de ([195.135.220.15]:56710 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756725AbcDMNWV (ORCPT ); Wed, 13 Apr 2016 09:22:21 -0400 Date: Wed, 13 Apr 2016 15:22:17 +0200 (CEST) From: Jiri Kosina X-X-Sender: jkosina@pobox.suse.cz To: Miroslav Benes cc: Michael Ellerman , linuxppc-dev@ozlabs.org, bsingharora@gmail.com, duwe@lst.de, 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 In-Reply-To: Message-ID: References: <1460552003-15409-1-git-send-email-mpe@ellerman.id.au> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1207 Lines: 31 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. > > > > 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. > > Hi, > > I'll definitely give it a proper look today or tomorrow, but there is one > thing that needs to be solved. The patch set from Jessica reworking > relocations for live patching is now merged in our for-next branch. This > means that we need to find out if there is something in struct > mod_arch_specific for powerpc which needs to be preserved and do it. Michael, if the plan is still the original one, i.e. you push it to your branch, and I merge it to livepatching (and resolve any dependencies on the relocations code during the merge) and push it to Linus from livepatching.git, then there shouldn't be anything do to on your side. Alternatively, you can rebase on top of livepatching.git#for-next, and I'll take it directly. Thanks, -- Jiri Kosina SUSE Labs