Capitalize the first word in the sentence. Use obj-m instead of obj-y. obj-y still works, but we have no built-in objects in external module builds. So, obj-m is better IMHO.
Unified · Split
| @@ -502,7 +502,7 @@ build. · 501 unmodified lines | |||
| 502 | ---------------------------------------- | 502 | ---------------------------------------- |
| 503 | 503 | ||
| 504 | Sometimes, an external module uses exported symbols from | 504 | Sometimes, an external module uses exported symbols from |
| 505 | another external module. kbuild needs to have full knowledge of | 505 | another external module. Kbuild needs to have full knowledge of |
| 506 | all symbols to avoid spitting out warnings about undefined | 506 | all symbols to avoid spitting out warnings about undefined |
| 507 | symbols. Three solutions exist for this situation. | 507 | symbols. Three solutions exist for this situation. |
| 508 | 508 | ||
| @@ -522,7 +522,7 @@ build. · 13 unmodified lines | |||
| 522 | The top-level kbuild file would then look like:: | 522 | The top-level kbuild file would then look like:: |
| 523 | 523 | ||
| 524 | #./Kbuild (or ./Makefile): | 524 | #./Kbuild (or ./Makefile): |
| 525 | obj-y := foo/ bar/ | 525 | obj-m := foo/ bar/ |
| 526 | 526 | ||
| 527 | And executing:: | 527 | And executing:: |
| 528 | 528 | ||