From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,akpm@linux-foundation.org,objecting@objecting.org,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] lib-glob-add-explicit-include-for-exporth.patch removed from -mm tree
Date: Fri, 27 Mar 2026 21:25:02 -0700 [thread overview]
Message-ID: <20260328042503.74C52C4CEF7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: lib: glob: add explicit include for export.h
has been removed from the -mm tree. Its filename was
lib-glob-add-explicit-include-for-exporth.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Josh Law <objecting@objecting.org>
Subject: lib: glob: add explicit include for export.h
Date: Sun, 1 Mar 2026 15:21:41 +0000
Include <linux/export.h> explicitly instead of relying on it being
implicitly included by <linux/module.h> for the EXPORT_SYMBOL macro.
Link: https://lkml.kernel.org/r/20260301152143.2572137-1-objecting@objecting.org
Signed-off-by: Josh Law <objecting@objecting.org>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/glob.c | 1 +
1 file changed, 1 insertion(+)
--- a/lib/glob.c~lib-glob-add-explicit-include-for-exporth
+++ a/lib/glob.c
@@ -1,6 +1,7 @@
// SPDX-License-Identifier: (GPL-2.0 OR MIT)
#include <linux/module.h>
#include <linux/glob.h>
+#include <linux/export.h>
/*
* The only reason this code can be compiled as a module is because the
_
Patches currently in -mm which might be from objecting@objecting.org are
mm-damon-core-document-damos_commit_dests-failure-semantics.patch
lib-maple_tree-fix-swapped-arguments-in-mas_safe_pivot-call.patch
lib-idr-fix-ida_find_first_range-missing-ids-across-chunk-boundaries.patch
reply other threads:[~2026-03-28 4:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260328042503.74C52C4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=objecting@objecting.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.