From d9409bbd37fc4cfdd841a754519518630d61f635 Mon Sep 17 00:00:00 2001
From: Jurij Smakov <jurij@wooyd.org>
Date: Mon, 23 May 2005 17:00:15 +0000
Subject: [PATCH] Allow passing arbitrary build_subarch string.

svn path=/branches/kernel-image-2.6.11/; revision=3227
---
 Makefile |  2 +-
 README   | 12 +++++-------
 2 files changed, 6 insertions(+), 8 deletions(-)

diff --git a/Makefile b/Makefile
index c9200109d..0fbdbfe6a 100755
--- a/Makefile
+++ b/Makefile
@@ -59,7 +59,7 @@ ifdef added_patches
   kpkg_build_cmd   += --added_patches $(subst @uver@,$(uver),$(added_patches))
 endif
 ifdef build_subarch
-  kpkg_build_cmd += --subarch @flavour@
+  kpkg_build_cmd += --subarch $(build_subarch)
 endif
 ifdef headers_subarch
   kpkg_headers_cmd += --subarch $(headers_subarch)
diff --git a/README b/README
index 50756def6..70f3c1538 100644
--- a/README
+++ b/README
@@ -144,15 +144,13 @@ added_patches
 build_subarch
 
   Setting this variable to non-empty value will cause an option
-  --subarch to be added to 'build' and 'kernel-image' make-kpkg
-  calls, followed by the flavour for which the kernel is built.
-  In general, if you wish to add subarch support for your 
-  architecture, you should contact kernel-package maintainer
+  --subarch $(build_subarch) added to 'build' and 'kernel-image'
+  make-kpkg calls. In general, if you wish to add subarch support
+  for your architecture, you should contact kernel-package maintainer
   to ensure that the flavour name correctly maps onto a kernel
-  subarch name. Currently only mips and sparc are using this
-  facility, and both of them should be fine. Typical usage:
+  subarch name. Typical usage:
 
-  build_subarch := yes
+  build_subarch := pmac
 
   Note that the value of this variable is ignored.