3rd-party/LKMPG
1
0
Fork 0
mirror of https://github.com/bashrc/LKMPG.git synced 2018-06-11 03:06:54 +02:00
Code Issues Releases Wiki Activity

Merge pull request #1 from SunyDays/master

Browse Source 
fix typo
This commit is contained in:
Bob Mottram
2017-02-11 22:30:20 +00:00
committed by GitHub
parent 9f06359259 6280865a1f
commit 7bc31b226a
6 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
3.16/LKMPG-3.16.html
View File

@@ -884,7 +884,7 @@ There is also an <b>__initdata</b> which works similarly to <b>__init</b> but fo
</p>
<p>
The <b>__exit</b> 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 <b>__exit</b> 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.
</p>
<p>

2
3.16/LKMPG-3.16.org
View File

@@ -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.

2
3.8/LKMPG-3.8.html
View File

@@ -934,7 +934,7 @@ There is also an __initdata which works similarly to __init but for init variabl
</p>
<p>
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.
</p>
<p>

2
3.8/LKMPG-3.8.org
View File

@@ -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.

2
4.7.4/LKMPG-4.7.4.html
View File

@@ -802,7 +802,7 @@ There is also an <b>__initdata</b> which works similarly to <b>__init</b> but fo
</p>
<p>
The <b>__exit</b> 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 <b>__exit</b> 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.
</p>
<p>

2
4.7.4/LKMPG-4.7.4.org
View File

@@ -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.