From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] x86: Zap some changelogs
Date: Thu, 7 May 2015 19:06:11 +0200 [thread overview]
Message-ID: <1431018374-25729-1-git-send-email-bp@alien8.de> (raw)
From: Borislav Petkov <bp@suse.de>
Kill some changelogs which simply take up space and serve almost no
purpose as git history has it all and detailed. Also, remove unneeded
function definitions from traps.c
Borislav Petkov (3):
x86/traps: Remove superfluous weak definitions and dead code
x86/mce/amd: Zap changelog
x86/cpu/microcode: Zap changelog
arch/x86/kernel/cpu/mcheck/mce_amd.c | 12 +-----
arch/x86/kernel/cpu/microcode/core.c | 76 +++++------------------------------
arch/x86/kernel/cpu/microcode/intel.c | 75 ++++------------------------------
arch/x86/kernel/traps.c | 17 --------
4 files changed, 18 insertions(+), 162 deletions(-)
--
2.3.5
next reply other threads:[~2015-05-07 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 17:06 Borislav Petkov [this message]
2015-05-07 17:06 ` [PATCH 1/3] x86/traps: Remove superfluous weak definitions and dead code Borislav Petkov
2015-05-07 17:06 ` [PATCH 2/3] x86/mce/amd: Zap changelog Borislav Petkov
2015-05-07 17:06 ` [PATCH 3/3] x86/cpu/microcode: " Borislav Petkov
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=1431018374-25729-1-git-send-email-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox