mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miroslav Benes <mbenes@suse.cz>
To: jpoimboe@redhat.com, jeyu@kernel.org, jikos@kernel.org
Cc: linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
	pmladek@suse.com, jbaron@akamai.com,
	Miroslav Benes <mbenes@suse.cz>
Subject: [PATCH 0/2] Remove immediate feature
Date: Fri,  8 Dec 2017 18:25:21 +0100	[thread overview]
Message-ID: <20171208172523.12150-1-mbenes@suse.cz> (raw)

Hi,

here it is. The first patch is only code removal and appropriate changes
in the documentation. The second patch is maybe more interesting. Do you
agree to do it this way, or have you got a better idea?

Miroslav Benes (2):
  livepatch: Remove immediate feature
  livepatch: Allow loading modules on architectures without
    HAVE_RELIABLE_STACKTRACE

 Documentation/livepatch/livepatch.txt        | 84 ++++++++--------------------
 include/linux/livepatch.h                    |  4 --
 kernel/livepatch/core.c                      | 19 ++-----
 kernel/livepatch/transition.c                | 49 ++--------------
 samples/livepatch/livepatch-callbacks-demo.c | 15 -----
 samples/livepatch/livepatch-sample.c         | 15 -----
 samples/livepatch/livepatch-shadow-fix1.c    | 15 -----
 samples/livepatch/livepatch-shadow-fix2.c    | 15 -----
 8 files changed, 33 insertions(+), 183 deletions(-)

-- 
2.15.1

             reply	other threads:[~2017-12-08 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 17:25 Miroslav Benes [this message]
2017-12-08 17:25 ` [PATCH 1/2] livepatch: " Miroslav Benes
2017-12-20 14:35   ` Petr Mladek
2017-12-20 17:09     ` Josh Poimboeuf
2017-12-21 13:30       ` Petr Mladek
2017-12-21 13:55         ` Miroslav Benes
2017-12-21 14:58   ` Petr Mladek
2017-12-22 13:10     ` Miroslav Benes
2017-12-08 17:25 ` [PATCH 2/2] livepatch: Allow loading modules on architectures without HAVE_RELIABLE_STACKTRACE Miroslav Benes
2017-12-21 15:14   ` Petr Mladek
2017-12-22 13:12     ` Miroslav Benes

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=20171208172523.12150-1-mbenes@suse.cz \
    --to=mbenes@suse.cz \
    --cc=jbaron@akamai.com \
    --cc=jeyu@kernel.org \
    --cc=jikos@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=pmladek@suse.com \
    /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
all inboxes | Powered by JetHome®