Tags give the ability to mark specific points in history as being important
-
-
-
-
-
sunxi-dt-for-4.2-2
16b2a7d4 · ·Allwinner DT changes for 4.2, take 2 A bunch of new DT changes for the 4.2 merge window, among which: - Enable the SRAM controller on the A10/A10s/A13/A20 - A33 support - New boards: A23 EVB, SinA33, GA10H-A33, Mele A1000G
-
wireless-drivers-for-davem-2015-06-01
38fe44e6 · ·iwlwifi: * fix OTP parsing 8260 * fix powersave handling for 8260 brcmfmac: * fix null pointer crash
-
hwmon-for-linus-v4.1-rc6
c7bd6dc3 · ·Some late hwmon patches, all headed for -stable - Fix sysfs attribute initialization in nct6775 and nct6683 drivers - Do not attempt to auto-detect tmp435 on I2C address 0x37 - Ensure iio channel is of type IIO_VOLTAGE in ntc_thermistor driver
-
acpi-pci-4.1-rc6
dc4fdaf0 · ·PCI / ACPI fix for v4.1-rc6 This fixes a bug uncovered by a recent driver core change that modified the implementation of the ACPI_COMPANION_SET() macro to strictly rely on its second argument to be either NULL or a valid pointer to struct acpi_device. As it turns out, pcibios_root_bridge_prepare() on x86 and ia64 works with the assumption that the only code path calling pci_create_root_bus() is pci_acpi_scan_root() and therefore the sysdata argument passed to it will always match the expectations of pcibios_root_bridge_prepare(). That need not be the case, however, and in particular it is not the case for the Xen pcifront driver that passes a pointer to its own private data strcture as sysdata to pci_scan_bus_parented() which then passes it to pci_create_root_bus() and it ends up being used incorrectly by pcibios_root_bridge_prepare(). /
-
xfs-for-linus-4.1-rc6
22419ac9 · ·xfs: update for 4.1-rc6 Changes in this update: o regression fix for new rename whiteout code o regression fixes for new superblock generic per-cpu counter code o fix for incorrect error return sign introduced in 3.17 o metadata corruption fixes that need to go back to -stable kernels
-
-
-
-