-next-20180706.orig/drivers/staging/rtl8192u/r8192U.h
+++ linux-next-20180706/drivers/staging/rtl8192u/r8192U.h
@@ -18,6 +18,7 @@
#ifndef R819xU_H
#define R819xU_H
+#include
#include
#include
#include
--- linux-next-20180706.orig/drivers/staging/rtl8192u/r8192U_core.c
+++ linux-next
From: Tobias Lindskog
When ashmem_shrink is called from direct reclaim on a user thread, a
call to do_fallocate will check for permissions against the security
policy of that user thread. It can thus fail by chance if called on a
thread that isn't permitted to modify the relevant ashmem areas.
> -Original Message-
> From: Roy Pledge
> Sent: Friday, July 6, 2018 9:52 PM
> To: Horia Geanta ; de...@driverdev.osuosl.org;
> linux-arm-ker...@lists.infradead.org; gre...@linuxfoundation.org; Leo Li
> ; Ioana Ciocoi Radulescu
>
> Cc: Laurentiu Tudor ; linux-
> ker...@vger.kernel.org;
remove parentheses reported as unnecessary by checkpatch
Signed-off-by: Tim Collier
---
drivers/staging/wlan-ng/prism2mgmt.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/wlan-ng/prism2mgmt.c
b/drivers/staging/wlan-ng/prism2mgmt.c
index
checkpatch reports "CHECK: Logical continuations should be on the
previous line" when a continuation line begins with an
operator. Reformat the code so that the operator appears at the end of
the line being continued.
Signed-off-by: Tim Collier
---
drivers/staging/wlan-ng/prism2mgmt.c | 10
Fix issues reported by checkpatch regarding the correct point to split
lines for coninuation and unnecessary parentheses.
Tim Collier (3):
staging: wlan-ng: fix expression continuation in prism2fw.c
staging: wlan-ng: fix expression continuation in prism2mgmt.c
staging: wlan-ng: remove
checkpatch reports "CHECK: Logical continuations should be on the
previous line" when a continuation line begins with an
operator. Reformat the code so that the operator appears at the end of
the line being continued.
Signed-off-by: Tim Collier
---
drivers/staging/wlan-ng/prism2fw.c | 7 ---
On 7/6/2018 8:25 AM, Horia Geanta wrote:
> On 7/5/2018 10:41 PM, Roy Pledge wrote:
>> Move the NXP DPIO (Datapath I/O driver) from the staging/fsl-mc/bus/dpio
>> directory to the drivers/soc/fsl directory.
>>
>> The DPIO driver enables access to the Queue and Buffer Managemer (QBMAN)
>> hardware
> -Original Message-
> On Fri, 6 Jul 2018, Thomas Gleixner wrote:
> > On Fri, 6 Jul 2018, KY Srinivasan wrote:
> > > >
> > > > The problem is that the wreckage is in Linus tree and needs to be fixed
> > > > there, i.e. via x86/urgent.
> > > >
> > > > Now we have the new bits queued in
On Fri, 6 Jul 2018, Michael Kelley (EOSG) wrote:
> > -Original Message-
> > From: Thomas Gleixner
> > Sent: Friday, July 6, 2018 3:42 AM
> > To: KY Srinivasan
> > Cc: Ingo Molnar ; x...@kernel.org;
> > gre...@linuxfoundation.org; linux-
> > ker...@vger.kernel.org;
> -Original Message-
> From: Thomas Gleixner
> Sent: Friday, July 6, 2018 3:42 AM
> To: KY Srinivasan
> Cc: Ingo Molnar ; x...@kernel.org;
> gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canonical.com;
>
On Thu, Jul 05, 2018 at 07:45:41PM -0400, Peter Vernia wrote:
> Replaces instances of "unsigned" with "unsigned int" in pinctrl-mt7621.c
>
> Signed-off-by: Peter Vernia
> ---
> drivers/staging/mt7621-pinctrl/pinctrl-rt2880.c | 27
> +
> 1 file changed, 14 insertions(+),
On 7/5/2018 10:41 PM, Roy Pledge wrote:
> Move the NXP DPIO (Datapath I/O driver) from the staging/fsl-mc/bus/dpio
> directory to the drivers/soc/fsl directory.
>
> The DPIO driver enables access to the Queue and Buffer Managemer (QBMAN)
> hardware of NXP DPAA2 devices. This is a prerequiste for
All functions declared in rtl8192c_rf.h have no definition/are not used
in any other file/anywhere. Checked with 'git grep '.
Signed-off-by: Michael Straube
---
.../staging/rtl8723bs/include/rtl8192c_rf.h | 28 ---
.../staging/rtl8723bs/include/rtl8723b_rf.h | 1 -
2 files
On Fri, 6 Jul 2018, Thomas Gleixner wrote:
> On Fri, 6 Jul 2018, KY Srinivasan wrote:
> > >
> > > The problem is that the wreckage is in Linus tree and needs to be fixed
> > > there, i.e. via x86/urgent.
> > >
> > > Now we have the new bits queued in x86/hyperv already which collide. So
> > > we
* Thomas Gleixner wrote:
> On Fri, 6 Jul 2018, Ingo Molnar wrote:
> > * KY Srinivasan wrote:
> > > I am confused. The label ipi_mask_done was introduced in this patch
> > > (the patch under question fixes a circular dependency in this patch):
> > >
> > > commit
On Fri, 6 Jul 2018, KY Srinivasan wrote:
> >
> > The problem is that the wreckage is in Linus tree and needs to be fixed
> > there, i.e. via x86/urgent.
> >
> > Now we have the new bits queued in x86/hyperv already which collide. So
> > we
> > need to merge x86/urgent into x86/hyperv after
This function only has one caller so mask_width is 1 and mask_shift is
32. Shifting an int by 32 bits is undefined, but I guess on GCC it
wraps to 0x1? Anyway it's supposed to be 0x1.
Fixes: 9a69f5087ccc ("drivers/staging: Gasket driver framework + Apex driver")
Signed-off-by: Dan
The > should be >= or we end up writing one element beyond the end of
the interrupt_data->eventfd_ctxs[] array.
Fixes: 9a69f5087ccc ("drivers/staging: Gasket driver framework + Apex driver")
Signed-off-by: Dan Carpenter
diff --git a/drivers/staging/gasket/gasket_interrupt.c
We forgot to set the error code on this error path so ret can be
uninitialized.
Fixes: 9a69f5087ccc ("drivers/staging: Gasket driver framework + Apex driver")
Signed-off-by: Dan Carpenter
diff --git a/drivers/staging/gasket/gasket_core.c
b/drivers/staging/gasket/gasket_core.c
index
20 matches
Mail list logo
