Re: [PATCH net-next V2 5/5] virtio-net: switch off offloads on demand if possible on XDP set

On Wed, Jul 19, 2017 at 04:54:49PM +0800, Jason Wang wrote: > Current XDP implementation wants guest offloads feature to be disabled > on device. This is inconvenient and means guest can't benefit from > offloads if XDP is not used. This patch tries to address this > limitation by disabling the

Re: [PATCH net-next V2 5/5] virtio-net: switch off offloads on demand if possible on XDP set

On Wed, Jul 19, 2017 at 04:54:49PM +0800, Jason Wang wrote: > Current XDP implementation wants guest offloads feature to be disabled > on device. This is inconvenient and means guest can't benefit from > offloads if XDP is not used. This patch tries to address this > limitation by disabling the

Re: [PATCH v3 3/9] perf annotate: Fix wrong --show-total-period option showing number of samples

On 07/25/2017 02:37 AM, Arnaldo Carvalho de Melo wrote: Em Mon, Jul 24, 2017 at 10:51:58AM +0900, Taeung Song escreveu: Hi Arnaldo, Sorry, I'm too late. On 07/21/2017 08:24 PM, Arnaldo Carvalho de Melo wrote: Em Fri, Jul 21, 2017 at 06:41:29PM +0900, Taeung Song escreveu: On 07/21/2017

Re: [PATCH v3 3/9] perf annotate: Fix wrong --show-total-period option showing number of samples

On 07/25/2017 02:37 AM, Arnaldo Carvalho de Melo wrote: Em Mon, Jul 24, 2017 at 10:51:58AM +0900, Taeung Song escreveu: Hi Arnaldo, Sorry, I'm too late. On 07/21/2017 08:24 PM, Arnaldo Carvalho de Melo wrote: Em Fri, Jul 21, 2017 at 06:41:29PM +0900, Taeung Song escreveu: On 07/21/2017

[PATCH v3 2/2] memory: ti-emif-sram: introduce relocatable suspend/resume handlers

Certain SoCs like Texas Instruments AM335x and AM437x require parts of the EMIF PM code to run late in the suspend sequence from SRAM, such as saving and restoring the EMIF context and placing the memory into self-refresh. One requirement for these SoCs to suspend and enter its lowest power mode,

[PATCH v3 2/2] memory: ti-emif-sram: introduce relocatable suspend/resume handlers

Certain SoCs like Texas Instruments AM335x and AM437x require parts of the EMIF PM code to run late in the suspend sequence from SRAM, such as saving and restoring the EMIF context and placing the memory into self-refresh. One requirement for these SoCs to suspend and enter its lowest power mode,

[PATCH v3 0/2] memory: Introduce ti-emif-sram driver

This is v3 of the series introduces a ti-emif-sram driver to be used on am335x and am437x, based on v4.13-rc2. This version addresses some comments from Russell King and Johan Hovold in v2 found here [1]. Main changes are to patch two with grouping all the driver data into a single struct and

[PATCH v3 0/2] memory: Introduce ti-emif-sram driver

This is v3 of the series introduces a ti-emif-sram driver to be used on am335x and am437x, based on v4.13-rc2. This version addresses some comments from Russell King and Johan Hovold in v2 found here [1]. Main changes are to patch two with grouping all the driver data into a single struct and

[PATCH v3 1/2] Documentation: dt: Update ti,emif bindings

Update the Texas Instruments EMIF binding document to include the device tree bindings for ti,emif-am3352 and ti,emif-am4372 which are used by the ti-emif-sram driver to provide low-level PM functionality. Acked-by: Rob Herring Acked-by: Tony Lindgren

[PATCH v3 1/2] Documentation: dt: Update ti,emif bindings

Update the Texas Instruments EMIF binding document to include the device tree bindings for ti,emif-am3352 and ti,emif-am4372 which are used by the ti-emif-sram driver to provide low-level PM functionality. Acked-by: Rob Herring Acked-by: Tony Lindgren Signed-off-by: Dave Gerlach ---

Re: [PATCH] kthread: Fix documentation build warning

On 07/24/2017 12:59 PM, Jonathan Corbet wrote: > The kerneldoc comment for kthread_create() had an incorrect argument name, > leading to a warning in the docs build. Correct it, and make one more > small step toward a warning-free build. > > Signed-off-by: Jonathan Corbet > ---

Re: [PATCH] kthread: Fix documentation build warning

On 07/24/2017 12:59 PM, Jonathan Corbet wrote: > The kerneldoc comment for kthread_create() had an incorrect argument name, > leading to a warning in the docs build. Correct it, and make one more > small step toward a warning-free build. > > Signed-off-by: Jonathan Corbet > --- >

Re: [PATCH 02/37] binder: use group leader instead of open thread

On Mon, Jul 24, 2017 at 02:00:45PM -0700, John Stultz wrote: > On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote: > > The binder allocator assumes that the thread that > > called binder_open will never die for the lifetime of > > that proc. That thread is normally the

Re: [PATCH 02/37] binder: use group leader instead of open thread

On Mon, Jul 24, 2017 at 02:00:45PM -0700, John Stultz wrote: > On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote: > > The binder allocator assumes that the thread that > > called binder_open will never die for the lifetime of > > that proc. That thread is normally the group_leader, > > however it

[PATCH 1/2] HID: multitouch: Support HID_GD_WIRELESS_RADIO_CTLS

Some keyboard + touchpad devices have the Microsoft Win8 Wireless Radio Controls extensions Usage Page define in the touchpad report descriptor, so we need to support them in this driver. Signed-off-by: João Paulo Rechi Vita --- drivers/hid/hid-multitouch.c | 6 +- 1

[PATCH 2/2] HID: multitouch: Support Asus T304UA media keys

The Asus T304UA convertible sports a magnetic detachable keyboard with touchpad, which is connected over USB. Most of the keyboard hotkeys are exposed through the same USB interface as the touchpad, defined in the report descriptor as follows: 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined

[PATCH 1/2] HID: multitouch: Support HID_GD_WIRELESS_RADIO_CTLS

Some keyboard + touchpad devices have the Microsoft Win8 Wireless Radio Controls extensions Usage Page define in the touchpad report descriptor, so we need to support them in this driver. Signed-off-by: João Paulo Rechi Vita --- drivers/hid/hid-multitouch.c | 6 +- 1 file changed, 5

[PATCH 2/2] HID: multitouch: Support Asus T304UA media keys

The Asus T304UA convertible sports a magnetic detachable keyboard with touchpad, which is connected over USB. Most of the keyboard hotkeys are exposed through the same USB interface as the touchpad, defined in the report descriptor as follows: 0x06, 0x31, 0xFF, // Usage Page (Vendor Defined

[PATCH 0/2] HID: multitouch: Support Asus T304UA media keys

The Asus T304UA convertible sports a magnetic detachable keyboard with touchpad, which is connected over USB. Most of the keyboard hotkeys are exposed through the same USB interface as the touchpad. The mapping defined here is the same present in hid-asus, but when using hid-asus to drive this

[PATCH 0/2] HID: multitouch: Support Asus T304UA media keys

The Asus T304UA convertible sports a magnetic detachable keyboard with touchpad, which is connected over USB. Most of the keyboard hotkeys are exposed through the same USB interface as the touchpad. The mapping defined here is the same present in hid-asus, but when using hid-asus to drive this

Re: [v3] mm: Add SLUB free list pointer obfuscation

>From 86f4f1f6deb76849e00c761fa30eeb479f789c35 Mon Sep 17 00:00:00 2001 From: Alexander Popov Date: Mon, 24 Jul 2017 23:16:28 +0300 Subject: [PATCH 2/2] mm/slub.c: add a naive detection of double free or corruption On 06.07.2017 03:27, Kees Cook wrote: > This SLUB free

Re: [v3] mm: Add SLUB free list pointer obfuscation

>From 86f4f1f6deb76849e00c761fa30eeb479f789c35 Mon Sep 17 00:00:00 2001 From: Alexander Popov Date: Mon, 24 Jul 2017 23:16:28 +0300 Subject: [PATCH 2/2] mm/slub.c: add a naive detection of double free or corruption On 06.07.2017 03:27, Kees Cook wrote: > This SLUB free list pointer obfuscation

[PATCH] perf: qcom_l2: fix column exclusion check

The check for column exclusion did not verify that the event being checked was an L2 event, and not a software event. Software events should not be checked for column exclusion. This resulted in a group with both software and L2 events sometimes incorrectly rejecting the L2 event for column

[PATCH] perf: qcom_l2: fix column exclusion check

The check for column exclusion did not verify that the event being checked was an L2 event, and not a software event. Software events should not be checked for column exclusion. This resulted in a group with both software and L2 events sometimes incorrectly rejecting the L2 event for column

Re: pull-request: wireless-drivers 2017-07-21

From: Kalle Valo Date: Fri, 21 Jul 2017 19:12:54 +0300 > important fixes for net which had accumulated while I was away. I only > applied the brcmfmac and rtlwifi patches only eight hours ago and I > haven't seen the kbuild report yet so they might have some build >

Re: pull-request: wireless-drivers 2017-07-21

From: Kalle Valo Date: Fri, 21 Jul 2017 19:12:54 +0300 > important fixes for net which had accumulated while I was away. I only > applied the brcmfmac and rtlwifi patches only eight hours ago and I > haven't seen the kbuild report yet so they might have some build > breakage in theory. But the

[PATCH v2 2/6] mei: Switch to use new generic UUID API

From: Andy Shevchenko There are new types and helpers that are supposed to be used in new code. As a preparation to get rid of legacy types and API functions do the conversion here. Cc: Tomas Winkler Cc: Guenter Roeck

[PATCH v2 2/6] mei: Switch to use new generic UUID API

From: Andy Shevchenko There are new types and helpers that are supposed to be used in new code. As a preparation to get rid of legacy types and API functions do the conversion here. Cc: Tomas Winkler Cc: Guenter Roeck Cc: Samuel Ortiz Signed-off-by: Andy Shevchenko Signed-off-by: Tomas

Re: [PATCH 00/10] percpu: replace percpu area map allocator with bitmap allocator

Hi Josef, On Tue, Jul 18, 2017 at 03:15:28PM -0400, Josef Bacik wrote: > Ok so you say that this test is better for the area map allocator, so > presumably > this is worst case for the bitmap allocator? What does the average case look > like? The bitmap allocator should perform relatively

Re: [PATCH 00/10] percpu: replace percpu area map allocator with bitmap allocator

Hi Josef, On Tue, Jul 18, 2017 at 03:15:28PM -0400, Josef Bacik wrote: > Ok so you say that this test is better for the area map allocator, so > presumably > this is worst case for the bitmap allocator? What does the average case look > like? The bitmap allocator should perform relatively

[PATCH 3/3] selftests: sync: convert to use TAP13 ksft framework

Convert test to use TAP13 ksft framework. Output after conversion: TAP version 13 # [RUN] Testing sync framework ok 1 [RUN] test_alloc_timeline ok 2 [RUN] test_alloc_fence ok 3 [RUN] test_alloc_fence_negative ok 4 [RUN] test_fence_one_timeline_wait ok 5 [RUN]

[PATCH 3/3] selftests: sync: convert to use TAP13 ksft framework

Convert test to use TAP13 ksft framework. Output after conversion: TAP version 13 # [RUN] Testing sync framework ok 1 [RUN] test_alloc_timeline ok 2 [RUN] test_alloc_fence ok 3 [RUN] test_alloc_fence_negative ok 4 [RUN] test_fence_one_timeline_wait ok 5 [RUN]

[PATCH 2/3] selftests: kselftest framework: add API to return pass/fail/* counts

Some tests print final pass/fail message based on fail count. Add ksft_get_*_cnt() API to kselftest framework to return counts. Update ksft_print_cnts() to print the test results summary message with individual pass, fail, ... counters. Signed-off-by: Shuah Khan ---

[PATCH 1/3] selftests: sync: differentiate between sync unsupported and access errors

Sync test doesn't differentiate between sync unsupported and test run by non-root user and treats both as unsupported cases. Fix it to add handling for these two different scenarios. Signed-off-by: Shuah Khan --- tools/testing/selftests/sync/sync_test.c | 23

[PATCH 2/3] selftests: kselftest framework: add API to return pass/fail/* counts

Some tests print final pass/fail message based on fail count. Add ksft_get_*_cnt() API to kselftest framework to return counts. Update ksft_print_cnts() to print the test results summary message with individual pass, fail, ... counters. Signed-off-by: Shuah Khan ---

[PATCH 1/3] selftests: sync: differentiate between sync unsupported and access errors

Sync test doesn't differentiate between sync unsupported and test run by non-root user and treats both as unsupported cases. Fix it to add handling for these two different scenarios. Signed-off-by: Shuah Khan --- tools/testing/selftests/sync/sync_test.c | 23 +++ 1 file

[PATCH 0/3] selftests: sync test conversion to TAP13

This patch series includes patches to convert sync test to use TAP13 ksft framework. In addition, fix to sync test to differentiate between unsupported feature and access error when a non-root user runs it. Updated kfst framework to return counters for sync test to use to print the final pass or

[PATCH 0/3] selftests: sync test conversion to TAP13

This patch series includes patches to convert sync test to use TAP13 ksft framework. In addition, fix to sync test to differentiate between unsupported feature and access error when a non-root user runs it. Updated kfst framework to return counters for sync test to use to print the final pass or

Re: [PATCH 02/37] binder: use group leader instead of open thread

On Mon, Jul 24, 2017 at 2:00 PM, John Stultz wrote: > On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote: >> The binder allocator assumes that the thread that >> called binder_open will never die for the lifetime of >> that proc. That thread is normally

Re: [PATCH 02/37] binder: use group leader instead of open thread

On Mon, Jul 24, 2017 at 2:00 PM, John Stultz wrote: > On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote: >> The binder allocator assumes that the thread that >> called binder_open will never die for the lifetime of >> that proc. That thread is normally the group_leader, >> however it may not be.

Re: [PATCH v5 0/3] some fixups for MediaTek cpufreq driver

On Tuesday, July 18, 2017 02:01:42 PM sean.w...@mediatek.com wrote: > From: Sean Wang > > Changes since v4: > - add back the missing Acked-by from v3 > > Changes since v3: > - remove the redundant line depends on ARM || ARM64 || COMPILE_TEST > since the whole Kconfig.arm

Re: [PATCH v5 0/3] some fixups for MediaTek cpufreq driver

On Tuesday, July 18, 2017 02:01:42 PM sean.w...@mediatek.com wrote: > From: Sean Wang > > Changes since v4: > - add back the missing Acked-by from v3 > > Changes since v3: > - remove the redundant line depends on ARM || ARM64 || COMPILE_TEST > since the whole Kconfig.arm file depends on ARM ||

Re: USB disk speed regression WD Elements - with bisect result 22547c4cc4fe20698a6a85a55b8788859134b8e4

On Mon, Jul 24, 2017 at 10:41:12AM -0400, Alan Stern wrote: > On Mon, 24 Jul 2017, Zdenek Kabelac wrote: > > > Hi > > > > I've problem with my USB storage devices: WD Elements 1TB. > > (Bus 004 Device 002: ID 1058:10a8 Western Digital Technologies, Inc. > > Elements > > Portable (WDBUZG)) > >

Re: USB disk speed regression WD Elements - with bisect result 22547c4cc4fe20698a6a85a55b8788859134b8e4

On Mon, Jul 24, 2017 at 10:41:12AM -0400, Alan Stern wrote: > On Mon, 24 Jul 2017, Zdenek Kabelac wrote: > > > Hi > > > > I've problem with my USB storage devices: WD Elements 1TB. > > (Bus 004 Device 002: ID 1058:10a8 Western Digital Technologies, Inc. > > Elements > > Portable (WDBUZG)) > >

Re: [PATCH net 0/2] bpf: fix verifier min/max handling in BPF_SUB

From: Edward Cree Date: Fri, 21 Jul 2017 14:35:17 +0100 > I managed to come up with a test for the swapped bounds in BPF_SUB, so here > it is along with a patch that fixes it, separated out from my 'rewrite > everything' series so it can go to -stable. Series applied and

Re: [PATCH net 0/2] bpf: fix verifier min/max handling in BPF_SUB

From: Edward Cree Date: Fri, 21 Jul 2017 14:35:17 +0100 > I managed to come up with a test for the swapped bounds in BPF_SUB, so here > it is along with a patch that fixes it, separated out from my 'rewrite > everything' series so it can go to -stable. Series applied and queued up for

Re: [PATCH v4] PM / suspend: Export pm_suspend_target_state

On Monday, July 17, 2017 05:19:25 PM Florian Fainelli wrote: > Have the core suspend/resume framework store the system-wide suspend > state (suspend_state_t) we are about to enter, and expose it to drivers > via pm_suspend_target_state in order to retrieve that. The state is > assigned in

Re: [PATCH v4] PM / suspend: Export pm_suspend_target_state

On Monday, July 17, 2017 05:19:25 PM Florian Fainelli wrote: > Have the core suspend/resume framework store the system-wide suspend > state (suspend_state_t) we are about to enter, and expose it to drivers > via pm_suspend_target_state in order to retrieve that. The state is > assigned in

Re: [PATCH v2 0/4] thermal: add brcmstb AVS TMON driver

On 07/21/2017 12:27 PM, Markus Mayer wrote: > From: Markus Mayer > > This series adds the brcmstb AVS TMON driver. > > The driver was originally written by Brian Norris. > > v1 of this series can be found at https://lkml.org/lkml/2017/6/5/921 Rui, Eduardo, I can take

Re: [PATCH v2 0/4] thermal: add brcmstb AVS TMON driver

On 07/21/2017 12:27 PM, Markus Mayer wrote: > From: Markus Mayer > > This series adds the brcmstb AVS TMON driver. > > The driver was originally written by Brian Norris. > > v1 of this series can be found at https://lkml.org/lkml/2017/6/5/921 Rui, Eduardo, I can take patches 3 and 4 through

Re: [PATCH 02/37] binder: use group leader instead of open thread

On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote: > The binder allocator assumes that the thread that > called binder_open will never die for the lifetime of > that proc. That thread is normally the group_leader, > however it may not be. Use the group_leader instead > of

Re: [PATCH 02/37] binder: use group leader instead of open thread

On Thu, Jun 29, 2017 at 12:01 PM, Todd Kjos wrote: > The binder allocator assumes that the thread that > called binder_open will never die for the lifetime of > that proc. That thread is normally the group_leader, > however it may not be. Use the group_leader instead > of current. > >

[PATCH v4 02/12] ALSA: ac97: add an ac97 bus

AC97 is a bus for sound usage. It enables for a AC97 AC-Link to link one controller to 0 to 4 AC97 codecs. The goal of this new implementation is to implement a device/driver model for AC97, with an automatic scan of the bus and automatic discovery of AC97 codec devices. Signed-off-by: Robert

[PATCH v4 02/12] ALSA: ac97: add an ac97 bus

AC97 is a bus for sound usage. It enables for a AC97 AC-Link to link one controller to 0 to 4 AC97 codecs. The goal of this new implementation is to implement a device/driver model for AC97, with an automatic scan of the bus and automatic discovery of AC97 codec devices. Signed-off-by: Robert

[PATCH v4 03/12] ASoC: add new ac97 bus support

Add the new ac97 bus support, with ac97 bus automatic probing. Signed-off-by: Robert Jarzmik Acked-by: Charles Keepax --- sound/Kconfig | 2 ++ sound/Makefile | 1 + 2 files changed, 3 insertions(+) diff --git a/sound/Kconfig

[PATCH v4 11/12] ASoC: wm9705: add ac97 new bus support

Add support for the new ac97 bus model, where devices are automatically discovered on AC-Links. Signed-off-by: Robert Jarzmik Acked-by: Charles Keepax --- sound/soc/codecs/Kconfig | 3 ++- sound/soc/codecs/wm9705.c | 35

[PATCH v4 03/12] ASoC: add new ac97 bus support

Add the new ac97 bus support, with ac97 bus automatic probing. Signed-off-by: Robert Jarzmik Acked-by: Charles Keepax --- sound/Kconfig | 2 ++ sound/Makefile | 1 + 2 files changed, 3 insertions(+) diff --git a/sound/Kconfig b/sound/Kconfig index ee2e69a9ecd1..141b145c4195 100644 ---

[PATCH v4 11/12] ASoC: wm9705: add ac97 new bus support

Add support for the new ac97 bus model, where devices are automatically discovered on AC-Links. Signed-off-by: Robert Jarzmik Acked-by: Charles Keepax --- sound/soc/codecs/Kconfig | 3 ++- sound/soc/codecs/wm9705.c | 35 +++ 2 files changed, 25 insertions(+),

[PATCH v4 05/12] Input: wm97xx: split out touchscreen registering

wm97xx-core does several things in it initialization : - touchscreen input device setup - battery device creation As the wm97xx is actually a multi-function device handling an audio codec, a touchscreen, a gpio block and an ADC, reshape the probing to isolate what is truly input/touchscreen

[PATCH v4 05/12] Input: wm97xx: split out touchscreen registering

wm97xx-core does several things in it initialization : - touchscreen input device setup - battery device creation As the wm97xx is actually a multi-function device handling an audio codec, a touchscreen, a gpio block and an ADC, reshape the probing to isolate what is truly input/touchscreen

[PATCH v4 01/12] ALSA: ac97: split out the generic ac97 registers

Split out from the ac97_codec.h the ac97 generic registers, which can be used by a codec, typically a generic ac97 codec, and by the ac97 bus, to scan an ac97 AC-Link. This split encompasses all the AC97 standard registers, but not the codec specific ones. In order to have a clean split between

[PATCH v4 01/12] ALSA: ac97: split out the generic ac97 registers

Split out from the ac97_codec.h the ac97 generic registers, which can be used by a codec, typically a generic ac97 codec, and by the ac97 bus, to scan an ac97 AC-Link. This split encompasses all the AC97 standard registers, but not the codec specific ones. In order to have a clean split between

[PATCH v4 04/12] ASoC: arm: make pxa2xx-ac97-lib ac97 codec agnostic

All pxa library functions don't use the input parameters for nothing but slot number. This simplifies their prototypes, and makes them usable by both the legacy ac97 bus and the new ac97 bus. Signed-off-by: Robert Jarzmik --- include/sound/pxa2xx-lib.h | 15

[PATCH v4 12/12] ASoC: pxa: switch to new ac97 bus support

Switch to the new ac97 bus support in sound/ac97 instead of the legacy snd_ac97 one. Signed-off-by: Robert Jarzmik --- Since v1: split into 2 patches, the former being XXX ac97 codec agnostic Since v2: fix driver unregistration Since v3: added platform driver data for

[PATCH v4 04/12] ASoC: arm: make pxa2xx-ac97-lib ac97 codec agnostic

All pxa library functions don't use the input parameters for nothing but slot number. This simplifies their prototypes, and makes them usable by both the legacy ac97 bus and the new ac97 bus. Signed-off-by: Robert Jarzmik --- include/sound/pxa2xx-lib.h | 15 +--

[PATCH v4 12/12] ASoC: pxa: switch to new ac97 bus support

Switch to the new ac97 bus support in sound/ac97 instead of the legacy snd_ac97 one. Signed-off-by: Robert Jarzmik --- Since v1: split into 2 patches, the former being XXX ac97 codec agnostic Since v2: fix driver unregistration Since v3: added platform driver data for controller removal ---

[PATCH v4 09/12] ASoC: wm9712: add ac97 new bus support

Add support for the new ac97 bus model, where devices are automatically discovered on AC-Links. Signed-off-by: Robert Jarzmik --- sound/soc/codecs/Kconfig | 3 ++- sound/soc/codecs/wm9712.c | 37 - 2 files changed, 26 insertions(+),

[PATCH v4 07/12] Input: wm97xx: add new AC97 bus support

This adds support for the new AC97 bus code, which discovers the devices rather than uses platform data. As part of this discovery, it enables a multi-function device wm97xx, which supports touchscreen, battery, ADC and an audio codec. This patch adds the code to bind the touchscreen "cell" as

[PATCH v4 09/12] ASoC: wm9712: add ac97 new bus support

Add support for the new ac97 bus model, where devices are automatically discovered on AC-Links. Signed-off-by: Robert Jarzmik --- sound/soc/codecs/Kconfig | 3 ++- sound/soc/codecs/wm9712.c | 37 - 2 files changed, 26 insertions(+), 14 deletions(-) diff

[PATCH v4 07/12] Input: wm97xx: add new AC97 bus support

This adds support for the new AC97 bus code, which discovers the devices rather than uses platform data. As part of this discovery, it enables a multi-function device wm97xx, which supports touchscreen, battery, ADC and an audio codec. This patch adds the code to bind the touchscreen "cell" as

[PATCH v4 10/12] ASoC: wm9705: add private structure

Add a private data structure. This is a preparation for a codec which would need an another data on top of snd_ac97, which will be the case when an MFD wm97xx device will probe wm9705. Signed-off-by: Robert Jarzmik Acked-by: Charles Keepax

[PATCH v4 08/12] ASoC: wm9713: add ac97 new bus support

Add support for the new ac97 bus model, where devices are automatically discovered on AC-Links. Signed-off-by: Robert Jarzmik --- sound/soc/codecs/Kconfig | 3 ++- sound/soc/codecs/wm9713.c | 39 +++ 2 files changed, 29

[PATCH v4 10/12] ASoC: wm9705: add private structure

Add a private data structure. This is a preparation for a codec which would need an another data on top of snd_ac97, which will be the case when an MFD wm97xx device will probe wm9705. Signed-off-by: Robert Jarzmik Acked-by: Charles Keepax --- sound/soc/codecs/wm9705.c | 36

[PATCH v4 08/12] ASoC: wm9713: add ac97 new bus support

Add support for the new ac97 bus model, where devices are automatically discovered on AC-Links. Signed-off-by: Robert Jarzmik --- sound/soc/codecs/Kconfig | 3 ++- sound/soc/codecs/wm9713.c | 39 +++ 2 files changed, 29 insertions(+), 13 deletions(-) diff

[PATCH v4 06/12] mfd: wm97xx-core: core support for wm97xx Codec

The WM9705, WM9712 and WM9713 are highly integrated codecs, with an audio codec, DAC and ADC, GPIO unit and a touchscreen interface. Historically the support was spread across drivers/input/touchscreen and sound/soc/codecs. The sharing was done through ac97 bus sharing. This model will not

[PATCH v4 06/12] mfd: wm97xx-core: core support for wm97xx Codec

The WM9705, WM9712 and WM9713 are highly integrated codecs, with an audio codec, DAC and ADC, GPIO unit and a touchscreen interface. Historically the support was spread across drivers/input/touchscreen and sound/soc/codecs. The sharing was done through ac97 bus sharing. This model will not

[PATCH v4 00/12] AC97 device/driver model revamp

Hi Lars, Mark, Charles, Lee, This is a minor revision after v3, mainly reviews from Takashi, Charles. I did more extensive testing of load/unload of the whole serie, and apart from a bug in wm97xx-core in touchscreen tree (for a which a patch will be sent apart), it seems to work properly. I

[PATCH v4 00/12] AC97 device/driver model revamp

Hi Lars, Mark, Charles, Lee, This is a minor revision after v3, mainly reviews from Takashi, Charles. I did more extensive testing of load/unload of the whole serie, and apart from a bug in wm97xx-core in touchscreen tree (for a which a patch will be sent apart), it seems to work properly. I

Re: [PATCH v2 net] net: ethernet: mediatek: avoid potential invalid memory access

From: Date: Sat, 22 Jul 2017 20:45:55 +0800 > From: Sean Wang > > Potential dangerous invalid memory might be accessed if invalid mac value > reflected from the forward port field in rxd4 caused by possible potential > hardware defects. So added

Re: [PATCH v2 net] net: ethernet: mediatek: avoid potential invalid memory access

From: Date: Sat, 22 Jul 2017 20:45:55 +0800 > From: Sean Wang > > Potential dangerous invalid memory might be accessed if invalid mac value > reflected from the forward port field in rxd4 caused by possible potential > hardware defects. So added a simple sanity checker to avoid the kind of >

Re: [PATCH] net: Convert to using %pOF instead of full_name

From: Rob Herring Date: Wed, 19 Jul 2017 10:09:13 -0500 > On Tue, Jul 18, 2017 at 4:51 PM, David Miller wrote: >> From: Rob Herring >> Date: Tue, 18 Jul 2017 16:43:19 -0500 >> >>> Now that we have a custom printf format specifier, convert

Re: [PATCH] net: Convert to using %pOF instead of full_name

From: Rob Herring Date: Wed, 19 Jul 2017 10:09:13 -0500 > On Tue, Jul 18, 2017 at 4:51 PM, David Miller wrote: >> From: Rob Herring >> Date: Tue, 18 Jul 2017 16:43:19 -0500 >> >>> Now that we have a custom printf format specifier, convert users of >>> full_name to use %pOF instead. This is

Re: [PATCH] mailbox: pcc: Fix crash when request PCC channel 0

On Friday, July 21, 2017 03:09:29 PM Hoan Tran wrote: > When PCCT is not available, kernel crashes as below when requests PCC > channel 0. This patch fixes this issue. > > [0.920454] PCCT header not found. > ... > [8.031309] Unable to handle kernel NULL pointer dereference at virtual >

Re: [PATCH] mailbox: pcc: Fix crash when request PCC channel 0

On Friday, July 21, 2017 03:09:29 PM Hoan Tran wrote: > When PCCT is not available, kernel crashes as below when requests PCC > channel 0. This patch fixes this issue. > > [0.920454] PCCT header not found. > ... > [8.031309] Unable to handle kernel NULL pointer dereference at virtual >

Re: [PATCH net-next V2 0/5] Refine virtio-net XDP

From: Jason Wang Date: Wed, 19 Jul 2017 16:54:44 +0800 > Hi: > > This series brings two optimizations for virtio-net XDP: > > - avoid reset during XDP set > - turn off offloads on demand > > Changes from V1: > - Various tweaks on commit logs and comments > - Use

Re: [PATCH net-next V2 0/5] Refine virtio-net XDP

From: Jason Wang Date: Wed, 19 Jul 2017 16:54:44 +0800 > Hi: > > This series brings two optimizations for virtio-net XDP: > > - avoid reset during XDP set > - turn off offloads on demand > > Changes from V1: > - Various tweaks on commit logs and comments > - Use virtnet_napi_enable() when

Re: [PATCH 2/2] acpi: Fix typo in SRAT table name

On Friday, July 21, 2017 04:51:24 PM Ross Zwisler wrote: > To save someone the time of searching the ACPI spec for "Static Resource > Affinity Table". > > Signed-off-by: Ross Zwisler > --- > drivers/acpi/numa.c | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH 2/2] acpi: Fix typo in SRAT table name

On Friday, July 21, 2017 04:51:24 PM Ross Zwisler wrote: > To save someone the time of searching the ACPI spec for "Static Resource > Affinity Table". > > Signed-off-by: Ross Zwisler > --- > drivers/acpi/numa.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

[Kein Betreff]

unsubscribe linux-kernel

[Kein Betreff]

unsubscribe linux-kernel

Re: [PATCH V4 net-next 7/8] net: hns3: Add Ethtool support to HNS3 driver

> On Jul 23, 2017, at 10:05 AM, Florian Fainelli wrote: >> + >> +strncpy(drvinfo->version, HNAE_DRIVER_VERSION, >> +sizeof(drvinfo->version)); >> +drvinfo->version[sizeof(drvinfo->version) - 1] = '\0'; > > strlcpy() would probably do that for you. You

Re: [PATCH V4 net-next 7/8] net: hns3: Add Ethtool support to HNS3 driver

> On Jul 23, 2017, at 10:05 AM, Florian Fainelli wrote: >> + >> +strncpy(drvinfo->version, HNAE_DRIVER_VERSION, >> +sizeof(drvinfo->version)); >> +drvinfo->version[sizeof(drvinfo->version) - 1] = '\0'; > > strlcpy() would probably do that for you. You need to be careful

Re: [PATCH 00/13] net: dsa: lan9303: unicast offload, fdb,mdb,STP

From: Egil Hjelmeland Date: Mon, 24 Jul 2017 16:47:51 +0200 > This is my first patches submitted to the kernel, so I am looking > forward to comments. Please clean up how the dates are handled in your submission. They are all over the place, over a period of 3

Re: [PATCH 00/13] net: dsa: lan9303: unicast offload, fdb,mdb,STP

From: Egil Hjelmeland Date: Mon, 24 Jul 2017 16:47:51 +0200 > This is my first patches submitted to the kernel, so I am looking > forward to comments. Please clean up how the dates are handled in your submission. They are all over the place, over a period of 3 days. Instead, they should be

Re: v4.13-rc2: usb mouse stopped working?

Hi! > > On thinkpad x220, USB mouse stopped working in v4.13-rc2. v4.12 was > > ok, iirc. > > > > Now, USB mouse is so common hw that I may have something wrong in my > > config...? But I did not change anything there. > > Well, your particular USB mouse requires an always-poll quirk, so it's

Re: v4.13-rc2: usb mouse stopped working?

Hi! > > On thinkpad x220, USB mouse stopped working in v4.13-rc2. v4.12 was > > ok, iirc. > > > > Now, USB mouse is so common hw that I may have something wrong in my > > config...? But I did not change anything there. > > Well, your particular USB mouse requires an always-poll quirk, so it's

Re: [PATCH v4 1/2] dt-bindings: arm: Add entry for Beckhoff CX9020

On Fri, Jul 21, 2017 at 06:06:39AM +0200, linux-kernel-...@beckhoff.com wrote: > From: Patrick Bruenn > > - add vendor prefix bhf for Beckhoff > - add new board binding bhf,cx9020 > > Signed-off-by: Patrick Bruenn > --- >

Re: [PATCH v4 1/2] dt-bindings: arm: Add entry for Beckhoff CX9020

On Fri, Jul 21, 2017 at 06:06:39AM +0200, linux-kernel-...@beckhoff.com wrote: > From: Patrick Bruenn > > - add vendor prefix bhf for Beckhoff > - add new board binding bhf,cx9020 > > Signed-off-by: Patrick Bruenn > --- > Documentation/devicetree/bindings/arm/bhf.txt | 6 ++ >

Re: [PATCH 1/3] dt-bindings: soc: update the binding document for SCPSYS on MediaTek MT7622 SoC

On Fri, Jul 21, 2017 at 11:57:12AM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > Update the binding document for enabling SCPSYS on MediaTek MT7622 SoC. > > Signed-off-by: Sean Wang > Signed-off-by: Chen Zhong

Re: [PATCH 1/3] dt-bindings: soc: update the binding document for SCPSYS on MediaTek MT7622 SoC

On Fri, Jul 21, 2017 at 11:57:12AM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > Update the binding document for enabling SCPSYS on MediaTek MT7622 SoC. > > Signed-off-by: Sean Wang > Signed-off-by: Chen Zhong > --- > Documentation/devicetree/bindings/soc/mediatek/scpsys.txt | 3

<    2   3   4   5   6   7   8   9   10   11   >