linux-kernel - [GIT]: Sparc fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 26 Jun 2009 00:29:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	torvalds@...ux-foundation.org
CC:	akpm@...ux-foundation.org, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [GIT]: Sparc fixes


1) Moving kmalloc initialization earlier created some bootup
   warnings on sparc64, fix.

2) The sparc port merge caused various regressions in the less
   used boot Makefile targets, only noticed recently.  Fixed by
   Sam Ravnborg, Robert Reif, and Julian Calaby who pulled all of
   these fixed together.

Please pull, thanks a lot!

The following changes since commit 28d0325ce6e0a52f53d8af687e6427fee59004d3:
  Linus Torvalds (1):
        Linux 2.6.31-rc1

are available in the git repository at:

  master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6.git master

David S. Miller (1):
      sparc64: Don't use alloc_bootmem() in init_IRQ() code paths.

Julian Calaby (3):
      sparc64: Fix build warnings in piggyback_64.c
      sparc32: Fix tftpboot.img Makefile
      sparc32: Fix makefile not generating required files

Robert Reif (1):
      sparc32: Fix obvious build issues for tftpboot.img build.

Sam Ravnborg (1):
      sparc: fix tftpboot.img build

 arch/sparc/boot/Makefile       |    6 ++--
 arch/sparc/boot/piggyback_32.c |    4 +-
 arch/sparc/boot/piggyback_64.c |    1 +
 arch/sparc/kernel/irq_64.c     |   45 ++++++++++++++++-----------------------
 4 files changed, 25 insertions(+), 31 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/