[PATCH] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-05 Thread Olav Haugan
succeeds. Change-Id: Ifff930dcf254915b497aec5cb36f152a5e5365d6 Signed-off-by: Olav Haugan ohau...@codeaurora.org --- drivers/staging/zsmalloc/zsmalloc-main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc

Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-06 Thread Olav Haugan
On 11/6/2013 12:56 PM, Nitin Gupta wrote: On Tue, Nov 5, 2013 at 5:17 PM, David Cohen david.a.co...@linux.intel.com wrote: Hi Olav, On 11/05/2013 04:54 PM, Olav Haugan wrote: zsmalloc encodes a handle using the page pfn and an object index. On some hardware platforms the pfn could be 0

Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-06 Thread Olav Haugan
On 11/5/2013 5:56 PM, Greg KH wrote: On Tue, Nov 05, 2013 at 04:54:12PM -0800, Olav Haugan wrote: zsmalloc encodes a handle using the page pfn and an object index. On some hardware platforms the pfn could be 0 and this causes the encoded handle to be 0 which is interpreted as an allocation

Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-07 Thread Olav Haugan
On 11/6/2013 7:06 PM, Greg KH wrote: On Wed, Nov 06, 2013 at 04:00:02PM -0800, Olav Haugan wrote: On 11/5/2013 5:56 PM, Greg KH wrote: On Tue, Nov 05, 2013 at 04:54:12PM -0800, Olav Haugan wrote: zsmalloc encodes a handle using the page pfn and an object index. On some hardware platforms

[PATCH v2] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-07 Thread Olav Haugan
will not be 0 when allocation succeeds. Signed-off-by: Olav Haugan ohau...@codeaurora.org --- drivers/staging/zsmalloc/zsmalloc-main.c | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc

[PATCH v3 1/1] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-22 Thread Olav Haugan
memory starting at 0x0. All MSM8974 SoCs which includes Google Nexus 5 devices are affected. To prevent this false error we ensure that the encoded handle will not be 0 when allocation succeeds. Signed-off-by: Olav Haugan ohau...@codeaurora.org --- drivers/staging/zsmalloc/zsmalloc-main.c | 17

[PATCH v3 0/1] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-22 Thread Olav Haugan
v3: Updated commit text with info about affected SoCs. v2: Added comments to code. Updated commit text. Olav Haugan (1): staging: zsmalloc: Ensure handle is never 0 on success drivers/staging/zsmalloc/zsmalloc-main.c | 17 + 1 file changed, 13 insertions(+), 4 deletions

Re: [PATCH v2] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-12 Thread Olav Haugan
Hi Greg, On 11/11/2013 4:19 PM, Greg KH wrote: On Thu, Nov 07, 2013 at 05:58:03PM -0800, Olav Haugan wrote: zsmalloc encodes a handle using the pfn and an object index. On hardware platforms with physical memory starting at 0x0 the pfn can be 0. This causes the encoded handle to be 0

Re: zram/zsmalloc issues in very low memory conditions

2013-10-31 Thread Olav Haugan
Hi Luigi, On 10/24/2013 6:12 PM, Luigi Semenzato wrote: On Thu, Oct 24, 2013 at 5:35 PM, Olav Haugan ohau...@codeaurora.org wrote: Hi Bob, Luigi, On 10/23/2013 5:55 PM, Bob Liu wrote: On 10/24/2013 05:51 AM, Olav Haugan wrote: By the way, could you take a try with zswap? Which can write

Re: zram/zsmalloc issues in very low memory conditions

2013-11-01 Thread Olav Haugan
On 10/25/2013 2:19 AM, Minchan Kim wrote: Hello, I had no enough time to think over your great questions since I should enjoy in Edinburgh so if I miss something, Sorry! On Wed, Oct 23, 2013 at 02:51:34PM -0700, Olav Haugan wrote: I am trying to use zram in very low memory conditions

zram/zsmalloc issues in very low memory conditions

2013-10-23 Thread Olav Haugan
. Is this feasible? Thanks, Olav Haugan -- The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http

Re: zram/zsmalloc issues in very low memory conditions

2013-10-24 Thread Olav Haugan
Hi Bob, Luigi, On 10/23/2013 5:55 PM, Bob Liu wrote: On 10/24/2013 05:51 AM, Olav Haugan wrote: I am trying to use zram in very low memory conditions and I am having some issues. zram is in the reclaim path. So if the system is very low on memory the system is trying to reclaim pages

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-07-10 Thread Olav Haugan
On 7/9/2014 3:54 AM, Will Deacon wrote: On Wed, Jul 09, 2014 at 02:07:38AM +0100, Olav Haugan wrote: On 6/30/2014 2:52 AM, Will Deacon wrote: On Fri, Jun 27, 2014 at 11:23:27PM +0100, Olav Haugan wrote: Lets say I have an IOMMU with 2 masters and 2 SMRn slots with the following stream IDs

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-06-24 Thread Olav Haugan
On 6/24/2014 2:18 AM, Will Deacon wrote: On Sat, Jun 21, 2014 at 12:16:25AM +0100, Olav Haugan wrote: On 5/30/2014 12:06 PM, Arnd Bergmann wrote: On Friday 30 May 2014 08:16:05 Rob Herring wrote: Presumably the ID would be the streamID on ARM's SMMU. How would a master with 8 streamIDs

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-06-24 Thread Olav Haugan
On 6/24/2014 11:11 AM, Will Deacon wrote: On Tue, Jun 24, 2014 at 06:57:44PM +0100, Olav Haugan wrote: On 6/24/2014 2:18 AM, Will Deacon wrote: On Sat, Jun 21, 2014 at 12:16:25AM +0100, Olav Haugan wrote: We have multiple-master SMMUs and each master emits a variable number of StreamIDs

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-06-20 Thread Olav Haugan
; }; master@b { ... iommus = iommu StreamID3 MASK3, iommu StreamID4 MASK4; }; Thanks, Olav Haugan -- The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-06-27 Thread Olav Haugan
On 6/25/2014 2:18 AM, Will Deacon wrote: On Tue, Jun 24, 2014 at 10:35:54PM +0100, Olav Haugan wrote: On 6/24/2014 11:11 AM, Will Deacon wrote: On Tue, Jun 24, 2014 at 06:57:44PM +0100, Olav Haugan wrote: On 6/24/2014 2:18 AM, Will Deacon wrote: On Sat, Jun 21, 2014 at 12:16:25AM +0100, Olav

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-07-08 Thread Olav Haugan
On 6/30/2014 2:52 AM, Will Deacon wrote: Hi Olav, On Fri, Jun 27, 2014 at 11:23:27PM +0100, Olav Haugan wrote: On 6/25/2014 2:18 AM, Will Deacon wrote: Why can't it be dynamically detected? Whilst the StreamIDs are fixed in hardware (from the SMMU architecture perspective), the SMRs

Re: [PATCH v4] devicetree: Add generic IOMMU device tree bindings

2014-07-15 Thread Olav Haugan
On 7/13/2014 4:43 AM, Rob Clark wrote: On Sun, Jul 13, 2014 at 5:43 AM, Will Deacon will.dea...@arm.com wrote: On Sat, Jul 12, 2014 at 01:57:31PM +0100, Rob Clark wrote: On Sat, Jul 12, 2014 at 8:22 AM, Arnd Bergmann a...@arndb.de wrote: On Saturday 12 July 2014, Rob Clark wrote: Was there

[PATCH] sched: Update task->on_rq when tasks are moving between runqueues

2015-10-24 Thread Olav Haugan
should be TASK_ON_RQ_MIGRATING Signed-off-by: Olav Haugan <ohau...@codeaurora.org> --- kernel/sched/core.c | 2 ++ kernel/sched/deadline.c | 4 kernel/sched/rt.c | 4 3 files changed, 10 insertions(+) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 10a8faa..5c

Re: [PATCH] sched: Update task->on_rq when tasks are moving between runqueues

2015-10-28 Thread Olav Haugan
On 15-10-25 11:09:24, Peter Zijlstra wrote: > On Sat, Oct 24, 2015 at 11:01:02AM -0700, Olav Haugan wrote: > > Task->on_rq has three states: > > 0 - Task is not on runqueue (rq) > > 1 (TASK_ON_RQ_QUEUED) - Task is on rq > > 2 (TASK_ON_RQ_MIGRATING) - Ta

[PATCH] staging: speakup: Clean up checkpatch warnings

2017-02-15 Thread Olav Haugan
Fix checkpatch warnings. Signed-off-by: Olav Haugan <ohau...@codeaurora.org> --- drivers/staging/speakup/synth.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c index a61c02

[PATCHv2 2/2] staging: speakup: (coding style) Limit line to 80 chars

2017-02-16 Thread Olav Haugan
Fix checkpatch warning about line being over 80 characters. Signed-off-by: Olav Haugan <ohau...@codeaurora.org> --- drivers/staging/speakup/synth.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c

[PATCHv2 0/2] Checkpatch fixes for speakup

2017-02-16 Thread Olav Haugan
v2: -Split fixes into separate patches Olav Haugan (2): staging: speakup: (coding style) Simplify comparisons to NULL staging: speakup: (coding style) Limit line to 80 chars drivers/staging/speakup/synth.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions

[PATCHv2 1/2] staging: speakup: (coding style) Simplify comparisons to NULL

2017-02-16 Thread Olav Haugan
Fix checkpatch check notices by simplifying comparisons to NULL. Signed-off-by: Olav Haugan <ohau...@codeaurora.org> --- drivers/staging/speakup/synth.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/s

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

2017-06-12 Thread Olav Haugan
On 17-06-12 13:29:04, Catalin Marinas wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); > > pgprot_t pr

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

2017-06-12 Thread Olav Haugan
On 17-06-12 13:29:04, Catalin Marinas wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); > > pgprot_t pr

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

2017-06-12 Thread Olav Haugan
On 17-06-10 23:03:54, Russell King - ARM Linux wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_de

[PATCH v2] arm64/dma-mapping: Remove extraneous null-pointer checks

2017-06-13 Thread Olav Haugan
The current null-pointer check in __dma_alloc_coherent and __dma_free_coherent is not needed anymore since the __dma_alloc/__dma_free functions won't be called if !dev (dummy ops will be called instead). Signed-off-by: Olav Haugan <ohau...@codeaurora.org> --- arch/arm64/include/asm/dma-map

[PATCH] staging: wlan-ng: prism2mib.c: Fix type cast issues

2017-06-13 Thread Olav Haugan
restricted __le16 [usertype] prism2mib.c:755:22: warning: incorrect type in assignment (different base types) prism2mib.c:755:22:expected unsigned short [unsigned] [usertype] len prism2mib.c:755:22:got restricted __le16 [usertype] Signed-off-by: Olav Haugan <ohau...@codeaurora.org> --- d

[PATCH] arm64/dma-mapping: Fix null-pointer check

2017-06-10 Thread Olav Haugan
The current null-pointer check in __dma_alloc_coherent and __dma_free_coherent is pretty much useless since we are dereferencing the pointer before checking for null. Check for null-pointer before the actual dereferencing of the pointer. Signed-off-by: Olav Haugan <ohau...@codeaurora.

[PATCH] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-05 Thread Olav Haugan
succeeds. Change-Id: Ifff930dcf254915b497aec5cb36f152a5e5365d6 Signed-off-by: Olav Haugan --- drivers/staging/zsmalloc/zsmalloc-main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c index

Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-06 Thread Olav Haugan
On 11/6/2013 12:56 PM, Nitin Gupta wrote: > On Tue, Nov 5, 2013 at 5:17 PM, David Cohen > wrote: >> Hi Olav, >> >> >> On 11/05/2013 04:54 PM, Olav Haugan wrote: >>> >>> zsmalloc encodes a handle using the page pfn and an object >>

Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-06 Thread Olav Haugan
On 11/5/2013 5:56 PM, Greg KH wrote: > On Tue, Nov 05, 2013 at 04:54:12PM -0800, Olav Haugan wrote: >> zsmalloc encodes a handle using the page pfn and an object >> index. On some hardware platforms the pfn could be 0 and this >> causes the encoded handle to be 0

Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-07 Thread Olav Haugan
On 11/6/2013 7:06 PM, Greg KH wrote: > On Wed, Nov 06, 2013 at 04:00:02PM -0800, Olav Haugan wrote: >> On 11/5/2013 5:56 PM, Greg KH wrote: >>> On Tue, Nov 05, 2013 at 04:54:12PM -0800, Olav Haugan wrote: >>>> zsmalloc encodes a handle using the page pfn and an objec

[PATCH v2] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-07 Thread Olav Haugan
will not be 0 when allocation succeeds. Signed-off-by: Olav Haugan --- drivers/staging/zsmalloc/zsmalloc-main.c | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c index 1a67537

[PATCH v3 1/1] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-22 Thread Olav Haugan
memory starting at 0x0. All MSM8974 SoCs which includes Google Nexus 5 devices are affected. To prevent this false error we ensure that the encoded handle will not be 0 when allocation succeeds. Signed-off-by: Olav Haugan --- drivers/staging/zsmalloc/zsmalloc-main.c | 17 + 1 file

[PATCH v3 0/1] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-22 Thread Olav Haugan
v3: Updated commit text with info about affected SoCs. v2: Added comments to code. Updated commit text. Olav Haugan (1): staging: zsmalloc: Ensure handle is never 0 on success drivers/staging/zsmalloc/zsmalloc-main.c | 17 + 1 file changed, 13 insertions(+), 4 deletions

Re: [PATCH v2] staging: zsmalloc: Ensure handle is never 0 on success

2013-11-12 Thread Olav Haugan
Hi Greg, On 11/11/2013 4:19 PM, Greg KH wrote: > On Thu, Nov 07, 2013 at 05:58:03PM -0800, Olav Haugan wrote: >> zsmalloc encodes a handle using the pfn and an object >> index. On hardware platforms with physical memory starting >> at 0x0 the pfn can be 0. This caus

Re: zram/zsmalloc issues in very low memory conditions

2013-10-31 Thread Olav Haugan
Hi Luigi, On 10/24/2013 6:12 PM, Luigi Semenzato wrote: > On Thu, Oct 24, 2013 at 5:35 PM, Olav Haugan wrote: >> Hi Bob, Luigi, >> >> On 10/23/2013 5:55 PM, Bob Liu wrote: >>> >>> On 10/24/2013 05:51 AM, Olav Haugan wrote: >> >>> By the way,

Re: zram/zsmalloc issues in very low memory conditions

2013-11-01 Thread Olav Haugan
On 10/25/2013 2:19 AM, Minchan Kim wrote: > Hello, > > I had no enough time to think over your great questions since I should enjoy > in Edinburgh so if I miss something, Sorry! > > On Wed, Oct 23, 2013 at 02:51:34PM -0700, Olav Haugan wrote: >> I am trying to use

zram/zsmalloc issues in very low memory conditions

2013-10-23 Thread Olav Haugan
s feasible? Thanks, Olav Haugan -- The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More maj

Re: zram/zsmalloc issues in very low memory conditions

2013-10-24 Thread Olav Haugan
Hi Bob, Luigi, On 10/23/2013 5:55 PM, Bob Liu wrote: > > On 10/24/2013 05:51 AM, Olav Haugan wrote: >> I am trying to use zram in very low memory conditions and I am having >> some issues. zram is in the reclaim path. So if the system is very low >> on memory the sys

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-07-10 Thread Olav Haugan
On 7/9/2014 3:54 AM, Will Deacon wrote: > On Wed, Jul 09, 2014 at 02:07:38AM +0100, Olav Haugan wrote: >> On 6/30/2014 2:52 AM, Will Deacon wrote: >>> On Fri, Jun 27, 2014 at 11:23:27PM +0100, Olav Haugan wrote: >>>> Lets say I have an IOMMU with 2 masters and 2 SMRn

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-06-20 Thread Olav Haugan
mber of StreamIDs. However, we have to apply a mask (the ARM SMMU spec allows for this) to the StreamIDs due to limited number of StreamID 2 Context Bank entries in the SMMU. If my understanding is correct we would represent this in the DT like this: iommu { #address-cells = <2>;

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-06-24 Thread Olav Haugan
On 6/24/2014 2:18 AM, Will Deacon wrote: > On Sat, Jun 21, 2014 at 12:16:25AM +0100, Olav Haugan wrote: >> On 5/30/2014 12:06 PM, Arnd Bergmann wrote: >>> On Friday 30 May 2014 08:16:05 Rob Herring wrote: >>>> Presumably the ID would be the streamID on ARM's SMMU.

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-06-24 Thread Olav Haugan
On 6/24/2014 11:11 AM, Will Deacon wrote: > On Tue, Jun 24, 2014 at 06:57:44PM +0100, Olav Haugan wrote: >> On 6/24/2014 2:18 AM, Will Deacon wrote: >>> On Sat, Jun 21, 2014 at 12:16:25AM +0100, Olav Haugan wrote: >>>> We have multiple-master SMMUs and each

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-07-08 Thread Olav Haugan
On 6/30/2014 2:52 AM, Will Deacon wrote: > Hi Olav, > > On Fri, Jun 27, 2014 at 11:23:27PM +0100, Olav Haugan wrote: >> On 6/25/2014 2:18 AM, Will Deacon wrote: >>> Why can't it be dynamically detected? Whilst the StreamIDs are fixed in >>> hardware (from

Re: [PATCH v2] devicetree: Add generic IOMMU device tree bindings

2014-06-27 Thread Olav Haugan
On 6/25/2014 2:18 AM, Will Deacon wrote: > On Tue, Jun 24, 2014 at 10:35:54PM +0100, Olav Haugan wrote: >> On 6/24/2014 11:11 AM, Will Deacon wrote: >>> On Tue, Jun 24, 2014 at 06:57:44PM +0100, Olav Haugan wrote: >>>> On 6/24/2014 2:18 AM, Will Deacon wrote: >&

Re: [PATCH v4] devicetree: Add generic IOMMU device tree bindings

2014-07-15 Thread Olav Haugan
On 7/13/2014 4:43 AM, Rob Clark wrote: > On Sun, Jul 13, 2014 at 5:43 AM, Will Deacon wrote: >> On Sat, Jul 12, 2014 at 01:57:31PM +0100, Rob Clark wrote: >>> On Sat, Jul 12, 2014 at 8:22 AM, Arnd Bergmann wrote: On Saturday 12 July 2014, Rob Clark wrote: >>> Was there actually a good

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

2017-06-12 Thread Olav Haugan
On 17-06-12 13:29:04, Catalin Marinas wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); > > pgprot_t pr

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

2017-06-12 Thread Olav Haugan
On 17-06-10 23:03:54, Russell King - ARM Linux wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_de

Re: [PATCH] arm64/dma-mapping: Fix null-pointer check

2017-06-12 Thread Olav Haugan
On 17-06-12 13:29:04, Catalin Marinas wrote: > On Sat, Jun 10, 2017 at 12:41:10PM -0700, Olav Haugan wrote: > > @@ -149,6 +140,11 @@ static void *__dma_alloc(struct device *dev, size_t > > size, > > bool coherent = is_device_dma_coherent(dev); > > pgprot_t pr

[PATCH v2] arm64/dma-mapping: Remove extraneous null-pointer checks

2017-06-13 Thread Olav Haugan
The current null-pointer check in __dma_alloc_coherent and __dma_free_coherent is not needed anymore since the __dma_alloc/__dma_free functions won't be called if !dev (dummy ops will be called instead). Signed-off-by: Olav Haugan --- arch/arm64/include/asm/dma-mapping.h | 2 -- arch/arm64/mm

[PATCH] staging: wlan-ng: prism2mib.c: Fix type cast issues

2017-06-13 Thread Olav Haugan
restricted __le16 [usertype] prism2mib.c:755:22: warning: incorrect type in assignment (different base types) prism2mib.c:755:22:expected unsigned short [unsigned] [usertype] len prism2mib.c:755:22:got restricted __le16 [usertype] Signed-off-by: Olav Haugan --- drivers/staging/wlan-ng

[PATCH] arm64/dma-mapping: Fix null-pointer check

2017-06-10 Thread Olav Haugan
The current null-pointer check in __dma_alloc_coherent and __dma_free_coherent is pretty much useless since we are dereferencing the pointer before checking for null. Check for null-pointer before the actual dereferencing of the pointer. Signed-off-by: Olav Haugan --- arch/arm64/mm/dma

[PATCH] staging: speakup: Clean up checkpatch warnings

2017-02-15 Thread Olav Haugan
Fix checkpatch warnings. Signed-off-by: Olav Haugan --- drivers/staging/speakup/synth.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c index a61c02ba06da..8340748ae9cb 100644

[PATCHv2 0/2] Checkpatch fixes for speakup

2017-02-16 Thread Olav Haugan
v2: -Split fixes into separate patches Olav Haugan (2): staging: speakup: (coding style) Simplify comparisons to NULL staging: speakup: (coding style) Limit line to 80 chars drivers/staging/speakup/synth.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions

[PATCHv2 1/2] staging: speakup: (coding style) Simplify comparisons to NULL

2017-02-16 Thread Olav Haugan
Fix checkpatch check notices by simplifying comparisons to NULL. Signed-off-by: Olav Haugan --- drivers/staging/speakup/synth.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c index

[PATCHv2 2/2] staging: speakup: (coding style) Limit line to 80 chars

2017-02-16 Thread Olav Haugan
Fix checkpatch warning about line being over 80 characters. Signed-off-by: Olav Haugan --- drivers/staging/speakup/synth.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/speakup/synth.c b/drivers/staging/speakup/synth.c index b57315110e67..8340748ae9cb

Re: [PATCH] sched: Update task->on_rq when tasks are moving between runqueues

2015-10-28 Thread Olav Haugan
On 15-10-25 11:09:24, Peter Zijlstra wrote: > On Sat, Oct 24, 2015 at 11:01:02AM -0700, Olav Haugan wrote: > > Task->on_rq has three states: > > 0 - Task is not on runqueue (rq) > > 1 (TASK_ON_RQ_QUEUED) - Task is on rq > > 2 (TASK_ON_RQ_MIGRATING) - Ta

[PATCH] sched: Update task->on_rq when tasks are moving between runqueues

2015-10-24 Thread Olav Haugan
should be TASK_ON_RQ_MIGRATING Signed-off-by: Olav Haugan --- kernel/sched/core.c | 2 ++ kernel/sched/deadline.c | 4 kernel/sched/rt.c | 4 3 files changed, 10 insertions(+) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 10a8faa..5c7b614 100644 --- a/kernel/sched/core.c