[PATCH v2 19/22] ncr5380: Update usage documentation

Update kernel parameter documentation for atari_scsi, mac_scsi and g_NCR5380 drivers. Remove duplication. Signed-off-by: Finn Thain Reviewed-by: Hannes Reinecke --- Documentation/scsi/g_NCR5380.txt | 17 ++-

Re: [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on PAT / non-PAT systems"

On Sat, Mar 05, 2016 at 12:52:55PM +0100, Ingo Molnar wrote: > > * Luis R. Rodriguez wrote: > > > The current documentation refers to using set_memory_wc() as a > > possible hole strategy when you have overlapping ioremap() regions, > > The whole explanation should talk

[PULL] Documentation for 4.6

The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d: Linux 4.5-rc1 (2016-01-24 13:06:47 -0800) are available in the git repository at: git://git.lwn.net/linux.git tags/docs-for-linus for you to fetch changes up to abfa6cd8cda71b9071191e72711bd474e539b1b2:

Re: [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on PAT / non-PAT systems"

On Sat, Mar 05, 2016 at 04:39:58AM +, Elliott, Robert (Persistent Memory) wrote: > > -Original Message- > > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > > ow...@vger.kernel.org] On Behalf Of Luis R. Rodriguez > > Sent: Friday, March 04, 2016 4:45 PM > > Subject:

[RESEND PATCH v2] ARM64: ACPI: Update documentation for latest specification version

The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to

Re: [PATCH v5 1/4] i2c: add a protocol parameter to the alert callback

On Mar 15 2016 or thereabouts, Guenter Roeck wrote: > On Tue, Mar 15, 2016 at 03:53:41PM +0100, Benjamin Tissoires wrote: > > .alert() is meant to be generic, but there is currently no way > > for the device driver to know which protocol generated the alert. > > Add a parameter in .alert() to help

Re: [PATCH v5 3/4] i2c: i801: add support of Host Notify

Hi Benjamin, [auto build test ERROR on input/next] [also build test ERROR on v4.5 next-20160315] [cannot apply to wsa/i2c/for-next] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Benjamin

Re: [PATCH v5 1/4] i2c: add a protocol parameter to the alert callback

On Tue, Mar 15, 2016 at 03:53:41PM +0100, Benjamin Tissoires wrote: > .alert() is meant to be generic, but there is currently no way > for the device driver to know which protocol generated the alert. > Add a parameter in .alert() to help the device driver to understand > what is given in data. >

[PATCH v5 1/4] i2c: add a protocol parameter to the alert callback

.alert() is meant to be generic, but there is currently no way for the device driver to know which protocol generated the alert. Add a parameter in .alert() to help the device driver to understand what is given in data. This patch is required to have the support of SMBus Host Notify protocol

[PATCH v5 2/4] i2c-smbus: add SMBus Host Notify support

SMBus Host Notify allows a slave device to act as a master on a bus to notify the host of an interrupt. On Intel chipsets, the functionality is directly implemented in the firmware. We just need to export a function to call .alert() on the proper device driver. i2c_handle_smbus_host_notify()

[PATCH v5 0/4] i2c-smbus: add support for HOST NOTIFY

Hi all, This is a resent of my series sent back in September[1]. The i801 driver has been updated to also match on the skylake chip, which makes the new Lenovo working with RMI4 too. The trigger for this series has been that RMI4 (the Synaptics protocol for their devices) is on its way to v4.6.

[PATCH v5 4/4] Input: synaptics-rmi4 - add SMBus support

Code obtained from https://raw.githubusercontent.com/mightybigcar/synaptics-rmi4/jf/drivers/input/rmi4/rmi_smbus.c and updated to match upstream. And fixed to make it work. Signed-off-by: Benjamin Tissoires Signed-off-by: Andrew Duggan ---

Re: [PATCH v3] can: rcar_canfd: Add Renesas R-Car CAN FD driver

On 03/15/2016 10:48 AM, Ramesh Shanmugasundaram wrote: > This patch adds support for the CAN FD controller found in Renesas R-Car > SoCs. The controller operates in CAN FD only mode by default. > > CAN FD mode supports both Classical CAN & CAN FD frame formats. The > controller supports ISO

Re: [PATCH 00/50] pinctrl: Add and use devm_ apis for pinctrl_{register, unregister}

On Wed, Mar 9, 2016 at 3:23 PM, Laxman Dewangan wrote: >> Pushed the change at: >> Branch "devm_pinctrl_register" of >> https://github.com/ldewangan/linux-upstream.git. >> >> Base repo is >> for-next of >>