linux-kernel - [GIT]: Sparc

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 30 Aug 2008 13:01:01 -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


Three Sparc bug fixes:

1) CONFIG_RELAY recently started using smp_call_function_single()
   even though that was not previously referenced from generic
   code.

   Anyways, add an implementation to 32-bit sparc to fix the
   build with RELAY enabled.

2) Resource flag setting fix for PCI sub-devices.

3) Section mismatch fix in sparc64 MM initialization code.

Please pull, thanks a lot!

The following changes since commit 349101da8e1f8e5eb1476b02823da80495224485:
  Martin Habets (1):
        sparc: Add target for a stripped kernel

are available in the git repository at:

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

David S. Miller (3):
      sparc32: Implement smp_call_function_single().
      sparc: Fix resource flags for PCI children in OF device tree.
      sparc64: setup_valid_addr_bitmap_from_pavail() should be __init

 arch/sparc/include/asm/smp_32.h |   25 +++++++++++++++----------
 arch/sparc/kernel/of_device.c   |   19 ++++++++++++++-----
 arch/sparc/kernel/sun4d_smp.c   |   16 ++++++++++------
 arch/sparc/kernel/sun4m_smp.c   |   12 ++++++++----
 arch/sparc64/kernel/of_device.c |   20 ++++++++++++++------
 arch/sparc64/mm/init.c          |    2 +-
 6 files changed, 62 insertions(+), 32 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/