Tags

5422_4.4.4_v3.6

5422_4.4.4_v3.8

xfs-for-linus-4.6-rc1

xfs: Changes for 4.6-rc1

Change summary:
o error propagation for direct IO failures fixes for both XFS and ext4
o new quota interfaces and XFS implementation for iterating all the quota IDs
  in the filesystem
o locking fixes for real-time device extent allocation
o reduction of duplicate information in the xfs and vfs inode, saving roughly
  100 bytes of memory per cached inode.
o buffer flag cleanup
o rework of the writepage code to use the generic write clustering mechanisms
o several fixes for inode flag based DAX enablement
o rework of remount option parsing
o compile time verification of on-disk format structure sizes
o delayed allocation reservation overrun fixes
o lots of little error handling fixes
o small memory leak fixes
o enable xfsaild freezing again

v3.4.111

This is the 3.4.111 stable release

v3.12.57

This is the 3.12.57 stable release

v4.1.20

Linux 4.1.20

v3.18.29

Linux 3.18.29

gpio-v4.6-1

This is the bulk of GPIO changes for kernel v4.6:

Core changes:

- The gpio_chip is now a *real device*. Until now the gpio chips
  were just piggybacking the parent device or (gasp) floating in
  space outside of the device model. We now finally make GPIO chips
  devices. The gpio_chip will create a gpio_device which contains
  a struct device, and this gpio_device struct is kept private.
  Anything that needs to be kept private from the rest of the kernel
  will gradually be moved over to the gpio_device.

- As a result of making the gpio_device a real device, we have added
  resource management, so devm_gpiochip_add_data() will cut down on
  overhead and reduce code lines. A huge slew of patches convert
  almost all drivers in the subsystem to use this.

- Building on making the GPIO a real device, we add the first step
  of a new userspace ABI: the GPIO character device. We take small
  steps here, so we first add a pure *information* ABI and the tool
  "lsgpio" that will list all GPIO devices on the system and all
  lines on these devices. We can now discover GPIOs properly from
  userspace. We still have not come up with a way to actually *use*
  GPIOs from userspace.

- To encourage people to use the character device for the future,
  we have it always-enabled when using GPIO. The old sysfs ABI is
  still opt-in (and can be used in parallel), but is marked as
  deprecated. We will keep it around for the foreseeable future,
  but it will not be extended to cover ever more use cases.

Cleanup:

- Bjorn Helgaas removed a whole slew of per-architecture <asm/gpio.h>
  includes. This dates back to when GPIO was an opt-in feature and
  no shared library even existed: just a header file with proper
  prototypes was provided and all semantics were up to the arch to
  implement. These patches make the GPIO chip even more a proper
  device and cleans out leftovers of the old in-kernel API here
  and there. Still some cruft is left but it's very little now.

- There is still some clamping of return values for .get() going
  on, but we now return sane values in the vast majority of drivers
  and the errorpath is sanitized. Some patches for powerpc, blackfin
  and unicore still drop in.

- We continue to switch the ARM, MIPS, blackfin, m68k local GPIO
  implementations to use gpiochip_add_data() and cut down on code
  lines.

- MPC8xxx is converted to use the generic GPIO helpers.

- ATH79 is converted to use the generic GPIO helpers.

New drivers:

- WinSystems WS16C48

- Acces 104-DIO-48E

- F81866 (a F7188x variant)

- Qoric (a MPC8xxx variant)

- TS-4800

- SPI serializers (pisosr): simple 74xx shift registers connected
  to SPI to obtain a dirt-cheap output-only GPIO expander.

- Texas Instruments TPIC2810

- Texas Instruments TPS65218

- Texas Instruments TPS65912

- X-Gene (ARM64) standby GPIO controller

v4.4.6

This is the 4.4.6 stable release

v3.14.65

This is the 3.14.65 stable release

v3.10.101

This is the 3.10.101 stable release

5422_4.4.4_v3.5

jenkins-deb_s905_kernel-37

Jenkins Build #37

jenkins-deb_s905_kernel-36

Jenkins Build #36

jenkins-deb_kernel_c1-143

Jenkins Build #143

libnvdimm-for-4.6

libnvdimm for 4.6

1/ Asynchronous address range scrub:
Given the capacities of next generation persistent memory devices a
scrub operation to find all poison may take 10s of seconds.  We want
this scrub work to be done asynchronously with the rest of system
initialization, so we move it out of line from the NFIT probing, i.e.
acpi_nfit_add().

2/ Clear poison:
ACPI 6.1 introduces the ability to send "clear error" commands to the
ACPI0012:00 device representing the root of an "nvdimm bus".  Similar to
relocating a bad block on a disk, this support clears media errors in
response to a write.

3/ Persistent memory resource tracking:
A persistent memory range may be designated as simply "reserved" by
platform firmware in the efi/e820 memory map.  Later when the NFIT
driver loads it discovers that the range is "Persistent Memory".  The
NFIT bus driver inserts a resource to advertise that "persistent"
attribute in the system resource tree for /proc/iomem and
kernel-internal usages.

4/ Miscellaneous cleanups and fixes:
Workaround section misaligned pmem ranges when allocating a struct page
memmap, fix handling of the read-only case in the ioctl path, and clean
up block device major number allocation.

media/v4.6-1

media updates for v4.6-rc1

jenkins-deb_s905_kernel-35

Jenkins Build #35

jenkins-deb_s905_kernel-34

Jenkins Build #34

jenkins-deb_s905_kernel-33

Jenkins Build #33