linux-kernel - [PATCH 0/8] Amiga Zorro updates

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>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1381921405-11206-1-git-send-email-geert@linux-m68k.org>
Date:	Wed, 16 Oct 2013 13:03:17 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	linux-m68k@...ts.linux-m68k.org
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/8] Amiga Zorro updates

Here is a set of miscellaneous updates for the Amiga Zorro bus code:
  - [1/8] Documentation/zorro.txt: Update path to arch-specific
  - [2/8] zorro: Do not allocate zorro_autocon[] statically
          This reduces memory usage, especially for multi-platform kernels
  - [3/8] zorro: Don't fill in dummy names in zorro_name_device()
  - [4/8] zorro: Refactor conditional handling of Zorro device
  - [5/8] zorro: Let the driver core handle device enumeration
  - [6/8] zorro: ZTWO_VADDR() should return "void __iomem *"
  - [7/8] zorro/UAPI: Disintegrate include/linux/zorro*.h
          This exports the Zorro definitions (again) to bootstraps.
  - [8/8] zorro/UAPI: Use proper types (endianness/size) in

All comments are welcome!

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
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/