You can view, comment on, or merge this pull request online at:

  https://github.com/openzfs/openzfs/pull/509

-- Commit Summary --

  * 8930 zfs_zinactive: do not remove the node if the filesystem is readonly
  * 8801 loader: always issue our dhcp request
  * 8919 loader.efi: remove efi_main() from libefi
  * 8897 zpool online -e fails assertion when run on non-leaf vdevs
  * 8898 creating fs with checksum=skein on the boot pools fails ungracefully
  * 8899 zpool list property documentation doesn't match actual behaviour
  * 8887 loader: Document recent changes on pxeboot
  * 8935 SMB ioctl fixes incomplete
  * Merge remote-tracking branch 'illumos/master' into illumos-sync

-- File Changes --

    M usr/src/boot/lib/libstand/bootp.c (11)
    M usr/src/boot/lib/libstand/bootp.h (2)
    M usr/src/boot/sys/boot/common/dev_net.c (39)
    M usr/src/boot/sys/boot/efi/boot1/boot1.c (4)
    M usr/src/boot/sys/boot/efi/include/efiapi.h (2)
    M usr/src/boot/sys/boot/efi/include/efidevp.h (2)
    M usr/src/boot/sys/boot/efi/include/efilib.h (4)
    M usr/src/boot/sys/boot/efi/libefi/libefi.c (180)
    M usr/src/boot/sys/boot/efi/loader/Makefile (8)
    A usr/src/boot/sys/boot/efi/loader/efi_main.c (217)
    M usr/src/lib/libzfs/common/libzfs_dataset.c (6)
    M usr/src/lib/libzfs/common/libzfs_pool.c (9)
    M usr/src/man/man1m/zfs.1m (6)
    M usr/src/man/man1m/zpool.1m (14)
    M usr/src/man/man5/pxeboot.5 (48)
    M usr/src/uts/common/fs/smbsrv/smb_kshare.c (19)
    M usr/src/uts/common/fs/smbsrv/smb_server.c (13)
    M usr/src/uts/common/smbsrv/smb_ioctl.h (1)

-- Patch Links --

https://github.com/openzfs/openzfs/pull/509.patch
https://github.com/openzfs/openzfs/pull/509.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/509

------------------------------------------
openzfs-developer
Archives: 
https://openzfs.topicbox.com/groups/developer/discussions/Tdd792aa4bc2ac157-M4c8af345b743ca4524789065
Powered by Topicbox: https://topicbox.com

Reply via email to