Re: [PATCH v8 1/5] mfd: hi655x: Add document for mfd hi665x PMIC

Lee, Thanks for your review. On 2016/2/15 16:32, Lee Jones wrote: > On Sun, 14 Feb 2016, Chen Feng wrote: > >> DT bindings for hisilicon hi655x MFD PMIC chip. >> >> Signed-off-by: Chen Feng >> Signed-off-by: Fei Wang >> Signed-off-by: Xinwei Kong

Re: [PATCH] drivers/hwtracing: make coresight-* explicitly non-modular

On 14 February 2016 at 10:19, Paul Gortmaker wrote: > None of the Kconfig currently controlling compilation of any of > the files here are tristate, meaning that none of it currently > is being built as a module by anyone. > > We need not be concerned about .remove

Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'

On Tuesday, February 16, 2016 06:43:35 AM Viresh Kumar wrote: > On 15-02-16, 19:41, Rafael J. Wysocki wrote: > > On Mon, Feb 15, 2016 at 6:05 PM, Guenter Roeck wrote: > > > [1.34] [] (__cpufreq_driver_target) from [] > > > (dbs_check_cpu+0x1ac/0x1e8) > > > [

Re: [PATCH v2 1/4] locking/mutex: Add waiter parameter to mutex_optimistic_spin()

On 02/12/2016 03:40 PM, Peter Zijlstra wrote: On Fri, Feb 12, 2016 at 12:32:12PM -0500, Waiman Long wrote: @@ -358,8 +373,8 @@ static bool mutex_optimistic_spin(struct mutex *lock, } mutex_set_owner(lock); -

Re: [PATCH 3/3] spi: rockchip: add debug interface support

Hi Mark, On 2016/2/16 1:26, Mark Brown wrote: On Mon, Feb 15, 2016 at 04:28:22PM +0800, Shawn Lin wrote: +#ifdef CONFIG_DEBUG_FS +#include +#endif Just include the header. Only add ifdefs if they do something. +static int rockchip_spi_debugfs_init(struct rockchip_spi *rs) +{ +

Re: [PATCH] usb: dwc2: host: fix the data toggle error in full speed descriptor dma

On 1/25/2016 10:20 PM, Jianqiang Tang wrote: > From: "Tang, Jianqiang" > > There will be data toggle error happen for full speed buld-out transfer. > The data toggle bit is saved in qh for non-control transfers, it is wrong > to check the qtd for that case. > > Also

Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'

On 16-02-16, 02:27, Rafael J. Wysocki wrote: > Yes, that's what we should be doing, but it seemed to me that we didn't. > > Or maybe the trace just contained the last one, because that's when the > crash happened. Ofcourse, it wouldn't mention the function calls that have already finished :) --

Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'

ren wrote: https://kernelci.org/boot/all/job/next/kernel/next-20160215/ The SMP ones seem to fail with some regulator issues? There is another problem, introduced with 6a0712f6f199e ("PM / OPP: Add dev_pm_opp_set_rate()"). The kernelci boot log for next-20160212:omap3-overo-tobi and ot

Re: [PATCH 1/2] firmware: arm_scpi: add support for 64-bit sensor values

On 02/09/2016 06:32 AM, Sudeep Holla wrote: SCPI specification version 1.1 extended the sensor from 32-bit to 64-bit values in order to accommodate new sensor class with 64-bit requirements Since the SCPI driver sets the higher 32-bit for older protocol version to zeros, there's no need to

Re: [PATCH 2/2] hwmon: (scpi) add energy meter support

On 02/09/2016 06:32 AM, Sudeep Holla wrote: SCPI specification v1.1 adds support for energy sensors. This patch adds support for the same. Cc: Punit Agrawal Signed-off-by: Sudeep Holla Acked-by: Guenter Roeck ---

Re: [PATCH 0/4][RESEND] thermal: rcar: use thermal-zone on DT

On Wed, Feb 10, 2016 at 12:34:13AM +, Kuninori Morimoto wrote: > > Hi Eduardo, Simon > > > > > Hi Eduardo > > > > > > > > I'm sorry I didn't mention you. > > > > Can you please check these patches ? > > > > > > Yes Morimoto, they are now on my todo list. > > > > > > Applied first one. >

Re: [ANNOUNCE] 4.4.1-rt6

On Mon, 2016-02-15 at 18:25 +0100, Mike Galbraith wrote: > On Sat, 2016-02-13 at 00:47 +0100, Sebastian Andrzej Siewior wrote: > > > Known issues: > > - bcache stays disabled > > > > - CPU hotplug got a little better but can deadlock. > > My x86_64 desktop box survived 100 iterations of

Re: [PATCH] PM / OPP: Initialize regulator pointer to an error value

On Tue, Feb 16, 2016 at 06:30:59AM +0530, Viresh Kumar wrote: > - And so I left the regulator pointer to NULL in OPP core. > - But then I realized that its not safe to call many regulator core > APIs with NULL regulator, as those caused the crashes reported by > multiple people now. > - clk

Re: checkpatch falsepositives in Lustre code

On Feb 15, 2016, at 7:56 PM, Joe Perches wrote: > [etc...] > > Yeah, that's a defect of some type. Also while I have your attention, here's another one: struct cfs_percpt_lock * cfs_percpt_lock_alloc(struct cfs_cpt_table *cptab) { struct cfs_percpt_lock *pcl; spinlock_t

Re: [PATCH 1/2] ideapad: No hardware switch after 2016

On 02/16/2016 01:32 AM, Bjørn Mork wrote: > Ike Panhc writes: >> On 02/15/2016 08:08 PM, Bjørn Mork wrote: >>> Ike Panhc writes: >>> There are complains on few ideapads that wireless is always hard blocked but there is no physical radio

[PATCH] rtc: s5m: De-inline large functions to save space

Few functions were marked inline even though they were relatively large and sometimes used in multiple places. De-inline them to let the compiler decide whether optimization makes sense. This fixes inline_hunt report: drivers/rtc/rtc-s5m.c: Deinline s5m8767_rtc_set_alarm_reg, save 704 bytes

Re: [media 7/7] PCI bridge driver for PT3 & PXQ3PE

2016-02-15 21:57 GMT+09:00 kbuild test robot <l...@intel.com>: > Hi Буди, > > [auto build test ERROR on linuxtv-media/master] > [cannot apply to v4.5-rc4 next-20160215] > [if your patch is applied to the wrong git tree, please drop us a note to > help improving the syst

Re: [PATCH v4 4/8] dt-bindings: Add a binding for Mediatek Video Encoder

Hi Daniel, On Mon, 2016-02-15 at 18:42 +0800, Daniel Kurtz wrote: > On Tue, Feb 9, 2016 at 7:29 PM, Daniel Kurtz wrote: > > Hi Tiffany, > > > > On Thu, Feb 4, 2016 at 7:34 PM, Tiffany Lin > > wrote: > >> Add a DT binding documentation of Video

[PATCH 2/2] ARM: dts: vf-colibri: add supply regulators

Colibri modules need to be powered using the power pins 3V3 and AVDD. Add fixed regulators which represent this power rails. Potentially, those power rails could be switched on a carrier board. A carrier board device tree could add a own regulator with a GPIO, and reference that regulator in a

[PATCH 1/2] ARM: dts: vf-colibri: remove container node of regulators

Drop the fake simple-bus container 'regulators' and put the regulators directly under the root node. This also makes the artificial 'reg' properties superfluous. Signed-off-by: Stefan Agner --- arch/arm/boot/dts/vf-colibri-eval-v3.dtsi | 44 +-- 1

[PATCH 1/8] fs crypto: add basic definitions for per-file encryption

This patch adds definitions for per-file encryption used by ext4 and f2fs. Signed-off-by: Jaegeuk Kim --- include/linux/fs.h | 8 ++ include/linux/fscrypto.h | 238 +++ include/uapi/linux/fs.h | 18 3 files changed,

[PATCH 2/9] ARM: dts: uniphier: rework UniPhier System Bus nodes

Tidy up the System Bus nodes in order to make the driver (drivers/bus/uniphier-system-bus.c) really available. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-common32.dtsi | 19 ++-

[PATCH 1/9] ARM: dts: uniphier: factor out ranges property of support card

This property is used in common by several boards. Move it to the common place (uniphier-support-card.dtsi). If necessary, each board can still override the property. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-ph1-ld4-ref.dts | 8

[PATCH 7/8] f2fs crypto: migrate into vfs's crypto engine

This patch removes the most parts of internal crypto codes. And then, it modifies some f2fs-specific crypt codes to use the generic facility. Signed-off-by: Jaegeuk Kim --- fs/f2fs/Kconfig | 10 +- fs/f2fs/Makefile| 2 - fs/f2fs/crypto.c| 473

[PATCH 2/8] fs crypto: add crypto.c for encrypt/decrypt functions

This patch adds crypto.c supporting encrypting and decrypting functions. 1. IO preparation: - fscrypt_get_ctx / fscrypt_release_ctx 2. before IOs: - fscrypt_encrypt_page - fscrypt_decrypt_page - fscrypt_zeroout_range 3. after IOs: - fscrypt_decrypt_bio_pages -

[PATCH 8/9] ARM: dts: uniphier: add PH1-Pro4 Sanji board support

Initial commit for PH1-Pro4 Sanji board support. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/Makefile| 1 + arch/arm/boot/dts/uniphier-ph1-pro4-sanji.dts | 108 ++ 2 files changed, 109 insertions(+) create

[PATCH 8/8] ext4 crypto: migrate into vfs's crypto engine

This patch removes the most parts of internal crypto codes. And then, it modifies and adds some ext4-specific crypt codes to use the generic facility. Signed-off-by: Jaegeuk Kim --- fs/ext4/Kconfig | 12 +- fs/ext4/Makefile| 2 - fs/ext4/crypto.c|

[PATCH 7/9] ARM: dts: uniphier: add PH1-Pro4 Ace board support

Initial commit for PH1-Pro4 Ace board support. Note: There are two variants for the amount of DDR memory; 1GB or 2GB. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/Makefile | 1 + arch/arm/boot/dts/uniphier-ph1-pro4-ace.dts | 113

Re: [PATCH v2 1/4] locking/mutex: Add waiter parameter to mutex_optimistic_spin()

On Fri, 2016-02-12 at 14:14 -0800, Davidlohr Bueso wrote: > On Fri, 12 Feb 2016, Peter Zijlstra wrote: > > >On Fri, Feb 12, 2016 at 12:32:12PM -0500, Waiman Long wrote: > >> static bool mutex_optimistic_spin(struct mutex *lock, > >> +struct ww_acquire_ctx *ww_ctx, >

[PATCH 0/9] ARM: uniphier: UniPhier updates for Linux 4.6-rc1

Hi Arnd and Olof, Here is a series I want you to apply to ASOC. I know this series includes DT updates for ARM 32bit and ARM 64bit, but this is intentional. Please apply the whole series to one branch. Otherwise, it would cause a build error and big conflicts. (some DT files are shared between

[PATCH 5/9] ARM: dts: uniphier: add EEPROM node for ProXstream2 Gentil board

This board has an EEPROM (STMicroelectronics M24C64-WMN6TP) connected to the I2C channel 0 of the SoC. Its slave address is 0x54. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-proxstream2-gentil.dts | 5 + 1 file changed, 5 insertions(+)

[PATCH 4/9] ARM: dts: uniphier: add reference clock nodes

Add master clock nodes generated by crystal oscillators. PH1-sLD3, PH1-LD4: 24.576 MHz PH1-Pro4, ProXstream2: 25.000 MHz PH1-Pro5: 20.000 MHz Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-common32.dtsi| 7 +++

[PATCH 9/9] ARM: dts: uniphier: add @{address} to EEPROM node

Just for consistent coding style. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-ref-daughter.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/uniphier-ref-daughter.dtsi

[PATCH 3/9] ARM: uniphier: add missing of_node_put()

This node pointer is allocated by of_find_compatible_node() in this function. It should be put before exitting this function. Signed-off-by: Masahiro Yamada --- arch/arm/mach-uniphier/platsmp.c | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH] acpi, pci, irq: account for early penalty assignment

On 2/15/2016 7:26 PM, Rafael J. Wysocki wrote: > On Mon, Feb 15, 2016 at 5:41 PM, Sinan Kaya wrote: >> A crash has been observed when assigning penalty on x86 systems. >> >> It looks like this problem happens on x86 platforms with IOAPIC and an SCI >> interrupt override in

[PATCH 3/8] fs crypto: add policy.c to handle contexts

This patch adds policy.c supporting context management. 1. For ioctls: - fscrypt_process_policy - fscrypt_get_policy 2. For context permission - fscrypt_has_permitted_context - fscrypt_inherit_context Signed-off-by: Michael Halcrow Signed-off-by: Theodore Ts'o

[PATCH 6/9] ARM: dts: uniphier: enable I2C channel 2 of ProXstream2 Gentil board

This is used for on-board inter-connection. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-proxstream2-gentil.dts | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/uniphier-proxstream2-gentil.dts

[PATCH 4/8] fs crypto: add keyinfo.c to handle permissions

This patch adds keyinfo.c supporting key management. - fscrypt_get_encryption_info - fscrypt_free_encryption_info Signed-off-by: Michael Halcrow Signed-off-by: Ildar Muslukhov Signed-off-by: Theodore Ts'o Signed-off-by: Jaegeuk Kim

[PATCH 6/8] fs crypto: add Makefile and Kconfig

This patch adds a facility to enable per-file encryption. Signed-off-by: Jaegeuk Kim --- fs/Kconfig | 2 ++ fs/Makefile| 1 + fs/crypto/Kconfig | 16 fs/crypto/Makefile | 2 ++ 4 files changed, 21 insertions(+) create mode 100644

[PATCH] gpio-mcp23s08: correctly handling failed allocation

Since devm_kzalloc can be failed in memory pressure, it needs to check and return -ENOMEM Signed-off-by: Insu Yun --- drivers/gpio/gpio-mcp23s08.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpio/gpio-mcp23s08.c b/drivers/gpio/gpio-mcp23s08.c index

[PATCH 5/8] fs crypto: add fname.c to support filename encryption

This patch adds fname.c supporting filename encryption. 1. general wrapper functions - fscrypt_fname_disk_to_usr - fscrypt_fname_usr_to_disk - fscrypt_setup_filename - fscrypt_free_filename 2. specific filename handling functions - fscrypt_fname_alloc_buffer - fscrypt_fname_free_buffer

Re: [PATCH] staging: wilc1000: remove wilc1000_spi_ops as it is not used

On Mon, Feb 15, 2016 at 03:18:27PM +, Colin King wrote: > From: Colin Ian King > > building with gcc 6 I hit a build failure: > > CC drivers/staging/wilc1000/wilc_spi.o > drivers/staging/wilc1000/wilc_spi.c:123:34: error: storage size of >

Re: [PATCH v2 1/4] locking/mutex: Add waiter parameter to mutex_optimistic_spin()

On Mon, 2016-02-15 at 18:15 -0800, Jason Low wrote: > On Fri, 2016-02-12 at 14:14 -0800, Davidlohr Bueso wrote: > > On Fri, 12 Feb 2016, Peter Zijlstra wrote: > > > > >On Fri, Feb 12, 2016 at 12:32:12PM -0500, Waiman Long wrote: > > >> static bool mutex_optimistic_spin(struct mutex *lock, > > >>

[PATCH] et131x: check return value of dma_alloc_coherent

For error handling, dma_alloc_coherent's return value needs to be checked, not argument. Signed-off-by: Insu Yun --- drivers/net/ethernet/agere/et131x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/agere/et131x.c

Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130()

On Feb 15, 2016 12:14 PM, "Borislav Petkov" wrote: > > --- > From: Borislav Petkov > Date: Mon, 15 Feb 2016 19:50:33 +0100 > Subject: [RFC PATCH] x86/FPU: Fix double FPU regs activation > > On the entry_INT80_32->do_syscall_32_irqs_on path on 32-bit we run with >

[PATCH] drbd: correctly handling failed crypto_alloc_hash

crypto_alloc_hash returns an error code, not NULL. Signed-off-by: Insu Yun --- drivers/block/drbd/drbd_receiver.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/block/drbd/drbd_receiver.c b/drivers/block/drbd/drbd_receiver.c index

Re: checkpatch falsepositives in Lustre code

On Mon, 2016-02-15 at 20:57 -0500, Oleg Drokin wrote: > On Feb 15, 2016, at 7:56 PM, Joe Perches wrote: > > [etc...] > > > > Yeah, that's a defect of some type. > > Also while I have your attention, here's another one: > > struct cfs_percpt_lock * > cfs_percpt_lock_alloc(struct cfs_cpt_table

Re: [PATCH] staging: lustre: Fixed the parenthesis

On Sun, Feb 14, 2016 at 07:37:02PM -0800, Shalin Mehta wrote: > The parentehsis are fixed in the macro for the ldlm lock to set and > clear the flags. "fixed" in what way? Did you test-build this patch? Also, you mispelled a word here... thanks, greg k-h

[PATCH] tcp: correctly crypto_alloc_hash return check

crypto_alloc_hash never returns NULL Signed-off-by: Insu Yun --- net/ipv4/tcp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c index fd17eec..a95aac1 100644 --- a/net/ipv4/tcp.c +++ b/net/ipv4/tcp.c @@ -2946,7 +2946,7 @@

[PATCH] rc: correctly handling failed allocation

Since rc_allocate_device() uses kmalloc, it can returns NULL, so need to check, otherwise, NULL derefenrece can be happened. Signed-off-by: Insu Yun --- drivers/media/rc/igorplugusb.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/media/rc/igorplugusb.c

[PATCH] bcm590xx: correctly handle return value of i2c_new_dummy()

i2c_new_dummy() returns NULL when failed, not an error code. Signed-off-by: Insu Yun --- drivers/mfd/bcm590xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mfd/bcm590xx.c b/drivers/mfd/bcm590xx.c index 320aaef..7aaf622 100644 ---

[PATCH v4 0/4] x86: sigcontext fixes, again

This is take 2 at fixing x86 64-bit signals wrt SS. After a lot of thought, this is not controlled by any flags -- I would much prefer to avoid opt-in behavior. Instead, it just tries hard to avoid triggering the cases that break DOSEMU. Stas, this now seems to pass the test you sent me. It

[PATCH v4 2/4] x86/signal/64: Fix SS if needed when delivering a 64-bit signal

Signals are always delivered to 64-bit tasks with CS set to a long mode segment. In long mode, SS doesn't matter as long as it's a present writable segment. If SS starts out invalid (this can happen if the signal was caused by an IRET fault or was delivered on the way out of set_thread_area or

[PATCH v4 4/4] selftests/x86: Add tests for UC_SIGCONTEXT_SS and UC_STRICT_RESTORE_SS

This tests the two ABI-preserving cases that DOSEMU cares about, and it also explicitly tests the new UC_SIGCONTEXT_SS and UC_STRICT_RESTORE_SS flags. Signed-off-by: Andy Lutomirski --- tools/testing/selftests/x86/sigreturn.c | 222 1 file

[PATCH v4 3/4] x86/signal/64: Re-add support for SS in the 64-bit signal context

This is a second attempt to make the improvements from c6f2062935c8 ("x86/signal/64: Fix SS handling for signals delivered to 64-bit programs"), which was reverted by 51adbfbba5c6 ("x86/signal/64: Add support for SS in the 64-bit signal context"). This adds two new uc_flags flags.

[PATCH v4 1/4] x86/signal/64: Add a comment about sigcontext->fs and gs

These fields have a strange history. This tries to document it. This borrows from 9a036b93a344 ("x86/signal/64: Remove 'fs' and 'gs' from sigcontext"), which was reverted by ed596cde9425 ("Revert x86 sigcontext cleanups"). Signed-off-by: Andy Lutomirski ---

Re: [PATCH] staging: lustre: Fixed the parenthesis

On Feb 15, 2016, at 9:28 PM, Greg KH wrote: > On Sun, Feb 14, 2016 at 07:37:02PM -0800, Shalin Mehta wrote: >> The parentehsis are fixed in the macro for the ldlm lock to set and >> clear the flags. > > "fixed" in what way? Did you test-build this patch? Also, you > mispelled a word here…

Re: [PATCH v4 00/13] mmc: use sdhci_pltfm_init for private allocation and clean up

Dear Adrian, Ulf, On Mon, 8 Feb 2016 16:09:37 +0200 Adrian Hunter wrote: > On 04/02/16 12:38, Ulf Hansson wrote: > > + Adrian > > > > On 26 January 2016 at 11:15, Jisheng Zhang wrote: > >> These patches are to complete the TODOs in Commit 0e748234293f ("mmc: > >> sdhci:

4.5 regression - [drm/vmwgfx] BUG: unable to handle kernel NULL pointer dereference at (null)

Hi all, With Linux 4.5-rc4, I still have a problem what I had reported, on VMWare workstation 10 (Linux guest, Windows 7 host); [drm/vmwgfx] BUG: unable to handle kernel NULL pointer dereference at (null)

Re: checkpatch falsepositives in Lustre code

On Feb 15, 2016, at 9:27 PM, Joe Perches wrote: > On Mon, 2016-02-15 at 20:57 -0500, Oleg Drokin wrote: >> On Feb 15, 2016, at 7:56 PM, Joe Perches wrote: >>> [etc...] >>> >>> Yeah, that's a defect of some type. >> >> Also while I have your attention, here's another one: >> >> struct

[PATCH] s5p_mfc: handling failed allocation for workqueue

create_singlethread_workqueue() can be failed in memory pressure. Signed-off-by: Insu Yun --- drivers/media/platform/s5p-mfc/s5p_mfc.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc.c b/drivers/media/platform/s5p-mfc/s5p_mfc.c

[PATCH] fusion-mptbase: handle failed allocation for workqueue

the failure of ioc->reset_work_q is checked, but not ioc->fw_event_q. Signed-off-by: Insu Yun --- drivers/message/fusion/mptbase.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/message/fusion/mptbase.c b/drivers/message/fusion/mptbase.c index

[PATCH] usb: check for signals in chaoskey read function

Call signal_pending before reading a chunk of data from the device so that long read operations can be interrupted with a signal. Signed-off-by: Keith Packard --- drivers/usb/misc/chaoskey.c | 7 +++ 1 file changed, 7 insertions(+) diff --git

Re: [PATCH 3/3] drivers/acpi: make pmic/intel_pmic_crc.c explicitly non-modular

On 02/15/2016 01:27 PM, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/acpi/Kconfig:config CRC_PMIC_OPREGION > drivers/acpi/Kconfig: bool "ACPI operation region support for CrystalCove > PMIC" > > ...meaning that it currently is not being

Re: [lustre-devel] [PATCH] staging: lustre: Fixed the parenthesis

On Feb 14, 2016, at 10:37 PM, Shalin Mehta wrote: > The parentehsis are fixed in the macro for the ldlm lock to set and > clear the flags. > > Signed-off-by: Shalin Mehta > --- > drivers/staging/lustre/lustre/include/lustre_dlm_flags.h | 4 ++-- > 1 file changed, 2

Re: [PATCH] ASoC: atmel_ssc_dai: distinguish the different SSC

Any comments on this patch? On 1/13/2016 23:08, Nicolas Ferre wrote: Le 13/01/2016 07:35, Songjun Wu a écrit : Cpu_dai id always equals 0, can't distinguish the different SSC. Use platform_device id to record and distinguish the different SSC. Signed-off-by: Songjun Wu

linux-next: manual merge of the char-misc tree with the staging tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/platform/goldfish/goldfish_pipe.c between commit: 1d427da1d7f9 ("Platform: goldfish: goldfish_pipe.c: Add DMA support using managed version") from the staging tree and commits: 2f3be88237a3

linux-next: manual merge of the char-misc tree with the staging tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/staging/goldfish/goldfish_nand.c between commit: 814625b539d3 ("staging: goldfish: goldfish_nand: Return correct error code") from the staging tree and commit: 3e2fbc7feec4 ("Staging: goldfish:

Re: [RFC 6/6] RCU: Track rcu_dereference() in RCU read-side critical section

On Mon, Feb 15, 2016 at 05:05:53PM -0800, Paul E. McKenney wrote: > On Thu, Feb 04, 2016 at 12:45:12AM +0800, Boqun Feng wrote: > > The variables protected by an RCU read-side critical section are > > sometimes hard to figure out, especially when the critical section is > > long or has some

Re: [PATCH v2 1/4] locking/mutex: Add waiter parameter to mutex_optimistic_spin()

On Mon, 2016-02-15 at 18:55 -0500, Waiman Long wrote: > On 02/12/2016 03:40 PM, Peter Zijlstra wrote: > > On Fri, Feb 12, 2016 at 12:32:12PM -0500, Waiman Long wrote: > >> @@ -358,8 +373,8 @@ static bool mutex_optimistic_spin(struct mutex *lock, > >>} > >> > >>

[PATCH 2/2] clk: bcm2835: Reuse CLK_DIVIDER_MAX_AT_ZERO for recalc_rate()

We were rolling this ourselves, but clk-divider can do it now. Signed-off-by: Eric Anholt --- drivers/clk/bcm/clk-bcm2835.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/drivers/clk/bcm/clk-bcm2835.c b/drivers/clk/bcm/clk-bcm2835.c index

[PATCH 1/2] clk: bcm2835: Fix setting of PLL divider clock rates

Our dividers weren't being set successfully because CM_PASSWORD wasn't included in the register write. It looks easier to just compute the divider to write ourselves than to update clk-divider for the ability to OR in some arbitrary bits on write. Fixes about half of the video modes on my HDMI

Re: checkpatch falsepositives in Lustre code

On Mon, 2016-02-15 at 21:45 -0500, Oleg Drokin wrote: > On Feb 15, 2016, at 9:27 PM, Joe Perches wrote: > > > On Mon, 2016-02-15 at 20:57 -0500, Oleg Drokin wrote: > > > On Feb 15, 2016, at 7:56 PM, Joe Perches wrote: > > > > [etc...] > > > > > > > > Yeah, that's a defect of some type. > > > >

Re: [PATCH 3.12 20/64] xhci: refuse loading if nousb is used

On Thu, 2016-02-11 at 14:58 +0100, Jiri Slaby wrote: > From: Oliver Neukum > > 3.12-stable review patch.  If anyone has any objections, please let me know. > > === > > commit 1eaf35e4dd592c59041bc1ed3248c46326da1f5f upstream. > > The module should fail to load. >

Re: [PATCH] kernel: fs: drop_caches: add dds drop_caches_count

We have a class of platforms that are essentially swap-less embedded systems that have limited memory resources (2GB and less). There is a need to implement early alerts (before the OOM killer kicks in) based on the current memory usage so admins can take appropriate steps (do not initiate

Re: checkpatch falsepositives in Lustre code

On Feb 15, 2016, at 10:05 PM, Joe Perches wrote: > On Mon, 2016-02-15 at 21:45 -0500, Oleg Drokin wrote: >> On Feb 15, 2016, at 9:27 PM, Joe Perches wrote: >> >>> On Mon, 2016-02-15 at 20:57 -0500, Oleg Drokin wrote: On Feb 15, 2016, at 7:56 PM, Joe Perches wrote: > [etc...] >

Re: [PATCH] ARM: don't print missing L2 cache as error

Hi Russel, Any comment to this? Currently the kernel prints an error message as follows on the platform at hand: [0.00] L2C: failed to init: -19 -- Stefan On 2016-01-27 17:27, Stefan Agner wrote: > Not having a L2 cache controller is a shame, but not an error. Avoid > printing an error

[PATCH] spi: rockchip: remove xfer_completion from rockchip_spi

xfer_completion isn't been used anywhere, so it can be removed. Signed-off-by: Shawn Lin --- drivers/spi/spi-rockchip.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c index 79a8bc4..07909ee9 100644 ---

Re: [PATCH v2 1/4] locking/mutex: Add waiter parameter to mutex_optimistic_spin()

On 02/15/2016 10:00 PM, Jason Low wrote: On Mon, 2016-02-15 at 18:55 -0500, Waiman Long wrote: On 02/12/2016 03:40 PM, Peter Zijlstra wrote: On Fri, Feb 12, 2016 at 12:32:12PM -0500, Waiman Long wrote: @@ -358,8 +373,8 @@ static bool mutex_optimistic_spin(struct mutex *lock,

linux-next: manual merge of the gpio tree with the mfd tree

Hi Linus, Today's linux-next merge of the gpio tree got conflicts in: drivers/gpio/Kconfig drivers/gpio/Makefile between commit: 5d8c473983fc ("gpio: tps65086: Add GPO driver for the TPS65086 PMIC") from the mfd tree and commit: b866526d0cfe ("gpio: Add driver for TI TPIC2810")

linux-next: manual merge of the gpio tree with the pinctrl tree

Hi Linus, Today's linux-next merge of the gpio tree got a conflict in: drivers/pinctrl/sunxi/pinctrl-sunxi.c between commit: be2d107f4433 ("pinctrl: sunxi: Use pin number when calling sunxi_pmx_set") from the pinctrl tree and commit: 6cee3821e4e4 ("gpio/pinctrl: sunxi: stop poking

[PATCH] irqchip/gicv3-its: Avoid cache flush beyond ITS_BASERn memory size

Function its_alloc_tables() maintains two local variables, "order" and and "alloc_size", to hold memory size that has been allocated to ITS_BASEn. We don't always refresh the variable alloc_size whenever value of the variable order changes, causing the following two problems. - Cache flush

[PATCH] ARM: dts: colibri-vf: Add pinmux for UART_0 aka UART_A RTS/CTS pins

Add pinmux for UART_A RTS, CTS pin's. Signed-off-by: Bhuvanchandra DV Acked-by: Stefan Agner --- arch/arm/boot/dts/vf-colibri.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/vf-colibri.dtsi

Re: [PATCH v2 05/10] regulator: axp20x: support AXP809 variant

On Tue, Feb 16, 2016 at 4:04 AM, Mark Brown wrote: > On Mon, Feb 15, 2016 at 06:31:23PM +0800, Chen-Yu Tsai wrote: >> The X-Powers AXP809 PMIC has a similar set of regulators as the AXP221, >> though a few LDOs were removed, and a new switch output added. Like the >> AXP221,

linux-next: build failure after merge of the gpio tree

esc[offset].flags; ^ Caused by commit c366c76a2c41 ("gpio: add tps65218 gpio") interacting with commit 1c3cdb186172 ("gpio: move descriptors into gpio_device") both from the gpio tree. I have used the gpio tree from next-20160215 fro today. -- Cheers, Stephen Rothwell

[PATCH] mmc: mmc_spi: Add Card Detect comments and fix CD GPIO case

From: Magnus Damm This patch adds comments to describe the various ways card detection may be implemented and when polling is needed. Also a fix is included to prevent the MMC SPI driver from polling when a CD GPIO that supports interrupts is specified using the gpios

Re: [RFC 6/6] RCU: Track rcu_dereference() in RCU read-side critical section

On Tue, Feb 16, 2016 at 11:01:43AM +0800, Boqun Feng wrote: > On Mon, Feb 15, 2016 at 05:05:53PM -0800, Paul E. McKenney wrote: > > On Thu, Feb 04, 2016 at 12:45:12AM +0800, Boqun Feng wrote: > > > The variables protected by an RCU read-side critical section are > > > sometimes hard to figure out,

linux-next: manual merge of the clk tree with the samsung-krzk tree

Hi all, Today's linux-next merge of the clk tree got a conflict in: drivers/clk/Kconfig drivers/clk/samsung/Kconfig between commit: fa6439544887 ("clk: samsung: Enable COMPILE_TEST for Samsung clocks") from the samsung-krzk tree and commit: b9e65ebc654d ("clk: Move vendor's Kconfig

RE: [PATCH 1/3] input: cygnus-update touchscreen dt node document

> -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: 12 February 2016 20:35 > To: Raveendra Padasalagi > Cc: Dmitry Torokhov; Arnd Bergmann; Russell King; devicet...@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; linux-in...@vger.kernel.org; Pawel Moll; >

Re: linux-next: manual merge of the clk tree with the samsung-krzk tree

On 16.02.2016 13:11, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the clk tree got a conflict in: > > drivers/clk/Kconfig > drivers/clk/samsung/Kconfig > > between commit: > > fa6439544887 ("clk: samsung: Enable COMPILE_TEST for Samsung clocks") > > from the

[PATCH v2] arm64: add alignment fault hanling

Userspace memory is mapped as below: F2A7F000--F2A7 Normal Memory F2A8--F2A80FFF Device nGnRnE And that userspace application makes a system call as below: -009 |do_strncpy_from_user(inline) -009 |strncpy_from_user() -010 |getname_flags() -011 |user_path_at_empty() -012 |user_path_at()

Re: [PATCH v8 4/8] ppc64 ftrace_with_regs configuration variables

On Mon, 2016-02-15 at 23:21 +0100, Torsten Duwe wrote: > On Mon, Feb 15, 2016 at 03:04:08PM +0100, Torsten Duwe wrote: > > If you use "-pg -mprofile-kernel", gcc seems to forget that, and omits the > > TOC > > load, for a similar assembler calling sequence. > > > > Looking at the code I can

Re: [ANNOUNCE] 4.4.1-rt6

On Sat, 13 Feb 2016 00:47:08 +0100 Sebastian Andrzej Siewior wrote: > - There is a useless rcu_bh thread which has been deactivated. > For some strange reason I had RCU_TORTURE_TEST defined in my config. This caused my compile to blow up because kernel/rcu/rcutorture.c

Re: [PATCH v2] clk: Move vendor's Kconfig into CCF menu section

2016-01-28 17:58 GMT+09:00 James Liao : > Move all vendor's Kconfig into CCF menu section to prevent > new drivers putting their Kconfig files in a wrong place. > > Some Kconigs need to modify at the same time to avoid build > warnings. > > Signed-off-by: James Liao

Re: [RFC 6/6] RCU: Track rcu_dereference() in RCU read-side critical section

On Mon, Feb 15, 2016 at 08:08:40PM -0800, Paul E. McKenney wrote: > On Tue, Feb 16, 2016 at 11:01:43AM +0800, Boqun Feng wrote: > > On Mon, Feb 15, 2016 at 05:05:53PM -0800, Paul E. McKenney wrote: > > > On Thu, Feb 04, 2016 at 12:45:12AM +0800, Boqun Feng wrote: > > > > The variables protected by

[PATCH v3 0/3] Allow iio_hwmon to accept hypen in node names

Hello, Initial versions of the patchset intended to introduce the use of iio_hwmon for Vybrid SoC's. Currently the iio_hwmon driver has two users and as per the binding documentation, the node names use the underscore. Use of hypen in device tree node names is acceptable, however currently the

[PATCH v3 2/3] ARM: dts: Change iio_hwmon nodes to use hypen in node names

Change iio_hwmon nodes to use hypen in node names instead of underscore. Signed-off-by: Sanchayan Maity --- Documentation/devicetree/bindings/iio/iio-bindings.txt | 2 +- arch/arm/boot/dts/imx23.dtsi | 2 +- arch/arm/boot/dts/imx28.dtsi

[PATCH v3 3/3] ARM: dts: vfxxx: Add iio_hwmon node for ADC temperature channel

Add iio-hwmon node to expose the temperature channel on Vybrid as hardware monitor device using the iio_hwmon driver. Signed-off-by: Sanchayan Maity --- arch/arm/boot/dts/vfxxx.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/vfxxx.dtsi

[PATCH v3 1/3] hwmon: iio_hwmon: Allow the driver to accept hypen in device tree node names

Currently the driver calls hwmon_device_register_with_groups which does not accept hypen in node name and returns EINVAL. Use of hypen in device tree node name results in probe failure., however use of hypen in device tree node name is perfectly acceptable. Change this by allocating a duplicate

Re: [PATCH V3] powerpc/mm: Fix Multi hit ERAT cause by recent THP update

On Mon, 2016-02-15 at 16:31 +0530, Aneesh Kumar K.V wrote: > Balbir Singh writes: > > > > Now we can't depend for mm_cpumask, a parallel find_linux_pte_hugepte > > > can happen outside that. Now i had a variant for kick_all_cpus_sync that > > > ignored idle cpus. But then

<    3   4   5   6   7   8   9   10   11   12   >