MFC r249622:
Make siis(4) and mvs(4) send bus_get_dma_tag() requests to parent buses
passing real bus' child pointers instead of grandchilds.
MFC r244981 (by jfv)
Add Intel Lynx Point PCH SMBus Device IDs
MFC r253475 (by jfv):
Add new Coleto Creek device support: SATA, SMBus, and Watchdog devices.
MFC r253647:
Decode some bits defined in AHCI 1.3.1 Device Sleep Technical Proposal.
For now this is only conmetics to report HBA capabilities (Haswell?).
MFC r254987 (by gavin):
Support the PCI-Express SSD in the new MacBook Air (model A1465)
MFC r250576 (by eadler):
Fix several typos

PR:		kern/176054
MFC r253644:
Add missing NULL check after malloc(M_NOWAIT).
MFC r249065 (by trasz):
Fix locking problem in ctl_maintenance_in() - one cannot use M_WAITOK or call
ctl_done() with mutex held.
MFC r254378 (by trasz):
Turn comments about locking into actual lock assertions.
MFC r254787:
Remove locking from taskqueue_member().  The list of threads is static
during the taskqueue life cycle, so there is no need to protect it,
taking quite congested lock several more times for each ZFS I/O.
MFC r239710 (by glebius):
Fix function name in keg_cachespread_init() assert.
MFC r240676 (by glebius):
If caller specifies UMA_ZONE_OFFPAGE explicitly, then do not waste memory
in an allocation for a slab.
MFC r246087 (by glebius):
Fix typo in debug printf.
MFC r257805, r257806, r257807:

r257805:
  Add a 'mini-memstick.img' release target, which will use the
  'bootonly.iso' components to create a smaller memory stick image.

  This is useful for system recovery, where a full memstick.img image
  is not necessarily needed (or wanted).  In addition, it is possible to
  do bootonly-style installation, where the base.txz, kernel.txz, etc.
  are fetched from a remote source.

  Provide backwards-compatible target (mini-memstick), to keep in sync
  with the targets documented in release/Makefile.

r257806:
  Remove extra target from 'memstick' in r257805.

r257807:
  Update release(7) to include 'mini-memstick' target.

Sponsored by:	The FreeBSD Foundation
MFC r257942, r258101:

r257942:
  Fix a few style nits.

r258101:
  Since the doc/ toolchain conversion to docbook 5.0, JADETEX
  is no longer a valid option, so remove 'WITHOUT_JADETEX=yes'
  from PBUILD_FLAGS.

  While here, also remove 'WITHOUT_X11=yes', since it will
  cause a dependency conflict by requiring both print/ghostscript9
  and print/ghostscript9-nox11.

  Switch to OPTIONSNG format (WITHOUT_* -> OPTIONS_UNSET='FOO'),
  and unset the FOP option, which requires Java (although it is
  disabled by default).  Also unset the 'IGOR' option, since
  textproc/igor is a validation tool, not necessarily a dependency
  of the doc/ build itself.

  While here, reduce the line length of PBUILD_FLAGS.

Sponsored by:	The FreeBSD Foundation
MFC r257874:

Fix extattr(2) MLINKS.
MFC 226145,226147,226148,226150,226151,226153,226157,226158,226164,226246,
226262,226329,226344,226608:
Merge most "infrastructure" changes to kdump to make other MFC's to add
new decodings, etc. easier:
- Some of the #defines or enums for which we auto-generate naming
  functions may be wider than int, so use intmax_t throughout.
- Auto-generate kdump_subr.h.
- Use a switch statement instead of a giant if-else.
- Remove a lot of (void) casts.
- Bring ioctlname() in line with all the other *name() functions, which
  actually print the name (or the numeric value, if they can't figure out
  the correct name) instead of just returning a pointer to it.  Also, since
  ioctl numbers are not and probably never will be unique, drop support for
  using a switch statement instead of an if/else chain.
- Mostly WARNS=6 clean.
- Update mkioctls to still work with both kdump and truss.
libcpp: Keep a record of changes from upstream GCC (pre-43).

This makes it easier to track the changes in the rare event of the code
being distributed without access to version control.

MFC after:	3 weeks
Revert r258528: wrong tree

Inofensive as it is, this was meant for current. It will be re-merged
along with related changes in 3 weeks.
MFC r258353: zfs page_busy: fix the boundaries of the cleared range

This is a fix for a regression introduced in r246293.

vm_page_clear_dirty expects the range to have DEV_BSIZE aligned boundaries,
otherwise it extends them.  Thus it can happen that the whole page is
marked clean while actually having some small dirty region(s).
This commit makes the range properly aligned and ensures that only
the clean data is marked as such.

It would interesting to evaluate how much benefit clearing with DEV_BSIZE
granularity produces.  Perhaps instead we should clear the whole page
when it is completely overwritten and don't bother clearing any bits
if only a portion a page is written.