1. 25 Nov, 2010 1 commit
  2. 11 Nov, 2010 1 commit
  3. 13 Oct, 2010 1 commit
  4. 06 Sep, 2010 1 commit
  5. 03 Jun, 2010 3 commits
  6. 27 May, 2010 1 commit
  7. 06 May, 2010 1 commit
  8. 14 Apr, 2010 6 commits
  9. 08 Apr, 2010 1 commit
  10. 23 Mar, 2010 4 commits
  11. 11 Mar, 2010 1 commit
  12. 10 Mar, 2010 1 commit
  13. 08 Mar, 2010 2 commits
    • Michal Marek's avatar
      Revert "kbuild: specify absolute paths for cscope" · e93bc1a0
      Michal Marek authored
      This reverts commit eb8f844c. Ian
      Campbell writes:
      > I keep my kernel source tree on a more powerful build box where I run my
      > builds etc (including "make cscope") but run my editor from my
      > workstation with an NFS mount to the source. This worked fine for me
      > using relative paths for cscope. Using absolute paths in cscope breaks
      > this previously working setup because the root path is not the same on
      > both systems. I guess this is similar to moving the source tree around.
      >
      > Without wanting to start a flamewar it really sounds to me like we are
      > working around a vim (or cscope) bug here, emacs with cscope bindings
      > works fine in this configuration.
      
      Given that absolute paths can be forced by make O=. cscope, change the
      default back to relative paths.
      
      Ian Campbell <ijc@hellion.org.uk>
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      e93bc1a0
    • Michal Marek's avatar
      kbuild: Do not unnecessarily regenerate modules.builtin · a6c36632
      Michal Marek authored
      Only regenerate it if the configuration has changed. Also, do this after
      the modules build to fix errors with some weird Makefiles that are
      generated during build.
      Reported-by: default avatarEric Miao <eric.y.miao@gmail.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      a6c36632
  14. 07 Mar, 2010 9 commits
  15. 03 Mar, 2010 7 commits