This is a note to let you know that I've just added the patch titled
MIPS: IP27: Fix __node_distances undefined error
to the 3.17-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
mips-ip27-fix-__node_distances-undefined-error.patch
and it can be found in the queue-3.17 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 5829b0ecc584d15ae4eeabe69f2ab554bdec4689 Mon Sep 17 00:00:00 2001
From: James Cowgill <James.Cowgill@xxxxxxxxxx>
Date: Thu, 13 Nov 2014 11:08:07 +0000
Subject: MIPS: IP27: Fix __node_distances undefined error
From: James Cowgill <James.Cowgill@xxxxxxxxxx>
commit 5829b0ecc584d15ae4eeabe69f2ab554bdec4689 upstream.
export the __node_distances symbol in the ip27 memory code to fix the
build error:
Building modules, stage 2.
MODPOST 311 modules
ERROR: "__node_distances" [drivers/block/nvme.ko] undefined!
scripts/Makefile.modpost:90: recipe for target '__modpost' failed
when building the kernel with:
CONFIG_SGI_IP27=y
CONFIG_BLK_DEV_NVME=m
Signed-off-by: James Cowgill <James.Cowgill@xxxxxxxxxx>
Reviewed-by: James Hogan <james.hogan@xxxxxxxxxx>
Signed-off-by: Ralf Baechle <ralf@xxxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
arch/mips/sgi-ip27/ip27-memory.c | 1 +
1 file changed, 1 insertion(+)
--- a/arch/mips/sgi-ip27/ip27-memory.c
+++ b/arch/mips/sgi-ip27/ip27-memory.c
@@ -107,6 +107,7 @@ static void router_recurse(klrou_t *rout
}
unsigned char __node_distances[MAX_COMPACT_NODES][MAX_COMPACT_NODES];
+EXPORT_SYMBOL(__node_distances);
static int __init compute_node_distance(nasid_t nasid_a, nasid_t nasid_b)
{
Patches currently in stable-queue which might be from James.Cowgill@xxxxxxxxxx are
queue-3.17/mips-loongson3-fix-__node_distances-undefined-error.patch
queue-3.17/mips-ip27-fix-__node_distances-undefined-error.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html