Tags give the ability to mark specific points in history as being important
-
watchdog-wim-v4.9
39487f66 · ·Watchdog patches for v4.9 * a new watchdog pretimeout governor framework * support to upload the firmware on the ziirave_wdt * several fixes and cleanups
-
-
4.7-muqss111
94a57bad · · -
-
xfs-reflink-for-linus-4.9-rc1
feac470e · ·xfs: reflink update for 4.9-rc1 < XFS has gained super CoW powers! > ---------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || Included in this update: - unshare range (FALLOC_FL_UNSHARE) support for fallocate - copy-on-write extent size hints (FS_XFLAG_COWEXTSIZE) for fsxattr interface - shared extent support for XFS - copy-on-write support for shared extents - copy_file_range support - clone_file_range support (implements reflink) - dedupe_file_range support - defrag support for reverse mapping enabled filesystems -
-
-
-
libnvdimm-for-4.9
e476f944 · ·libnvdimm for 4.9 * PMEM sub-division support: Allow a single PMEM region to be divided into multiple namespaces. Originally, ~2 years ago, it was thought that partitions of a /dev/pmemX block device could handle sub-allocations of persistent memory for different use cases. With the decision to not support DAX mappings of raw block-devices, and the genesis of device-dax, the need for having multiple pmem-namespace per region has grown. * Device-DAX unified inode: In support of dynamic-resizing of a device-dax instance the kernel arranges for all mappings of a device-dax node to share the same inode. This allows unmap / truncate / invalidation events to affect all instances of the device similar to the behavior of mmap on block devices. * Hardware error scrubbing reworks: The original address-range-scrub + badblocks tracking solution allowed clearing entries at the individual namespace level, but it failed to clear the internal list of media errors maintained at the bus level. The result was that the next scrub or namespace disable/re-enable event would restore the cleared badblocks, but now that is fixed. The v4.8 kernel introduced an auto-scrub-on-machine-check behavior to repopulate the badblocks list. Now, in v4.9, the auto-scrub behavior can be disabled and simply arrange for the error reported in the machine-check to be added to the list. * DIMM health-event notification support: ACPI 6.1 defines a notification event code that can be send to ACPI NVDIMM devices. A poll(2) capable file descriptor for these events can be obtained from the nmemX/nfit/flags sysfs-attribute of a libnvdimm memory device. * Miscellaneous fixes: NVDIMM-N probe error, device-dax build error, and a change to dedup the flush hint list to not flush the memory controller more than necessary.
-
drm-intel-next-2016-10-10
738bb80e · ·- dsi/backlight fixes (Jani&Shawn) - a few reset improvements (Ben, Chris, Imre) - refactor port tracking for audio support (Dhinakaran) - a pile of gen9 wm fixes from Paulo - drop skl pre-production w/a (Jani) - refactor forcewake and shadow reg filters into tables, and unify the funcs/macros using them across platforms (Tvrtko) - fix DP detection to not require an edid (Ville) - register shadow VGA port (for testing), from Ville
-
-
-
-
xfs-for-linus-4.9-rc1
155cd433 · ·xfs: updates for 4.9-rc1 Included in this update: - change of XFS mailing list to linux-xfs@vger.kernel.org - iomap-based DAX infrastructure w/ XFS and ext2 support - small iomap fixes and additions - more efficient XFS delayed allocation infrastructure based on iomap - a rework of log recovery writeback scheduling to ensure we don't fail recovery when trying to replay items that are already on disk - some preparation patches for upcoming reflink support - configurable error handling fixes and documentation - aio access time update race fixes for XFS and generic_file_read_iter