Skip to contentSkip to conversation

Two question about kernel global function declaration and directory layout

DISCUSSION daley 2 participants 2 messages Sep 3, 2012 – Sep 4, 2012

lore
Share & tools
lore

daley

author
#0 lore raw

hi, everyone, I'm a big fan of the kernel, I was always being attracted by its clean and intelligent design. I'm new to the mailing list and this is my first post. I want to ask two basic question about kernel which bother me a lot, I've googled a lot but nobody could give a suitable answer .

The first one is about global function declaration, I was confused about the usage of keyword "extern" before a global function which declared in the header file. for example,

<include/linux/kernel.h>
extern long (*panic_blink)(int state);
__printf(1, 2)
void panic(const char *fmt, ...)

        __noreturn __cold;

extern void oops_enter(void);
extern void oops_exit(void);
void print_oops_end_marker(void);
extern int oops_may_print(void);
void do_exit(long error_code)

        __noreturn;
void complete_and_exit(struct completion *, long)
        __noreturn;

the same thing also appeared on other header files a lot. To my knowledge, there's no difference between whether has the "extern" before global function, is this due to the legacy problem or have other meaning?

The second question is why not move the *sound* directory into the *drivers* directory or put bigger subsystem out of drivers, since there are more bigger subsystems(e.g. media, scsi) than sound?

Can anybody help?
Thanks.

Signature · 2 lines
daleydeng
Beijing, China
#1 lore raw
Quoted 9 lines · daley

hi, everyone, I'm a big fan of the kernel, I was always being attracted by its clean and intelligent design. I'm new to the mailing list and this is my first post. I want to ask two basic question about kernel which bother me a lot, I've googled a lot but nobody could give a suitable answer .

The first one is about global function declaration, I was confused about the usage of keyword "extern" before a global function which declared in the header file. for example,

It specifies that the function has external linkage, which is the opposite of internal (static keyword) linkage. The default linkage for functions in external, so the extern keyword is not technically required, but many developers like to specify it explicitly. C linkage is explained here:

http://publications.gbdirect.co.uk/c_book/chapter4/linkage.html

Quoted 3 lines

The second question is why not move the *sound* directory into the *drivers* directory or put bigger subsystem out of drivers, since there are more bigger subsystems(e.g. media, scsi) than sound?

This was discussed a couple of years back, but never happened. I'm not sure what the reasons were. You can read through the discussion yourself if you are so inclined. There is an email from Linus explaining some of the historical reasons why the sound code is in sound/ and not drivers/sound:

http://lkml.indiana.edu/hypermail/linux/kernel/0805.2/3026.html

~Ryan