Eric Lee / smarc-fsl-linux-kernel

11 Mar, 2010

1 commit

  • ef8ff89b5   kbuild: Really don't clean bounds.h and asm-offsets.h ... Browse Code »

    Commit 7d3cc8b tried to keep bounds.h and asm-offsets.h during make
    clean by filtering these out of $(clean-files), but they are listed in
    $(targets) and $(always) and thus removed automatically. Introduce a new
    $(no-clean-files) variable to really skip such files in Makefile.clean.

    Signed-off-by: Michal Marek

    Michal Marek
     

26 Apr, 2008

1 commit

13 Oct, 2007

1 commit

  • 836caba77   kbuild: kill backward compatibility checks ... Browse Code »

    These checks has been present for several kernel releases (> 5).
    So lets just get rid of them.
    With this we no longer check for use of:
    EXTRA_TARGETS, O_TARGET, L_TARGET, list-multi, export-objs

    There were three remaining in-tree users of O_TARGET in some
    unmaintained sh64 code - mail sent to the maintainer + list.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

06 Mar, 2006

1 commit

  • 4f1933620   kbuild: change kbuild to not rely on incorrect GNU make behavior ... Browse Code »

    The kbuild system takes advantage of an incorrect behavior in GNU make.
    Once this behavior is fixed, all files in the kernel rebuild every time,
    even if nothing has changed. This patch ensures kbuild works with both
    the incorrect and correct behaviors of GNU make.

    For more details on the incorrect behavior, see:

    http://lists.gnu.org/archive/html/bug-make/2006-03/msg00003.html

    Changes in this patch:
    - Keep all targets that are to be marked .PHONY in a variable, PHONY.
    - Add .PHONY: $(PHONY) to mark them properly.
    - Remove any $(PHONY) files from the $? list when determining whether
    targets are up-to-date or not.

    Signed-off-by: Paul Smith
    Signed-off-by: Sam Ravnborg

    Paul Smith
     

28 Jul, 2005

1 commit

  • db8c1a7b2   kbuild: fix building external modules ... Browse Code »

    kbuild failed to locate Makefile for external modules.
    This brought to my attention how the variables for directories
    have different values in different usage scenarios.

    Different kbuild usage scenarios:
    make - plain make in same directory where kernel source lives
    make O= - kbuild is told to store output files in another directory
    make M= - building an external module
    make O= M= - building an external module with kernel output seperate from src

    Value assigned to the different variables:

    |$(src) |$(obj) |$(srctree) |$(objtree)
    make |reldir to k src |as src |abs path to k src |abs path to k src
    make O= |reldir to k src |as src |abs path to k src |abs path to output dir
    make M= |abs path to src |as src |abs path to k src |abs path to k src
    make O= M= |abs path to src |as src |abs path to k src |abs path to k output

    path to kbuild file:

    make | $(srctree)/$(src), $(src)
    make O= | $(srctree)/$(src)
    make M= | $(src)
    make O= M= | $(src)

    From the table above it can be seen that the only good way to find the
    home directory of the kbuild file is to locate the one of the two variants
    that is an absolute path. If $(src) is an absolute path (starts with /)
    then use it, otherwise prefix $(src) with $(srctree).

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

26 Jul, 2005

2 commits

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds