OpenBSD src changes summary for 2017-11-19 ==========================================
distrib/alpha distrib/amd64 distrib/arm64 distrib/armv7 distrib/hppa distrib/i386 distrib/landisk distrib/loongson distrib/luna88k distrib/macppc distrib/octeon distrib/sgi distrib/socppc distrib/sparc64 distrib/special sys/arch/amd64/amd64 sys/arch/i386/i386 sys/arch/mips64/mips64 sys/arch/sparc64/sparc64 sys/dev sys/dev/fdt == distrib =========================================================== 01/02 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib alpha ~ bsd.rd/list.local > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) amd64 ~ ramdisk_cd/list.local > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) arm64 ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) armv7 ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) hppa ~ ramdisk/list.local > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) i386 ~ ramdisk_cd/list.local > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) landisk ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) loongson ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) luna88k ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) macppc ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) octeon ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) sgi ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) socppc ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) sparc64 ~ ramdisk/list > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) special ~ Makefile + growfs/Makefile > add growfs(8) to ramdisk > Some resizing scenarios can be done from within single user mode, but > resizing the root partition required you to bring your own growfs(8) > binary into the ramdisk environment. This commit adds growfs(8) to the > ramdisks (the ones that don't have space constraints) to simplify such > operations. > OK deraadt@ (job@) == sys =============================================================== 02/02 == http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys arch/amd64/amd64 - lock_machdep.c > Remove lock_machdep.c from amd64, i386, mips64 and sparc64. > The architectures have been using the MI mplock for a while. > OK deraadt@, kettenis@ (visa@) arch/i386/i386 - lock_machdep.c > Remove lock_machdep.c from amd64, i386, mips64 and sparc64. > The architectures have been using the MI mplock for a while. > OK deraadt@, kettenis@ (visa@) arch/mips64/mips64 - lock_machdep.c > Remove lock_machdep.c from amd64, i386, mips64 and sparc64. > The architectures have been using the MI mplock for a while. > OK deraadt@, kettenis@ (visa@) arch/sparc64/sparc64 - lock_machdep.c > Remove lock_machdep.c from amd64, i386, mips64 and sparc64. > The architectures have been using the MI mplock for a while. > OK deraadt@, kettenis@ (visa@) dev ~ rnd.c > Remove interlocks between producers and consumers of randomness data > A lot of randomness event producers are executed in the interrupt > context increasing the time spent in the interrupt handler resulting > in extra costs when adding randomness data to the pool. However, in > practice randomness event producers require interlocking between each > other, but not with with consumers due to the opportunistic nature of > event consumers. > To be able to take advantage of this idea, the ring buffer indexing > is now done with two free running producer and consumer counters modulo > power of 2 size of the ring buffer. > With input from and OK visa, tb, jasper (mikeb@) dev/fdt ~ sxiccmu.c ~ sxiccmu_clocks.h > Implement support for the "next-generation" clock bindings for the > Allwinner A10/A20. (kettenis@) =============================================================================== _______________________________________________ odc mailing list [email protected] http://www.squish.net/mailman/listinfo/odc
