aboutsummaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorDenis ChengRq <crquan@gmail.com>2008-08-04 09:51:40 +0800
committerSam Ravnborg <sam@ravnborg.org>2008-08-06 22:17:06 +0200
commit64a99d2a8c3ed5c4e39f3ae1cc682aa8fd3977fc (patch)
treeb36eaea204e2d8b66431497c9a5a1c2ad6125c25 /drivers
parent0b0de144333fca335a0111a6f9c59176ad43ba0a (diff)
downloadkernel_samsung_crespo-64a99d2a8c3ed5c4e39f3ae1cc682aa8fd3977fc.zip
kernel_samsung_crespo-64a99d2a8c3ed5c4e39f3ae1cc682aa8fd3977fc.tar.gz
kernel_samsung_crespo-64a99d2a8c3ed5c4e39f3ae1cc682aa8fd3977fc.tar.bz2
kbuild: a better way to generate cscope database change
It's a problem about cscope target of kernel Makefile, and the cscope plugin of emacs: 1. `make cscope` will generate cscope.files cscope.{in,po,}.out; 2. the cscope plugin expect a cscope.out.{in,po,}; 3. the default `cscope -b` would generate cscope.{in,po,}.out; There are three approach to solve it: 1. modify the cscope C code; 2. modify the cscope emacs plugin lisp code; 3. modify the Makefile; I have tried to communicate with the cscope upstream, but later I realize the third approach is most meaningful. Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions