[PATCH 20/46] selinux: Move four assignments for the variable "rc" in range_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 19:55:00 +0100 One local variable was set to an error code in four cases before a concrete error situation was detected. Thus move the corresponding assignments into if branches to indicate a software failure there.

[PATCH 20/46] selinux: Move four assignments for the variable "rc" in range_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 19:55:00 +0100 One local variable was set to an error code in four cases before a concrete error situation was detected. Thus move the corresponding assignments into if branches to indicate a software failure there. Signed-off-by: Markus Elfring ---

Re: [patch v2] mm, memcg: do not retry precharge charges

On Sat, Jan 14, 2017 at 09:42:48PM -0800, David Rientjes wrote: > On Sat, 14 Jan 2017, Johannes Weiner wrote: > > > The OOM killer livelock was the motivation for this patch. With that > > ruled out, what's the point of this patch? Try a bit less hard to move > > charges during task migration? >

Re: [patch v2] mm, memcg: do not retry precharge charges

On Sat, Jan 14, 2017 at 09:42:48PM -0800, David Rientjes wrote: > On Sat, 14 Jan 2017, Johannes Weiner wrote: > > > The OOM killer livelock was the motivation for this patch. With that > > ruled out, what's the point of this patch? Try a bit less hard to move > > charges during task migration? >

[PATCH 19/46] selinux: Return directly after a failed next_entry() in range_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 19:35:59 +0100 Return directly after a call of the function "next_entry" failed at the beginning. Signed-off-by: Markus Elfring --- security/selinux/ss/policydb.c | 2 +- 1 file changed,

[PATCH 19/46] selinux: Return directly after a failed next_entry() in range_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 19:35:59 +0100 Return directly after a call of the function "next_entry" failed at the beginning. Signed-off-by: Markus Elfring --- security/selinux/ss/policydb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 18/46] selinux: One function call less in filename_trans_read() after error detection

From: Markus Elfring Date: Sat, 14 Jan 2017 19:19:42 +0100 Adjust a jump target to avoid a function call at the end after a memory allocation failed for the local variable "ft". Signed-off-by: Markus Elfring ---

[PATCH 18/46] selinux: One function call less in filename_trans_read() after error detection

From: Markus Elfring Date: Sat, 14 Jan 2017 19:19:42 +0100 Adjust a jump target to avoid a function call at the end after a memory allocation failed for the local variable "ft". Signed-off-by: Markus Elfring --- security/selinux/ss/policydb.c | 3 ++- 1 file changed, 2 insertions(+), 1

[PATCH 17/46] selinux: Delete an unnecessary variable assignment in filename_trans_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 19:02:42 +0100 The local variable "ft" was set to a null pointer despite of an immediate reassignment. Thus remove this statement from the beginning of a loop. Signed-off-by: Markus Elfring

[PATCH 17/46] selinux: Delete an unnecessary variable assignment in filename_trans_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 19:02:42 +0100 The local variable "ft" was set to a null pointer despite of an immediate reassignment. Thus remove this statement from the beginning of a loop. Signed-off-by: Markus Elfring --- security/selinux/ss/policydb.c | 1 - 1 file changed, 1

[PATCH 16/46] selinux: Move two assignments for the variable "rc" in filename_trans_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 18:50:52 +0100 One local variable was set to an error code in two cases before a concrete error situation was detected. Thus move the corresponding assignments into if branches to indicate a software failure there.

[PATCH 16/46] selinux: Move two assignments for the variable "rc" in filename_trans_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 18:50:52 +0100 One local variable was set to an error code in two cases before a concrete error situation was detected. Thus move the corresponding assignments into if branches to indicate a software failure there. Signed-off-by: Markus Elfring ---

[PATCH 15/46] selinux: One check and function call less in genfs_read() after error detection

From: Markus Elfring Date: Sat, 14 Jan 2017 18:29:20 +0100 Adjust a jump target to avoid a check repetition at the end after a memory allocation failed for the local variable "newgenfs". Signed-off-by: Markus Elfring ---

[PATCH 15/46] selinux: One check and function call less in genfs_read() after error detection

From: Markus Elfring Date: Sat, 14 Jan 2017 18:29:20 +0100 Adjust a jump target to avoid a check repetition at the end after a memory allocation failed for the local variable "newgenfs". Signed-off-by: Markus Elfring --- security/selinux/ss/policydb.c | 4 ++-- 1 file changed, 2

[PATCH 14/46] selinux: One function call less in genfs_read() after null pointer detection

From: Markus Elfring Date: Sat, 14 Jan 2017 17:43:47 +0100 Call the function "kfree" at the end only after it was determined that the local variable "newgenfs" contained a non-null pointer. Signed-off-by: Markus Elfring ---

[PATCH 14/46] selinux: One function call less in genfs_read() after null pointer detection

From: Markus Elfring Date: Sat, 14 Jan 2017 17:43:47 +0100 Call the function "kfree" at the end only after it was determined that the local variable "newgenfs" contained a non-null pointer. Signed-off-by: Markus Elfring --- security/selinux/ss/policydb.c | 5 +++-- 1 file changed, 3

[PATCH 13/46] selinux: Move four assignments for the variable "rc" in genfs_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 17:21:59 +0100 One local variable was set to an error code in four cases before a concrete error situation was detected. Thus move the corresponding assignments into if branches to indicate a software failure there.

[PATCH 13/46] selinux: Move four assignments for the variable "rc" in genfs_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 17:21:59 +0100 One local variable was set to an error code in four cases before a concrete error situation was detected. Thus move the corresponding assignments into if branches to indicate a software failure there. Signed-off-by: Markus Elfring ---

[PATCH 12/46] selinux: Move assignments for two pointers in genfs_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 16:56:51 +0100 Move the assignment for the local variables "newc" and "newgenfs" behind a call of the function "next_entry" at the beginning so that they will only be set after a successful call. Signed-off-by: Markus

[PATCH 12/46] selinux: Move assignments for two pointers in genfs_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 16:56:51 +0100 Move the assignment for the local variables "newc" and "newgenfs" behind a call of the function "next_entry" at the beginning so that they will only be set after a successful call. Signed-off-by: Markus Elfring ---

[PATCH 11/46] selinux: Return directly after a failed next_entry() in genfs_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 16:34:25 +0100 Return directly after a call of the function "next_entry" failed at the beginning. Signed-off-by: Markus Elfring --- security/selinux/ss/policydb.c | 2 +- 1 file changed,

[PATCH 11/46] selinux: Return directly after a failed next_entry() in genfs_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 16:34:25 +0100 Return directly after a call of the function "next_entry" failed at the beginning. Signed-off-by: Markus Elfring --- security/selinux/ss/policydb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 10/46] selinux: Move some assignments for the variable "rc" in policydb_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 15:22:29 +0100 One local variable was set to an error code in some cases before a concrete error situation was detected. Thus move the corresponding assignments into if branches to indicate a software failure there.

[PATCH 10/46] selinux: Move some assignments for the variable "rc" in policydb_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 15:22:29 +0100 One local variable was set to an error code in some cases before a concrete error situation was detected. Thus move the corresponding assignments into if branches to indicate a software failure there. Signed-off-by: Markus Elfring ---

[PATCH 09/46] selinux: Delete an error message for a failed memory allocation in policydb_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 14:20:41 +0100 Omit an extra message for a memory allocation failure in this function. Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf Signed-off-by: Markus Elfring

[PATCH 09/46] selinux: Delete an error message for a failed memory allocation in policydb_read()

From: Markus Elfring Date: Sat, 14 Jan 2017 14:20:41 +0100 Omit an extra message for a memory allocation failure in this function. Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf Signed-off-by: Markus Elfring ---

[PATCH 08/46] selinux: Delete an unnecessary return statement in policydb_destroy()

From: Markus Elfring Date: Sat, 14 Jan 2017 14:00:02 +0100 The script "checkpatch.pl" pointed information out like the following. WARNING: void function return statements are not generally useful Thus remove such a statement in the affected function.

[PATCH 08/46] selinux: Delete an unnecessary return statement in policydb_destroy()

From: Markus Elfring Date: Sat, 14 Jan 2017 14:00:02 +0100 The script "checkpatch.pl" pointed information out like the following. WARNING: void function return statements are not generally useful Thus remove such a statement in the affected function. Signed-off-by: Markus Elfring ---

[PATCH 07/46] selinux: Delete unnecessary variable assignments in policydb_index()

From: Markus Elfring Date: Sat, 14 Jan 2017 13:40:25 +0100 The local variable "rc" was reset with an error code up to five times before a memory allocation failure was detected. Add a jump target so that this assignment will only be performed after a concrete

[PATCH 07/46] selinux: Delete unnecessary variable assignments in policydb_index()

From: Markus Elfring Date: Sat, 14 Jan 2017 13:40:25 +0100 The local variable "rc" was reset with an error code up to five times before a memory allocation failure was detected. Add a jump target so that this assignment will only be performed after a concrete software failure. Signed-off-by:

[PATCH 06/46] selinux: Use kcalloc() in policydb_index()

From: Markus Elfring Date: Sat, 14 Jan 2017 13:08:59 +0100 Multiplications for the size determination of memory allocations indicated that array data structures should be processed. Thus use the corresponding function "kcalloc". This issue was detected by using

[PATCH 06/46] selinux: Use kcalloc() in policydb_index()

From: Markus Elfring Date: Sat, 14 Jan 2017 13:08:59 +0100 Multiplications for the size determination of memory allocations indicated that array data structures should be processed. Thus use the corresponding function "kcalloc". This issue was detected by using the Coccinelle software.

[PATCH 05/46] selinux: Adjust four checks for null pointers

From: Markus Elfring Date: Sat, 14 Jan 2017 12:36:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script "checkpatch.pl" pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH 05/46] selinux: Adjust four checks for null pointers

From: Markus Elfring Date: Sat, 14 Jan 2017 12:36:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script "checkpatch.pl" pointed information out like the following. Comparison to NULL could be written !… Thus fix affected source code

[PATCH 04/46] selinux: Use kmalloc_array() in hashtab_create()

From: Markus Elfring Date: Sat, 14 Jan 2017 12:06:13 +0100 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected

[PATCH 04/46] selinux: Use kmalloc_array() in hashtab_create()

From: Markus Elfring Date: Sat, 14 Jan 2017 12:06:13 +0100 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle

[PATCH 03/46] selinux: Improve size determinations in four functions

From: Markus Elfring Date: Sat, 14 Jan 2017 11:22:12 +0100 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer. Signed-off-by: Markus Elfring

[PATCH 03/46] selinux: Improve size determinations in four functions

From: Markus Elfring Date: Sat, 14 Jan 2017 11:22:12 +0100 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer. Signed-off-by: Markus Elfring ---

[PATCH 02/46] selinux: Delete an unnecessary return statement in cond_compute_av()

From: Markus Elfring Date: Sat, 14 Jan 2017 11:00:23 +0100 The script "checkpatch.pl" pointed information out like the following. WARNING: void function return statements are not generally useful Thus remove such a statement in the affected function.

[PATCH 02/46] selinux: Delete an unnecessary return statement in cond_compute_av()

From: Markus Elfring Date: Sat, 14 Jan 2017 11:00:23 +0100 The script "checkpatch.pl" pointed information out like the following. WARNING: void function return statements are not generally useful Thus remove such a statement in the affected function. Signed-off-by: Markus Elfring ---

Re: [PATCH v9 1/3] gpio: exar: add gpio for exar cards

On Sun, Jan 15, 2017 at 12:50 AM, Sudip Mukherjee wrote: > From: Sudip Mukherjee > > Exar XR17V352/354/358 chips have 16 multi-purpose inputs/outputs which > can be controlled using gpio interface. > > Add the gpio specific code.

Re: [PATCH v9 1/3] gpio: exar: add gpio for exar cards

On Sun, Jan 15, 2017 at 12:50 AM, Sudip Mukherjee wrote: > From: Sudip Mukherjee > > Exar XR17V352/354/358 chips have 16 multi-purpose inputs/outputs which > can be controlled using gpio interface. > > Add the gpio specific code. Thanks for an updated code. Briefly looking into first two

[PATCH 01/46] selinux: Use kmalloc_array() in cond_init_bool_indexes()

From: Markus Elfring Date: Sat, 14 Jan 2017 10:48:28 +0100 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was

[PATCH 01/46] selinux: Use kmalloc_array() in cond_init_bool_indexes()

From: Markus Elfring Date: Sat, 14 Jan 2017 10:48:28 +0100 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle

[PATCH 00/46] SELinux: Fine-tuning for several function implementations

From: Markus Elfring Date: Sun, 15 Jan 2017 15:15:14 +0100 Several update suggestions were taken into account from static source code analysis. Markus Elfring (46): Use kmalloc_array() in cond_init_bool_indexes() Delete an unnecessary return statement in

[PATCH 00/46] SELinux: Fine-tuning for several function implementations

From: Markus Elfring Date: Sun, 15 Jan 2017 15:15:14 +0100 Several update suggestions were taken into account from static source code analysis. Markus Elfring (46): Use kmalloc_array() in cond_init_bool_indexes() Delete an unnecessary return statement in cond_compute_av() Improve size

Re: Calling device_init_wakeup() on driver removal

On Saturday, January 14, 2017 08:46:05 PM Guenter Roeck wrote: > Hi folks, Hi, > while looking through driver initialization and removal functions, I noticed > that many drivers > call device_init_wakeup(dev, false) in the removal function. Given that the > driver is about > to be removed,

Re: Calling device_init_wakeup() on driver removal

On Saturday, January 14, 2017 08:46:05 PM Guenter Roeck wrote: > Hi folks, Hi, > while looking through driver initialization and removal functions, I noticed > that many drivers > call device_init_wakeup(dev, false) in the removal function. Given that the > driver is about > to be removed,

Re: [PATCH v4] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

Am 13.01.2017 um 21:03 schrieb Kevin Hilman: > Neil Armstrong writes: > >> The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of the memory space, >> this patch adds this reserved zone and redefines the usable memory range. >> >> The memory node is also moved from

Re: [PATCH v4] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

Am 13.01.2017 um 21:03 schrieb Kevin Hilman: > Neil Armstrong writes: > >> The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of the memory space, >> this patch adds this reserved zone and redefines the usable memory range. >> >> The memory node is also moved from the dtsi files into the

Re: [PATCH 02/19] staging: iio: isl29028: remove enable flag from isl29028_enable_proximity()

On 14/01/17 20:00, Brian Masney wrote: > On Sun, Dec 04, 2016 at 11:16:04AM +, Jonathan Cameron wrote: >> On 04/12/16 02:19, Brian Masney wrote: >>> isl29028_enable_proximity() has a boolean argument named enable. This >>> function is only called once and the enable flag is set to true in that

Re: [PATCH 02/19] staging: iio: isl29028: remove enable flag from isl29028_enable_proximity()

On 14/01/17 20:00, Brian Masney wrote: > On Sun, Dec 04, 2016 at 11:16:04AM +, Jonathan Cameron wrote: >> On 04/12/16 02:19, Brian Masney wrote: >>> isl29028_enable_proximity() has a boolean argument named enable. This >>> function is only called once and the enable flag is set to true in that

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

On Sun, Jan 15, 2017 at 03:15:35PM +0100, Jason A. Donenfeld wrote: > On Sun, Jan 15, 2017 at 3:11 PM, Jason A. Donenfeld wrote: > > According to Ralf, it's queued up for 4.11? Is that right? > > It's in -next: > > Part 1: >

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

On Sun, Jan 15, 2017 at 03:15:35PM +0100, Jason A. Donenfeld wrote: > On Sun, Jan 15, 2017 at 3:11 PM, Jason A. Donenfeld wrote: > > According to Ralf, it's queued up for 4.11? Is that right? > > It's in -next: > > Part 1: >

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

On Sun, Jan 15, 2017 at 3:11 PM, Jason A. Donenfeld wrote: > According to Ralf, it's queued up for 4.11? Is that right? It's in -next: Part 1: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=fe8bd18ffea5327344d4ec2bf11f47951212abd0 Part 2:

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

On Sun, Jan 15, 2017 at 3:11 PM, Jason A. Donenfeld wrote: > According to Ralf, it's queued up for 4.11? Is that right? It's in -next: Part 1: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=fe8bd18ffea5327344d4ec2bf11f47951212abd0 Part 2:

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

Hi Greg, On Sun, Jan 15, 2017 at 2:48 PM, Greg Kroah-Hartman wrote: > How many patches is the irqstacks "feature" for MIPS? What kernel was > it released in? Have any git commit ids I can look at? According to Ralf, it's queued up for 4.11? Is that right? Part 1:

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

Hi Greg, On Sun, Jan 15, 2017 at 2:48 PM, Greg Kroah-Hartman wrote: > How many patches is the irqstacks "feature" for MIPS? What kernel was > it released in? Have any git commit ids I can look at? According to Ralf, it's queued up for 4.11? Is that right? Part 1:

cc1: error: '-march=r3000' requires '-mfp32'

Hi James, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f4d3935e4f4884ba80561db5549394afb8eef8f7 commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 3 months ago config:

cc1: error: '-march=r3000' requires '-mfp32'

Hi James, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f4d3935e4f4884ba80561db5549394afb8eef8f7 commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 3 months ago config:

Re: [PATCH 0/3] ti,ads7950 device tree bindings

On 11/01/17 17:52, David Lechner wrote: > This series adds device tree bindings for the TI ADS7950 family of A/DC chips. > The series includes the bindings documentation and some fixes to the iio > driver > to make it work with the device tree bindings. > > FYI, the ads7950 driver has not made

Re: [PATCH 0/3] ti,ads7950 device tree bindings

On 11/01/17 17:52, David Lechner wrote: > This series adds device tree bindings for the TI ADS7950 family of A/DC chips. > The series includes the bindings documentation and some fixes to the iio > driver > to make it work with the device tree bindings. > > FYI, the ads7950 driver has not made

Re: [PATCH 3/3] iio: adc: ti-ads7950: Change regulator matching string to "vref"

On 14/01/17 18:09, David Lechner wrote: > On 01/14/2017 06:52 AM, Jonathan Cameron wrote: >> On 11/01/17 17:52, David Lechner wrote: >>> This changes the reference voltage regulator matching string from "refin" >>> to "vref". This is to be consistent with other A/DC chips that also use >>>

Re: [PATCH 3/3] iio: adc: ti-ads7950: Change regulator matching string to "vref"

On 14/01/17 18:09, David Lechner wrote: > On 01/14/2017 06:52 AM, Jonathan Cameron wrote: >> On 11/01/17 17:52, David Lechner wrote: >>> This changes the reference voltage regulator matching string from "refin" >>> to "vref". This is to be consistent with other A/DC chips that also use >>>

Re: [PATCH 2/3] iio: adc: ti-ads7950: Drop "ti-" prefix from module name

On 14/01/17 18:07, David Lechner wrote: > On 01/14/2017 06:49 AM, Jonathan Cameron wrote: >> On 11/01/17 17:52, David Lechner wrote: >>> This drops the "ti-" prefix from the module name. It makes the module name >>> consistent with other iio ti-ads* drivers and it makes the driver work >>> with

Re: [PATCH 2/3] iio: adc: ti-ads7950: Drop "ti-" prefix from module name

On 14/01/17 18:07, David Lechner wrote: > On 01/14/2017 06:49 AM, Jonathan Cameron wrote: >> On 11/01/17 17:52, David Lechner wrote: >>> This drops the "ti-" prefix from the module name. It makes the module name >>> consistent with other iio ti-ads* drivers and it makes the driver work >>> with

Re: [PATCH] drm/i915: Avoid drm_atomic_state_put(NULL) in intel_display_resume

Hi Chris, this fixes the problem for me, thanks! Tested-by: Stefan Seyfried Am 15.01.2017 um 13:58 schrieb Chris Wilson: > intel_display_resume() may be called without a atomic state to restore, > i.e. dev_priv->modeset_reset_restore state is NULL. One such case

Re: [PATCH] drm/i915: Avoid drm_atomic_state_put(NULL) in intel_display_resume

Hi Chris, this fixes the problem for me, thanks! Tested-by: Stefan Seyfried Am 15.01.2017 um 13:58 schrieb Chris Wilson: > intel_display_resume() may be called without a atomic state to restore, > i.e. dev_priv->modeset_reset_restore state is NULL. One such case is > following a lid open/close

Re: [PATCH 1/3] DT/bindings: Add bindings for TI ADS7950 A/DC chips

On 14/01/17 18:00, David Lechner wrote: > On 01/14/2017 06:53 AM, Jonathan Cameron wrote: >> On 11/01/17 17:52, David Lechner wrote: >>> This adds device tree bindings for the TI ADS7950 family of A/DC chips. >>> >>> Signed-off-by: David Lechner >> This is in of itself good,

Re: [PATCH 1/3] DT/bindings: Add bindings for TI ADS7950 A/DC chips

On 14/01/17 18:00, David Lechner wrote: > On 01/14/2017 06:53 AM, Jonathan Cameron wrote: >> On 11/01/17 17:52, David Lechner wrote: >>> This adds device tree bindings for the TI ADS7950 family of A/DC chips. >>> >>> Signed-off-by: David Lechner >> This is in of itself good, but we may need to

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

On Sun, Jan 15, 2017 at 02:39:49PM +0100, Jason A. Donenfeld wrote: > Hi James, > > On Fri, Jan 13, 2017 at 10:49 AM, James Hogan wrote: > > Its quite a significant change/feature, especially in terms of potential > > for further breakage. I don't think its really stable

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

On Sun, Jan 15, 2017 at 02:39:49PM +0100, Jason A. Donenfeld wrote: > Hi James, > > On Fri, Jan 13, 2017 at 10:49 AM, James Hogan wrote: > > Its quite a significant change/feature, especially in terms of potential > > for further breakage. I don't think its really stable material to be > >

arch/xtensa/include/asm/initialize_mmu.h:41: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Pete, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f4d3935e4f4884ba80561db5549394afb8eef8f7 commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for Diamond 233L - Rev C processor variant

arch/xtensa/include/asm/initialize_mmu.h:41: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Pete, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f4d3935e4f4884ba80561db5549394afb8eef8f7 commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for Diamond 233L - Rev C processor variant

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

Hi James, On Fri, Jan 13, 2017 at 10:49 AM, James Hogan wrote: > Its quite a significant change/feature, especially in terms of potential > for further breakage. I don't think its really stable material to be > honest. It sounds bad if the kernel stack requirement can be

Re: [PATCH v3 0/5] MIPS: Add per-cpu IRQ stack

Hi James, On Fri, Jan 13, 2017 at 10:49 AM, James Hogan wrote: > Its quite a significant change/feature, especially in terms of potential > for further breakage. I don't think its really stable material to be > honest. It sounds bad if the kernel stack requirement can be made > arbitrarily

Re: [alsa-devel] [PATCH 1/1] ASoC: fsl_asrc: use dma_transfer_direction enum when calling dmaengine_prep_dma_cyclic

On Sun, Jan 15, 2017 at 10:43 AM, Nicolas Iooss wrote: > When fsl_asrc_dma_prepare_and_submit() calls > dmaengine_prep_dma_cyclic(), it uses either DMA_TO_DEVICE or > DMA_FROM_DEVICE. These values are both items of dma_data_direction enum, > not of dma_data_direction

Re: [alsa-devel] [PATCH 1/1] ASoC: fsl_asrc: use dma_transfer_direction enum when calling dmaengine_prep_dma_cyclic

On Sun, Jan 15, 2017 at 10:43 AM, Nicolas Iooss wrote: > When fsl_asrc_dma_prepare_and_submit() calls > dmaengine_prep_dma_cyclic(), it uses either DMA_TO_DEVICE or > DMA_FROM_DEVICE. These values are both items of dma_data_direction enum, > not of dma_data_direction enum, which is the type

arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32'

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f4d3935e4f4884ba80561db5549394afb8eef8f7 commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier

arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32'

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f4d3935e4f4884ba80561db5549394afb8eef8f7 commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier

[PATCH] pcie: ti: Provide patch to force GEN1 PCIe operation

Some devices (due to e.g. bad PCIe signal integrity) require to run with forced GEN1 speed on PCIe bus. This patch changes the speed explicitly on dra7 based devices when proper device tree attribute is defined for the PCIe controller. Signed-off-by: Lukasz Majewski --- Patch

[PATCH] pcie: ti: Provide patch to force GEN1 PCIe operation

Some devices (due to e.g. bad PCIe signal integrity) require to run with forced GEN1 speed on PCIe bus. This patch changes the speed explicitly on dra7 based devices when proper device tree attribute is defined for the PCIe controller. Signed-off-by: Lukasz Majewski --- Patch applies on newest

Re: [PATCH v2 2/2] iio: distance: srf08: add IIO driver for us ranger

On 14/01/17 17:48, Andreas Klinger wrote: > Hi Jonathan, > > see comments below. > > Andreas > > > Jonathan Cameron schrieb am Sat, 14. Jan 12:17: >> On 10/01/17 18:48, Andreas Klinger wrote: >>> This is the IIO driver for devantech srf08 ultrasonic ranger which can be >>>

Re: [PATCH v2 2/2] iio: distance: srf08: add IIO driver for us ranger

On 14/01/17 17:48, Andreas Klinger wrote: > Hi Jonathan, > > see comments below. > > Andreas > > > Jonathan Cameron schrieb am Sat, 14. Jan 12:17: >> On 10/01/17 18:48, Andreas Klinger wrote: >>> This is the IIO driver for devantech srf08 ultrasonic ranger which can be >>> used to measure the

arch/mips/vdso/elf.S:1:0: error: '-march=r3000' requires '-mfp32'

Hi Alex, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f4d3935e4f4884ba80561db5549394afb8eef8f7 commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO date: 1 year, 2 months ago

arch/mips/vdso/elf.S:1:0: error: '-march=r3000' requires '-mfp32'

Hi Alex, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f4d3935e4f4884ba80561db5549394afb8eef8f7 commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO date: 1 year, 2 months ago

[PATCH] drm/i915: Avoid drm_atomic_state_put(NULL) in intel_display_resume

intel_display_resume() may be called without a atomic state to restore, i.e. dev_priv->modeset_reset_restore state is NULL. One such case is following a lid open/close event and the forced modeset in intel_lid_notiy(). Reported-by: Stefan Seyfried Fixes:

[PATCH] drm/i915: Avoid drm_atomic_state_put(NULL) in intel_display_resume

intel_display_resume() may be called without a atomic state to restore, i.e. dev_priv->modeset_reset_restore state is NULL. One such case is following a lid open/close event and the forced modeset in intel_lid_notiy(). Reported-by: Stefan Seyfried Fixes: 0853695c3ba4 ("drm: Add reference

Linux 4.9.4

I'm announcing the release of the 4.9.4 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.9.4

diff --git a/Makefile b/Makefile index ae42a0aaab06..9175706bfe7f 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 3 +SUBLEVEL = 4 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/configs/qcom_defconfig b/arch/arm/configs/qcom_defconfig

Linux 4.9.4

I'm announcing the release of the 4.9.4 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.9.4

diff --git a/Makefile b/Makefile index ae42a0aaab06..9175706bfe7f 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 3 +SUBLEVEL = 4 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/configs/qcom_defconfig b/arch/arm/configs/qcom_defconfig

Re: Linux 4.4.43

diff --git a/Makefile b/Makefile index b8a90f9a463d..04a2186a4276 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 42 +SUBLEVEL = 43 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm/mach-omap2/omap-mpuss-lowpower.c

Re: Linux 4.4.43

diff --git a/Makefile b/Makefile index b8a90f9a463d..04a2186a4276 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 42 +SUBLEVEL = 43 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm/mach-omap2/omap-mpuss-lowpower.c

Linux 4.4.43

I'm announcing the release of the 4.4.43 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Linux 4.4.43

I'm announcing the release of the 4.4.43 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

[PATCH] staging: rtl8192e: rtl8192e: Remove NULL test before vfree

vfree frees the virtually continuous block of memory beginning at addr. If addr is NULL, no operation is performed. So, NULL test is not needed before vfree. Signed-off-by: Shyam Saini --- drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 6 ++ 1 file changed, 2

[PATCH] staging: rtl8192e: rtl8192e: Remove NULL test before vfree

vfree frees the virtually continuous block of memory beginning at addr. If addr is NULL, no operation is performed. So, NULL test is not needed before vfree. Signed-off-by: Shyam Saini --- drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-)

[PATCH 1/1] ASoC: fsl_asrc: use dma_transfer_direction enum when calling dmaengine_prep_dma_cyclic

When fsl_asrc_dma_prepare_and_submit() calls dmaengine_prep_dma_cyclic(), it uses either DMA_TO_DEVICE or DMA_FROM_DEVICE. These values are both items of dma_data_direction enum, not of dma_data_direction enum, which is the type expected by dmaengine_prep_dma_cyclic(). Replace DMA_TO_DEVICE with

[PATCH 1/1] ASoC: fsl_asrc: use dma_transfer_direction enum when calling dmaengine_prep_dma_cyclic

When fsl_asrc_dma_prepare_and_submit() calls dmaengine_prep_dma_cyclic(), it uses either DMA_TO_DEVICE or DMA_FROM_DEVICE. These values are both items of dma_data_direction enum, not of dma_data_direction enum, which is the type expected by dmaengine_prep_dma_cyclic(). Replace DMA_TO_DEVICE with

<    1   2   3   4   5   6   7   >