mm-commits.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [merged] lib-include-memregionh-in-memregionc.patch removed from -mm tree
@ 2020-09-28 21:14 akpm
  0 siblings, 0 replies; only message in thread
From: akpm @ 2020-09-28 21:14 UTC (permalink / raw)
  To: hulkci, mm-commits, yanaijie


The patch titled
     Subject: lib/memregion.c: include memregion.h
has been removed from the -mm tree.  Its filename was
     lib-include-memregionh-in-memregionc.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
From: Jason Yan <yanaijie@huawei.com>
Subject: lib/memregion.c: include memregion.h

This addresses the following sparse warning:

lib/memregion.c:8:5: warning: symbol 'memregion_alloc' was not declared.
Should it be static?
lib/memregion.c:14:6: warning: symbol 'memregion_free' was not declared.
Should it be static?

Link: https://lkml.kernel.org/r/20200921142852.875312-1-yanaijie@huawei.com
Signed-off-by: Jason Yan <yanaijie@huawei.com>
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 lib/memregion.c |    1 +
 1 file changed, 1 insertion(+)

--- a/lib/memregion.c~lib-include-memregionh-in-memregionc
+++ a/lib/memregion.c
@@ -2,6 +2,7 @@
 /* identifiers for device / performance-differentiated memory regions */
 #include <linux/idr.h>
 #include <linux/types.h>
+#include <linux/memregion.h>
 
 static DEFINE_IDA(memregion_ids);
 
_

Patches currently in -mm which might be from yanaijie@huawei.com are



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-09-28 21:14 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-28 21:14 [merged] lib-include-memregionh-in-memregionc.patch removed from -mm tree akpm

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).