This patch fixes an issue in drivers/hid/hid-input.c where values
outside of the logical range are not clamped when "null state" bit of
the input control is not set.
This was discussed on the lists [1] and this change stems from the fact
due to the ambiguity of the HID specification it might be
The v4.11-rc1 kernel emits the following splat in some configurations:
[ 43.681891] BUG: using smp_processor_id() in preemptible [] code:
kworker/3:1/49
[ 43.682511] caller is debug_smp_processor_id+0x17/0x20
[ 43.682893] CPU: 0 PID: 49 Comm: kworker/3:1 Not tainted 4.11.0-rc1+ #1
On Wed, Mar 08, 2017 at 12:25:59PM +0800, Chen-Yu Tsai wrote:
> On Tue, Mar 7, 2017 at 4:56 PM, Maxime Ripard
> wrote:
> > It seems like what's called a backporch in the datasheet is actually the
> > backporch plus the sync period. Fix that in our driver.
> >
> > Signed-off-by: Maxime Ripard
> >
From: Roy Pledge
Create header for global dpaa2 definitions. Add definitions
for dequeue results.
Signed-off-by: Roy Pledge
Signed-off-by: Stuart Yoder
---
drivers/staging/fsl-mc/include/dpaa2-global.h | 202 +
1 file changed, 202 insertions(+)
create mode 100644
This patch series adds the driver for the DPIO object which is a step to
addressing the final item in the staging TODO list-- adding a functional driver
on top of the bus driver. The DPIO driver is a dependency for other functional
drivers such as Ethernet.
An overview of the DPIO object and
From: Roy Pledge
Add QBman APIs for frame queue and buffer pool operations.
Signed-off-by: Roy Pledge
Signed-off-by: Haiying Wang
Signed-off-by: Stuart Yoder
---
drivers/staging/fsl-mc/bus/dpio/Makefile |2 +-
drivers/staging/fsl-mc/bus/dpio/qbman-portal.c | 1033
From: Roy Pledge
Add global definitions for DPAA2 frame descriptors and scatter
gather entries.
Signed-off-by: Roy Pledge
Signed-off-by: Stuart Yoder
---
drivers/staging/fsl-mc/include/dpaa2-fd.h | 448 +
1 file changed, 448 insertions(+)
create mode 100644
From: Roy Pledge
The DPIO service interface handles initialization of DPIO objects
and exports APIs to be used by other DPAA2 object drivers to perform
queuing and buffer management related operations. The service allows
registration of callbacks when frames or notifications are received.
The DPIO driver registers with the fsl-mc bus to handle bus-related
events for DPIO objects. Key responsibility is mapping I/O
regions, setting up interrupt handlers, and calling the DPIO
service initialization during probe.
Signed-off-by: Roy Pledge
Signed-off-by: Haiying Wang
Signed-off-by:
From: Ioana Radulescu
Add the command build/parse APIs for operating on DPIO objects through
the DPAA2 Management Complex.
Signed-off-by: Ioana Radulescu
Signed-off-by: Roy Pledge
Signed-off-by: Stuart Yoder
---
drivers/staging/fsl-mc/bus/Kconfig | 10 ++
From: Stuart Yoder
add document describing the dpio driver and it's role, components
and major interfaces
Signed-off-by: Stuart Yoder
---
drivers/staging/fsl-mc/bus/dpio/dpio-driver.txt | 135 +++
1 file changed, 135 insertions(+)
create mode 100644
From: Roy Pledge
add Roy Pledge as maintainer of DPIO
Signed-off-by: Roy Pledge
Signed-off-by: Stuart Yoder
---
MAINTAINERS |6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6e06cf4..9c85028 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4040,6
On 03/08, Chao Yu wrote:
> On 2017/3/7 5:51, Jaegeuk Kim wrote:
> > This patch fixes that SSR can overwrite previous warm node block consisting
> > of
> > a node chain since the last checkpoint.
>
> Good catch!
>
> Need to consider the impact to other accesser, e.g. is_checkpointed_data,
>
On Wed, Mar 8, 2017 at 7:50 AM, Christoph Hellwig wrote:
>> - ASSERT(atomic_read(>t_ref) > 0);
>> - atomic_inc(>t_ref);
>> + ASSERT(refcount_read(>t_ref) > 0);
>> + refcount_inc(>t_ref);
>
> With strict refcount semantics refcount_inc should check that
> the count is larger than
From: Matthew Wilcox
memset_l() is like memset() but allows the user to fill the destination
with a pattern which fits in an unsigned long. memset32() and memset64()
are 32-bit and 64-bit variants of this; memset_l() will call the
appropriate one. memset32() is also useful by itself, while I
Thanks for catching that!
Reviewed-by: Lyude Paul
On Wed, 2017-03-08 at 17:22 +0900, Naohiro Aota wrote:
> While commit 5523662edd4f ("Input: add userio module") added userio.h
> under the uapi/ directory, it forgot to add the header file to
> Kbuild.
> Thus, the file is missing from header
On Wed, Mar 8, 2017 at 8:27 AM, Linus Torvalds
wrote:
>
> Hmm. Did you guys miss the patch I sent for this yesterday? It avoided
> the header file dependency, and imho also generated better code by
> uninlining the slow path.
Ahh, I see I have another thread that has reactions to it. Will go
On Tue, Feb 28, 2017 at 10:33 AM, Kyle Huey wrote:
> On Tue, Feb 14, 2017 at 12:11 AM, Kyle Huey wrote:
>> GCC generates lousy code in __switch_to_xtra. This patch series is an
>> updated version of tglx's patches from last year
>> (https://lkml.org/lkml/2016/12/15/432) that address review
On 03/07/2017 09:09 PM, Zhou Chengming wrote:
> From: z00354408
The patch looks correct to me, but please provide a better
changelog for the change. There's nothing here.
--
Jens Axboe
On Wed, Mar 08, 2017 at 01:38:41PM -0800, Thomas Garnier wrote:
> This patch prevents a syscall to modify the address limit of the
> caller. The address limit is kept by the syscall wrapper and restored
> just after the syscall ends.
I would much rather architectures were given the opportunity to
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/fjes/fjes_ethtool.c | 19 +--
1 files
On Wed, Mar 08, 2017 at 12:19:22PM -0800, Andy Lutomirski wrote:
> On Wed, Mar 8, 2017 at 10:48 AM, Andy Lutomirski wrote:
> > Hi-
> >
> > Here are my notes on SGX issues from KS/LPC. It seems that I never
> > emailed it out to a public list -- oops. It may contain any number of
> > typos or
08.03.2017 19:06, Andy Lutomirski пишет:
On Wed, Mar 8, 2017 at 6:08 AM, Stas Sergeev wrote:
08.03.2017 03:32, Ricardo Neri пишет:
These are the instructions covered by UMIP:
* SGDT - Store Global Descriptor Table
* SIDT - Store Interrupt Descriptor Table
* SLDT - Store Local Descriptor Table
On Wed, Mar 08, 2017 at 07:45:42PM +0200, Krzysztof Kozlowski wrote:
> On Mon, Mar 06, 2017 at 03:29:48PM -0600, Nathan Royce wrote:
> > OK, I just tried 4.10.0 and the output is looking the same.
> >
> > I can't say my setup is all that odd. The cryptographic use is only
> > with the swap
[ + Kees, Laura, and Dave ]
On 03/08/2017 08:25 PM, Linus Torvalds wrote:
Adding x86 people too, since this seems to be something off about
ARCH_HAS_SET_MEMORY for x86-32.
The code seems to be shared between x86-32 and 64, I'm not seeing why
set_memory_r[ow]() should fail on one but not the
the
verify_pre_usermode_state function is called.
Signed-off-by: Thomas Garnier
---
Based on next-20170308
---
include/linux/syscalls.h | 19 +++
init/Kconfig | 16
kernel/sys.c | 11 +++
3 files changed, 46 insertions(+)
diff --git a/include/linux
On Wed, Mar 8, 2017 at 2:27 PM, Daniel Borkmann wrote:
> [ 28.474232] rodata_test: test data was not read only
> [...]
In my tests so far, I've never been able to get rodata_test to fail
(Qemu 2.5.0, Ubuntu). I'll retry with your .config and see if I can
recheck under Qemu 2.7.1. Do you see
Linus,
Please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
# HEAD: fc69910f329d61821897871e0e957eda39beb3d8 MIPS: Add missing include
files
These are the fixes for MIPS build failures due to the
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/hyperv/netvsc_drv.c | 39
On Wed, 8 Mar 2017, Thomas Garnier wrote:
> Implement specific usage of verify_pre_usermode_state for user-mode
> returns for arm.
> ---
> Based on next-20170308
> ---
> arch/arm/Kconfig | 1 +
> arch/arm/kernel/entry-common.S | 5 +
> 2 files changed, 6
Hi James,
On Wed, Mar 08, 2017 at 06:44:36PM +, James Morse wrote:
> Hi!
>
> On 03/01/17 06:34, Rajat Jain wrote:
> > Add code to actually configure the L1 substate settigns on the
> > upstream and downstream device, while taking care of the rules
> > dictated by the PCIe spec.
>
> While
On Wed, Mar 8, 2017 at 6:08 AM, Stas Sergeev wrote:
> 08.03.2017 03:32, Ricardo Neri пишет:
>>
>> These are the instructions covered by UMIP:
>> * SGDT - Store Global Descriptor Table
>> * SIDT - Store Interrupt Descriptor Table
>> * SLDT - Store Local Descriptor Table
>> * SMSW - Store Machine
On Wed, 2017-03-08 at 17:19 +0100, Romain Perier wrote:
> The PCI pool API is deprecated. This commit replaces the PCI pool old
> API by the appropriate function with the DMA pool API.
>
> Signed-off-by: Romain Perier
> Acked-by: Peter Senna Tschudin
> Tested-by: Peter Senna Tschudin
> ---
>
On Wed, Mar 8, 2017 at 2:27 PM, Daniel Borkmann wrote:
>
> The issue seems to be accessing buff first (can be read or write access)
> and then doing set_memory_ro() doesn't make it read-only immediately,
> meaning the subsequent call into probe_kernel_write() will succeed without
> error.
>
>
Implement specific usage of verify_pre_usermode_state for user-mode
returns for arm64.
---
Based on next-20170308
---
arch/arm64/Kconfig| 1 +
arch/arm64/kernel/entry.S | 2 ++
2 files changed, 3 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 896eba61e5ed
On Thu, Mar 09 2017, Trond Myklebust wrote:
> On Wed, 2017-03-08 at 11:29 -0500, Jeff Layton wrote:
>> If launder_page fails, then we hit a problem writing back some inode
>> data. Ensure that we communicate that fact in a subsequent fsync
>> since
>> another task could still have it open for
On Wed, Mar 8, 2017 at 12:19 PM, Andy Lutomirski wrote:
> There's a change coming to SGX
> in future CPUs called "Flexible Launch Control" (marketing speak) and
> IA32_PUBKEYHASH (in the SDM)
And if you try to look this up, you'll notice that I typed it wrong.
It's IA32_SGXLEPUBKEYHASH. Whoops.
On Wed, Mar 8, 2017 at 11:05 PM, Dmitry Torokhov
wrote:
> On Wed, Mar 08, 2017 at 10:50:16PM +0200, Andy Shevchenko wrote:
>> On Wed, Mar 8, 2017 at 8:12 PM, Dmitry Torokhov
>> wrote:
>> > On Wed, Mar 08, 2017 at 09:22:17AM +0100, Michał Kępień wrote:
>> If there PDx86 related patches are
On Wed, Mar 08, 2017 at 10:00:40AM +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
On 03/08/2017 10:19 PM, Russell King - ARM Linux wrote:
> On Wed, Mar 08, 2017 at 09:44:17PM +0100, Lars-Peter Clausen wrote:
>> On 03/08/2017 08:59 PM, Russell King - ARM Linux wrote:
>>> On Wed, Mar 08, 2017 at 08:48:31PM +0100, Lars-Peter Clausen wrote:
When the DMA memory is mapped for
While stress testing a usb controller using a bind/unbind looop, the
following error loop was observed.
usb 7-1.2: new low-speed USB device number 3 using xhci-hcd
usb 7-1.2: hub failed to enable device, error -108
usb 7-1-port2: cannot disable (err = -22)
usb 7-1-port2: couldn't allocate
On Thu, Mar 09 2017, Jeff Layton wrote:
> Currently we don't clear the address space error when there is a -EIO
> error on fsynci, due to writeback initiation failure. If writes fail
> with -EIO and the mapping is flagged with an AS_EIO or AS_ENOSPC error,
> then we can end up returning errors on
On Wed, 8 Mar 2017 20:25:33 +0100, Vasile Dumitrescu wrote:
> sudo sensors
> =>
Note that you don't need to be root to run "sensors".
> (...)
> dell_smm-virtual-0
> Adapter: Virtual device
> Processor Fan: 2490 RPM
> Video Fan: 2493 RPM
> CPU:+48.0°C
> Ambient:+48.0°C
>
On 03/08/2017 11:36 PM, Kees Cook wrote:
On Wed, Mar 8, 2017 at 2:27 PM, Daniel Borkmann wrote:
[ 28.474232] rodata_test: test data was not read only
[...]
In my tests so far, I've never been able to get rodata_test to fail
(Qemu 2.5.0, Ubuntu). I'll retry with your .config and see if I
Not all platform drivers have pcm_{new,free} callbacks. Seen with a
"snd-soc-dummy" codec from sound/soc/rockchip/rk3399_gru_sound.c.
Resolves an OOPS seen on v4.11-rc1 with Google Kevin (Samsung Chromebook
Plus):
[2.863304] rk3399-gru-sound sound: HiFi <-> ff88.i2s mapping ok
[
Hi!
> > - CONFIG_FUNCTION_GRAPH_TRACER sets it on x86-32 because of a gcc bug
> > where the stack gets aligned before the mcount call. This issue
> > should be mostly obsolete as most modern compilers now have -mfentry.
> > We could make it dependent on CC_USING_FENTRY.
>
> Yeah. At some
Luis Henriques writes:
> Hi,
>
> I've seen this only once, and can't reproduce it. But here it is anyway:
>
> https://postimg.org/image/pn94k1yov
>
> (Not sure png files are accepted on LKML.)
>
> This occurred in a VM while booting 4.11.0-rc1
Any idea what was happening when you triggered
Implement specific usage of verify_pre_usermode_state for user-mode
returns for x86.
---
Based on next-20170308
---
arch/x86/Kconfig | 1 +
arch/x86/entry/common.c | 3 +++
arch/x86/entry/entry_64.S | 6 ++
3 files changed, 10 insertions(+)
diff --git a/arch/x86/Kconfig b/arch/x86
There's no way to get here with 'err != 0'. Just return 0 to be more
obvious and prevent future changes from accidentally erroring out here
without going through the right error paths.
Signed-off-by: Brian Norris
---
drivers/pci/host/pcie-rockchip.c | 2 +-
1 file changed, 1 insertion(+), 1
The regulator framework can return negative error codes via
regulator_get_current_limit() for regulators that don't provide current
information. The subsequent check for postive values isn't very useful,
if the variable is unsigned.
Let's just match the signedness of the return value.
Prevents
*** THIS IS WIP; DO NOT MERGE ***
I haven't quite figured out the right way to invert pci_remap_iospace().
I guess no one supports this yet? So currently, if you try to
remove/re-probe we'll hit a BUG() in ioremap code when we call this a
second time.
I post the unfinished work here as a bug
On Wed, Mar 08, 2017 at 02:16:56PM -0800, Paul E. McKenney wrote:
> Hello!
>
> I am seeing the following splat in rcutorture testing of v4.11-rc1:
>
> [ 30.694013] =
> [ 30.694013] WARNING: suspicious RCU usage
> [ 30.694013] 4.11.0-rc1+ #1 Not tainted
> [
Signed-off-by: Andrey Utkin
Signed-off-by: Andrey Utkin
Please welcome Anton who is now in charge of solo6x10 and tw5864 support
and development in Bluecherry company, I have sent out to him the
hardware samples I possessed. (We will prepare the patch updating
MAINTAINERS file soon.)
If
On Wed, 8 Mar 2017 16:46:57 +0100
Corentin Labbe wrote:
> Printing copyright does not give any useful information on the boot
> process.
> Furthermore, the email address printed is obsolete since
> commit ba57b6f20429 ("MAINTAINERS: fix bouncing tun/tap entries")
>
> Signed-off-by: Corentin
Hi,
On Thu, Jan 26, 2012 at 07:03:43PM +0100, Denys Vlasenko wrote:
> Hi Linus,
>
> On Thu, Jan 26, 2012 at 4:47 AM, Linus Torvalds
> wrote:
> >> Please look at strace source, get_scno() function, where
> >> it reads syscall no and parameters. Let's see
> >> - POWERPC: has 32-bit and 64-bit
Hi all,
This patch series implements a new transport for 9pfs, aimed at Xen
systems.
The transport is based on a traditional Xen frontend and backend drivers
pair. This patch series implements the frontend, which typically runs in
a regular unprivileged guest.
I also sent a series that
Upon receiving a notification from the backend, schedule the
p9_xen_response work_struct. p9_xen_response checks if any responses are
available, if so, it reads them one by one, calling p9_client_cb to send
them up to the 9p layer (p9_client_cb completes the request). Handle the
ring following the
Implement functions to handle the xenbus handshake. Upon connection,
allocate the rings according to the protocol specification.
Initialize a work_struct and a wait_queue. The work_struct will be used
to schedule work upon receiving an event channel notification from the
backend. The wait_queue
Implement struct p9_trans_module create and close functions by looking
at the available Xen 9pfs frontend-backend connections. We don't expect
many frontend-backend connections, thus walking a list is OK.
Send requests to the backend by copying each request to one of the
available rings (each
This patch adds a Kconfig option and Makefile support for building the
9pfs Xen driver.
Signed-off-by: Stefano Stabellini
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
CC: Eric Van Hensbergen
CC: Ron Minnich
CC: Latchesar Ionkov
CC: v9fs-develo...@lists.sourceforge.net
---
Sync the ring.h file with upstream Xen, to introduce the new ring macros.
They will be used by the Xen transport for 9pfs.
Signed-off-by: Stefano Stabellini
CC: konrad.w...@oracle.com
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
---
NB: The new macros have not been committed to Xen yet.
On 2017/03/08 11:29AM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Mar 08, 2017 at 07:54:12PM +0530, Naveen N. Rao escreveu:
> > Hi Michael,
> >
> > On 2017/03/08 09:43PM, Michael Ellerman wrote:
> > > "Naveen N. Rao" writes:
> > >
> > > > With ABIv2, we offset 8 bytes into a function to get at
It uses the new ring.h macros to declare rings and interfaces.
Signed-off-by: Stefano Stabellini
CC: konrad.w...@oracle.com
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
---
include/xen/interface/io/9pfs.h | 40
1 file changed, 40 insertions(+)
Introduce the Xen 9pfs transport driver: add struct xenbus_driver to
register as a xenbus driver and add struct p9_trans_module to register
as v9fs driver.
All functions are empty stubs for now.
Signed-off-by: Stefano Stabellini
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
CC: Eric Van
On Thu, 2017-03-09 at 08:23 +1100, NeilBrown wrote:
> On Thu, Mar 09 2017, Jeff Layton wrote:
>
> > Currently we don't clear the address space error when there is a -EIO
> > error on fsynci, due to writeback initiation failure. If writes fail
> > with -EIO and the mapping is flagged with an
Hi Kuninori,
On Thu, Mar 09, 2017 at 12:17:41AM +, Kuninori Morimoto wrote:
> > Not all platform drivers have pcm_{new,free} callbacks. Seen with a
> > "snd-soc-dummy" codec from sound/soc/rockchip/rk3399_gru_sound.c.
> (snip)
> > Fixes: 99b04f4c4051 ("ASoC: add Component level
On 03/08/2017 02:36 PM, Kees Cook wrote:
> On Wed, Mar 8, 2017 at 2:27 PM, Daniel Borkmann wrote:
>> [ 28.474232] rodata_test: test data was not read only
>> [...]
>
> In my tests so far, I've never been able to get rodata_test to fail
> (Qemu 2.5.0, Ubuntu). I'll retry with your .config and
Hi Brian
Thank you for your patch
> Not all platform drivers have pcm_{new,free} callbacks. Seen with a
> "snd-soc-dummy" codec from sound/soc/rockchip/rk3399_gru_sound.c.
(snip)
> Fixes: 99b04f4c4051 ("ASoC: add Component level pcm_new/pcm_free")
> Signed-off-by: Brian Norris
> ---
> I'm
On Wed, Mar 08, 2017 at 03:49:19PM -0300, Diego Viola wrote:
> It hangs on resume from suspend if I have USB 3.0 enabled on the BIOS,
> it works fine with ehci_hcd or USB 2.0.
>
> The way I reproduce the problem is with this command:
>
> $ i3lock && systemctl suspend
>
> This is what I see on
Implement specific usage of verify_pre_usermode_state for user-mode
returns for arm.
---
Based on next-20170308
---
arch/arm/Kconfig | 1 +
arch/arm/kernel/entry-common.S | 5 +
2 files changed, 6 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 0d4e71b42c77
On 01/03/2017 at 15:33:23 -0800, Dmitry Torokhov wrote:
> 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
[Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed
16:32) Peter Rosin wrote:
> On 2017-03-08 15:38, Paul Gortmaker wrote:
[...]
> >
> > Note that mux-core doesn't have a .ko (modular variant) and also you can
> > confirm with nm that everything in mux-core.o is in
On 02/03/2017 at 01:27:08 +0100, Sebastian Reichel wrote:
> Motorola was involved in semiconductor and mobile phone business.
> The "motorola," prefix is already used by a couple of bindings:
>
> * rtc/rtc-cmos.txt
> * mfd/motorola-cpcap.txt
> * regulator/cpcap-regulator.txt
>
> Apart from that
On 02/03/2017 at 01:27:09 +0100, Sebastian Reichel wrote:
> This driver supports the Motorola CPCAP PMIC found on
> some of Motorola's mobile phones, such as the Droid 4.
>
> Tested-by: Tony Lindgren
> Signed-off-by: Sebastian Reichel
> ---
> Changes since PATCHv3:
> - Modified DT binding
On 01/03/2017 at 15:34:38 -0800, Dmitry Torokhov wrote:
> Instead of using #ifdef guards around PM methods, let's annotate
> them as __maybe_unused, as it provides better compile coverage.
>
> Also drop empty stub for omap_rtc_runtime_resume().
>
> Signed-off-by: Dmitry Torokhov
> ---
>
From: Jia Jie Ho
This patch enables Altera TSE support for
Arria10 SoC FPGA
Signed-off-by: Jia Jie Ho
---
arch/arm/configs/socfpga_defconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/configs/socfpga_defconfig
b/arch/arm/configs/socfpga_defconfig
index
* Carlos O'Donell [2017-03-08 10:53:00 -0500]:
> On 11/11/2016 07:08 AM, Felix Janda wrote:
> > fixes the following compiler errors when is included
> > after musl :
> >
> > ./linux/in6.h:32:8: error: redefinition of 'struct in6_addr'
> > ./linux/in6.h:49:8: error: redefinition of 'struct
> "Kashyap" == Kashyap Desai writes:
Kashyap,
Kashyap> Agree on this point. I am planning to study all possible such
Kashyap> sanity in driver for VD and not trying to fix one specific
Kashyap> scenario as described here. Do you think fix in this area is
Kashyap> good for kernel-stable as
On Fri, Feb 10, 2017 at 03:44:13PM +0800, Chris Zhong wrote:
> There are 2 Type-c PHYs in RK3399, but only one DP controller. Hence
> only one PHY can connect to DP controller at one time, the other should
> be disconnected. The GRF_SOC_CON26 register has a switch bit to do it,
> set this bit
On 03/08/17 at 11:50am, Borislav Petkov wrote:
> On Wed, Mar 08, 2017 at 06:17:50PM +0800, Baoquan He wrote:
> > All right, I will just update the code comment. Just back ported kaslr
> > to our OS product, people reviewed and found the upper boundary of kaslr
> > mm region is EFI_VA_START, that's
In original driver was implemented support for half-
and full-duplex modes, but it was not enabled. Instead
of it ks8851_rx_1msg method always returns "true" that
means "full-duplex" mode.
This patch replaces hard-coded functionality with
flexible solution that supports both SPI modes.
Hi Brian
> > It is a littlle bit strange for me.
>
> Yes, and honestly I'm a little confused by the inheritance in this
> framework.
Yes, I agree :)
This is 1st prepare for future ALSA SoC framework cleanup
It is Lars-Peter's idea
> I have a feeling you're checking the wrong thing below for
On 03/08/2017 07:14 PM, Szabolcs Nagy wrote:
> * Carlos O'Donell [2017-03-08 10:53:00 -0500]:
>> On 11/11/2016 07:08 AM, Felix Janda wrote:
>>> fixes the following compiler errors when is included
>>> after musl :
>>>
>>> ./linux/in6.h:32:8: error: redefinition of 'struct in6_addr'
>>>
As the driver is using generic device properties, it should work
properly when CONFIG_OF is turned off. This patch removes the
ifdef CONFIGOF and make sure the driver always have of_match_table.
Signed-off-by: Jingkui Wang
---
drivers/input/misc/drv260x.c | 4 +---
1 file changed, 1
On Wed, Mar 08, 2017 at 04:54:02PM -0800, Jingkui Wang wrote:
> As the driver is using generic device properties, it should work
> properly when CONFIG_OF is turned off. This patch removes the
> ifdef CONFIGOF and make sure the driver always have of_match_table.
>
> Signed-off-by: Jingkui Wang
>
On Wed, 2017-03-08 at 19:53 +0300, Stas Sergeev wrote:
> 08.03.2017 19:46, Andy Lutomirski пишет:
> >> No no, since I meant prot mode, this is not what I need.
> >> I would never need to disable UMIP as to allow the
> >> prot mode apps to do SLDT. Instead it would be good
> >> to have an ability
Sorry.. my text editor was misconfigured. Will fix and send again.
On Wed, Mar 8, 2017 at 5:08 PM, Dmitry Torokhov
wrote:
> On Wed, Mar 08, 2017 at 04:54:02PM -0800, Jingkui Wang wrote:
>> As the driver is using generic device properties, it should work
>> properly when CONFIG_OF is turned off.
On Wed, 2017-03-08 at 08:46 -0800, Andy Lutomirski wrote:
> On Wed, Mar 8, 2017 at 8:29 AM, Stas Sergeev wrote:
> > 08.03.2017 19:06, Andy Lutomirski пишет:
> >>
> >> On Wed, Mar 8, 2017 at 6:08 AM, Stas Sergeev wrote:
> >>>
> >>> 08.03.2017 03:32, Ricardo Neri пишет:
>
> These are the
We have seen a few incidents lately where a dst_enty has been freed
with a dangling TCP socket reference (sk->sk_dst_cache) pointing to that
dst_entry. If the conditions/timings are right a crash then ensues when the
freed dst_entry is referenced later on. A Common crashing back trace is:
#8 []
The MTR_DRAM_WIDTH macro returns the data width. It is sometimes used as
if it returned a boolean true if the width if 8. This patch fixes the
tests where MTR_DRAM_WIDTH is misused.
Signed-off-by: Jérémy Lefaure
---
drivers/edac/i5000_edac.c | 2 +-
drivers/edac/i5400_edac.c | 5 +++--
2 files
Balbir Singh writes:
> On Wed, 2017-03-08 at 15:26 +0800, Huang, Ying wrote:
>> From: Huang Ying
>>
>> This patch make it possible to charge or uncharge a set of continuous
>> swap entries in the swap cgroup. The number of swap entries is
>> specified via an added parameter.
>>
>> This will
Am Mittwoch, 8. März 2017, 16:39:23 CET schrieb Brian Norris:
> On Fri, Feb 10, 2017 at 03:44:13PM +0800, Chris Zhong wrote:
> > There are 2 Type-c PHYs in RK3399, but only one DP controller. Hence
> > only one PHY can connect to DP controller at one time, the other should
> > be disconnected. The
On 01/10/2017 03:02 PM, Mike Kravetz wrote:
> Another more concrete topic is hugetlb reservations. Michal Hocko
> proposed the topic "mm patches review bandwidth", and brought up the
> related subject of areas in need of attention from an architectural
> POV. I suggested that hugetlb
On 2017/3/8 21:35, Kinglong Mee wrote:
> On 3/8/2017 20:08, Chao Yu wrote:
>> In commit d9cdc9033181 ("ext4 crypto: enforce context consistency") we
>> declared that:
>>
>> 2) All files or directories in a directory must be protected using the
>> same key as their containing directory.
>>
>>
On Wed, Mar 08, 2017 at 02:43:44PM -0800, Linus Torvalds wrote:
On Wed, Mar 8, 2017 at 2:27 PM, Daniel Borkmann wrote:
The issue seems to be accessing buff first (can be read or write access)
and then doing set_memory_ro() doesn't make it read-only immediately,
meaning the subsequent call
From: Eric Biggers
As is the case for a number of other architectures that have a 32-bit
compat mode, enable KEYS_COMPAT if both COMPAT and KEYS are enabled.
This allows AArch32 programs to use the keyctl() system call when
running on an AArch64 kernel.
Signed-off-by: Eric Biggers
---
Hi,
On 03/08/17 at 04:45pm, Baoquan He wrote:
> Forgot cc to Boris, add him.
>
> On 03/08/17 at 04:18pm, Dave Young wrote:
> > On 03/08/17 at 03:47pm, Baoquan He wrote:
> > > EFI allocate runtime services regions down from EFI_VA_START, -4G.
> > > It should be top-down handling.
> > >
> > >
Hi Ingo and Thomas,
Are these patches acceptable to you? We want to get these upstream as soon as
possible, so please send along any more comments you have. If you're annoyed by
the format of the emails just let me know and I'll resubmit.
Thank you,
Andrew
On 2/17/17 4:06 PM, Andrew Banman
On Wed, 2017-03-08 at 17:08 +0300, Stas Sergeev wrote:
> 08.03.2017 03:32, Ricardo Neri пишет:
> > These are the instructions covered by UMIP:
> > * SGDT - Store Global Descriptor Table
> > * SIDT - Store Interrupt Descriptor Table
> > * SLDT - Store Local Descriptor Table
> > * SMSW - Store
Hi, Matthew,
Matthew Wilcox writes:
> On Wed, Mar 08, 2017 at 03:26:05PM +0800, Huang, Ying wrote:
>> In this patch, the size of the swap cluster is changed to that of the
>> THP (Transparent Huge Page) on x86_64 architecture (512). This is for
>> the THP swap support on x86_64. Where one
1501 - 1600 of 1714 matches
Mail list logo
