Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
d254c8f7
Commit
d254c8f7
authored
Jun 30, 2006
by
Adrian Bunk
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
typo fixes: specfic -> specific
Signed-off-by:
Adrian Bunk
<
bunk@stusta.de
>
parent
d0f19d82
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
3 additions
and
3 deletions
+3
-3
arch/i386/mm/discontig.c
arch/i386/mm/discontig.c
+1
-1
include/asm-arm/arch-at91rm9200/board.h
include/asm-arm/arch-at91rm9200/board.h
+1
-1
sound/sparc/dbri.c
sound/sparc/dbri.c
+1
-1
No files found.
arch/i386/mm/discontig.c
View file @
d254c8f7
...
...
@@ -43,7 +43,7 @@ EXPORT_SYMBOL(node_data);
bootmem_data_t
node0_bdata
;
/*
* numa interface - we expect the numa architecture specfic code to have
* numa interface - we expect the numa architecture spec
i
fic code to have
* populated the following initialisation.
*
* 1) node_online_map - the map of all nodes configured (online) in the system
...
...
include/asm-arm/arch-at91rm9200/board.h
View file @
d254c8f7
...
...
@@ -20,7 +20,7 @@
/*
* These are data structures found in platform_device.dev.platform_data,
* and describing board-specfic data needed by drivers. For example,
* and describing board-spec
i
fic data needed by drivers. For example,
* which pin is used for a given GPIO role.
*
* In 2.6, drivers should strongly avoid board-specific knowledge so
...
...
sound/sparc/dbri.c
View file @
d254c8f7
...
...
@@ -46,7 +46,7 @@
*
* I've tried to stick to the following function naming conventions:
* snd_* ALSA stuff
* cs4215_* CS4215 codec specfic stuff
* cs4215_* CS4215 codec spec
i
fic stuff
* dbri_* DBRI high-level stuff
* other DBRI low-level stuff
*/
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment