Re: [PATCH] [RFC] x86: avoid -mtune=atom for objtool warnings

On Thu, Mar 2, 2017 at 7:25 PM, Josh Poimboeuf wrote: >> It was on the current linux-next, so that commit should certainly be >> included. >> >> > Can you attach the object file? > > Here's the preliminary fix for this one (still needs more testing): It fixes the warning for me. Arnd

[PATCH] ARM: dts: mvebu: remove unnecessary PCI range from 98dx3236

The Marvell 98dx3236 SoC only has a single PCIe x1 interface. The "Port 0.1 MEM" range was errantly kept when creating a specific dts for the SoC. Signed-off-by: Chris Packham --- arch/arm/boot/dts/armada-xp-98dx3236.dtsi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

Re: [PATCH] module: set __jump_table alignment to 8

+++ David Daney [02/03/17 11:24 -0800]: On 03/02/2017 10:26 AM, Jessica Yu wrote: +++ Steven Rostedt [02/03/17 13:11 -0500]: Can I get an Ack from a module maintainer? Acked-by: Jessica Yu Thanks! Jessica Thanks Jessica, Can you also add scripts/module-common.lds to

Re: [PATCH] module: set __jump_table alignment to 8

+++ David Daney [02/03/17 11:24 -0800]: On 03/02/2017 10:26 AM, Jessica Yu wrote: +++ Steven Rostedt [02/03/17 13:11 -0500]: Can I get an Ack from a module maintainer? Acked-by: Jessica Yu Thanks! Jessica Thanks Jessica, Can you also add scripts/module-common.lds to MAINTAINERS so

Re: [PATCH 24/26] ocfs2: reduce stack size with KASAN

On Thu, 2017-03-02 at 23:22 +0100, Arnd Bergmann wrote: > On Thu, Mar 2, 2017 at 6:46 PM, Joe Perches wrote: > > On Thu, 2017-03-02 at 17:38 +0100, Arnd Bergmann wrote: > > > The internal logging infrastructure in ocfs2 causes special warning code > > > to be > > > used with

Re: [PATCH 24/26] ocfs2: reduce stack size with KASAN

On Thu, 2017-03-02 at 23:22 +0100, Arnd Bergmann wrote: > On Thu, Mar 2, 2017 at 6:46 PM, Joe Perches wrote: > > On Thu, 2017-03-02 at 17:38 +0100, Arnd Bergmann wrote: > > > The internal logging infrastructure in ocfs2 causes special warning code > > > to be > > > used with KASAN, which

Re: [PATCH v2] blkcg: allocate struct blkcg_gq outside request queue spinlock

On Thu, Mar 2, 2017 at 11:32 AM, Tejun Heo wrote: > Hello, Tahsin. > > On Wed, Mar 01, 2017 at 03:43:19PM -0800, Tahsin Erdogan wrote: >> @@ -258,18 +258,22 @@ static struct blkcg_gq *blkg_create(struct blkcg >> *blkcg, >> struct blkcg_gq *blkg_lookup_create(struct blkcg

Re: [PATCH v2] blkcg: allocate struct blkcg_gq outside request queue spinlock

On Thu, Mar 2, 2017 at 11:32 AM, Tejun Heo wrote: > Hello, Tahsin. > > On Wed, Mar 01, 2017 at 03:43:19PM -0800, Tahsin Erdogan wrote: >> @@ -258,18 +258,22 @@ static struct blkcg_gq *blkg_create(struct blkcg >> *blkcg, >> struct blkcg_gq *blkg_lookup_create(struct blkcg *blkcg, >> -

[PATCH 1/2] cpufreq: mt8173: Mark mt8173_cpufreq_driver_init as __init

This function is only called once at boot by device_initcall(), so mark it as __init. Signed-off-by: Daniel Kurtz --- drivers/cpufreq/mt8173-cpufreq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/cpufreq/mt8173-cpufreq.c

[PATCH 1/2] cpufreq: mt8173: Mark mt8173_cpufreq_driver_init as __init

This function is only called once at boot by device_initcall(), so mark it as __init. Signed-off-by: Daniel Kurtz --- drivers/cpufreq/mt8173-cpufreq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/cpufreq/mt8173-cpufreq.c b/drivers/cpufreq/mt8173-cpufreq.c index

[PATCH 00/11] drm/meson: Initial support for HDMI Output

The Amlogic GX SoCs implements a Synopsys DesignWare HDMI TX Controller in combination with a very custom PHY. This patchset depends on Laurent Pinchart v4 patchset at [1] and my v2 patchset at [2] to permit PHY control from outside the dw-hdmi driver. The Synopsys DesignWare HDMI TX Controller

[PATCH 00/11] drm/meson: Initial support for HDMI Output

The Amlogic GX SoCs implements a Synopsys DesignWare HDMI TX Controller in combination with a very custom PHY. This patchset depends on Laurent Pinchart v4 patchset at [1] and my v2 patchset at [2] to permit PHY control from outside the dw-hdmi driver. The Synopsys DesignWare HDMI TX Controller

Re: [PATCH] jump_label: Fix anonymous union initialization

On Thu, 2 Mar 2017 16:07:19 -0500 Jason Baron wrote: > On 02/28/2017 11:32 AM, Boris Ostrovsky wrote: > > Pre-4.6 gcc do not allow direct static initialization of members of > > anonymous structs/unions. After commit 3821fd35b58d ("jump_label: > > Reduce the size of struct

Re: [PATCH] jump_label: Fix anonymous union initialization

On Thu, 2 Mar 2017 16:07:19 -0500 Jason Baron wrote: > On 02/28/2017 11:32 AM, Boris Ostrovsky wrote: > > Pre-4.6 gcc do not allow direct static initialization of members of > > anonymous structs/unions. After commit 3821fd35b58d ("jump_label: > > Reduce the size of struct static_key")

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, Mar 3, 2017 at 3:29 AM, Joe Perches wrote: > On Fri, 2017-03-03 at 03:25 +0530, SIMRAN SINGHAL wrote: >> On Fri, Mar 3, 2017 at 3:13 AM, Joe Perches wrote: >> > On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: >> > > The following Coccinelle

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, Mar 3, 2017 at 3:29 AM, Joe Perches wrote: > On Fri, 2017-03-03 at 03:25 +0530, SIMRAN SINGHAL wrote: >> On Fri, Mar 3, 2017 at 3:13 AM, Joe Perches wrote: >> > On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: >> > > The following Coccinelle script was used to detect this: >> > >

[PATCH] jump_label: Add comment about initialization order for anonymous unions

Commit 3821fd35b58d ("jump_label: Reduce the size of struct static_key") broke old compilers that could not handle static initialization of anonymous unions. Boris fixed it with a patch that added brackets around the static initializer. But this creates a dependency between those initializers and

[PATCH] jump_label: Add comment about initialization order for anonymous unions

Commit 3821fd35b58d ("jump_label: Reduce the size of struct static_key") broke old compilers that could not handle static initialization of anonymous unions. Boris fixed it with a patch that added brackets around the static initializer. But this creates a dependency between those initializers and

[Update][PATCH v3 2/3] cpufreq: intel_pstate: Do not reinit performance limits in ->setpolicy

From: Rafael J. Wysocki If the current P-state selection algorithm is set to "performance" in intel_pstate_set_policy(), the limits may be initialized from scratch, but only if no_turbo is not set and the maximum frequency allowed for the given CPU (i.e. the policy

[Update][PATCH v3 2/3] cpufreq: intel_pstate: Do not reinit performance limits in ->setpolicy

From: Rafael J. Wysocki If the current P-state selection algorithm is set to "performance" in intel_pstate_set_policy(), the limits may be initialized from scratch, but only if no_turbo is not set and the maximum frequency allowed for the given CPU (i.e. the policy object representing it) is at

[GIT PULL] target updates for v4.11-rc1

Hello Linus, Here are the outstanding target pending changes for v4.11-rc1. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next The highlights this round include: - Enable dual mode (initiator + target) qla2xxx operation. (Quinn +

[GIT PULL] target updates for v4.11-rc1

Hello Linus, Here are the outstanding target pending changes for v4.11-rc1. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next The highlights this round include: - Enable dual mode (initiator + target) qla2xxx operation. (Quinn +

Re: [PATCH] drivers: net: ethernet: remove incorrect __exit markups

From: Dmitry Torokhov Date: Wed, 1 Mar 2017 17:24:47 -0800 > Even if bus is not hot-pluggable, devices can be unbound from the > driver via sysfs, so we should not be using __exit annotations on > remove() methods. The only exception is drivers registered with >

Re: [PATCH] drivers: net: ethernet: remove incorrect __exit markups

From: Dmitry Torokhov Date: Wed, 1 Mar 2017 17:24:47 -0800 > Even if bus is not hot-pluggable, devices can be unbound from the > driver via sysfs, so we should not be using __exit annotations on > remove() methods. The only exception is drivers registered with > platform_driver_probe() which

[PATCH 2/3] cpufreq: intel_pstate: Fix intel_cpufreq_verify_policy()

From: Rafael J. Wysocki The intel_pstate_update_perf_limits() called from intel_cpufreq_verify_policy() may cause global P-state limits to change which is generally confusing and unnecessary. In the passive mode the global limits are only applied to the frequency

[PATCH 2/3] cpufreq: intel_pstate: Fix intel_cpufreq_verify_policy()

From: Rafael J. Wysocki The intel_pstate_update_perf_limits() called from intel_cpufreq_verify_policy() may cause global P-state limits to change which is generally confusing and unnecessary. In the passive mode the global limits are only applied to the frequency selected by the scaling

[PATCH 3/3] cpufreq: intel_pstate: Avoid triggering cpu_frequency tracepoint unnecessarily

From: Rafael J. Wysocki In the passive mode the cpu_frequency trace event is already triggered by the cpufreq core or by scaling governors, so intel_pstate should not trigger it once again for the same P-state updates. Fixes: 001c76f05b01 (cpufreq: intel_pstate:

[PATCH 3/3] cpufreq: intel_pstate: Avoid triggering cpu_frequency tracepoint unnecessarily

From: Rafael J. Wysocki In the passive mode the cpu_frequency trace event is already triggered by the cpufreq core or by scaling governors, so intel_pstate should not trigger it once again for the same P-state updates. Fixes: 001c76f05b01 (cpufreq: intel_pstate: Generic governors support)

[PATCH 1/3] cpufreq: intel_pstate: Do not use performance_limits in passive mode

From: Rafael J. Wysocki Using performance_limits in the passive mode doesn't make sense, because in that mode the global limits are applied to the frequency selected by the scaling governor. The maximum and minimum P-state limits in performance_limits are both set to

[PATCH 1/3] cpufreq: intel_pstate: Do not use performance_limits in passive mode

From: Rafael J. Wysocki Using performance_limits in the passive mode doesn't make sense, because in that mode the global limits are applied to the frequency selected by the scaling governor. The maximum and minimum P-state limits in performance_limits are both set to 100 percent which will put

[PATCH 18/26] [media] i2c: cx25840: avoid stack overflow with KASAN

With CONFIG_KASAN, this driver has shown a ridiculously large stack frame in one configuration: drivers/media/i2c/cx25840/cx25840-core.c:4960:1: error: the frame size of 94000 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] In most builds, it's only about 3300 bytes, but that's

[PATCH 18/26] [media] i2c: cx25840: avoid stack overflow with KASAN

With CONFIG_KASAN, this driver has shown a ridiculously large stack frame in one configuration: drivers/media/i2c/cx25840/cx25840-core.c:4960:1: error: the frame size of 94000 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] In most builds, it's only about 3300 bytes, but that's

Re: [Outreachy kernel] [PATCH 4/5] staging: rts5208: Remove unnecessary cast on void pointer

On Fri, Mar 3, 2017 at 3:26 AM, Julia Lawall wrote: >> diff --git a/drivers/staging/rts5208/rtsx_transport.c >> b/drivers/staging/rts5208/rtsx_transport.c >> index 2379901..d745b93 100644 >> --- a/drivers/staging/rts5208/rtsx_transport.c >> +++

Re: [Outreachy kernel] [PATCH 4/5] staging: rts5208: Remove unnecessary cast on void pointer

On Fri, Mar 3, 2017 at 3:26 AM, Julia Lawall wrote: >> diff --git a/drivers/staging/rts5208/rtsx_transport.c >> b/drivers/staging/rts5208/rtsx_transport.c >> index 2379901..d745b93 100644 >> --- a/drivers/staging/rts5208/rtsx_transport.c >> +++ b/drivers/staging/rts5208/rtsx_transport.c >> @@

Re: [PATCH v2 1/2] drm: bridge: dw-hdmi: Take input format from plat_data

Hi Neil, Thank you for the patch. On Thursday 02 Mar 2017 16:29:31 Neil Armstrong wrote: > Some display pipelines can only provide non-RBG input pixels to the HDMI TX > Controller, this patch takes the pixel format from the plat_data if > provided. > > Signed-off-by: Neil Armstrong

Re: [PATCH v2 1/2] drm: bridge: dw-hdmi: Take input format from plat_data

Hi Neil, Thank you for the patch. On Thursday 02 Mar 2017 16:29:31 Neil Armstrong wrote: > Some display pipelines can only provide non-RBG input pixels to the HDMI TX > Controller, this patch takes the pixel format from the plat_data if > provided. > > Signed-off-by: Neil Armstrong > --- >

Re: [PATCH v1] gpio: acpi: Add managed variant of acpi_dev_add_driver_gpios()

On Thursday, March 02, 2017 03:48:05 PM Andy Shevchenko wrote: > Introduce device managed variant of acpi_dev_add_driver_gpios() and its > counterpart acpi_dev_remove_driver_gpios(). > > The functions in most cases are used in driver's ->probe() and > ->remove() callbacks, that's why it's useful

Re: [PATCH v1] gpio: acpi: Add managed variant of acpi_dev_add_driver_gpios()

On Thursday, March 02, 2017 03:48:05 PM Andy Shevchenko wrote: > Introduce device managed variant of acpi_dev_add_driver_gpios() and its > counterpart acpi_dev_remove_driver_gpios(). > > The functions in most cases are used in driver's ->probe() and > ->remove() callbacks, that's why it's useful

Re: [PATCH v3 0/5] perf report: Show inline stack

On Dienstag, 21. Februar 2017 01:28:17 CET Jin, Yao wrote: > Hi, > > Any comments for this patch series? Sorry for the delay. I just tested it again. Overall, this is a clear improvement, so I'm all for getting this functionality in. But from a usability point of view, I still have the some

Re: [PATCH v3 0/5] perf report: Show inline stack

On Dienstag, 21. Februar 2017 01:28:17 CET Jin, Yao wrote: > Hi, > > Any comments for this patch series? Sorry for the delay. I just tested it again. Overall, this is a clear improvement, so I'm all for getting this functionality in. But from a usability point of view, I still have the some

[PATCH v2 05/21] x86/xen: split off enlighten_hvm.c

Move PVHVM related code to enlighten_hvm.c. Three functions: xen_cpuhp_setup(), xen_reboot(), xen_emergency_restart() are shared, drop static qualifier from them. These functions will go to common code once it is split from enlighten.c. Signed-off-by: Vitaly Kuznetsov ---

[PATCH v2 03/21] x86/xen: add CONFIG_XEN_PV to Kconfig

All code to supprot Xen PV will get under this new option. For the beginning, check for it in the common code. Signed-off-by: Vitaly Kuznetsov --- arch/x86/kernel/cpu/hypervisor.c | 4 +++- arch/x86/kernel/process_64.c | 2 +- arch/x86/xen/Kconfig | 23

[PATCH v2 05/21] x86/xen: split off enlighten_hvm.c

Move PVHVM related code to enlighten_hvm.c. Three functions: xen_cpuhp_setup(), xen_reboot(), xen_emergency_restart() are shared, drop static qualifier from them. These functions will go to common code once it is split from enlighten.c. Signed-off-by: Vitaly Kuznetsov --- arch/x86/xen/Makefile

[PATCH v2 03/21] x86/xen: add CONFIG_XEN_PV to Kconfig

All code to supprot Xen PV will get under this new option. For the beginning, check for it in the common code. Signed-off-by: Vitaly Kuznetsov --- arch/x86/kernel/cpu/hypervisor.c | 4 +++- arch/x86/kernel/process_64.c | 2 +- arch/x86/xen/Kconfig | 23 ++-

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, 2017-03-03 at 03:35 +0530, SIMRAN SINGHAL wrote: > On Fri, Mar 3, 2017 at 3:29 AM, Joe Perches wrote: > > On Fri, 2017-03-03 at 03:25 +0530, SIMRAN SINGHAL wrote: > > > On Fri, Mar 3, 2017 at 3:13 AM, Joe Perches wrote: > > > > On Fri, 2017-03-03 at

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, 2017-03-03 at 03:35 +0530, SIMRAN SINGHAL wrote: > On Fri, Mar 3, 2017 at 3:29 AM, Joe Perches wrote: > > On Fri, 2017-03-03 at 03:25 +0530, SIMRAN SINGHAL wrote: > > > On Fri, Mar 3, 2017 at 3:13 AM, Joe Perches wrote: > > > > On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: > >

Re: [Outreachy kernel] [PATCH 4/5] staging: rts5208: Remove unnecessary cast on void pointer

> diff --git a/drivers/staging/rts5208/rtsx_transport.c > b/drivers/staging/rts5208/rtsx_transport.c > index 2379901..d745b93 100644 > --- a/drivers/staging/rts5208/rtsx_transport.c > +++ b/drivers/staging/rts5208/rtsx_transport.c > @@ -767,7 +767,7 @@ int rtsx_transfer_data(struct rtsx_chip

Re: [Outreachy kernel] [PATCH 4/5] staging: rts5208: Remove unnecessary cast on void pointer

> diff --git a/drivers/staging/rts5208/rtsx_transport.c > b/drivers/staging/rts5208/rtsx_transport.c > index 2379901..d745b93 100644 > --- a/drivers/staging/rts5208/rtsx_transport.c > +++ b/drivers/staging/rts5208/rtsx_transport.c > @@ -767,7 +767,7 @@ int rtsx_transfer_data(struct rtsx_chip

[PATCH v2 02/21] x86/xen: globalize have_vcpu_info_placement

have_vcpu_info_placement applies to both PV and HVM and as we're going to split the code we need to make it global. Rename to xen_have_vcpu_info_placement. Signed-off-by: Vitaly Kuznetsov --- arch/x86/xen/enlighten.c | 12 ++-- arch/x86/xen/xen-ops.h | 2 ++ 2

[PATCH v2 10/21] x86/xen: split off smp_hvm.c

Move PVHVM related code to smp_hvm.c. Drop 'static' qualifier from xen_smp_send_reschedule(), xen_smp_send_call_function_ipi(), xen_smp_send_call_function_single_ipi(), these functions will be moved to common smp code when smp_pv.c is split. Signed-off-by: Vitaly Kuznetsov

[PATCH v2 02/21] x86/xen: globalize have_vcpu_info_placement

have_vcpu_info_placement applies to both PV and HVM and as we're going to split the code we need to make it global. Rename to xen_have_vcpu_info_placement. Signed-off-by: Vitaly Kuznetsov --- arch/x86/xen/enlighten.c | 12 ++-- arch/x86/xen/xen-ops.h | 2 ++ 2 files changed, 8

[PATCH v2 10/21] x86/xen: split off smp_hvm.c

Move PVHVM related code to smp_hvm.c. Drop 'static' qualifier from xen_smp_send_reschedule(), xen_smp_send_call_function_ipi(), xen_smp_send_call_function_single_ipi(), these functions will be moved to common smp code when smp_pv.c is split. Signed-off-by: Vitaly Kuznetsov ---

Re: [PATCH v4 23/23] drm/rockchip: dw-mipi-dsi: add reset control

Oh, one more thing: On Fri, Feb 24, 2017 at 12:55:06PM +, John Keeping wrote: > diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi.c > b/drivers/gpu/drm/rockchip/dw-mipi-dsi.c > index 0c4bae711e84..30da75667334 100644 > --- a/drivers/gpu/drm/rockchip/dw-mipi-dsi.c > +++

Re: [PATCH v4 23/23] drm/rockchip: dw-mipi-dsi: add reset control

Oh, one more thing: On Fri, Feb 24, 2017 at 12:55:06PM +, John Keeping wrote: > diff --git a/drivers/gpu/drm/rockchip/dw-mipi-dsi.c > b/drivers/gpu/drm/rockchip/dw-mipi-dsi.c > index 0c4bae711e84..30da75667334 100644 > --- a/drivers/gpu/drm/rockchip/dw-mipi-dsi.c > +++

[PATCH v2 01/21] x86/xen: separate PV and HVM hypervisors

As a preparation to splitting the code we need to untangle it: x86_hyper_xen -> x86_hyper_xen_hvm and x86_hyper_xen_pv xen_platform() -> xen_platform_hvm() and xen_platform_pv() xen_cpu_up_prepare() -> xen_cpu_up_prepare_pv() and xen_cpu_up_prepare_hvm() xen_cpu_dead() -> xen_cpu_dead_pv() and

[PATCH v2 01/21] x86/xen: separate PV and HVM hypervisors

As a preparation to splitting the code we need to untangle it: x86_hyper_xen -> x86_hyper_xen_hvm and x86_hyper_xen_pv xen_platform() -> xen_platform_hvm() and xen_platform_pv() xen_cpu_up_prepare() -> xen_cpu_up_prepare_pv() and xen_cpu_up_prepare_hvm() xen_cpu_dead() -> xen_cpu_dead_pv() and

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, Mar 3, 2017 at 3:13 AM, Joe Perches wrote: > On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: >> The following Coccinelle script was used to detect this: >> @r@ >> expression x; >> void* e; >> type T; >> identifier f; >> @@ >> ( >> *((T *)e) >> > >> >> ((T

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, Mar 3, 2017 at 3:13 AM, Joe Perches wrote: > On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: >> The following Coccinelle script was used to detect this: >> @r@ >> expression x; >> void* e; >> type T; >> identifier f; >> @@ >> ( >> *((T *)e) >> > >> >> ((T *)x)[...] >> > >> >>

Re: [PATCH] jump_label: Fix anonymous union initialization

On 03/02/2017 04:42 PM, Steven Rostedt wrote: On Thu, 2 Mar 2017 16:07:19 -0500 Jason Baron wrote: On 02/28/2017 11:32 AM, Boris Ostrovsky wrote: Pre-4.6 gcc do not allow direct static initialization of members of anonymous structs/unions. After commit 3821fd35b58d

Re: [PATCH] jump_label: Fix anonymous union initialization

On 03/02/2017 04:42 PM, Steven Rostedt wrote: On Thu, 2 Mar 2017 16:07:19 -0500 Jason Baron wrote: On 02/28/2017 11:32 AM, Boris Ostrovsky wrote: Pre-4.6 gcc do not allow direct static initialization of members of anonymous structs/unions. After commit 3821fd35b58d ("jump_label: Reduce the

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, 2017-03-03 at 03:25 +0530, SIMRAN SINGHAL wrote: > On Fri, Mar 3, 2017 at 3:13 AM, Joe Perches wrote: > > On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: > > > The following Coccinelle script was used to detect this: > > > @r@ > > > expression x; > > > void* e;

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, 2017-03-03 at 03:25 +0530, SIMRAN SINGHAL wrote: > On Fri, Mar 3, 2017 at 3:13 AM, Joe Perches wrote: > > On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: > > > The following Coccinelle script was used to detect this: > > > @r@ > > > expression x; > > > void* e; > > > type T; > >

Re: [Outreachy kernel] [PATCH 5/5] staging: rtl8712: Remove unnecessary cast on void pointer

> @@ -635,7 +635,7 @@ void r8712_reordering_ctrl_timeout_handler(void *pcontext) > { > unsigned long irql; > struct recv_reorder_ctrl *preorder_ctrl = > - (struct recv_reorder_ctrl *)pcontext; > + pcontext; Coccinelle doesn't

Re: [Outreachy kernel] [PATCH 5/5] staging: rtl8712: Remove unnecessary cast on void pointer

> @@ -635,7 +635,7 @@ void r8712_reordering_ctrl_timeout_handler(void *pcontext) > { > unsigned long irql; > struct recv_reorder_ctrl *preorder_ctrl = > - (struct recv_reorder_ctrl *)pcontext; > + pcontext; Coccinelle doesn't

[PATCH] clk: sunxi-ng: sun5i: Fix mux width for csi clock

Mux for CSI clock is 3 bits, not 2. Signed-off-by: Priit Laes --- drivers/clk/sunxi-ng/ccu-sun5i.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/sunxi-ng/ccu-sun5i.c b/drivers/clk/sunxi-ng/ccu-sun5i.c index 06edaa5..5c476f9 100644 ---

[PATCH] clk: sunxi-ng: sun5i: Fix mux width for csi clock

Mux for CSI clock is 3 bits, not 2. Signed-off-by: Priit Laes --- drivers/clk/sunxi-ng/ccu-sun5i.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/sunxi-ng/ccu-sun5i.c b/drivers/clk/sunxi-ng/ccu-sun5i.c index 06edaa5..5c476f9 100644 ---

[RFC PATCH 01/12] staging: android: ion: Remove dmap_cnt

The reference counting of dma_map calls was removed. Remove the associated counter field as well. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion_priv.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/staging/android/ion/ion_priv.h

[RFC PATCH 01/12] staging: android: ion: Remove dmap_cnt

The reference counting of dma_map calls was removed. Remove the associated counter field as well. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion_priv.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/staging/android/ion/ion_priv.h

[RFC PATCH 11/12] staging: android: ion: Make Ion heaps selectable

Currently, all heaps are compiled in all the time. In switching to a better platform model, let's allow these to be compiled out for good measure. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/Kconfig| 32

[RFC PATCH 11/12] staging: android: ion: Make Ion heaps selectable

Currently, all heaps are compiled in all the time. In switching to a better platform model, let's allow these to be compiled out for good measure. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/Kconfig| 32 drivers/staging/android/ion/Makefile | 8 +++--

[RFC PATCH 09/12] cma: Introduce cma_for_each_area

Frameworks (e.g. Ion) may want to iterate over each possible CMA area to allow for enumeration. Introduce a function to allow a callback. Signed-off-by: Laura Abbott --- include/linux/cma.h | 2 ++ mm/cma.c| 14 ++ 2 files changed, 16 insertions(+)

[RFC PATCH 09/12] cma: Introduce cma_for_each_area

Frameworks (e.g. Ion) may want to iterate over each possible CMA area to allow for enumeration. Introduce a function to allow a callback. Signed-off-by: Laura Abbott --- include/linux/cma.h | 2 ++ mm/cma.c| 14 ++ 2 files changed, 16 insertions(+) diff --git

[RFC PATCH 10/12] staging: android: ion: Use CMA APIs directly

When CMA was first introduced, its primary use was for DMA allocation and the only way to get CMA memory was to call dma_alloc_coherent. This put Ion in an awkward position since there was no device structure readily available and setting one up messed up the coherency model. These days, CMA can

[RFC PATCH 10/12] staging: android: ion: Use CMA APIs directly

When CMA was first introduced, its primary use was for DMA allocation and the only way to get CMA memory was to call dma_alloc_coherent. This put Ion in an awkward position since there was no device structure readily available and setting one up messed up the coherency model. These days, CMA can

[RFC PATCH 06/12] staging: android: ion: Remove crufty cache support

Now that we call dma_map in the dma_buf API callbacks there is no need to use the existing cache APIs. Remove the sync ioctl and the existing bad dma_sync calls. Explicit caching can be handled with the dma_buf sync API. Signed-off-by: Laura Abbott ---

[RFC PATCH 06/12] staging: android: ion: Remove crufty cache support

Now that we call dma_map in the dma_buf API callbacks there is no need to use the existing cache APIs. Remove the sync ioctl and the existing bad dma_sync calls. Explicit caching can be handled with the dma_buf sync API. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion-ioctl.c

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: > The following Coccinelle script was used to detect this: > @r@ > expression x; > void* e; > type T; > identifier f; > @@ > ( > *((T *)e) > > > > ((T *)x)[...] > > > > ((T*)x)->f > > > > - (T*) > e > ) NAK. Nice, but you

Re: [PATCH 3/5] staging: lustre: lustre: Remove unnecessary cast on void pointer

On Fri, 2017-03-03 at 02:49 +0530, simran singhal wrote: > The following Coccinelle script was used to detect this: > @r@ > expression x; > void* e; > type T; > identifier f; > @@ > ( > *((T *)e) > > > > ((T *)x)[...] > > > > ((T*)x)->f > > > > - (T*) > e > ) NAK. Nice, but you

[RFC PATCH 04/12] staging: android: ion: Call dma_map_sg for syncing and mapping

Technically, calling dma_buf_map_attachment should return a buffer properly dma_mapped. Add calls to dma_map_sg to begin_cpu_access to ensure this happens. As a side effect, this lets Ion buffers take advantage of the dma_buf sync ioctls. Signed-off-by: Laura Abbott ---

[RFC PATCH 04/12] staging: android: ion: Call dma_map_sg for syncing and mapping

Technically, calling dma_buf_map_attachment should return a buffer properly dma_mapped. Add calls to dma_map_sg to begin_cpu_access to ensure this happens. As a side effect, this lets Ion buffers take advantage of the dma_buf sync ioctls. Signed-off-by: Laura Abbott ---

[RFC PATCH 08/12] cma: Store a name in the cma structure

Frameworks that may want to enumerate CMA heaps (e.g. Ion) will find it useful to have an explicit name attached to each region. Store the name in each CMA structure. Signed-off-by: Laura Abbott --- drivers/base/dma-contiguous.c | 5 +++-- include/linux/cma.h |

Re: [PATCH 02/26] rewrite READ_ONCE/WRITE_ONCE

On Thu, Mar 2, 2017 at 8:00 PM, Christian Borntraeger wrote: > On 03/02/2017 06:55 PM, Arnd Bergmann wrote: >> On Thu, Mar 2, 2017 at 5:51 PM, Christian Borntraeger >> wrote: >>> On 03/02/2017 05:38 PM, Arnd Bergmann wrote: This attempts

[RFC PATCH 08/12] cma: Store a name in the cma structure

Frameworks that may want to enumerate CMA heaps (e.g. Ion) will find it useful to have an explicit name attached to each region. Store the name in each CMA structure. Signed-off-by: Laura Abbott --- drivers/base/dma-contiguous.c | 5 +++-- include/linux/cma.h | 4 +++- mm/cma.c

Re: [PATCH 02/26] rewrite READ_ONCE/WRITE_ONCE

On Thu, Mar 2, 2017 at 8:00 PM, Christian Borntraeger wrote: > On 03/02/2017 06:55 PM, Arnd Bergmann wrote: >> On Thu, Mar 2, 2017 at 5:51 PM, Christian Borntraeger >> wrote: >>> On 03/02/2017 05:38 PM, Arnd Bergmann wrote: This attempts a rewrite of the two macros, using a simpler

[RFC PATCH 07/12] staging: android: ion: Remove old platform support

Device specific platform support has been haphazard for Ion. There have been several independent attempts and there are still objections to what bindings exist right now. Just remove everything for a fresh start. Signed-off-by: Laura Abbott ---

[RFC PATCH 12/12] staging; android: ion: Enumerate all available heaps

Practiaclly speaking, most Ion heaps are either going to be available all the time (system heaps) or found based off of the reserved-memory node. Parse the CMA and reserved-memory nodes to assign the heaps. Signed-off-by: Laura Abbott ---

[RFC PATCH 07/12] staging: android: ion: Remove old platform support

Device specific platform support has been haphazard for Ion. There have been several independent attempts and there are still objections to what bindings exist right now. Just remove everything for a fresh start. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/Kconfig

[RFC PATCH 12/12] staging; android: ion: Enumerate all available heaps

Practiaclly speaking, most Ion heaps are either going to be available all the time (system heaps) or found based off of the reserved-memory node. Parse the CMA and reserved-memory nodes to assign the heaps. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/Makefile| 2 +-

[RFC PATCH 03/12] staging: android: ion: Duplicate sg_table

Ion currently returns a single sg_table on each dma_map call. This is incorrect for later usage. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 30 +- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git

[RFC PATCH 03/12] staging: android: ion: Duplicate sg_table

Ion currently returns a single sg_table on each dma_map call. This is incorrect for later usage. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 30 +- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git

[RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

Hi, There's been some recent discussions[1] about Ion-like frameworks. There's apparently interest in just keeping Ion since it works reasonablly well. This series does what should be the final clean ups for it to possibly be moved out of staging. This includes the following: - Some general

[RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

Hi, There's been some recent discussions[1] about Ion-like frameworks. There's apparently interest in just keeping Ion since it works reasonablly well. This series does what should be the final clean ups for it to possibly be moved out of staging. This includes the following: - Some general

[RFC PATCH 05/12] staging: android: ion: Remove page faulting support

The new method of syncing with dma_map means that the page faulting sync implementation is no longer applicable. Remove it. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 117 -- 1 file changed, 117 deletions(-) diff

[RFC PATCH 02/12] staging: android: ion: Remove alignment from allocation field

The align field was supposed to be used to specify the alignment of the allocation. Nobody actually does anything with it except to check if the alignment specified is out of bounds. Since this has no effect on the actual allocation, just remove it. Signed-off-by: Laura Abbott

[RFC PATCH 05/12] staging: android: ion: Remove page faulting support

The new method of syncing with dma_map means that the page faulting sync implementation is no longer applicable. Remove it. Signed-off-by: Laura Abbott --- drivers/staging/android/ion/ion.c | 117 -- 1 file changed, 117 deletions(-) diff --git

[RFC PATCH 02/12] staging: android: ion: Remove alignment from allocation field

The align field was supposed to be used to specify the alignment of the allocation. Nobody actually does anything with it except to check if the alignment specified is out of bounds. Since this has no effect on the actual allocation, just remove it. Signed-off-by: Laura Abbott ---

Re: [PATCH net v4 0/2] net: ethernet: bgmac: bug fixes

From: Jon Mason Date: Tue, 28 Feb 2017 13:41:49 -0500 > Changes in v4: > * Added the udelays from the previous code (per David Miller) > > Changes in v3: > * Reworked the init sequence patch to only remove the device reset if > the device is actually in reset. Given

Re: [PATCH net v4 0/2] net: ethernet: bgmac: bug fixes

From: Jon Mason Date: Tue, 28 Feb 2017 13:41:49 -0500 > Changes in v4: > * Added the udelays from the previous code (per David Miller) > > Changes in v3: > * Reworked the init sequence patch to only remove the device reset if > the device is actually in reset. Given that this code doesn't

Re: tty: panic in tty_ldisc_restore

On Thu, Mar 02, 2017 at 08:30:48PM +0100, Dmitry Vyukov wrote: > On Thu, Mar 2, 2017 at 8:27 PM, Greg Kroah-Hartman > wrote: > >> > >> >> Hello, > >> > >> >> > >> > >> >> Syzkaller fuzzer started crashing kernel with the following > >> > >> >> panics:

Re: tty: panic in tty_ldisc_restore

On Thu, Mar 02, 2017 at 08:30:48PM +0100, Dmitry Vyukov wrote: > On Thu, Mar 2, 2017 at 8:27 PM, Greg Kroah-Hartman > wrote: > >> > >> >> Hello, > >> > >> >> > >> > >> >> Syzkaller fuzzer started crashing kernel with the following > >> > >> >> panics: > >> > >> >> > >> >

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