From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Minchan Kim <minchan@kernel.org>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<kasan-dev@googlegroups.com>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: [PATCH 0/4] mm: add missing MODULE_DESCRIPTION() macros
Date: Mon, 13 May 2024 12:37:37 -0700 [thread overview]
Message-ID: <20240513-mm-md-v1-0-8c20e7d26842@quicinc.com> (raw)
This fixes the instances of "WARNING: modpost: missing
MODULE_DESCRIPTION()" that I'm seeing in 'mm'.
Note I'm not using an "everything enabled" configuration so there may
be more left to fix.
Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
---
Jeff Johnson (4):
mm/hwpoison: add MODULE_DESCRIPTION()
mm/dmapool: add MODULE_DESCRIPTION()
mm/kfence: add MODULE_DESCRIPTION()
mm/zsmalloc: add MODULE_DESCRIPTION()
mm/dmapool_test.c | 1 +
mm/hwpoison-inject.c | 1 +
mm/kfence/kfence_test.c | 1 +
mm/zsmalloc.c | 1 +
4 files changed, 4 insertions(+)
---
base-commit: dd5a440a31fae6e459c0d6271dddd62825505361
change-id: 20240513-mm-md-9bdb524ea9a8
next reply other threads:[~2024-05-13 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 19:37 Jeff Johnson [this message]
2024-05-13 19:37 ` [PATCH 1/4] mm/hwpoison: add MODULE_DESCRIPTION() Jeff Johnson
2024-05-14 3:14 ` Miaohe Lin
2024-05-13 19:37 ` [PATCH 2/4] mm/dmapool: " Jeff Johnson
2024-05-13 19:37 ` [PATCH 3/4] mm/kfence: " Jeff Johnson
2024-05-13 19:42 ` Marco Elver
2024-05-13 19:37 ` [PATCH 4/4] mm/zsmalloc: " Jeff Johnson
2024-05-14 0:41 ` Sergey Senozhatsky
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=20240513-mm-md-v1-0-8c20e7d26842@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=senozhatsky@chromium.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