3947 zpool(1M) references nonexistent zfs-features(5)
4540 zpool(1M) man page doesn't describe "readonly" property
3948 zfs sync=default is not accepted
4611 zfs(1M) still mentions 'send -r' in synopsis
4415 zpool(1M) man page missing "import -m" description

illumos/illumos-gate@409f1c06a8ed7e94e186a77bff5bfe5f77c5ebb1
4570 Document dedupditto pool property
4572 Dedup-related documentation additions for zpool and zdb.
1371 Add -D option description to zpool(1M) manpage

illumos/illumos-gate@e902ed8e4d63380fc7ba67f74c52053dcedf7761
4571 Add documentation for -T and interval to "zpool list"

illumos/illumos-gate@b55998b6d68438193f311140cafa2104f2038571
4573 ZFS snapshot alias

illumos/illumos-gate@7dbbcd8300f0241d3ec9686f2a0a06107c1b90cb
3993 zpool(1M) and zfs(1M) should support -p for "list" and "get"
4700 "zpool get" doesn't support -H or -o options

illumos/illumos-gate@c58b352673e88983cd2b8a388a8c7625f35e2f18
4374 dn_free_ranges should use range_tree_t

(MD code for highbit64 omitted)

illumos/illumos-gate@bf16b11e8deb633dd6c4296d46e92399d1582df4
3897 zfs filesystem and snapshot limits

illumos/illumos@a2afb611b30628fb74ad9eade4ae465f9031e262
3835 zfs need not store 2 copies of all metadata

illumos/illumos-gate@edf345e6b8342e8627ec20ce821a977a62cee19d
2915 DTrace in a zone should see "cpu", "curpsinfo", et al
2916 DTrace in a zone should be able to access fds[]
2917 DTrace in a zone should have limited provider access

illumos/illumos-gate@b0f673c4626e4cb1db7785287eaeed2731dfefe8
4477 DTrace should speak JSON

illumos/illumos-gate@f497f9fe231e0e400f339c84a7d80c4aae2ac4d5
4248 dtrace(1M) should never create DOF with empty probes section
4249 Only probes from the first DTrace object file will be included

illumos/illumos-gate@54a20ab41aadcb81c53e72fc65886e964e9add59

The r258379 import of this change omitted the tests.
Don't destroy bus_dma maps created by bus_dmamem_alloc().  In some cases,
don't create a map before calling bus_dmamem_alloc() (such maps were
leaked).  It is believed that the extra destroy of the map was generally
harmless since bus_dmamem_alloc() often uses special maps for which
bus_dmamap_destroy() is a no-op (e.g. on x86).

Reviewed by:	scottl
Use bitwise OR instead of logical OR when constructing value for
SET_FEATURES/NUMBER_OF_QUEUES command.

Sponsored by:	Intel
MFC after:	3 days
Move root_mount_hold() functionality to separate mutex.

It has nothing to share with mutex protecting list of mounted file systems.
Add a driver for Serial Peripheral Interface (SPI).
Add UUIDs for DragonFlyBSD's partition types.

MFC after:	2 weeks
Add DragonFlyBSD's Hammer FS types and type names.

MFC after:	2 weeks
Add aliases for DragonFlyBSD's partition types.

MFC after:	2 weeks
Allow swapping to DragonFlyBSD's swap partition.

MFC after:	2 weeks
Add disklabel64 support to GEOM_PART class.

This partitioning scheme is used in DragonFlyBSD. It is similar to
BSD disklabel, but has the following improvements:
* metadata has own dedicated place and isn't accessible through partitions;
* all offsets are 64-bit;
* supports 16 partitions by default (has reserved place for more);
* has reserved place for backup label (but not yet implemented);
* has UUIDs for partitions and partition types;

No objections from:	geom
MFC after:	2 weeks
Relnotes:	yes