[PATCH 11/17] lightnvm: remove nested lock conflict with mm

If a media manager tries to initialize it targets upon media manager initialization, the media manager will need to know which target types are available in LightNVM. The lists of which managers and target types are available shares the same lock. Therefore, on initialization, the nvm_lock is take

[PATCH 07/17] lightnvm: fix checkpatch terse errors

A couple of small checkpatch fixups to stop it from complaining. ./drivers/lightnvm/core.c:360: WARNING: line over 80 characters ./drivers/lightnvm/core.c:360: ERROR: trailing statements should be on next line ./drivers/lightnvm/core.c:503: WARNING: Block comments use a trailing */ on a separate l

[PATCH 15/17] lightnvm: fix lun offset calculation for mark blk

The gen_mark_blk_bad function marks the wrong block when a block is on a different channel. Fix the index calculation, so that it updates the correct block. Reported-by: Javier Gonzalez Signed-off-by: Matias Bjørling --- drivers/lightnvm/gennvm.c | 2 +- 1 file changed, 1 insertion(+), 1 deleti

[PATCH 13/17] lightnvm: remove _unlocked variant of [get/put]_blk

The [get/put]_blk API enables targets to get ownership of blocks at runtime. This information is currently not recorded on disk, and the information is therefore lost on power failure. To restore the metadata, the [get/put]_blk must persist its metadata. In that case, we need to control the outer l

[PATCH 08/17] lightnvm: remove open/close statistics for gennvm

The responsibility of the media manager is not to keep track of open/closed blocks. This is better maintained within a target, that already manages this information on writes. Remove the statistics and merge the states NVM_BLK_ST_OPEN and NVM_BLK_ST_CLOSED. Signed-off-by: Matias Bjørling --- dr

[PATCH 01/17] lightnvm: break the loop when rqd is not null

From: Wenwei Tao Break the loop when rqd is not null to reduce an unnecessary schedule. Signed-off-by: Wenwei Tao Signed-off-by: Matias Bjørling --- drivers/lightnvm/rrpc.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/lightnvm/rrpc.c b/drivers/lightnvm/rr

[PATCH 16/17] lightnvm: make ppa_list const in nvm_set_rqd_list

The passed by reference ppa list in nvm_set_rqd_list() is updated when multiple planes are available. In that case, each PPA plane is incremented when the device side PPA list is created. This prevents the caller to rely on the PPA list to be unmodified after a call. Signed-off-by: Matias Bjørling

Re: [PATCH net-next V2] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

Hi, [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Netanel-Belgazal/net-ena-Add-a-driver-for-Amazon-Elastic-Network-Adapters-ENA/20160707-142005 config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430

[PATCH 17/17] lightnvm: make __nvm_submit_ppa static

The __nvm_submit_ppa() function is not used outside lightnvm core. Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/lightnvm/core.c b/drivers/lightnvm/core.c index 00b64f7..9ebd2cf 100644 --- a/drivers/lightnvm

[PATCH 3/3] MIPS: Move CPU Hotplug config option into submenu

The KConfig option HOTPLUG_CPU should appear in the "Kernel Type" submenu. Relocate it to where SMP support is configured. Signed-off-by: Matt Redfearn --- arch/mips/Kconfig | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/arch/mips/Kconfig b/arch/mips/

[PATCH 2/3] MIPS: smp-cps: Add support for CPU hotplug of MIPSr6 processors

Introduce support for hotplug of Virtual Processors in MIPSr6 systems. The method is simpler than the VPE parallel from the now-deprecated MT ASE, it can now simply write the VP_STOP register with the mask of VPs to halt, and use the VP_RUNNING register to determine when the VP has halted. Signed-

[PATCH 1/3] MIPS: smp-cps: Allow booting of CPU other than VP0 within a core

The boot_core function was hardcoded to always start VP0 when starting a core via the CPC. When hotplugging a CPU this may not be the desired behaviour. Make boot_core receive the VP ID to start running on the core, such that alternate VPs can be started via CPU hotplug. Also ensure that all other

[PATCH 0/3] Support for MIPSr6 CPU hotplug.

This series adds support for hotplug of MIPSr6 Virtual Processors such as found in the I6400. Patch 1 allows VPs other than VP0 within a MIPSr6 core to start when a core is booted. Patch 2 adds support for removing CPUs, allowing CPU hotpug to be used with MIPSr6 devices. Patch 3 is a tidy up to

[PATCH] xen-fbfront: prefer xenbus_write() over xenbus_printf() where possible

... as being the simpler variant. Signed-off-by: Jan Beulich --- drivers/video/fbdev/xen-fbfront.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) --- 4.7-rc6-prefer-xenbus_write.orig/drivers/video/fbdev/xen-fbfront.c +++ 4.7-rc6-prefer-xenbus_write/drivers/video/fbdev/xen-fbfron

[PATCH v4] powerpc: Export thread_struct.used_vr/used_vsr to user space

From: Simon Guo These 2 fields track whether user process has used Altivec/VSX registers or not. They are used by kernel to setup signal frame on user stack correctly regarding vector part. CRIU(Checkpoint and Restore In User space) builds signal frame for restored process. It will need this exp

vgacon.c:undefined reference to `screen_info'

Hi, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 076501ff6ba265a473689c112eda9f1f34f620b5 commit: f69405ce6c0fc9f4a039011007371b31f80b470d openrisc: include: asm: Kbuild: add default "vga.h" date:

Re: [PATCH] clocksource: cadence_ttc: fix a return value in case of error

On Wed, Jul 06, 2016 at 07:35:23AM +0200, Christophe JAILLET wrote: > IS_ERR and PTR_ERR should use the same variable, clk_ce in this case. > > Fixes: 4de1eb07c47f (Convert init function to return error) > > Signed-off-by: Christophe JAILLET Applied, thanks. -- Daniel

[PATCH] ACPI: Update the maximum depth of C-state from 6 to 9

From: Chuansheng Liu Currently, CPUIDLE_STATE_MAX has been defined as 10 in the cpuidle head file, and max_cstate = CPUIDLE_STATE_MAX – 1, so 9 is the right maximum depth of C-state. This change is reflected in one place of the kernel-param file, but not in the other place where I suggest changi

Re: [PATCH 1/9] mm: Hardened usercopy

On Wed, 6 Jul 2016, Kees Cook wrote: > + > +#if defined(CONFIG_FRAME_POINTER) && defined(CONFIG_X86) > + const void *frame = NULL; > + const void *oldframe; > +#endif That's ugly > + > + /* Object is not on the stack at all. */ > + if (obj + len <= stack || stackend <= obj) > +

Re: [PATCH v3 8/8] mm/zsmalloc: add per-class compact trace event

Hello Ganesh, On Wed, Jul 06, 2016 at 02:23:53PM +0800, Ganesh Mahendran wrote: > add per-class compact trace event to get scanned objects and freed pages > number. > trace log is like below: > > kswapd0-629 [001] 293.161053: zs_compact_start: pool zram0 > kswapd0-6

[PATCH] [v1.1] driver: input :touchscreen : Raydium I2C touch driver

Add and fix below function. 1.Touch report points chechsum 2.update firmware naming decision by firmware version 3.fix reset pins control issue Signed-off-by: jeffrey.lin --- drivers/input/touchscreen/raydium_i2c_ts.c | 261 +++-- 1 file changed, 213 insertions(+), 48 del

[PATCH] xen/manage: correct return value check on xenbus_scanf()

Only a positive return value indicates success. Signed-off-by: Jan Beulich --- drivers/xen/manage.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- 4.7-rc6-xenbus_scanf.orig/drivers/xen/manage.c +++ 4.7-rc6-xenbus_scanf/drivers/xen/manage.c @@ -275,7 +275,7 @@ static void sysrq_han

[PATCH] xenbus: check return value of xenbus_scanf()

Set backend state to unknown when unsuccessful. Signed-off-by: Jan Beulich --- drivers/xen/xenbus/xenbus_probe_frontend.c |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) --- 4.7-rc6-xenbus_scanf.orig/drivers/xen/xenbus/xenbus_probe_frontend.c +++ 4.7-rc6-xenbus_scanf/drivers/xen/xen

Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault vanilla 4.4.6

On Thu, Jul 07, 2016 at 11:20:36AM +1200, Campbell Steven wrote: > > commit 8974189222159154c55f24ddad33e3613960521a > > Author: Peter Zijlstra > > Date: Thu Jun 16 10:50:40 2016 +0200 > Since these early reports from Stefan and I it looks like it's been > hit but alot more folks now so I'd li

[PATCH] xen-blkfront: avoid NULL de-reference in CDROM ioctl handling

The ioctl can be called prior to full device setup having completed. Signed-off-by: Jan Beulich --- drivers/block/xen-blkfront.c |6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) --- 4.7-rc6-xen.orig/drivers/block/xen-blkfront.c +++ 4.7-rc6-xen/drivers/block/xen-blkfront.c @@ -496,

Re: [PATCH 0/3] x86: Remove duplicate turbo ratio MSRs

On Thu, 7 Jul 2016, Rafael J. Wysocki wrote: > On Thu, Jul 7, 2016 at 1:07 AM, Srinivas Pandruvada > wrote: > > MSR_NHM_TURBO_RATIO_LIMIT and MSR_IVT_TURBO_RATIO_LIMIT are > > duplicate MSRs with MSR_TURBO_RATIO_LIMIT and MSR_TURBO_RATIO_LIMIT1 > > respectively. So remove them by first removing th

[PATCH] xen-blkback: constify instance of "struct attribute_group"

The functions such get passed to have been taking pointers to const since at least 2.6.16. Signed-off-by: Jan Beulich --- drivers/block/xen-blkback/xenbus.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- 4.7-rc6-xen.orig/drivers/block/xen-blkback/xenbus.c +++ 4.7-rc6-xen/drivers/b

[PATCH] xenbus: prefer list_for_each()

... over list_for_each_safe() when list modification if accompanied by breaking out of the loop. Signed-off-by: Jan Beulich --- drivers/xen/xenbus/xenbus_dev_frontend.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- 4.7-rc6-xen.orig/drivers/xen/xenbus/xenbus_dev_frontend.c +++

[PATCH] xen-blkback: really don't leak mode property

Commit 9d092603cc ("xen-blkback: do not leak mode property") left one path unfixed; correct this. Signed-off-by: Jan Beulich --- drivers/block/xen-blkback/xenbus.c |5 - 1 file changed, 4 insertions(+), 1 deletion(-) --- 4.7-rc6-xen.orig/drivers/block/xen-blkback/xenbus.c +++ 4.7-rc6-xe

[PATCH] xen/privcmd: sprinkle around cond_resched() calls in mmap ioctl handling

Many of these operations can take arbitrarily long, which can become a problem irrespective of them being exposed to privileged users only. Signed-off-by: Jan Beulich --- drivers/xen/privcmd.c | 18 ++ 1 file changed, 14 insertions(+), 4 deletions(-) --- 4.7-rc6-xen.orig/drive

[PATCH v3 1/2] drm/mediatek: Add gamma correction

Apply gamma function to correct brightness values. It applies arbitrary mapping curve to compensate the incorrect transfer function of the panel. Signed-off-by: Bibby Hsieh --- drivers/gpu/drm/mediatek/mtk_drm_crtc.c |8 +++ drivers/gpu/drm/mediatek/mtk_drm_crtc.h |1 + drivers/g

[PATCH] xen/mcelog: eliminate redundant setting of interface version

This already gets done in HYPERVISOR_mca(). Signed-off-by: Jan Beulich --- drivers/xen/mcelog.c |2 -- 1 file changed, 2 deletions(-) --- 4.7-rc6-xen.orig/drivers/xen/mcelog.c +++ 4.7-rc6-xen/drivers/xen/mcelog.c @@ -288,7 +288,6 @@ static int mc_queue_handle(uint32_t flag int ret =

[PATCH v3 0/2] drm/mediatek: MT8173 gamma & dither support

This is MT8173 gamma & dither support PATCH v3, based on 4.7-rc1. Changes since v2: -Modify defines to match the register field names in the MT8173 datasheet -Made dithering function support hardware mirroring well on two monitor. Bibby Hsieh (2): drm/mediatek: Add gamma correction drm/med

[PATCH v3 2/2] drm/mediatek: set mt8173 dithering function

Some panels only accept bpc (bit per color) 6-bit. But, the default bpc in mt8173 display data path is 8-bit. If we didn't enable dithering function to convert bpc, display cannot show the smooth grayscale image. In mt8173, the dithering function in OD (OverDrive) and GAMMA module, we have to conf

[PATCH] xen/mcelog: also build for x86-32

There's no reason why this would need to be limited to x86-64. Signed-off-by: Jan Beulich --- drivers/xen/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- 4.7-rc6-xen.orig/drivers/xen/Kconfig +++ 4.7-rc6-xen/drivers/xen/Kconfig @@ -264,7 +264,7 @@ config XEN_ACPI_PROCESSOR

[PATCH] ovl:support fsinotify on overlayfs.

From: zhangaihua fix the inode to suppoert fsinotify, the inode should point to overlay rather than upper. before patch: [root@localhost bin]# ./inotify01 inotify011 TPASS : get event: wd=1 mask=4 cookie=0 len=0 inotify012 TFAIL : inotify01.c:185: didn't get event: mask=20 inotify0

Re: [PATCH 0/9] mm: Hardened usercopy

On 07/07/2016 12:25 AM, Kees Cook wrote: > Hi, > > This is a start of the mainline port of PAX_USERCOPY[1]. After I started > writing tests (now in lkdtm in -next) for Casey's earlier port[2], I > kept tweaking things further and further until I ended up with a whole > new patch series. To that en

[PATCH 2/2] xenbus: simplify xenbus_dev_request_and_reply()

No need to retain a local copy of the full request message, only the type is really needed. Signed-off-by: Jan Beulich --- drivers/xen/xenbus/xenbus_xs.c |7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) --- 4.7-rc6-xen.orig/drivers/xen/xenbus/xenbus_xs.c +++ 4.7-rc6-xen/drivers/x

[PATCH 1/2] xenbus: don't bail early from xenbus_dev_request_and_reply()

We must not skip the transaction_end() call for a failed XS_TRANSACTION_START. The removed code fragment got introduced by commit 027bd7e899 ("xen/xenbus: Avoid synchronous wait on XenBus stalling shutdown/restart") without its description really indicating why it was added (and hence I can't ident

Re: [PATCH -next] ARM: dts: sun8i: Add NFC node to Allwinner A23/A33 SoC

On Thu, Jul 07, 2016 at 08:04:41AM +0800, Icenowy Zheng wrote: > with a http://linux-sunxi.org/Aoson_M751s tablet, (SKhynix > H27UCG8T2ETR-BC NAND chip). > > I used the patchset at > http://lists.infradead.org/pipermail/linux-mtd/2016-June/067848.html > to ensure the NAND chip to work properly (ot

[PATCH 0/2] xenbus: xenbus_dev_request_and_reply() adjustments

1: don't bail early from xenbus_dev_request_and_reply() 2: simplify xenbus_dev_request_and_reply() Signed-off-by: Jan Beulich

Re: [PATCH v3 1/2] KVM: nVMX: Fix incorrect preemption timer vmexit in nested guest

On 07/07/16 15:07, Wanpeng Li wrote: > 2016-07-07 15:02 GMT+08:00 Haozhong Zhang : > > On 07/07/16 14:56, Wanpeng Li wrote: > >> 2016-07-07 14:48 GMT+08:00 Haozhong Zhang : > >> > On 07/07/16 11:46, Wanpeng Li wrote: > >> >> From: Wanpeng Li > >> >> > >> >> BUG: unable to handle kernel NULL pointe

[PATCH] spi: s3c64xx: do not disable the clock while configuring the spi

When the clock is coming from the cmu it is not required to be disabled and then re-enabled in order to change the rate. Besides, some exynos chipsets (e.g. exynos5433) do not deliver any to the SFR if one from the pclk ("spi" in this case) or sclk ("busclk") is disabled. Remove the clock disabli

[PATCH] xenbus: don't BUG() on user mode induced condition

Inability to locate a user mode specified transaction ID should not lead to a kernel crash. For other than XS_TRANSACTION_START also don't issue anything to xenbus if the specified ID doesn't match that of any active transaction. Signed-off-by: Jan Beulich --- drivers/xen/xenbus/xenbus_dev_front

[PATCH] kexec: Fix kdump failure with notsc

If we specify the 'notsc' boot parameter for the dump-capture kernel, and then trigger a crash(panic) by using "ALT-SysRq-c" or "echo c > /proc/sysrq-trigger", the dump-capture kernel will hang in calibrate_delay_converge(): /* wait for "start of" clock tick */ ticks = jiffies; while (

Re: [PATCH v4 4/5] soc: Add SoC driver for Freescale Vybrid platform

On Thursday, July 7, 2016 12:09:29 PM CEST Sanchayan Maity wrote: > root@colibri-vf:/sys/bus/soc/devices/soc0# cat family > Freescale Vybrid VF610 > root@colibri-vf:/sys/bus/soc/devices/soc0# cat machine > Freescale Vybrid > I only have one very high-level comment: I think that "family" is genera

[GIT PULL v2] STi SoC changes for v4.8

The following changes since commit 4c2e07c6a29e0129e975727b9f57eede813eea85: Linux 4.7-rc5 (2016-06-26 17:52:03 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/pchotard/sti.git tags/sti-soc-for-v4.8 for you to fetch changes up to 55aa35180c57d

Re: [GIT PULL] STi SoC changes for v4.8

Hi Olof On 07/07/2016 07:30 AM, Olof Johansson wrote: On Fri, Jul 01, 2016 at 04:47:46PM +0200, Patrice Chotard wrote: Hi Olof, Arnd and Kevin, Please consider this first round of STi SoC updates for v4.8: The following changes since commit 4c2e07c6a29e0129e975727b9f57eede813eea85: Linux

[PATCH v2 1/4] ACPI: Add documentation describing ACPICA release automation

This patch adds documentation on ACPICA release automation into the kernel Documentation/acpi folder. Signed-off-by: Lv Zheng --- Documentation/acpi/linuxized-acpica.txt | 253 +++ 1 file changed, 253 insertions(+) create mode 100644 Documentation/acpi/linuxized-acp

[PATCH v2 2/4] ACPI / debugger: Add AML debugger documentation

This patch adds AML debugger documentation. Signed-off-by: Lv Zheng --- Documentation/acpi/aml-debugger.txt | 56 +++ 1 file changed, 56 insertions(+) create mode 100644 Documentation/acpi/aml-debugger.txt diff --git a/Documentation/acpi/aml-debugger.txt b/Do

[PATCH v2 3/4] ACPI / button: Add SW_ACPI_LID for new usage model

There are many AML tables reporting wrong initial lid state, and some of them never reports lid state. As a proxy layer acting between, ACPI button driver is not able to handle all such cases, but need to re-define the usage model of the ACPI lid. That is: 1. It's initial state is not reliable; 2.

[PATCH v2 4/4] ACPI / button: Add document for ACPI control method lid device restrictions

There are many AML tables reporting wrong initial lid state, and some of them never reports lid state. As a proxy layer acting between, ACPI button driver is not able to handle all such cases, but need to re-define the usage model of the ACPI lid. That is: 1. It's initial state is not reliable; 2.

[PATCH net-next 3/3] r8152: remove cancel_delayed_work_sync in rtl8152_set_speed

There is no conflict between the work_queue function and rtl8152_set_speed(), so we don't have to cancel the delayed work in rtl8152_set_speed(). Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r81

[PATCH v2 0/4] ACPI: ACPI documentation

This patch adds new ACPI documents related to: 1. ACPICA release process 2. AML debugger 3. ACPI control method lid device This patch also contains an update of the ACPI LID input event in order to support the new usage model defined by the documentation change. History: 1. Remove the upstreamed t

[PATCH net-next 1/3] r8152: remove rtl_phy_reset function

In rtl_hw_phy_work_func_t(), the flag of PHY_RESET is set in rtl_ops.hw_phy_cfg() and cleared in rtl8152_set_speed(). Therefore, the rtl_phy_reset() is never run and is unnecessary. Signed-off-by: Hayes Wang --- drivers/net/usb/r8152.c | 24 1 file changed, 24 deletions(

[PATCH net-next 0/3] r8152: remove the redundant code

Remove the unnacessary code. Hayes Wang (3): r8152: remove rtl_phy_reset function r8152: remove a netif_carrier_off in rtl8152_open function r8152: remove cancel_delayed_work_sync in rtl8152_set_speed drivers/net/usb/r8152.c | 27 --- 1 file changed, 27 deletions(-)

[PATCH net-next 2/3] r8152: remove a netif_carrier_off in rtl8152_open function

After commit 90186af404ad ("r8152: fix lockup when runtime PM is enabled"), the autoresume wouldn't start the device before rtl8152_open() is finished. Therefore, we don't have to reset the linking status before and after autoresume. That is, one of netif_carrier_off() in rtl8152_open() could be re

Re: [PATCH v3 1/2] KVM: nVMX: Fix incorrect preemption timer vmexit in nested guest

2016-07-07 15:02 GMT+08:00 Haozhong Zhang : > On 07/07/16 14:56, Wanpeng Li wrote: >> 2016-07-07 14:48 GMT+08:00 Haozhong Zhang : >> > On 07/07/16 11:46, Wanpeng Li wrote: >> >> From: Wanpeng Li >> >> >> >> BUG: unable to handle kernel NULL pointer dereference at (null) >> >> IP: [<

Re: [PATCH v3 1/2] KVM: nVMX: Fix incorrect preemption timer vmexit in nested guest

On 07/07/16 14:56, Wanpeng Li wrote: > 2016-07-07 14:48 GMT+08:00 Haozhong Zhang : > > On 07/07/16 11:46, Wanpeng Li wrote: > >> From: Wanpeng Li > >> > >> BUG: unable to handle kernel NULL pointer dereference at (null) > >> IP: [< (null)>] (null) > >> PGD 0 > >> Oops:

<    5   6   7   8   9   10