From 6280865a1f5fd058b81f212c16d124cfb5740bc6 Mon Sep 17 00:00:00 2001 From: SunyDays Date: Sun, 12 Feb 2017 00:59:57 +0300 Subject: [PATCH] fix little typo --- 3.16/LKMPG-3.16.html | 2 +- 3.16/LKMPG-3.16.org | 2 +- 3.8/LKMPG-3.8.html | 2 +- 3.8/LKMPG-3.8.org | 2 +- 4.7.4/LKMPG-4.7.4.html | 2 +- 4.7.4/LKMPG-4.7.4.org | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/3.16/LKMPG-3.16.html b/3.16/LKMPG-3.16.html index fddb492..10862f6 100644 --- a/3.16/LKMPG-3.16.html +++ b/3.16/LKMPG-3.16.html @@ -884,7 +884,7 @@ There is also an __initdata which works similarly to __init but fo

-The __exit macro causes the omission of the function when the module is built into the kernel, and like __exit, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. +The __exit macro causes the omission of the function when the module is built into the kernel, and like __init, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do.

diff --git a/3.16/LKMPG-3.16.org b/3.16/LKMPG-3.16.org index 7d1ecae..04d79fa 100644 --- a/3.16/LKMPG-3.16.org +++ b/3.16/LKMPG-3.16.org @@ -314,7 +314,7 @@ This demonstrates a feature of kernel 2.2 and later. Notice the change in the de There is also an *__initdata* which works similarly to *__init* but for init variables rather than functions. -The *__exit* macro causes the omission of the function when the module is built into the kernel, and like __exit, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. +The *__exit* macro causes the omission of the function when the module is built into the kernel, and like __init, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. These macros are defined in *linux/init.h* and serve to free up kernel memory. When you boot your kernel and see something like Freeing unused kernel memory: 236k freed, this is precisely what the kernel is freeing. diff --git a/3.8/LKMPG-3.8.html b/3.8/LKMPG-3.8.html index 65c04c0..3ed3a0a 100644 --- a/3.8/LKMPG-3.8.html +++ b/3.8/LKMPG-3.8.html @@ -934,7 +934,7 @@ There is also an __initdata which works similarly to __init but for init variabl

-The __exit macro causes the omission of the function when the module is built into the kernel, and like __exit, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. +The __exit macro causes the omission of the function when the module is built into the kernel, and like __init, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do.

diff --git a/3.8/LKMPG-3.8.org b/3.8/LKMPG-3.8.org index a5d0285..759544e 100644 --- a/3.8/LKMPG-3.8.org +++ b/3.8/LKMPG-3.8.org @@ -301,7 +301,7 @@ This demonstrates a feature of kernel 2.2 and later. Notice the change in the de There is also an __initdata which works similarly to __init but for init variables rather than functions. -The __exit macro causes the omission of the function when the module is built into the kernel, and like __exit, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. +The __exit macro causes the omission of the function when the module is built into the kernel, and like __init, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. These macros are defined in linux/init.h and serve to free up kernel memory. When you boot your kernel and see something like Freeing unused kernel memory: 236k freed, this is precisely what the kernel is freeing. diff --git a/4.7.4/LKMPG-4.7.4.html b/4.7.4/LKMPG-4.7.4.html index dad68c1..b343432 100644 --- a/4.7.4/LKMPG-4.7.4.html +++ b/4.7.4/LKMPG-4.7.4.html @@ -802,7 +802,7 @@ There is also an __initdata which works similarly to __init but fo

-The __exit macro causes the omission of the function when the module is built into the kernel, and like __exit, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. +The __exit macro causes the omission of the function when the module is built into the kernel, and like __init, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do.

diff --git a/4.7.4/LKMPG-4.7.4.org b/4.7.4/LKMPG-4.7.4.org index 7adf15f..c1c1f0e 100644 --- a/4.7.4/LKMPG-4.7.4.org +++ b/4.7.4/LKMPG-4.7.4.org @@ -280,7 +280,7 @@ This demonstrates a feature of kernel 2.2 and later. Notice the change in the de There is also an *__initdata* which works similarly to *__init* but for init variables rather than functions. -The *__exit* macro causes the omission of the function when the module is built into the kernel, and like __exit, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. +The *__exit* macro causes the omission of the function when the module is built into the kernel, and like __init, has no effect for loadable modules. Again, if you consider when the cleanup function runs, this makes complete sense; built-in drivers don't need a cleanup function, while loadable modules do. These macros are defined in *linux/init.h* and serve to free up kernel memory. When you boot your kernel and see something like Freeing unused kernel memory: 236k freed, this is precisely what the kernel is freeing.