From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jiri Slaby <jslaby@suse.cz>,
jpoimboe@redhat.com, sjenning@redhat.com, vojtech@suse.cz,
live-patching@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] livepatch: add support on s390
Date: Fri, 27 Mar 2015 10:19:00 +0100 [thread overview]
Message-ID: <20150327091900.GA4379@osiris> (raw)
In-Reply-To: <alpine.LNX.2.00.1503261924430.6781@pobox.suse.cz>
On Thu, Mar 26, 2015 at 07:24:58PM +0100, Jiri Kosina wrote:
> On Thu, 26 Mar 2015, Jiri Slaby wrote:
>
> > This is a trivial port from kGraft. Module relocations are not
> > supported.
> >
> > Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> > ---
> > [v2] return ENOSYS
> > [v3] proper return value from klp_check_compiler_support
>
> Applied to for-4.1/core.
Hello Jiri,
while I do appreciate your work on the s390 architecture backend for
livepatching: this should go upstream only via the s390 tree or with
an Ack from Martin or me.
That being said, what is the reason why module relocations are not
supported?
As far as I can tell right now there is only one simple in-kernel
test case available (which is fine). However is the tool chain to
generate additional livepatch modules, available somewhere?
If so, where?
Thanks,
Heiko
next prev parent reply other threads:[~2015-03-27 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 9:10 [PATCH 1/1] livepatch: add support on s390 Jiri Slaby
2015-03-26 12:15 ` Josh Poimboeuf
2015-03-26 18:24 ` Jiri Kosina
2015-03-27 9:19 ` Heiko Carstens [this message]
2015-03-27 9:29 ` Jiri Kosina
2015-03-27 13:58 ` Heiko Carstens
2015-03-27 14:09 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2015-03-24 14:51 Jiri Slaby
2015-03-24 14:52 ` Jiri Slaby
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=20150327091900.GA4379@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=sjenning@redhat.com \
--cc=vojtech@suse.cz \
/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