From: Jiri Kosina <jikos@kernel.org>
To: Miroslav Benes <mbenes@suse.cz>
Cc: Jessica Yu <jeyu@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Petr Mladek <pmladek@suse.com>,
Chris J Arges <chris.j.arges@canonical.com>,
Eugene Shatokhin <eugene.shatokhin@rosalab.ru>,
live-patching@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] livepatch/x86: apply alternatives and paravirt patches after relocations
Date: Tue, 2 Aug 2016 15:02:44 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1608021501470.22028@cbobk.fhfr.pm> (raw)
In-Reply-To: <alpine.LNX.2.00.1608021049460.12272@pobox.suse.cz>
On Tue, 2 Aug 2016, Miroslav Benes wrote:
> > +#include <linux/module.h>
> > +#include <linux/kallsyms.h>
> > +#include <linux/livepatch.h>
> > +#include <asm/text-patching.h>
>
> It seems I don't have such header file here and it causes a build error.
> Shouldn't it be <asm/alternative.h>?
I've now refreshed our for-next branch so that it's based on v4.7 to allow
for it being used as a up-to-date basis for development.
(there have been no KLP patches this merge window, which made for-next
also quite silent).
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2016-08-02 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 5:23 [PATCH v2 0/2] Fix issue with alternatives/paravirt patches Jessica Yu
2016-07-21 5:23 ` [PATCH v2 1/2] livepatch: use arch_klp_init_object_loaded() to finish arch-specific tasks Jessica Yu
2016-08-02 8:25 ` Miroslav Benes
2016-07-21 5:24 ` [PATCH v2 2/2] livepatch/x86: apply alternatives and paravirt patches after relocations Jessica Yu
2016-08-02 8:59 ` Miroslav Benes
2016-08-02 12:59 ` Petr Mladek
2016-08-02 13:02 ` Jiri Kosina [this message]
2016-07-26 20:59 ` [PATCH v2 0/2] Fix issue with alternatives/paravirt patches Josh Poimboeuf
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=alpine.LNX.2.00.1608021501470.22028@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=chris.j.arges@canonical.com \
--cc=eugene.shatokhin@rosalab.ru \
--cc=jeyu@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.