All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] x86/CPU: Get rid of show_msr
Date: Mon, 24 Oct 2016 19:38:41 +0200	[thread overview]
Message-ID: <20161024173844.23038-1-bp@alien8.de> (raw)

From: Borislav Petkov <bp@suse.de>

Hi,

respective patches should explain it all but in short, this removes some
useles crap.

Borislav Petkov (3):
  x86/CPU: Remove the printk format specifier in "CPU0: "
  x86/CPU: Merge bugs.c and bugs_64.c
  x86/CPU: Get rid of show_msr

 Documentation/kernel-parameters.txt |  6 -----
 arch/x86/kernel/cpu/Makefile        |  4 +--
 arch/x86/kernel/cpu/bugs.c          | 26 +++++++++++++++---
 arch/x86/kernel/cpu/bugs_64.c       | 33 -----------------------
 arch/x86/kernel/cpu/common.c        | 53 -------------------------------------
 arch/x86/kernel/smpboot.c           |  2 +-
 6 files changed, 24 insertions(+), 100 deletions(-)
 delete mode 100644 arch/x86/kernel/cpu/bugs_64.c

-- 
2.10.0

             reply	other threads:[~2016-10-24 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 17:38 Borislav Petkov [this message]
2016-10-24 17:38 ` [PATCH 1/3] x86/CPU: Remove the printk format specifier in "CPU0: " Borislav Petkov
2016-10-25 10:33   ` [tip:x86/cpu] x86/cpu: " tip-bot for Borislav Petkov
2016-10-24 17:38 ` [PATCH 2/3] x86/CPU: Merge bugs.c and bugs_64.c Borislav Petkov
2016-10-25 10:33   ` [tip:x86/cpu] x86/cpu: " tip-bot for Borislav Petkov
2016-10-24 17:38 ` [PATCH 3/3] x86/CPU: Get rid of show_msr Borislav Petkov
2016-10-25 10:34   ` [tip:x86/cpu] x86/cpu: Get rid of the show_msr= boot option tip-bot for Borislav Petkov
2016-10-26 22:25     ` Yinghai Lu

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=20161024173844.23038-1-bp@alien8.de \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.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.