[PATCH v3] DM: dm-inplace-compress: inplace compressed DM target

This patch provides a generic device-mapper compression device. Originally written by Shaohua Li. https://www.redhat.com/archives/dm-devel/2013-December/msg00143.html I have optimized and hardened the code. Testing: --- This compression block device is tested in the following

[PATCH v3 1/1] DM: inplace compressed DM target

This is a simple DM target supporting inplace compression. Its best suited for SSD. The underlying disk must support 512B sector size. The target only supports 4k sector size. Disk layout: |super|...meta...|..data...| Store unit is 4k (a block). Super is 1 block, which stores meta and data size

Re: [PATCH v8 07/12] dt-bindings: i2c: i2c-mux-simple: document i2c-mux-simple bindings

On 2017-01-30 18:20, Rob Herring wrote: > On Sat, Jan 28, 2017 at 4:42 PM, Peter Rosin wrote: >> On 2017-01-27 20:39, Rob Herring wrote: >>> On Wed, Jan 18, 2017 at 04:57:10PM +0100, Peter Rosin wrote: Describe how a generic multiplexer controller is used to mux an i2c bus.

Re: [PATCH 2/3] doc-rst: Delete output of failed dot-SVG conversion

On Tue, 31 Jan 2017, Ben Hutchings wrote: > As we use redirection to create the SVG file, even a failed conversion > will create the file and 'make' will consider it up-to-date if the > build is retried. We should delete it in case of failure. > > Fixes: ec868e4ee2bc

Re: Sphinx builds always write to the source directory

On Tue, 31 Jan 2017, Ben Hutchings wrote: > I'm having trouble with the Debian packaging of kernel documentation. > We try to build everything in a separate output directory (underneath > debian/build), but the new Sphinx-based build system writes to the > source directory.

[PATCH 3/3] doc-rst: Fix recursive make invocation from macros

In any case where we recurse but don't mention $(MAKE) literally in the recipe, we need to add a '+' at the start of the command to ensure that parallel makes and various other options work properly. Fixes: 609afe6b49ef ("Documentation/sphinx: build the media intermediate ...") Signed-off-by: Ben

[PATCH 0/3] doc-rst: Build fixes

This series fixes some bugs I found in the new doc build system. Ben. Ben Hutchings (3): doc-rst: Break shell command sequences on failure doc-rst: Delete output of failed dot-SVG conversion doc-rst: Fix recursive make invocation from macros Documentation/Makefile.sphinx | 16

[PATCH linux v5 2/6] hwmon: occ: Add sysfs interface

From: "Edward A. James" Add a generic mechanism to expose the sensors provided by the OCC in sysfs. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery --- Documentation/hwmon/occ | 62 +++

[PATCH linux v5 0/6] drivers: hwmon: Add On-Chip Controller driver

From: "Edward A. James" This patchset adds a hwmon driver to support the OCC (On-Chip Controller) on the IBM POWER8 and POWER9 processors, from a BMC (Baseboard Management Controller). The OCC is an embedded processor that provides real time power and thermal monitoring. The

[PATCH linux v5 1/6] hwmon: Add core On-Chip Controller support for POWER CPUs

From: "Edward A. James" Add core support for polling the OCC for it's sensor data and parsing that data into sensor-specific information. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery --- Documentation/hwmon/occ| 40

[RFC] tty: pl011: Work around stuck BUSY bit on QDF2400

N.B. I'm not confident that this patch is ready to be included as-is. Rather I'm hoping for guidance from reviewers and maintainers on broad implementation choices--whether A) the bitmask of flags to invert makes sense or B) vendor-specific is_busy() function pointers or C) hot-patching using the

[PATCH linux v5 5/6] hwmon: occ: Add hwmon implementation for the P8 OCC

From: "Edward A. James" Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as well as probe the entire driver from the I2C bus. I2C is the communication method between the BMC and the P8 OCC. Signed-off-by: Edward A. James

[PATCH v5 2/2] arm64: Work around Falkor erratum 1009

During a TLB invalidate sequence targeting the inner shareable domain, Falkor may prematurely complete the DSB before all loads and stores using the old translation are observed. Instruction fetches are not subject to the conditions of this erratum. If the original code sequence includes multiple

[PATCH v5 1/2] arm64: Work around Falkor erratum 1003

The Qualcomm Datacenter Technologies Falkor v1 CPU may allocate TLB entries using an incorrect ASID when TTBRx_EL1 is being updated. When the erratum is triggered, page table entries using the new translation table base address (BADDR) will be allocated into the TLB using the old ASID. All

Sphinx builds always write to the source directory

I'm having trouble with the Debian packaging of kernel documentation. We try to build everything in a separate output directory (underneath debian/build), but the new Sphinx-based build system writes to the source directory. Firstly, Python creates bytecode files alongside the module sources.

Re: [PATCH v5 4/4] sparc64: Add support for ADI (Application Data Integrity)

From: Khalid Aziz Date: Wed, 25 Jan 2017 12:57:16 -0700 > +static inline void enable_adi(void) > +{ ... > + __asm__ __volatile__( > + "rdpr %%pstate, %%g1\n\t" > + "or %%g1, %0, %%g1\n\t" > + "wrpr %%g1, %%g0, %%pstate\n\t" > +

Re: [PATCH v4 2/4] arm64: Work around Falkor erratum 1003

Hi Mark, On 01/30/2017 05:56 AM, Mark Rutland wrote: > Hi, > > On Fri, Jan 27, 2017 at 04:52:23PM -0500, Christopher Covington wrote: >> On 01/27/2017 09:38 AM, Mark Rutland wrote: >>> On Wed, Jan 25, 2017 at 10:52:30AM -0500, Christopher Covington wrote: > Replacing the above sequence

Re: [PATCH v8 07/12] dt-bindings: i2c: i2c-mux-simple: document i2c-mux-simple bindings

On Sat, Jan 28, 2017 at 4:42 PM, Peter Rosin wrote: > On 2017-01-27 20:39, Rob Herring wrote: >> On Wed, Jan 18, 2017 at 04:57:10PM +0100, Peter Rosin wrote: >>> Describe how a generic multiplexer controller is used to mux an i2c bus. >>> >>> Acked-by: Jonathan Cameron

Re: [PATCH] Documentation/sphinx: make targets independent of Sphinx work for HAVE_SPHINX=0

On Mon, 30 Jan 2017, Jani Nikula wrote: > Make targets that don't depend on Sphinx work without warnings about > missing Sphinx. 'make cleandocs' will work without Sphinx just fine, and > the targets that are no-ops for Sphinx should just be skipped. Move them > outside of

[PATCH] Documentation/sphinx: make targets independent of Sphinx work for HAVE_SPHINX=0

Make targets that don't depend on Sphinx work without warnings about missing Sphinx. 'make cleandocs' will work without Sphinx just fine, and the targets that are no-ops for Sphinx should just be skipped. Move them outside of the HAVE_SPHINX checks to take precedence over the .DEFAULT target for

Re: [PATCH v8 12/12] mux: support simplified bindings for single-user gpio mux

On 2017-01-27 16:52, Rob Herring wrote: > On Mon, Jan 23, 2017 at 11:24:18AM +0100, Peter Rosin wrote: >> On 2017-01-22 14:30, Jonathan Cameron wrote: >>> On 18/01/17 15:57, Peter Rosin wrote: Allow bindings for a GPIO controlled mux to be specified in the mux consumer node.