typo fixes: specfic -> specific
Signed-off-by: Adrian Bunk <bunk@stusta.de>
This commit is contained in:
parent
d0f19d8217
commit
d254c8f70a
|
@ -43,7 +43,7 @@ EXPORT_SYMBOL(node_data);
|
||||||
bootmem_data_t node0_bdata;
|
bootmem_data_t node0_bdata;
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* numa interface - we expect the numa architecture specfic code to have
|
* numa interface - we expect the numa architecture specific code to have
|
||||||
* populated the following initialisation.
|
* populated the following initialisation.
|
||||||
*
|
*
|
||||||
* 1) node_online_map - the map of all nodes configured (online) in the system
|
* 1) node_online_map - the map of all nodes configured (online) in the system
|
||||||
|
|
|
@ -20,7 +20,7 @@
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* These are data structures found in platform_device.dev.platform_data,
|
* These are data structures found in platform_device.dev.platform_data,
|
||||||
* and describing board-specfic data needed by drivers. For example,
|
* and describing board-specific data needed by drivers. For example,
|
||||||
* which pin is used for a given GPIO role.
|
* which pin is used for a given GPIO role.
|
||||||
*
|
*
|
||||||
* In 2.6, drivers should strongly avoid board-specific knowledge so
|
* In 2.6, drivers should strongly avoid board-specific knowledge so
|
||||||
|
|
|
@ -46,7 +46,7 @@
|
||||||
*
|
*
|
||||||
* I've tried to stick to the following function naming conventions:
|
* I've tried to stick to the following function naming conventions:
|
||||||
* snd_* ALSA stuff
|
* snd_* ALSA stuff
|
||||||
* cs4215_* CS4215 codec specfic stuff
|
* cs4215_* CS4215 codec specific stuff
|
||||||
* dbri_* DBRI high-level stuff
|
* dbri_* DBRI high-level stuff
|
||||||
* other DBRI low-level stuff
|
* other DBRI low-level stuff
|
||||||
*/
|
*/
|
||||||
|
|
Loading…
Reference in a new issue