From: Arjan van de Ven <arjan@linux.intel.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH 1/8] x86: don't use module.h just for AUTHOR / LICENSE tags
Date: Wed, 13 Jul 2016 17:22:56 -0700 [thread overview]
Message-ID: <3bd2a68f-06e2-4fd2-eab3-a05ef50ff854@linux.intel.com> (raw)
In-Reply-To: <20160714001901.31603-2-paul.gortmaker@windriver.com>
On 7/13/2016 5:18 PM, Paul Gortmaker wrote:
> The Kconfig controlling compilation of these files are:
>
> arch/x86/Kconfig.debug:config DEBUG_RODATA_TEST
> arch/x86/Kconfig.debug: bool "Testcase for the marking rodata read-only"
>
> arch/x86/Kconfig.debug:config X86_PTDUMP_CORE
> arch/x86/Kconfig.debug: def_bool n
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets remove the couple traces of modular infrastructure use, so that
> when reading the driver there is no doubt it is builtin-only.
>
> We delete the MODULE_LICENSE tag etc. since all that information
> is already contained at the top of the file in the comments.
>
> Cc: Arjan van de Ven <arjan@linux.intel.com>
Acked-by: Arjan van de Ven <arjan@linux.intel.com>
original these were tested as modules, but they really shouldn't be modules
in the normal kernel (and aren't per Kconfig)
next prev parent reply other threads:[~2016-07-14 0:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 0:18 [PATCH 0/8] x86: audit and remove needless module.h includes Paul Gortmaker
2016-07-14 0:18 ` [PATCH 1/8] x86: don't use module.h just for AUTHOR / LICENSE tags Paul Gortmaker
2016-07-14 0:22 ` Arjan van de Ven [this message]
2016-07-14 18:43 ` [tip:x86/headers] x86: Don't " tip-bot for Paul Gortmaker
2016-07-14 0:18 ` [PATCH 2/8] x86: mm: audit and remove any unnecessary uses of module.h Paul Gortmaker
2016-07-14 18:43 ` [tip:x86/headers] x86/mm: Audit " tip-bot for Paul Gortmaker
2016-07-14 0:18 ` [PATCH 3/8] x86: kernel: audit " Paul Gortmaker
2016-07-14 18:43 ` [tip:x86/headers] x86/kernel: Audit " tip-bot for Paul Gortmaker
2016-07-14 0:18 ` [PATCH 4/8] x86: lib: audit " Paul Gortmaker
2016-07-14 18:44 ` [tip:x86/headers] x86/lib: Audit " tip-bot for Paul Gortmaker
2016-07-14 0:18 ` [PATCH 5/8] x86: platform: audit " Paul Gortmaker
2016-07-14 18:44 ` [tip:x86/headers] x86/platform: Audit " tip-bot for Paul Gortmaker
2016-07-14 0:18 ` [PATCH 6/8] x86: xen: audit " Paul Gortmaker
2016-07-14 3:59 ` Juergen Gross
2016-07-14 18:45 ` [tip:x86/headers] x86/xen: Audit " tip-bot for Paul Gortmaker
2016-07-14 0:19 ` [PATCH 7/8] x86: kvm: audit " Paul Gortmaker
2016-07-14 7:42 ` Paolo Bonzini
2016-07-14 18:45 ` [tip:x86/headers] x86/kvm: Audit " tip-bot for Paul Gortmaker
2016-07-14 0:19 ` [PATCH 8/8] x86: audit and remove any remaining " Paul Gortmaker
2016-07-14 18:45 ` [tip:x86/headers] x86: Audit " tip-bot for Paul Gortmaker
2016-07-14 13:04 ` [PATCH 0/8] x86: audit and remove needless module.h includes Ingo Molnar
2016-07-14 15:18 ` Paul Gortmaker
2016-07-14 18:39 ` Ingo Molnar
2016-07-14 18:46 ` Paul Gortmaker
2016-07-14 18:56 ` Ingo Molnar
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=3bd2a68f-06e2-4fd2-eab3-a05ef50ff854@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--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