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.h...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
