From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] Add SPDX identifiers to some more files
Date: Fri, 9 Nov 2018 16:04:27 +0100 [thread overview]
Message-ID: <20181109150431.14147-1-bp@alien8.de> (raw)
From: Borislav Petkov <bp@suse.de>
Hi,
here's some more files converted to SPDX identifiers.
In the MCE and microcode cases, I've made one patch per subsystem as
this is shared functionality so maybe splitting them even more would not
make any sense.
But I could be wrong and the lawyer logic could very well work in a
completely different way so I'm open to suggestions here.
Thanks.
Borislav Petkov (4):
EDAC, mce_amd: Add an SPDX identifier
EDAC, amd64: Add SPDX identifiers
x86/microcode: Add SPDX license identifiers
x86/mce: Add an SPDX license identifiers
arch/x86/kernel/cpu/mcheck/dev-mcelog.c | 1 +
arch/x86/kernel/cpu/mcheck/mce-apei.c | 14 +-------------
arch/x86/kernel/cpu/mcheck/mce-genpool.c | 3 +--
arch/x86/kernel/cpu/mcheck/mce-inject.c | 9 +--------
arch/x86/kernel/cpu/mcheck/mce-severity.c | 6 +-----
arch/x86/kernel/cpu/mcheck/mce.c | 1 +
arch/x86/kernel/cpu/mcheck/therm_throt.c | 1 +
arch/x86/kernel/cpu/microcode/amd.c | 4 +---
arch/x86/kernel/cpu/microcode/core.c | 6 +-----
arch/x86/kernel/cpu/microcode/intel.c | 6 +-----
drivers/edac/amd64_edac.c | 1 +
drivers/edac/amd64_edac.h | 4 +---
drivers/edac/mce_amd.c | 1 +
13 files changed, 13 insertions(+), 44 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-09 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 15:04 Borislav Petkov [this message]
2018-11-09 15:04 ` [PATCH 1/4] EDAC, mce_amd: Add an SPDX identifier Borislav Petkov
2018-11-09 15:04 ` [PATCH 2/4] EDAC, amd64: Add SPDX identifiers Borislav Petkov
2018-11-09 15:04 ` [PATCH 3/4] x86/microcode: Add SPDX license identifiers Borislav Petkov
2018-11-09 15:34 ` Tigran Aivazian
2018-11-09 17:04 ` Borislav Petkov
2018-11-09 15:04 ` [PATCH 4/4] x86/mce: Add an " 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=20181109150431.14147-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).