All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Jason Baron <jbaron@akamai.com>, Borislav Petkov <bp@suse.de>
Subject: [PATCH 0/3] jump_label: Robustify jump label patching
Date: Wed, 14 Feb 2018 10:40:40 -0600	[thread overview]
Message-ID: <cover.1518626149.git.jpoimboe@redhat.com> (raw)

Warn if a jump_label fails to patch, and fix up a couple of issues found
by the warning.

Josh Poimboeuf (3):
  jump_label: Warn on failed jump_label patch
  x86/xen: Remove inert tracepoint in __init code
  percpu: Remove inert tracepoint in __init code

 arch/x86/xen/enlighten_pv.c | 2 --
 kernel/jump_label.c         | 8 ++++++--
 mm/percpu.c                 | 1 -
 3 files changed, 6 insertions(+), 5 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-02-14 16:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 16:40 Josh Poimboeuf [this message]
2018-02-14 16:40 ` [PATCH 1/3] jump_label: Warn on failed jump_label patch Josh Poimboeuf
2018-02-14 17:01   ` Steven Rostedt
2018-02-14 17:18     ` Jason Baron
2018-02-14 17:34       ` Josh Poimboeuf
2018-02-14 17:40         ` Steven Rostedt
2018-02-14 21:17           ` Josh Poimboeuf
2018-02-15 22:35             ` Josh Poimboeuf
2018-02-16 17:31               ` Steven Rostedt
2018-02-14 17:01   ` Borislav Petkov
2018-02-14 16:40 ` [PATCH 2/3] x86/xen: Remove inert tracepoint in __init code Josh Poimboeuf
2018-02-14 16:49   ` Juergen Gross
2018-02-14 16:40 ` [PATCH 3/3] percpu: " Josh Poimboeuf
2018-02-15 15:22   ` Tejun Heo
2018-02-15 15:33     ` Josh Poimboeuf
2018-02-16  9:02       ` Ingo Molnar
2018-02-16 12:52         ` 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=cover.1518626149.git.jpoimboe@redhat.com \
    --to=jpoimboe@redhat.com \
    --cc=bp@suse.de \
    --cc=jbaron@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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.