From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Steven Rostedt <rostedt@goodmis.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
Karol Herbst <karolherbst@gmail.com>,
"Pekka Paalanen" <ppaalanen@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Naveen N Rao <naveen@kernel.org>, Jeremy Kerr <jk@ozlabs.org>,
Joel Stanley <joel@jms.id.au>,
Alistar Popple <alistair@popple.id.au>,
Eddie James <eajames@linux.ibm.com>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <nouveau@lists.freedesktop.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-pm@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
<linux-fsi@lists.ozlabs.org>, <linux-aspeed@lists.ozlabs.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: [PATCH 0/5] treewide: add missing MODULE_DESCRIPTION() macros
Date: Tue, 30 Jul 2024 07:43:17 -0700 [thread overview]
Message-ID: <20240730-module_description_orphans-v1-0-7094088076c8@quicinc.com> (raw)
Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
description is missing"), a module without a MODULE_DESCRIPTION() will
result in a warning when built with make W=1.
Recently, multiple developers have been eradicating these warnings
treewide, and I personally submitted almost 300 patches over the past
few months. Almost all of my patches landed by 6.11-rc1, either by
being merged in a 6.10-rc or by being merged in the 6.11 merge
window. However, a few of my patches did not land.
In some cases I see them in linux-next, but they did not land during
the merge window. I'm still monitoring those.
In a few cases I have not had any feedback that the patches have been
accepted into a maintainer's tree. At the advice of Greg KH I've
consolidated those patches into this single series with the hope these
can still land before 6.11-final.
https://lore.kernel.org/all/2024071518-ridden-election-8118@gregkh/
Links to the original individual patches:
crypto: arm/xor - add missing MODULE_DESCRIPTION() macro
https://lore.kernel.org/all/20240711-md-arm-arch-arm-lib-v2-1-ab08653dc106@quicinc.com/
x86/mm: add testmmiotrace MODULE_DESCRIPTION()
https://lore.kernel.org/all/20240515-testmmiotrace-md-v1-1-10919a8b2842@quicinc.com/
cpufreq: powerpc: add missing MODULE_DESCRIPTION() macros
https://lore.kernel.org/all/20240722-md-powerpc-drivers-cpufreq-v2-1-bb84d715eb3d@quicinc.com/
fsi: add missing MODULE_DESCRIPTION() macros
https://lore.kernel.org/all/20240605-md-drivers-fsi-v1-1-fefc82d81b12@quicinc.com/
locking/ww_mutex/test: add MODULE_DESCRIPTION()
https://lore.kernel.org/all/20240528-md-test-ww_mutex-v2-1-a2a19e920b12@quicinc.com/
---
Jeff Johnson (5):
crypto: arm/xor - add missing MODULE_DESCRIPTION() macro
x86/mm: add testmmiotrace MODULE_DESCRIPTION()
cpufreq: powerpc: add missing MODULE_DESCRIPTION() macros
fsi: add missing MODULE_DESCRIPTION() macros
locking/ww_mutex/test: add MODULE_DESCRIPTION()
arch/arm/lib/xor-neon.c | 1 +
arch/x86/mm/testmmiotrace.c | 1 +
drivers/cpufreq/maple-cpufreq.c | 1 +
drivers/cpufreq/pasemi-cpufreq.c | 1 +
drivers/cpufreq/pmac64-cpufreq.c | 1 +
drivers/cpufreq/powernv-cpufreq.c | 1 +
drivers/cpufreq/ppc_cbe_cpufreq.c | 1 +
drivers/fsi/fsi-core.c | 1 +
drivers/fsi/fsi-master-aspeed.c | 1 +
drivers/fsi/fsi-master-ast-cf.c | 3 ++-
drivers/fsi/fsi-master-gpio.c | 1 +
drivers/fsi/fsi-master-hub.c | 1 +
drivers/fsi/fsi-scom.c | 1 +
kernel/locking/test-ww_mutex.c | 1 +
14 files changed, 15 insertions(+), 1 deletion(-)
---
base-commit: 94ede2a3e9135764736221c080ac7c0ad993dc2d
change-id: 20240730-module_description_orphans-cb5e25fe1656
next reply other threads:[~2024-07-30 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 14:43 Jeff Johnson [this message]
2024-07-30 14:43 ` [PATCH 1/5] crypto: arm/xor - add missing MODULE_DESCRIPTION() macro Jeff Johnson
2024-07-30 14:43 ` [PATCH 2/5] x86/mm: add testmmiotrace MODULE_DESCRIPTION() Jeff Johnson
2024-07-30 14:43 ` [PATCH 3/5] cpufreq: powerpc: add missing MODULE_DESCRIPTION() macros Jeff Johnson
2024-07-30 14:43 ` [PATCH 4/5] fsi: " Jeff Johnson
2024-07-30 14:43 ` [PATCH 5/5] locking/ww_mutex/test: add MODULE_DESCRIPTION() Jeff Johnson
2024-07-30 14:50 ` Waiman Long
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=20240730-module_description_orphans-v1-0-7094088076c8@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.torgue@foss.st.com \
--cc=alistair@popple.id.au \
--cc=andrew@codeconstruct.com.au \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=eajames@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=karolherbst@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=longman@redhat.com \
--cc=luto@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=ppaalanen@gmail.com \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=will@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
all inboxes | Powered by JetHome®