1. 20 Aug, 2014 1 commit
  2. 18 Jun, 2014 1 commit
  3. 09 Jun, 2014 1 commit
  4. 26 Aug, 2013 1 commit
    • Stuart Longland's avatar
      kbuild: Add MIPS specific files to generated package. · 7848ea79
      Stuart Longland authored
      A lot of 64-bit systems supported by Linux/MIPS have boot firmware or
      bootloaders that only understand 32-bit ELF files, and as such, the vmlinux.32
      target exists to support these systems.  Therefore, it'd be nice if the tar-pkg
      target recognised this, and included the right version when packaging up a
      binary of the kernel.
      This updates buildtar to support MIPS targets.  MIPS may use 'vmlinux'
      or 'vmlinux.32' depending on the target system.  This uses 'vmlinux.32'
      in preference to 'vmlinux' where present (although I should check which
      is newer), including either file as /boot/vmlinux-${version}.
      Cc: linux-mips@linux-mips.org
      Cc: linux-kernel@vger.kernel.org
      Patchwork: https://patchwork.linux-mips.org/patch/1673/Signed-off-by: default avatarRalf Baechle <ralf@linux-mips.org>
  5. 08 Apr, 2013 1 commit
    • Borislav Petkov's avatar
      buildtar: Add ARCH to the archive name · 6bc6c940
      Borislav Petkov authored
      When dealing with multiple sub-arches (like 32- and 64-bit on x86, for
      example) generating a bunch of kernel tar archives with the same name
      but for different sub-arches could get confusing and error-prone. Also,
      the build process could overwrite otherwise unrelated builds and you
      probably don't want that. So, add the architecture to the archive name
      for more clarity and less shoot-yourself-in-the-foot practices.
      Signed-off-by: default avatarBorislav Petkov <bp@suse.de>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
  6. 27 Sep, 2012 2 commits
  7. 31 Mar, 2011 1 commit
  8. 09 Mar, 2011 1 commit
  9. 12 Dec, 2009 1 commit
    • Michal Marek's avatar
      scripts/package: tar-pkg: use tar --owner=root · 91d16185
      Michal Marek authored
      Use the --owner= and --group= options to make sure the entries in
      the built tar file are owned by root.  Without this change, a
      careless sysadmin using the tar-pkg target can easily end up
      installing a kernel that is writable by the unprivileged user
      account used to build the kernel.
      Test that these options are understood before using them so that
      non-GNU versions of tar can still be used if the operator is
      appropriately cautious.
      Signed-off-by: default avatarJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
  10. 02 Apr, 2009 1 commit
  11. 28 Jan, 2008 1 commit
  12. 21 May, 2007 1 commit
  13. 01 Jan, 2006 1 commit
  14. 12 Jul, 2005 1 commit