From: Michael Ellerman <mpe@ellerman.id.au>
To: Jiri Kosina <jikos@kernel.org>
Cc: linuxppc-dev@ozlabs.org, pmladek@suse.com, jeyu@redhat.com,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
kamalesh@linux.vnet.ibm.com, duwe@lst.de,
live-patching@vger.kernel.org, mbenes@suse.cz
Subject: Re: [v3,1/8] powerpc: Create a helper for getting the kernel toc value
Date: Wed, 16 Mar 2016 21:23:19 +1100 [thread overview]
Message-ID: <1458123799.27361.3.camel@ellerman.id.au> (raw)
In-Reply-To: <alpine.LNX.2.00.1603150220231.3656@cbobk.fhfr.pm>
On Tue, 2016-03-15 at 02:27 +0100, Jiri Kosina wrote:
> On Mon, 14 Mar 2016, Michael Ellerman wrote:
>
> > > Move the logic to work out the kernel toc pointer into a header. This is
> > > a good cleanup, and also means we can use it elsewhere in future.
> > >
> > > Reviewed-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
> > > Reviewed-by: Torsten Duwe <duwe@suse.de>
> > > Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> > > Tested-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
> >
> > Series applied to powerpc next.
> >
> > https://git.kernel.org/powerpc/c/a5cab83cd3d2d75d3893276cb5
>
> Thanks Michael; this is an excellent basis for ppc live patching, but FYI
> I am not merging that one to my tree just yet.
Yeah OK.
> The solution (*) for functions with non-trivial argument list is not there
> yet, and it's my requirement for this to be taken care of in a way that's
> not prone to easily-done human errors on the patch-producer side.
Sure. I'll try and get something working, though this merge window is not
starting well so I may not get time for a few weeks :)
cheers
next prev parent reply other threads:[~2016-03-16 10:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 4:26 [PATCH v3 1/8] powerpc: Create a helper for getting the kernel toc value Michael Ellerman
2016-03-03 4:26 ` [PATCH v3 2/8] powerpc/module: Only try to generate the ftrace_caller() stub once Michael Ellerman
2016-03-03 4:26 ` [PATCH v3 3/8] powerpc/module: Mark module stubs with a magic value Michael Ellerman
2016-03-03 4:26 ` [PATCH v3 4/8] powerpc/module: Create a special stub for ftrace_caller() Michael Ellerman
2016-03-03 4:26 ` [PATCH v3 5/8] powerpc/ftrace: Use generic ftrace_modify_all_code() Michael Ellerman
2016-03-03 4:26 ` [PATCH v3 6/8] powerpc/ftrace: Use $(CC_FLAGS_FTRACE) when disabling ftrace Michael Ellerman
2016-03-03 4:26 ` [PATCH v3 7/8] powerpc/ftrace: Add support for -mprofile-kernel ftrace ABI Michael Ellerman
2016-03-04 1:57 ` Balbir Singh
2016-03-03 4:27 ` [PATCH v3 8/8] powerpc/ftrace: Add Kconfig & Make glue for mprofile-kernel Michael Ellerman
2016-03-03 6:47 ` [PATCH v3 1/8] powerpc: Create a helper for getting the kernel toc value Kamalesh Babulal
2016-03-04 1:56 ` Balbir Singh
2016-03-14 9:25 ` [v3,1/8] " Michael Ellerman
2016-03-15 1:27 ` Jiri Kosina
2016-03-16 10:23 ` Michael Ellerman [this message]
2016-03-16 14:58 ` Torsten Duwe
2016-03-16 23:56 ` Balbir Singh
2016-03-16 23:58 ` Balbir Singh
2016-03-17 15:59 ` Torsten Duwe
2016-03-18 10:52 ` 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=1458123799.27361.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=duwe@lst.de \
--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=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