From: akpm@linux-foundation.org
To: bunk@kernel.org, mm-commits@vger.kernel.org
Subject: - make-mm-sparsec-make-a-function-static.patch removed from -mm tree
Date: Sat, 26 Jul 2008 14:18:12 -0700 [thread overview]
Message-ID: <200807262118.m6QLICOU020069@imap1.linux-foundation.org> (raw)
The patch titled
make mm/sparse.c: make a function static
has been removed from the -mm tree. Its filename was
make-mm-sparsec-make-a-function-static.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: make mm/sparse.c: make a function static
From: Adrian Bunk <bunk@kernel.org>
This patch makes the needlessly global sparse_early_mem_map_alloc()
static.
Signed-off-by: Adrian Bunk <bunk@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/sparse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/sparse.c~make-mm-sparsec-make-a-function-static mm/sparse.c
--- a/mm/sparse.c~make-mm-sparsec-make-a-function-static
+++ a/mm/sparse.c
@@ -377,7 +377,7 @@ struct page __init *sparse_mem_map_popul
}
#endif /* !CONFIG_SPARSEMEM_VMEMMAP */
-struct page __init *sparse_early_mem_map_alloc(unsigned long pnum)
+static struct page __init *sparse_early_mem_map_alloc(unsigned long pnum)
{
struct page *map;
struct mem_section *ms = __nr_to_section(pnum);
_
Patches currently in -mm which might be from bunk@kernel.org are
origin.patch
linux-next.patch
m32r-remove-the-unused-nohighmem-option.patch
if-0-ses_match_host.patch
git-xtensa.patch
include-linux-kernelh-userspace-header-cleanup.patch
make-mm-rmapc-anon_vma_cachep-static.patch
reiser4.patch
reply other threads:[~2008-07-26 21:18 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=200807262118.m6QLICOU020069@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.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 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.