Re: [PATCH 0/7] KVM: syzkaller fixes

2016-06-01 14:09+0200, Paolo Bonzini: > These fix most of the bugs reported by Dmitry Vyukov a while back. > I couldn't reproduce one of the bugs (patch 7) but the fix is easy. > Probably, more VM ioctls should take kvm->lock, but I have not looked > at it yet. Applied, thanks. > I have only

Re: [PATCH] coresight: Remove erroneous dma_free_coherent in tmc_probe

On 31 May 2016 at 11:47, Suzuki K Poulose wrote: > commit de5461970b3e9e194 ("coresight: tmc: allocating memory when needed") > removed the static allocation of buffer for the trace data in ETR mode in > tmc_probe. However it failed to remove the "devm_free_coherent" in

[PATCH] sched, cpuidle: Do not access cpuidle_devices when !CONFIG_CPU_IDLE

The cpuidle_devices per-CPU variable is only defined when CPU_IDLE is enabled. Commit c8cc7d4de7a4 ("sched/idle: Reorganize the idle loop") removed the #ifdef CONFIG_CPU_IDLE around cpuidle_idle_call() with the compiler optimising away __this_cpu_read(cpuidle_devices). However, with CONFIG_UBSAN

Re: [PATCH 4.6 000/100] 4.6.1-stable review

On Tue, May 31, 2016 at 10:35:32PM -0700, Guenter Roeck wrote: > On 05/30/2016 01:48 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.6.1 release. > > There are 100 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH] tipc: fix an infoleak in tipc_nl_compat_link_dump

link_info.str is a char array of size 60. Memory after the NULL byte is not initialized. Sending the whole object out can cause a leak. Signed-off-by: Kangjie Lu --- net/tipc/netlink_compat.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/tipc/netlink_compat.c

Re: [RFC PATCH 0/2] scpi: Add SCPI framework to handle vendors variants

On 01/06/16 17:30, Kevin Hilman wrote: [ + Heiko, who may know about the Rockchip implementation ] Sudeep Holla writes: On 30/05/16 09:30, Neil Armstrong wrote: On 05/27/2016 10:17 AM, Neil Armstrong wrote: [..] While looking for other ARMv8 based platform, I

Re: [PATCH 3/3] tda998x: add HPD delay to avoid disabling sound when EDID checksum fails.

On Tue, May 31, 2016 at 05:58:31PM +0100, Joao Pinto wrote: > Hi Russell, > > On 5/30/2016 8:10 PM, Russell King - ARM Linux wrote: > > On Mon, May 30, 2016 at 04:15:54PM +0100, Joao Pinto wrote: > >> When using ffplay to reproduce video+sound it was noticed that sometimes > >> the > >> sound

Re: [PATCH 3/3] tda998x: add HPD delay to avoid disabling sound when EDID checksum fails.

On 6/1/2016 5:32 PM, Russell King - ARM Linux wrote: > On Tue, May 31, 2016 at 05:58:31PM +0100, Joao Pinto wrote: >> Hi Russell, >> >> On 5/30/2016 8:10 PM, Russell King - ARM Linux wrote: >>> On Mon, May 30, 2016 at 04:15:54PM +0100, Joao Pinto wrote: When using ffplay to reproduce

[PATCH] x86, fpu: add tracepoints to dump FPU state at key points

I posted this a few months ago, and Ingo sounded like he'd be willing to merge this. So here goes. -- From: Dave Hansen I've been carrying this patch around for a bit and it's helped me solve at least a couple FPU-related bugs. In addition to using it for

Re: [RFC PATCH] sched: fix hierarchical order in rq->leaf_cfs_rq_list

Peter Zijlstra writes: > On Tue, May 24, 2016 at 11:55:10AM +0200, Vincent Guittot wrote: >> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c >> index 218f8e8..6d3fbf2 100644 >> --- a/kernel/sched/fair.c >> +++ b/kernel/sched/fair.c >> @@ -290,15 +290,31 @@ static

Re: [PATCH 2/5] x86, perf: use Intel family macros for core perf events

On Wed, Jun 01, 2016 at 10:34:42AM -0700, Dave Hansen wrote: > > From: Dave Hansen > > Use the new model number macros instead of spelling things out > in the comments. > > Note that this is missing a Nehalem model that is mentioned in > intel_idle. Is that a a

[PATCH v2] of: add vendor prefix for UniWest

United Western Technologies Corp, known primarily as UniWest, is a manufacturer of eddy current and ultrasonic testing equipment. Signed-off-by: Joshua Clayton --- This vendor string is needed primarily for a imx6q-env.dts which made its way into mainline through the

Re: [PATCH v5 5/6] clocksource/drivers/arm_arch_timer: Simplify ACPI support code.

fu@linaro.org wrote: diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig index 47352d2..5a5baa1 100644 --- a/drivers/clocksource/Kconfig +++ b/drivers/clocksource/Kconfig @@ -8,6 +8,7 @@ config CLKSRC_OF config CLKSRC_ACPI bool select CLKSRC_PROBE +

Re: [RFC PATCH 0/4] Make inotify instance/watches be accounted per userns

Cc'd the containers list. Nikolay Borisov writes: > Currently the inotify instances/watches are being accounted in the > user_struct structure. This means that in setups where multiple > users in unprivileged containers map to the same underlying > real user (e.g.

Re: [RFC PATCH 0/2] scpi: Add SCPI framework to handle vendors variants

[ + Heiko, who may know about the Rockchip implementation ] Sudeep Holla writes: > On 30/05/16 09:30, Neil Armstrong wrote: >> On 05/27/2016 10:17 AM, Neil Armstrong wrote: > > [..] > >> >> While looking for other ARMv8 based platform, I found that the RK3368 >> platform

Re: [PATCH -v3 7/8] locking: Move smp_cond_load_acquire() and friends into asm-generic/barrier.h

On Wed, Jun 01, 2016 at 03:07:14PM +0100, Will Deacon wrote: > On Wed, Jun 01, 2016 at 02:45:41PM +0200, Peter Zijlstra wrote: > > On Wed, Jun 01, 2016 at 01:13:33PM +0100, Will Deacon wrote: > > > On Wed, Jun 01, 2016 at 02:06:54PM +0200, Peter Zijlstra wrote: > > > > > > Works for me; but that

Re: [PATCH 3.14 00/20] 3.14.71-stable review

On Wed, Jun 01, 2016 at 08:19:51AM -0600, Shuah Khan wrote: > On 05/30/2016 02:49 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.14.71 release. > > There are 20 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 3.14 00/20] 3.14.71-stable review

On Wed, Jun 01, 2016 at 01:13:51AM -0700, kernelci.org bot wrote: > stable-queue boot: 114 boots: 0 failed, 113 passed with 1 offline > (v3.14.70-20-gd418e2694f52) > > Full Boot Summary: > https://kernelci.org/boot/all/job/stable-queue/kernel/v3.14.70-20-gd418e2694f52/ > Full Build Summary: >

Re: [PATCH 04/17] arm: get rid of superfluous __GFP_REPEAT

On Mon, May 30, 2016 at 11:14:46AM +0200, Michal Hocko wrote: > From: Michal Hocko > > __GFP_REPEAT has a rather weak semantic but since it has been introduced > around 2.6.12 it has been ignored for low order allocations. > > PGALLOC_GFP uses __GFP_REPEAT but none of the

[PATCH] rtl8xxxu: fix typo on variable name, compare against correct variable

From: Colin Ian King path_b_ok is being assigned but immediately after path_a_ok is being compared to the value 0x03. This appears to be a typo on the variable name, compare path_b_ok instead. Signed-off-by: Colin Ian King ---

Re: [PATCH 02/11] dma-buf/fence: add fence_array fences v6

Hi Christian, Gustavo, Thanks for these patches. On 1 June 2016 at 20:55, Gustavo Padovan wrote: > 2016-06-01 Christian König : > >> From: Gustavo Padovan >> >> struct fence_collection inherits from struct fence and

[PATCH v3 2/8] [media] Add signed 16-bit pixel format

This will be used for output of raw touch delta data. This format is used by Atmel maXTouch (atmel_mxt_ts) and also Synaptics RMI4. Signed-off-by: Nick Dyer --- Documentation/DocBook/media/v4l/pixfmt-ys16.xml | 79 +

[PATCH v3 7/8] Input: atmel_mxt_ts - add diagnostic data support for mXT1386

The mXT1386 family of chips have a different architecture which splits the diagnostic data into 3 columns. Signed-off-by: Nick Dyer --- drivers/input/touchscreen/atmel_mxt_ts.c | 29 ++--- 1 file changed, 26 insertions(+), 3 deletions(-) diff

[PATCH v3 5/8] Input: atmel_mxt_ts - read touchscreen size

The touchscreen may have a margin where not all the matrix is used. Read the parameters from T9 and T100 and take account of the difference. Note: this does not read the XORIGIN/YORIGIN fields so it assumes that the touchscreen starts at (0,0) Signed-off-by: Nick Dyer ---

Re: [PATCH 0/1] shiftfs: uid/gid shifting filesystem

On Wed, 2016-06-01 at 18:21 +0200, Michał Zegan wrote: > As I sent a reply in a ... wrong way, I do it again. my question was: > Why isn't it done at the vfs layer when you mount the fs in different > userns, instead of using a separate filesystem for it? Well, that is what this patch does:

Fwd: Investment Proposal More Details

Business Proposal view the attached letter for more details'' CONFIDENTIAL INVESTMENT PROPOSAL.doc Description: MS-Word document

[PATCH v3 8/8] Input: atmel_mxt_ts - add support for reference data

There are different datatypes available from a maXTouch chip. Add support to retrieve reference data as well. Signed-off-by: Nick Dyer --- drivers/input/touchscreen/atmel_mxt_ts.c | 58 1 file changed, 51 insertions(+), 7 deletions(-)

Re: [PATCH 1/2] KVM: x86: avoid simultaneous queueing of both IRQ and SMI

2016-06-01 14:35+0200, Paolo Bonzini: > If the processor exits to KVM while delivering an interrupt, > the hypervisor then requeues the interrupt for the next vmentry. > Trying to enter SMM in this same window causes to enter non-root > mode in emulated SMM (i.e. with IF=0) and with a request to >

Re: Regression in IO resource allocation

On Tue, May 31, 2016 at 3:31 PM, Rafael J. Wysocki wrote: > It may not be called at all if _PTC is used on that system, for example. Yes, that's exactly the case on my system. So from my POV: Tested-by: Roland Dreier Thanks!

[RFC][PATCH 1/2] clk: hi6220: Add RTC clock for pl031

From: Zhangfei Gao Adds clk support for the pl031 RTC on hi6220 Cc: Michael Turquette Cc: Stephen Boyd Cc: Rob Herring Cc: Pawel Moll Cc: Wei Xu Cc: Guodong

[RFC][PATCH 2/2] arm64: dts: hi6220: Add pl031 RTC support

From: Zhangfei Gao Add pl031 rtc0 support to hi6220 dtsi Cc: Michael Turquette Cc: Stephen Boyd Cc: Rob Herring Cc: Pawel Moll Cc: Wei Xu Cc: Guodong Xu

Re: [PATCH 1/2] rtc-cmos: Clear expired alarm after resume

On 01/06/2016 17:40, Gabriele Mazzotta wrote: > If the system wakes up because of a wake alarm, the internal state > of the alarm is not updated. As consequence, the state no longer > reflects the actual state of the hardware and setting a new alarm > is not possible until the expired alarm is

[PATCH] net: fix potential infoleak in rds_inc_info_copy

The last field "flags" of object "minfo" is not initialized. Copying this object out may leak kernel stack data. Assign 0 to it to avoid leak. Signed-off-by: Kangjie Lu --- net/rds/recv.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net/rds/recv.c b/net/rds/recv.c

Re: [PATCH -v3 7/8] locking: Move smp_cond_load_acquire() and friends into asm-generic/barrier.h

On 06/01/2016 05:31 AM, Peter Zijlstra wrote: On Tue, May 31, 2016 at 04:01:06PM -0400, Waiman Long wrote: You are doing two READ_ONCE's in the smp_cond_load_acquire loop. Can we change it to do just one READ_ONCE, like --- a/include/asm-generic/barrier.h +++ b/include/asm-generic/barrier.h @@

Re: [PATCH 7/8] pkeys: add details of system call use to Documentation/

On 06/01/2016 09:49 AM, Jonathan Corbet wrote: >> > + sys_pkey_alloc(0, PKEY_DISABLE_WRITE | PKEY_DISABLE_READ); >> > + sys_pkey_mprotect(ptr, size, PROT_READ|PROT_WRITE); >> > + something(ptr); > That should, IMO, be something like: > > key = pkey_alloc(...); > pkey_mprotect(ptr,

Re: [PATCH v3 0/4] Amlogic: Meson: Add reset controller

Philipp Zabel writes: > Hi Kevin, > > Am Montag, den 30.05.2016, 15:27 +0200 schrieb Neil Armstrong: >> Patchset to add and enable the reset controller driver on Meson SoCs >> platforms. >> >> This reset controller has up to 256 reset lines with reset pulse generation

Re: [PATCH 0/1] shiftfs: uid/gid shifting filesystem

As I sent a reply in a ... wrong way, I do it again. my question was: Why isn't it done at the vfs layer when you mount the fs in different userns, instead of using a separate filesystem for it? I believe it could be useful to be able to mount all filesystems in userns with autoshifted uids,

Re: [PATCH] mm: kasan: don't touch metadata in kasan_[un]poison_element()

On 06/01/2016 03:53 PM, Alexander Potapenko wrote: > To avoid draining the mempools, KASAN shouldn't put the mempool elements > into the quarantine upon mempool_free(). Correct, but unfortunately this patch doesn't fix that. > It shouldn't store > allocation/deallocation stacks upon

Re: [PATCH 3.14 00/20] 3.14.71-stable review

Greg Kroah-Hartman writes: > On Wed, Jun 01, 2016 at 01:13:51AM -0700, kernelci.org bot wrote: >> stable-queue boot: 114 boots: 0 failed, 113 passed with 1 offline >> (v3.14.70-20-gd418e2694f52) >> >> Full Boot Summary: >>

[RFC][PATCH 0/2] Add pl031 RTC support for Hi6220/HiKey

This patchset enables the pl031 RTC on the Hi6220 SoC. I wanted to submit it out for an initial RFC, to see if there were any objections or feedback, and to try to figure out how these two patches should go upstream (independently via separate maintainers trees, or acked and through one?).

Re: [PATCH] hwmon: (fam15h_power) Disable preemption when reading registers

Sent from my iPad > On Jun 1, 2016, at 11:27 PM, Huang, Ray wrote: > > > >>> On Jun 1, 2016, at 9:23 PM, Guenter Roeck wrote: >>> >>> On 06/01/2016 03:04 AM, Borislav Petkov wrote: >>> From: Borislav Petkov >>> >>> We need to read a

Re: [PATCH -v3 3/8] locking: Introduce smp_acquire__after_ctrl_dep

On Wed, Jun 01, 2016 at 09:52:14PM +0800, Boqun Feng wrote: > On Tue, May 31, 2016 at 11:41:37AM +0200, Peter Zijlstra wrote: > > @@ -292,7 +282,7 @@ static void sem_wait_array(struct sem_ar > > sem = sma->sem_base + i; > > spin_unlock_wait(>lock); > > } > > -

Re: [PATCH v2 4/8] Input: atmel_mxt_ts - output diagnostic debug via v4l2 device

On 27/05/2016 13:54, Hans Verkuil wrote: > Hi Nick, Thanks for the useful review. Most of it is straightforward and I've updated it in a new version of these patches which I will post now. I think the open question is whether you're happy with the V4L2_PIX_FMT_YS16 or whether I need to rename

[PATCH v3 4/8] Input: atmel_mxt_ts - output diagnostic debug via v4l2 device

Register a video device to output T37 diagnostic data. Signed-off-by: Nick Dyer --- drivers/input/touchscreen/Kconfig| 2 + drivers/input/touchscreen/atmel_mxt_ts.c | 247 +++ 2 files changed, 249 insertions(+) diff --git

[PATCH v3 1/8] Input: atmel_mxt_ts - add support for T37 diagnostic data

Atmel maXTouch devices have a T37 object which can be used to read raw touch deltas from the device. This consists of an array of 16-bit integers, one for each node on the touchscreen matrix. Signed-off-by: Nick Dyer --- drivers/input/touchscreen/atmel_mxt_ts.c | 152

Re: [PATCH 7/8] pkeys: add details of system call use to Documentation/

On 06/01/2016 09:43 AM, Jonathan Corbet wrote: >> > +There are 5 system calls which directly interact with pkeys: >> > + >> > + int pkey_alloc(unsigned long flags, unsigned long init_access_rights) >> > + int pkey_free(int pkey); >> > + int sys_pkey_mprotect(unsigned long start, size_t len, >>

Re: [PATCH 7/8] pkeys: add details of system call use to Documentation/

On Wed, 1 Jun 2016 09:46:07 -0700 Dave Hansen wrote: > On 06/01/2016 09:43 AM, Jonathan Corbet wrote: > >> > +There are 5 system calls which directly interact with pkeys: > >> > + > >> > +int pkey_alloc(unsigned long flags, unsigned long > >> > init_access_rights) > >> >

[PATCH] ppdev: use new parport device model

Modify ppdev driver to use the new parallel port device model. Initially submitted and committed as: e7223f186033 ("ppdev: use new parport device model") But due to some regression it was reverted by: 1701f680407c ("Revert "ppdev: use new parport device model"") Now that the original source of

Re: [PATCH] ethtool: fix a kernel infoleak in ethtool_get_pauseparam

On Wed, 2016-06-01 at 16:39 +0200, Kangjie Lu wrote: > The field autoneg of pauseparam is not initialized in some > implementations of get_pauseparam(), Nonsense.  The current implementation initialises all fields.  (If there was padding in the structure, this change would be needed to guarantee

[PATCH 4/5] x86, intel_idle: use Intel family macros for intel_idle

From: Dave Hansen Use the new INTEL_FAM6_MODEL_* macros for intel_idle.c. Also fix up some of the macros to be consistent with how some of the intel_idle code refers to the model. There's on oddity here: model 0x1F is uniquely referred to here and nowhere else

[PATCH 3/5] x86, rapl: use Intel family macros for rapl

From: Dave Hansen Use the new INTEL_FAM6_MODEL_* macros for rapl.c. Note that this is missing at least one Westmere model and Skylake Server. The resulting binary structure 'rapl_cpu_match' is the same before and after this patch. Signed-off-by: Dave Hansen

[PATCH 5/5] x86, msr: use Intel family macros for msr events code

From: Dave Hansen Use the new INTEL_FAM6_MODEL_* macros for arch/x86/events/msr.c. This code appears to be missing handling for "WESTMERE2" and "SKYLAKE_X". Signed-off-by: Dave Hansen Cc: Andy Lutomirski Cc: Peter

[PATCH 2/5] x86, perf: use Intel family macros for core perf events

From: Dave Hansen Use the new model number macros instead of spelling things out in the comments. Note that this is missing a Nehalem model that is mentioned in intel_idle. Is that a a problem? The resulting binary (arch/x86/events/intel/core.o) is exactly the

[PATCH 1/5] x86, intel: Introduce macros for Intel family numbers

From: Dave Hansen We have at least four long lists of open-coded family-6 model numbers. Half of them have these model numbers in hex and the other half in decimal. This makes grepping for them tons of fun, if you were to try. So, let's consolidate them. Put all

Re: [PATCH v4] extcon: gpio: Add the support for Device tree bindings

On Wed, Jun 1, 2016 at 9:49 AM, Laxman Dewangan wrote: > > On Tuesday 31 May 2016 09:18 PM, Rob Herring wrote: >> >> On Tue, May 31, 2016 at 8:44 AM, Laxman Dewangan >> wrote: >>> >>> Hi Rob, >>> >>> On Tuesday 31 May 2016 07:05 PM, Rob Herring wrote:

Re: [PATCH] staging: iio: ad5933: fix handling of settling time cycles

On 06/01/2016 05:55 PM, Luis de Bethencourt wrote: > Correctly handle the settling time cycles value. The else branch was an > impossible condition (> 1022 in the else branch of > 511) and the handling > of the values was dividing by 2 and 4, with a left shift, instead of > multiplying. > > Based

Re: [PATCH] mm, kasan: introduce a special shadow value for allocator metadata

On Wed, Jun 1, 2016 at 5:23 PM, Andrey Ryabinin wrote: > On 05/31/2016 08:49 PM, Alexander Potapenko wrote: >> On Tue, May 31, 2016 at 1:52 PM, Andrey Ryabinin >> wrote: >>> >>> >>> On 05/31/2016 01:44 PM, Alexander Potapenko wrote: Add a

[PATCH v3 3/8] [media] v4l2-core: Add VFL_TYPE_TOUCH_SENSOR

Some touch controllers send out raw touch data in a similar way to a greyscale frame grabber. Add a new device type for these devices. Use a new device prefix v4l-touch for these devices, to stop generic capture software from treating them as webcams. Signed-off-by: Nick Dyer

[PATCH v3 6/8] Input: atmel_mxt_ts - handle diagnostic data orientation

Invert the diagnostic data to match the orientation of the input device. Signed-off-by: Nick Dyer --- drivers/input/touchscreen/atmel_mxt_ts.c | 26 +- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git

Re: [PATCH 7/8] pkeys: add details of system call use to Documentation/

On Tue, 31 May 2016 08:28:24 -0700 Dave Hansen wrote: > +There are 5 system calls which directly interact with pkeys: > + > + int pkey_alloc(unsigned long flags, unsigned long init_access_rights) > + int pkey_free(int pkey); > + int sys_pkey_mprotect(unsigned long

[PATCH v3 0/8] Input: atmel_mxt_ts - output raw touch diagnostic data via V4L

This is a series of patches to add diagnostic data support to the Atmel maXTouch driver. It's a rewrite of the previous implementation which output via debugfs: it now uses a V4L2 device in a similar way to the sur40 driver. There are significant performance advantages to putting this code into

[PATCH 32/34] clk: u300: Migrate to clk_hw based registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Linus Walleij Signed-off-by: Stephen Boyd

[PATCH 34/34] clk: wm831x: Migrate to clk_hw based registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Mark Brown Signed-off-by: Stephen Boyd

[PATCH 04/34] clk: bcm2835: Migrate to clk_hw based registration and OF APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Eric Anholt Cc: Martin Sperl

[PATCH 28/34] clk: si5351: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Sebastian Hesselbarth Cc: Guenter Roeck

[PATCH 29/34] clk: si570: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Guenter Roeck Cc: Sören Brinkmann

[PATCH 25/34] clk: s2mps11: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Andi Shyti Cc: Krzysztof Kozlowski

[PATCH 27/34] clk: si514: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Sebastian Hesselbarth Cc: Guenter Roeck

[PATCH 13/34] clk: clps711x: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Alexander Shiyan Signed-off-by: Stephen Boyd

[PATCH 12/34] clk: cdce925: Migrate to clk_hw based OF and provider APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Mike Looijmans Signed-off-by: Stephen Boyd

[PATCH 22/34] clk: palmas: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Peter Ujfalusi Cc: Nishanth Menon

[PATCH 21/34] clk: nspire: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Daniel Tang Signed-off-by: Stephen Boyd

[PATCH 10/34] clk: axm5516: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Make thing simple by using the existing clk_hw array and implementing a custom

[PATCH 23/34] clk: pwm: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Janusz Uzycki Cc: Philipp Zabel

[PATCH 15/34] clk: efm32gg: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Uwe Kleine-König Signed-off-by: Stephen

[PATCH 14/34] clk: cs2000: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Kuninori Morimoto Signed-off-by:

Re: [PATCH v4 0/8] Replay Protected Memory Block (RPMB) subsystem

On Wed, Jun 1, 2016 at 2:41 PM, Tomas Winkler wrote: > Few storage technology such is EMMC, UFS, and NVMe support RPMB > hardware partition with common protocol and frame layout. > The RPMB partition cannot be accessed via standard block layer, but > by a set of specific

[PATCH 07/34] clk: berlin: Migrate to clk_hw based registration and OF APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Jisheng Zhang Cc: Alexandre Belloni

[PATCH 08/34] clk: asm9260: Migrate to clk_hw based registration and OF APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Oleksij Rempel Signed-off-by: Stephen Boyd

[PATCH 20/34] clk: nomadik: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Linus Walleij Signed-off-by: Stephen Boyd

[PATCH 18/34] clk: mb86s7x: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Jassi Brar Signed-off-by: Stephen Boyd

[PATCH 19/34] clk: moxart: Migrate to clk_hw based OF and registration APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Jonas Jensen Signed-off-by: Stephen Boyd

[PATCH 02/34] clk: at91: Migrate to clk_hw based registration and OF APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers in this driver, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Alexandre Belloni Cc: Boris Brezillon

[PATCH 03/34] clk: highbank: Migrate to clk_hw based registration and OF APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers in this driver, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Rob Herring Signed-off-by: Stephen Boyd --- See

[PATCH 05/34] clk: bcm: iproc: Migrate to clk_hw based registration and OF APIs

Now that we have clk_hw based provider APIs to register clks, we can get rid of struct clk pointers while registering clks in these drivers, allowing us to move closer to a clear split of consumer and provider clk APIs. Cc: Ray Jui Cc: Jon Mason Cc:

[PATCH 00/34] Convert clk providers to clk_hw based APIs (part 1)

This is an initial set of patches to convert clk provider drivers over to the clk_hw based approach of registering clks. The foundational part of that has merged into v4.7-rc1 (see commit 58657d189a2f and it's children for details), so this series updates some drivers for the new registration

Re: [PATCH] ARM: Keystone: Introduce Kconfig option to compile in typical Keystone features

On 6/1/2016 3:49 PM, Nishanth Menon wrote: On 06/01/2016 05:31 PM, Arnd Bergmann wrote: [...] Santosh, Bill, Lokesh, Grygorii: could you help feedback on the above comments from Arnd? Already responded to Arnds email.

Re: [PATCH] ARM: Keystone: Introduce Kconfig option to compile in typical Keystone features

: Lokesh Vutla <lokeshvu...@ti.com> Signed-off-by: Nishanth Menon <n...@ti.com> --- Based on: next-20160601 Tested for basic initramfs boot for K2HK/K2G platforms with the http://pastebin.ubuntu.com/16904991/ fragment + multi_v7_defconfig Side note on LPAE: For our current

[PATCH 2/2] f2fs: handle writepage correctly

Previously, f2fs_write_data_pages() calls __f2fs_writepage() which calls f2fs_write_data_page(). If f2fs_write_data_page() returns AOP_WRITEPAGE_ACTIVATE, __f2fs_writepage() calls mapping_set_error(). But, this should not happen at every time, since sometimes f2fs_write_data_page() tries to skip

[PATCH 1/2] f2fs: return error of f2fs_lookup

Now we can report an error to f2fs_lookup given by f2fs_find_entry. Suggested-by: He YunLei Signed-off-by: Jaegeuk Kim --- fs/f2fs/dir.c | 2 +- fs/f2fs/namei.c | 5 - 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/dir.c

Re: [PATCH] befs/btree: remove unneeded initializations

On 01/06/16 23:42, Andrew Morton wrote: > On Mon, 30 May 2016 01:39:59 +0100 Luis de Bethencourt > wrote: > >> off in befs_bt_read_node() will be written by befs_read_datastream(), with >> the value that node->od_node needs. >> >> node_off in befs_btree_read() isn't read

Re: [PATCH 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Frank, Am Dienstag, 31. Mai 2016, 14:40:11 schrieb Frank Wang: > The newer SoCs (rk3366, rk3399) take a different usb-phy IP block > than rk3288 and before, and most of phy-related registers are also > different from the past, so a new phy driver is required necessarily. > > Signed-off-by:

Re: script relative shebang

Sorry for insisting, but I would like to explore potential solutions for fixing the root problem (missing relative shebang), I know there are ways to workaround that, but I would like to make sure the proper fix is not possible. I understood that it is too late to introduce additional keywords

Re: [PATCH 5/8] x86, pkeys: allocation/free syscalls

Hi Dave, On 1 June 2016 at 14:32, Dave Hansen wrote: > On 06/01/2016 11:37 AM, Jonathan Corbet wrote: >>> +static inline >>> +int mm_pkey_free(struct mm_struct *mm, int pkey) >>> +{ >>> +/* >>> + * pkey 0 is special, always allocated and can never >>> + * be freed. >>>

[PATCH 07/20] x86, intel: use Intel model macros intead of open-coding

From: Dave Hansen Use the new macros to remove another large set of open-coded values. Signed-off-by: Dave Hansen Cc: "Rafael J. Wysocki" Cc: linux...@vger.kernel.org --- b/arch/x86/include/asm/intel-family.h |

[PATCH 20/20] x86, powercap, rapl: add Skylake Server model number

From: Dave Hansen SKX uses similar RAPL interface as Broadwell server according to Jacob Pan. Signed-off-by: Dave Hansen Cc: Jacob Pan Cc: "Rafael J. Wysocki" Cc:

[PATCH 19/20] x86, rapl: add Skylake server model detection

From: Jacob Pan SKX uses similar RAPL interface as Broadwell server. Signed-off-by: Jacob Pan Signed-off-by: Dave Hansen Cc: Thomas Gleixner --- b/arch/x86/events/intel/rapl.c |

[PATCH 14/20] x86, acpi, lss: use Intel family name macros for lpss driver

From: Dave Hansen Another straightforward replacement of magic numbers. Signed-off-by: Dave Hansen Cc: "Rafael J. Wysocki" Cc: Len Brown Cc: linux-a...@vger.kernel.org ---

[PATCH 15/20] x86, intel_telemetry: use Intel family name macros for telemetry driver

From: Dave Hansen Another straightforward replacement of magic numbers. Signed-off-by: Dave Hansen Cc: Souvik Kumar Chakravarty Cc: Darren Hart Cc:

[PATCH 13/20] x86, cpufreq: use Intel family name macros for intel_pstate cpufreq driver

From: Dave Hansen Another straightforward replacement of magic numbers. Signed-off-by: Dave Hansen Cc: Srinivas Pandruvada Cc: Len Brown Cc: "Rafael J. Wysocki"

  1   2   3   4   5   6   7   8   9   10   >