public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Russell King <linux@armlinux.org.uk>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
	"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	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>
Subject: Re: MODULE_DESCRIPTION() patches with no maintainer action
Date: Fri, 19 Jul 2024 07:00:17 -0700	[thread overview]
Message-ID: <55341a0d-b07b-4f25-be45-dd0b352315aa@quicinc.com> (raw)
In-Reply-To: <bdac7f10-4c65-4be2-952b-aed1af04e2c9@app.fastmail.com>

On 7/19/2024 3:51 AM, Arnd Bergmann wrote:
> On Sun, Jul 14, 2024, at 23:46, Jeff Johnson wrote:
>> Andrew & Greg,
>>
>> I hate to bother you with such mundane patches, but the following have been
>> posted for a while without any maintainer or reviewer comment or action, and
>> they have not yet landed in linux-next.
>>
>> What is the path forward to have these MODULE_DESCRIPTION() warnings fixed?
>>
>> arch/arm/probes/kprobes/
>> https://lore.kernel.org/all/20240622-md-arm-arch-arm-probes-kprobes-v1-1-0832bd6e45db@quicinc.com/
>>
>> arch/x86/mm/
>> https://lore.kernel.org/all/20240515-testmmiotrace-md-v1-1-10919a8b2842@quicinc.com/
>>
>> drivers/spmi/
>> https://lore.kernel.org/all/20240609-md-drivers-spmi-v1-1-f1d5b24e7a66@quicinc.com/
>>
>> (note that beyond these 3 patches I still have an additional 13 patches which
>> need to land in order to fix these warnings tree-wide, but those 13 patches
>> have had recent maintainer or reviewer action so I'm not seeking your help at
>> this time).
> 
> Hi Jeff,
> 
> For completeness, this is a patch that I have in my local
> test tree now after I addressed the build issues for all
> randconfig builds on arm, arm64 and x86.
> 
> I assume you already a version of most of these,
> but please have a look in case there are some still
> missing.

You have found and fixed some that I didn't encounter with make allmodconfig
builds. I do have a list of ones for further analysis that I created by
looking for files with a MODULE_LICENSE but not a MODULE_DESCRIPTION, and the
ones I haven't yet fixed are on that list, but I'm very happy for you to
submit your fixes.

Details follow:

>  arch/arm/lib/xor-neon.c                         | 1 +
https://lore.kernel.org/all/20240711-md-arm-arch-arm-lib-v2-1-ab08653dc106@quicinc.com/

>  arch/x86/mm/testmmiotrace.c                     | 1 +
https://lore.kernel.org/all/20240515-testmmiotrace-md-v1-1-10919a8b2842@quicinc.com/

>  drivers/fpga/tests/fpga-bridge-test.c           | 1 +
>  drivers/fpga/tests/fpga-mgr-test.c              | 1 +
>  drivers/fpga/tests/fpga-region-test.c           | 1 +
I do not have a patch for these three

>  drivers/fsi/fsi-core.c                          | 1 +
>  drivers/fsi/fsi-master-aspeed.c                 | 2 ++
>  drivers/fsi/fsi-master-ast-cf.c                 | 1 +
>  drivers/fsi/fsi-master-gpio.c                   | 1 +
>  drivers/fsi/fsi-master-hub.c                    | 1 +
>  drivers/fsi/fsi-scom.c                          | 1 +
https://lore.kernel.org/all/20240605-md-drivers-fsi-v1-1-fefc82d81b12@quicinc.com/

>  drivers/xen/xenbus/xenbus_probe_frontend.c      | 1 +
I do not have a patch for this one

>  fs/adfs/super.c                                 | 2 ++
https://lore.kernel.org/all/20240523-md-adfs-v1-1-364268e38370@quicinc.com/

>  fs/exportfs/expfs.c                             | 1 +
I do not have a patch for this one

>  kernel/locking/test-ww_mutex.c                  | 1 +
https://lore.kernel.org/all/20240528-md-test-ww_mutex-v2-1-a2a19e920b12@quicinc.com/

>  lib/asn1_decoder.c                              | 1 +
>  lib/slub_kunit.c                                | 1 +
>  lib/ucs2_string.c                               | 1 +
>  lib/zlib_inflate/inflate_syms.c                 | 1 +
I do not have a patch for these four

>  mm/kasan/kasan_test.c                           | 1 +
>  mm/kasan/kasan_test_module.c                    | 1 +
I do not have a patch for these two

>  samples/livepatch/livepatch-callbacks-busymod.c | 1 +
>  samples/livepatch/livepatch-callbacks-demo.c    | 1 +
>  samples/livepatch/livepatch-callbacks-mod.c     | 1 +
>  samples/livepatch/livepatch-sample.c            | 1 +
>  samples/livepatch/livepatch-shadow-fix1.c       | 1 +
>  samples/livepatch/livepatch-shadow-fix2.c       | 1 +
I do not have a patch for these six

>  security/apparmor/policy_unpack_test.c          | 1 +
https://lore.kernel.org/all/20240529-md-apparmor_policy_unpack_test-v1-1-9efc582078c4@quicinc.com/




      reply	other threads:[~2024-07-19 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-14 21:46 MODULE_DESCRIPTION() patches with no maintainer action Jeff Johnson
2024-07-15  5:35 ` Greg Kroah-Hartman
2024-07-19 10:51 ` Arnd Bergmann
2024-07-19 14:00   ` Jeff Johnson [this message]

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=55341a0d-b07b-4f25-be45-dd0b352315aa@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=karolherbst@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux@armlinux.org.uk \
    --cc=luto@kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=peterz@infradead.org \
    --cc=ppaalanen@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=sboyd@kernel.org \
    --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