[PATCH 5/5] clarification of _shipped files intent

[PATCH 5/5] clarification of _shipped files intent

[Nicholas Mc Guire]

clarification of _shipped files intent

The rational for using _shipped files should be clearly
indicated so that it does not look like it is encouraging
binary blobs.

This patch is against linux 3.18.0-rc6

Note that the original file uses leading tabs so for this
patch this was retained.

Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>
---
 Documentation/kbuild/modules.txt |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/Documentation/kbuild/modules.txt b/Documentation/kbuild/modules.txt
index 450af1f..eeca125 100644
--- a/Documentation/kbuild/modules.txt
+++ b/Documentation/kbuild/modules.txt
@@ -268,7 +268,10 @@ module 8123.ko, which is built from the following files:
 
 --- 3.3 Binary Blobs
 
-	Some external modules need to include an object file as a blob.
+	Some external modules need to include an object file as a
+	prebuilt binary if they depend on exotic tools or if the
+	build time penalty of generating such files might be seen
+	to be too high.
 	kbuild has support for this, but requires the blob file to be
 	named <filename>_shipped. When the kbuild rules kick in, a copy
 	of <filename>_shipped is created with _shipped stripped off,
-- 
1.7.10.4