Re: [PATCH] timekeeping: Limit system time to prevent 32-bit time_t overflow

On Fri, Oct 09, 2015 at 12:38:32PM +0200, Thomas Gleixner wrote: > On Fri, 9 Oct 2015, Miroslav Lichvar wrote: > > Do you feel the same about preventing the time from reaching > > KTIME_MAX? > > That's going to happen in ~500 years from now. At any time if you include accidents and attacks on

Re: [PATCH] can: at91: remove at91_can_data

On 09/10/2015 at 12:07:40 +0200, Marc Kleine-Budde wrote : > On 10/08/2015 04:56 PM, Alexandre Belloni wrote: > > struct at91_can_data was used to pass a callback to the driver, allowing it > > to switch the transceiver on and off. As all at91 boards are now using DT, > > this is not used anymore,

Re: [PATCHv3] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ

On Friday 09 October 2015 11:33:52 Will Deacon wrote: > Acked-by: Will Deacon > > Arnd: are you planning to take this via asm-generic, or shall I queue it > on the arm64 fixes branch? > Please merge it for arm64 with my Acked-by: Arnd Bergmann Arnd -- To unsubscribe from this list:

Re: [PATCHv3 1/2] ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4

Hi Krzysztof, On 9 October 2015 at 16:17, Krzysztof Kozlowski wrote: > W dniu 09.10.2015 o 19:28, Arnd Bergmann pisze: >> On Friday 09 October 2015 11:59:05 Sjoerd Simons wrote: >>> I realize that building things as modules is a hassle, it is so for some things more than for others, so

Re: [PATCH v2 07/22] arm64: Keep track of CPU feature registers

On 08/10/15 10:55, Suzuki K. Poulose wrote: On 07/10/15 18:16, Catalin Marinas wrote: On Mon, Oct 05, 2015 at 06:01:56PM +0100, Suzuki K. Poulose wrote: diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c index 1ae8b24..d42ad90 100644 ---

Re: Re: [PATCHv3] ARM64:Fix MINSIGSTKSZ and SIGSTKSZ

>> MINSIGSTKSZ and SIGSTKSZ for ARM64 are not correctly set in latest kernel. >> This patch fixes this issue. >> >> This issue is reported in LTP (testcase: sigaltstack02.c). >> Testcase failed when sigaltstack() called with stack size "MINSIGSTKSZ - 1" >> Since in Glibc-2.22, MINSIGSTKSZ is set

Re: [PATCH 1/5] thermal: exynos: Fix unbalanced regulator disable on probe failure

W dniu 09.10.2015 o 01:45, Alim Akhtar pisze: > Hello, > > On Thu, Oct 8, 2015 at 11:04 AM, Krzysztof Kozlowski > wrote: >> During probe if the regulator could not be enabled, the error exit path >> would still disable it. This could lead to unbalanced counter of >> regulator enable/disable. >>

Re: [PATCH v3] tpm, tpm_crb: fix unaligned read of the command buffer address

Hi This would desperately neeed Tested-by's (with Haswell PTT). /Jarkko On Tue, Sep 15, 2015 at 08:05:40PM +0300, Jarkko Sakkinen wrote: > The command buffer address must be read with exactly two 32-bit reads. > Otherwise, on some HW platforms, it seems that HW will abort the read > operation,

Re: [PATCH v2 0/2] KVM: x86: fix edge EOI and IOAPIC reconfig race

On 08/10/2015 20:23, Radim Krčmář wrote: > v2: > * rewritten [1/2] and > * refactored [2/2], all thanks to Paolo's comments > > This problem is not fixed for split userspace part as I think that it > would be better to solve that by excluding edge interrupts from > eoi_exit_bitmap (see the

Re: [PATCH v9 2/3] tpm: move the PPI attributes to character device directory.

This would need Tested-by's. I've run it both with dTPM 2.0 and fTPM based platforms. It would require testing with TPM 1.2 chip to make sure it doesn't break anything. Thank you. /Jarkko On Tue, Sep 29, 2015 at 10:36:32AM +0300, Jarkko Sakkinen wrote: > Moved PPI attributes to the character

Re: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation

On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote: > Stepping back a second, I believe that there are three cases: > > > RELEASE X -> ACQUIRE Y (same CPU) >* Needs a barrier on TSO architectures for full ordering +PPC > UNLOCK X -> LOCK Y (same CPU) >* Needs a

Re: [PATCH] KVM: x86: don't notify userspace IOAPIC on edge EOI

On 08/10/2015 20:34, Radim Krčmář wrote: > 2015-10-08 20:30+0200, Radim Krčmář: >> On real hardware, edge-triggered interrupts don't set a bit in TMR, >> which means that IOAPIC isn't notified on EOI. Do the same here. >> >> Staying in guest/kernel mode after edge EOI is what we want for most

RE: [PATCH v8 0/9] Goodix touchscreen enhancements

> -Original Message- > From: linux-input-ow...@vger.kernel.org > [mailto:linux-input-ow...@vger.kernel.org] On Behalf Of Arnd Bergmann > Sent: 08 October, 2015 17:32 > To: Tirdea, Irina > Cc: Dmitry Torokhov; Bastien Nocera; Aleksei Mamlin; > linux-in...@vger.kernel.org; Mark Rutland;

[PATCH v3] arm: Adding support for atomic half word exchange

Hello Will, Thank you so much for your patience. My sincere apologies with the issues with formatting. I have taken care of them and hope now things are ok. - Included patchesATarm.linux.org.uk. - Removed the changelog from commit message. - Moved the patch to "superseded" in patch system. -

[PATCH] staging: wilc1000: fix memory leak on mgmt_tx on error return path

From: Colin Ian King Static analysis with cppcheck found the following memory leak: [drivers/staging/wilc1000/linux_mon.c:255]: (error) Memory leak: mgmt_tx Free mgmt_tx on the error return path when mgmt_tx->buff fails to be allocated. Signed-off-by: Colin Ian King ---

Re: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation

On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote: > > Which leads me to think I would like to suggest alternative rules for > > RELEASE/ACQUIRE (to replace those Will suggested; as I think those are > > partly responsible for my confusion). > > Yeah, sorry. I originally used the phrase

Re: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation

On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote: > > > - RELEASE -> ACQUIRE _chains_ (on shared variables) preserve causality, > >(because each link is fully ordered) but are not transitive. > > Yup, and that's the same for UNLOCK -> LOCK, too. Agreed, except RELEASE/ACQUIRE is

Re: [PATCH] kvm: svm: Only propagate next_rip when guest supports it

On 09/10/2015 11:51, Joerg Roedel wrote: > From: Joerg Roedel > > Currently we always write the next_rip of the shadow vmcb to > the guests vmcb when we emulate a vmexit. This could confuse > the guest when its cpuid indicated no support for the > next_rip feature. > > Fix this by only

Re: [PATCH 1/5] leds: core: Drivers shouldn't enforce SYNC/ASYNC brightness setting

On Fri 2015-10-09 10:08:12, Jacek Anaszewski wrote: > On 10/09/2015 09:02 AM, Pavel Machek wrote: > >On Fri 2015-10-09 08:28:44, Jacek Anaszewski wrote: > >>On 10/08/2015 05:50 PM, Pavel Machek wrote: > >>>On Mon 2015-09-21 16:29:26, Jacek Anaszewski wrote: > This patch removes

Re: [PATCH v2 01/12] leds: core: Use EXPORT_SYMBOL_GPL consistently

On Fri 2015-10-09 10:19:48, Jacek Anaszewski wrote: > On 10/08/2015 05:51 PM, Pavel Machek wrote: > >On Mon 2015-09-28 17:13:39, Jacek Anaszewski wrote: > >>This patch isn't going to be applied since it can cause > >>legal implications for existing users. > >> > > > >Are there any? Best do this

Re: [PATCH] genirq: Move irq_set_vcpu_affinity out of "#ifdef CONFIG_SMP"

On 08/10/2015 06:43, Wu, Feng wrote: > Hi Thomas & Paolo, > > What is your option about this patch, Thanks a lot! > > Thanks, > Feng > >>> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c >>> index 1c58655..90b378d 100644 >>> --- a/kernel/irq/manage.c >>> +++ b/kernel/irq/manage.c >>>

Hello

Chevrolet auto mobile company selected your email for the electronic Balloting. 900,000.00 USD was issued to you as winner send name,address and mobile for claim: chev.cla...@yandex.com --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus --

Re: crazy idea: big percpu lock (Re: task isolation)

On Thu, 8 Oct 2015, Andy Lutomirski wrote: > Will this really end up working? I can see two problems: > > 1. It's rather expensive. For processes that still make syscalls but > just not many, it means that you're forcibly quiescing every time. A process that does a lot of syscalls to

Re: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation

On Fri, Oct 09, 2015 at 10:51:29AM +0100, Will Deacon wrote: > > The corresponding litmus tests are below. > > How do people feel about including these in memory-barriers.txt? I find > them considerably easier to read than our current kernel code + list of > possible orderings + wall of text, but

Re: [PATCH v5 06/10] dmaengine: add API for getting dma controller's quirk

On 2015/10/7 22:32, Vinod Koul wrote: On Tue, Oct 06, 2015 at 05:21:13PM +0800, Shawn Lin wrote: + int (*device_get_quirks)(struct dma_chan *chan); And why do we want to expose this to users? THis doesnt seem right! Basically I agree not to expose dma's quirk to slave

[PATCH 1/6] staging: comedi: don't poll_wait on same subdevice twice

Comedi subdevices that support asynchronous acquisition commands have a wait queue head used for blocking reads or writes and for the poll file operation. The comedi device may have several subdevices that support "read" and/or "write" commands, but each open file object has at most one "read"

[PATCH 6/6] staging: comedi: don't use mutex when polling file

The main mutex in a comedi device can get held for quite a while when processing comedi instructions, so for performance reasons, the "read" and "write" file operations do not use it; they use use the `attach_lock` rwsemaphore to protect against the comedi device becoming detached at an

[PATCH 3/6] staging: comedi: add new comedi_buf_write_n_available()

Add a new function `comedi_buf_write_n_available()` to return the amount of buffer space available for writing, including space already allocated by `comedi_buf_write_alloc()` plus any unallocated space available. This is currently just for internal use by the comedi core, so is not exported.

[PATCH 2/6] staging: comedi: rename comedi_buf_write_n_available

Rename the local function `comedi_buf_write_n_available()` to `comedi_buf_write_n_unalloc()`. It is the amount of unallocated space available in the buffer that is available to be allocated for writing and does not include the space that has already been allocated for writing. This is unlike the

[PATCH 5/6] staging: comedi: check command started by file being polled

Currently, the "poll" file operation checks if an asynchronous "read" (or "write" command is active on the "read" (or "write" subdevice, but does not consider whether the command was started from the file object being polled. Since that is the only file object able to read (or write) data, take

[PATCH 4/6] staging: comedi: don't allocate buffer space when polling for write

When handling the "poll" file operation and checking for `POLLOUT`, don't allocate space from the buffer for writing, just check that space is available for writing. That check is done after checking that an asynchronous "write" command is running on the subdevice. Allocating the buffer space

[PATCH 0/6] staging: comedi: fix some minor issues with file poll op

A few changes for the "poll" file operation to avoid poll-waiting on the same subdevice for both read and write (patch 1), avoid allocating write buffer space unnecessarily and possibly inappropriately (patch 4), consider whether any active commands belong to the current file object (patch 5), and

Re: [PATCH 02/10] Drivers: hv: utils: run polling callback always in interrupt context

On Fri, Oct 09, Vitaly Kuznetsov wrote: > Olaf Hering writes: > > > On Thu, Oct 08, KY Srinivasan wrote: > > > >> > yes, but after doing fcopy_respond_to_host(). I'd suggest we leave the > >> > check in place, better safe than sorry. > >> > >> Agreed; Olaf, if it is ok with you, I can fix it

Re: [alsa-devel] [PATCH v5 06/10] dmaengine: add API for getting dma controller's quirk

在 2015/10/8 16:31, Lars-Peter Clausen 写道: On 10/06/2015 11:21 AM, Shawn Lin wrote: Hi Vinod, On 2015/10/5 23:37, Vinod Koul wrote: On Mon, Sep 14, 2015 at 07:48:59AM +0800, Shawn Lin wrote: Add dmaengine_get_quirks API for peripheral devices to query quirks if they need it to make special

RE: [PATCH 05/12] mwifiex: avoid gettimeofday in ba_threshold setting

Hi Arnd, > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: Wednesday, September 30, 2015 4:57 PM > To: net...@vger.kernel.org > Cc: y2...@lists.linaro.org; linux-kernel@vger.kernel.org; David S. > Miller; Arnd Bergmann; Amitkumar Karwar; Nishant Sarmukadam; Kalle Valo; >

Re: [PATCH] thermal: exynos: fix register read in TMU

2015-10-08 23:21 GMT+09:00 Sudip Mukherjee : > On Fri, Oct 02, 2015 at 08:43:52AM +0900, Krzysztof Kozlowski wrote: >> 2015-10-01 23:12 GMT+09:00 Sudip Mukherjee : >> > On Thu, Oct 01, 2015 at 10:18:57PM +0900, Krzysztof Kozlowski wrote: >> >> 2015-10-01 20:39 GMT+09:00 Sudip Mukherjee : >> >> >

Re: [PATCH v4 5/8] clk: rockchip: Allow the RK3288 SPDIF clocks to change their parent

Hey Heiko, On Thu, 2015-10-08 at 17:10 +0200, Heiko Stuebner wrote: > Am Donnerstag, 8. Oktober 2015, 15:31:16 schrieb Sjoerd Simons: > > The clock branches leading to sclk_spdif and sclk_spdif_8ch on > > RK3288 > > SoCs only feed those clocks, allow those clocks to change their > > parents > >

Re: [RFC]: Possible race condition in kernel futex code

On Fri, Oct 09, 2015 at 11:25:09AM +0100, Thomas Gleixner wrote: > Hans, > > On Fri, 9 Oct 2015, Hans Zuidam wrote: > > On 9 okt. 2015, at 11:06, Thomas Gleixner wrote: > > > You cannot use an explicit 32bit read. We need an access which > > > handles the fault gracefully. > > > > The reason for

RE: [PATCH 04/12] mwifiex: use ktime_get_real for timestamping

Hi Arnd, > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: Wednesday, September 30, 2015 4:57 PM > To: net...@vger.kernel.org > Cc: y2...@lists.linaro.org; linux-kernel@vger.kernel.org; David S. > Miller; Arnd Bergmann; Amitkumar Karwar; Nishant Sarmukadam; Kalle Valo; >

RE: [PATCH] mwifiex: fix a comment typo

> From: Geliang Tang [mailto:geliangt...@163.com] > Sent: Sunday, October 04, 2015 2:17 PM > To: Amitkumar Karwar; Nishant Sarmukadam; Kalle Valo > Cc: Geliang Tang; linux-wirel...@vger.kernel.org; > net...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: [PATCH] mwifiex: fix a comment

Re: [alsa-devel] [PATCH v5 06/10] dmaengine: add API for getting dma controller's quirk

On 10/09/2015 01:31 PM, Shawn Lin wrote: > 在 2015/10/8 16:31, Lars-Peter Clausen 写道: >> On 10/06/2015 11:21 AM, Shawn Lin wrote: >>> Hi Vinod, >>> >>> On 2015/10/5 23:37, Vinod Koul wrote: On Mon, Sep 14, 2015 at 07:48:59AM +0800, Shawn Lin wrote: > Add dmaengine_get_quirks API for

Re: [RFC PATCH] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

On Thu, Oct 08, 2015 at 10:21:05AM -0500, Michael Welling wrote: > On Thu, Oct 08, 2015 at 04:45:00PM +0200, Neil Armstrong wrote: > What is the point of doing this void cast below? > Avoiding compiler warning perhaps? > Perhaps you can __maybe_unused for the variable instead? > > + /* Ignore

Re: [PATCH 4/4] spi: spi-coldfire-qspi: enable RuntimePM before registering to the core

On Fri, Oct 09, 2015 at 07:54:53AM +0100, Wolfram Sang wrote: > From: Wolfram Sang > > The core may register clients attached to this master which may use > funtionality from the master. So, RuntimePM must be enabled before, otherwise > this will fail. I'm missing patches 1-3 and the cover

Re: [RFC V3] regmap: change bool to 1 bit variable in struct regmap

On Fri, Oct 09, 2015 at 03:51:22PM +0800, yalin wang wrote: > This patch change some bool variables in struct regmap { } > to be u8 v : 1 type, so that we can shrink the sizeof of struct regmap. This still doesn't apply against current code - I'm looking for something that applies at least

Re: [PATCH V1 0/2] Add DA9021 support to the existing DA9052/53 driver

On Thu, Oct 08, 2015 at 04:17:52PM +0100, Steve Twiss wrote: > From: Steve Twiss > > Two patches to add missing registers and add support for DA9053-BB > silicon in the regulators component. These patches modify existing > files for the Dialog Power Management IC driver for the DA9052/53 >

PLS I NEED YOUR HELP!

I am Mrs Zaara Heyet an oil-servicing equipment merchant, am writing this mail to you with tears and love from my heart of charity work i could not fulfill before the end of my days due to my present healness ,Please do not think of this letter as one of those being sent around to ask for

Re: submit bio directly from userspace

Mike Krinkin writes: > Hi, > > i'm developing block layer workload simulator/player and need to > generate bios as close as possible to the ones in original workload. > To play workload i employ aio + O_DIRECT, but all IOs end up as bios > with SYNC flag set. So i wonder is there any way to

Re: [PATCH v2 00/12] THP support for ARC

On Fri, Oct 09, 2015 at 04:59:43PM +0530, Vineet Gupta wrote: > On Friday 09 October 2015 03:40 PM, Kirill A. Shutemov wrote: > > On Fri, Oct 09, 2015 at 03:03:26PM +0530, Vineet Gupta wrote: > >> On Thursday 01 October 2015 11:32 AM, Vineet Gupta wrote: > >>> On Tuesday 22 September 2015 04:04

[PATCH v3] mm,thp: reduce ifdef'ery for THP in generic code

- pgtable-generic.c: Fold individual #ifdef for each helper into a top level #ifdef. Makes code more readable - Converted the stub helpers for !THP to BUILD_BUG() vs. runtime BUG() Signed-off-by: Vineet Gupta --- Somehow the msg didn't make it to mailing list ! ---

Re: [PATCH v2 net-next 1/3] bpf: enable non-root eBPF programs

Hi, Alexei Starovoitov writes: > On 10/8/15 11:20 AM, Hannes Frederic Sowa wrote: >> Hi Alexei, >> >> On Thu, Oct 8, 2015, at 07:23, Alexei Starovoitov wrote: >>> The feature is controlled by sysctl kernel.unprivileged_bpf_disabled. >>> This toggle defaults to off (0), but can be set true (1).

Re: [PATCH v4 1/8] ASoC: dt-bindings: add rockchip tranceiver bindings

Hey Rob, On Thu, 2015-10-08 at 11:50 -0500, Rob Herring wrote: > On Thu, Oct 8, 2015 at 8:31 AM, Sjoerd Simons > wrote: > > Add devicetree bindings for the spdif tranceiver found on > > found on rk3066, rk3188 and rk3288 SoCs > > > > Signed-off-by: Sjoerd Simons > > > > --- > > > > Changes

Re: [PATCH v8 0/9] Goodix touchscreen enhancements

On Friday 09 October 2015 11:02:01 Tirdea, Irina wrote: > > -Original Message- > > From: linux-input-ow...@vger.kernel.org > > [mailto:linux-input-ow...@vger.kernel.org] On Behalf Of Arnd Bergmann > > Sent: 08 October, 2015 17:32 > > To: Tirdea, Irina > > Cc: Dmitry Torokhov; Bastien

[PATCH] HID: hiddev: change hiddev_connect() to return bool

Since hid_connect() only cares about hiddev_connect() succeeding or failing, there is no need for this function to return an int and it can return a bool instead. Suggested-by: Jiri Kosina Signed-off-by: Luis de Bethencourt --- Hi, The suggestion to change the return type of the function was

Re: [PATCH v2] block: flush queued bios when the process blocks

Hi Mike, [auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore] config: x86_64-lkp (attached as .config) reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones prefixed by >>): In file included from

[PATCH v5 7/7] arm64: dts: berlin4ct: add default pinmux for uart0

Add urt0 txd and rxd muxing setup in the dtsi because uart0 always uses them to work, no other possibilities. Signed-off-by: Jisheng Zhang --- arch/arm64/boot/dts/marvell/berlin4ct.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/marvell/berlin4ct.dtsi

[PATCH v5 1/7] pinctrl: berlin: introduce berlin_pinctrl_probe_regmap()

This is to prepare for the next berlin4ct support, where we won't use simple-mfd any more. Signed-off-by: Jisheng Zhang --- drivers/pinctrl/berlin/berlin.c | 26 +- drivers/pinctrl/berlin/berlin.h | 4 2 files changed, 21 insertions(+), 9 deletions(-) diff --git

[PATCH v5 5/7] pinctrl: dt-binding: document berlin4ct SoC pinctrl

Add berlin4ct to existing berlin pinctrl device tree binding. Signed-off-by: Jisheng Zhang --- Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt

[PATCH v5 3/7] pinctrl: berlin: add the berlin4ct pinctrl driver

Add the pin-controller driver for Marvell Berlin BG4CT SoC, with definition of its groups and functions. This uses the core Berlin pinctrl driver. Signed-off-by: Jisheng Zhang --- drivers/pinctrl/berlin/Kconfig| 5 + drivers/pinctrl/berlin/Makefile | 1 +

[PATCH v5 0/7] arm64: berlin: add pinctrl support

This series adds support for Marvell berlin4ct pin-controller, allowing to configure the pin muxing from the device tree. Since v4: - drop ARCH_BERLIN dependency for it has been met - drop COMPILE_TEST dependency but make berlin pinctrl driver visible if COMPILE_TEST=y, and let this change

[PATCH v5 4/7] arm64: berlin: add the pinctrl dependency for Marvell Berlin SoCs

This is to add the pinctrl dependency for Marvell Berlin SoCs. Signed-off-by: Jisheng Zhang --- arch/arm64/Kconfig.platforms | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms index c6e2c75..3d17ee2 100644 ---

[PATCH v5 6/7] arm64: dts: berlin4ct: add the pinctrl node

Add the avio, soc, sm pinctrl nodes for Marvell berlin4ct SoC. Signed-off-by: Jisheng Zhang --- arch/arm64/boot/dts/marvell/berlin4ct.dtsi | 15 +++ 1 file changed, 15 insertions(+) diff --git a/arch/arm64/boot/dts/marvell/berlin4ct.dtsi

[PATCH v5 2/7] pinctrl: berlin: Make berlin pinctrl driver visible if COMPILE_TEST=y

It is good to allow berlin pinctrl driver to build with COMPILE_TEST, so make the it menu visible when compile-testing. Signed-off-by: Jisheng Zhang --- drivers/pinctrl/berlin/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pinctrl/berlin/Kconfig

Re: [PATCH] thermal: exynos: fix register read in TMU

Hi Krzysztof, > 2015-10-08 23:21 GMT+09:00 Sudip Mukherjee > : > > On Fri, Oct 02, 2015 at 08:43:52AM +0900, Krzysztof Kozlowski wrote: > >> 2015-10-01 23:12 GMT+09:00 Sudip Mukherjee > >> : > >> > On Thu, Oct 01, 2015 at 10:18:57PM +0900, Krzysztof Kozlowski > >> > wrote: > >> >> 2015-10-01

[PATCH] md: fix 32-bit build warning

On 32-bit architectures, the md code produces this warning when CONFIG_LDAF is set: drivers/md/md.c: In function 'check_sb_changes': drivers/md/md.c:8990:10: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'sector_t {aka long long unsigned int}'

Re: [PATCH] HID: hiddev: change hiddev_connect() to return bool

Hi Luis, [auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore] config: x86_64-lkp (attached as .config) reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones prefixed by >>): >>

[PATCH] locktorture: fix wrong parameter handling

Calling locktorture with a wrong parameter makes it unusable: $ modprobe locktorture torture_type=help modprobe: ERROR: could not insert 'locktorture': Invalid argument $ modprobe locktorture torture_type=spin_lock modprobe: ERROR: could not insert 'locktorture': Device or resource busy $ dmesg

Re: [PATCH v2 2/5] mmc: sdhci-pxav3: enable usage of DAT3 pin as HW card detect

On Fri, 9 Oct 2015 03:03:52 +0200 Marcin Wojtas wrote: > Marvell Armada 38x SDHCI controller enable using DAT3 pin as a hardware > card detection. According to the SD sdandard this signal can be used for > this purpose combined with a pull-up resistor, implying inverted (active > low)

[PATCH v3] clocksource/drivers/tango_xtal: Add new timer for Tango SoCs

Sigma Designs Tango platforms provide a 27 MHz crystal oscillator. Use it for clocksource, sched_clock, and delay_timer. Signed-off-by: Marc Gonzalez --- I have a nagging feeling that the QUIT_IF macro will get this patch NAKed ;-) My rationale: error-handling tends to take the focus away from

Re: [PATCH 1/2] irqchip/renesas-intc-irqpin: Remove obsolete platform data support

On Wed, 7 Oct 2015, Geert Uytterhoeven wrote: > On Wed, Oct 7, 2015 at 8:51 PM, kbuild test robot wrote: > > [auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please > > ignore] > > > > config: arm-bockw_defconfig (attached as .config) > > reproduce: > > wget > >

Re: [PATCH] Fix cpupower reporting uninitialized values for offline cpus

On 10/01/2015 03:09 PM, Jacob Tanenbaum wrote: > cpupower monitor reports uninitialized values for offline cpus > > [root@hp-dl980g7-02 linux]# cpupower monitor > ... > 5472| 0| 1|**|**|**|**||**|**|**|| 0.00| > 0.00| 0.00| 0.00| 0.00 *is offline > 10567|

Re: [PATCH] kvm: fix waitqueue_active without memory barrier in virt/kvm/async_pf.c

Paolo Bonzini wrote: > On 09/10/2015 11:04, Kosuke Tatsukawa wrote: >> smp_store_mb() called from set_current_state(), which is called from >> prepare_to_wait() should prevent reordering such as below from >> happening. wait_event*() also calls set_current_state() inside. > > Ah, I missed that

[PATCH v2] kvm: fix waitqueue_active without memory barrier in virt/kvm/async_pf.c

async_pf_execute() seems to be missing a memory barrier which might cause the waker to not notice the waiter and miss sending a wake_up as in the following figure. async_pf_executekvm_vcpu_block

Re: [PATCH v3] arm: Adding support for atomic half word exchange

On Fri, Oct 09, 2015 at 11:10:02AM +, Sarbojit Ganguly wrote: > Hello Will, > > Thank you so much for your patience. My sincere apologies with the issues with > formatting. I have taken care of them and hope now things are ok. > > - Included patchesATarm.linux.org.uk. > - Removed the

[PATCH] clk: add support for Sigma Designs SMP86xx/87xx clocks

This adds support for most of the clocks in the Sigma Designs SMP86xx (tango3) and SMP87xx (tango4) chips. Signed-off-by: Mans Rullgard --- I'm sending this now to avoid the maintainers wasting more time reviewing the woefully incomplete patch that was posted earlier this week. Unlike that

Re: [PATCHv2 0/3] align zpool/zbud/zsmalloc on the api

On Sat, Sep 26, 2015 at 4:04 AM, Vitaly Wool wrote: > Here comes the second iteration over zpool/zbud/zsmalloc API alignment. > This time I divide it into three patches: for zpool, for zbud and for > zsmalloc :) > Patches are non-intrusive and do not change any existing functionality. They >

[PATCH] regulator: core: avoid unused variable warning

The second argument of the mutex_lock_nested() helper is only evaluated if CONFIG_DEBUG_LOCK_ALLOC is set. Otherwise we get this build warning for the new regulator_lock_supply function: drivers/regulator/core.c: In function 'regulator_lock_supply': drivers/regulator/core.c:142:6: warning: unused

Re: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation

On Fri, Oct 09, 2015 at 01:02:46PM +0200, Peter Zijlstra wrote: > On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote: > > Stepping back a second, I believe that there are three cases: > > > > > > RELEASE X -> ACQUIRE Y (same CPU) > >* Needs a barrier on TSO architectures for full

Re: [PATCH v6 0/6] KASAN for arm64

On Fri, Oct 09, 2015 at 01:18:09PM +0300, Andrey Ryabinin wrote: > 2015-10-09 12:48 GMT+03:00 Mark Rutland : > > On Fri, Oct 09, 2015 at 12:32:18PM +0300, Andrey Ryabinin wrote: > > [...] > > > >> I thought the EFI stub isolation patches create a copy of mem*() functions > >> in the stub, > >>

Re: [PATCH] panic: release stale console lock to always get the logbuf printed out

Vitaly Kuznetsov writes: > Andrew Morton writes: > >> On Thu, 08 Oct 2015 12:03:25 +0200 Vitaly Kuznetsov >> wrote: >> >>> > If we picked up patch "kernel: Avoid softlockups in >>> > stop_machine() during heavy printing" from my series (it's completely >>> > independent, I've attached the

[PATCH] netfilter: turn NF_HOOK into an inline function

A recent change to the dst_output handling caused a new warning when the call to NF_HOOK() is the only used of a local variable passed as 'dev', and CONFIG_NETFILTER is disabled: net/ipv6/ip6_output.c: In function 'ip6_output': net/ipv6/ip6_output.c:135:21: warning: unused variable 'dev'

Re: [PATCH v2 4/5] firmware: generalize reading file contents as a helper

On Thu, Oct 8, 2015 at 6:54 PM, Luis R. Rodriguez wrote: > On Thu, Oct 08, 2015 at 01:36:53PM -0400, Josh Boyer wrote: >> On Thu, Oct 1, 2015 at 1:44 PM, Luis R. Rodriguez >> wrote: >> > From: David Howells >> > >> > We'll want to reuse this same code later in order to >> > read two separate

Re: [RFCv5 PATCH 25/46] sched: Add over-utilization/tipping point indicator

On Tue, Sep 29, 2015 at 01:08:46PM -0700, Steve Muckle wrote: > On 08/14/2015 06:02 AM, Morten Rasmussen wrote: > > To be sure not to break smp_nice, we have defined over-utilization as > > when: > > > > cpu_rq(any)::cfs::avg::util_avg + margin > cpu_rq(any)::capacity > > > > is true for any cpu

Re: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation

On Fri, Oct 09, 2015 at 01:12:02PM +0200, Peter Zijlstra wrote: > On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote: > > > Which leads me to think I would like to suggest alternative rules for > > > RELEASE/ACQUIRE (to replace those Will suggested; as I think those are > > > partly

RE: [PATCH V1 0/2] Add DA9021 support to the existing DA9052/53 driver

On 09 October 2015 12:36 Mark Brown wrote: > To: Opensource [Steve Twiss] > Cc: LINUXKERNEL; Lee Jones; Liam Girdwood; Samuel Ortiz; David Dajun > Chen; Support Opensource > Subject: Re: [PATCH V1 0/2] Add DA9021 support to the existing DA9052/53 > driver > > On Thu, Oct 08, 2015 at 04:17:52PM

[PATCH] net: HNS: fix MDIO dependencies

The newly introduced HNS_MDIO Kconfig symbol selects 'MDIO', but that is the wrong symbol as the code used by this driver is provided by PHYLIB rather than the MDIO driver. Also, there is no need to make this driver user selectable, because it is already selected by all drivers that need it. This

Re: [PATCH v2] kvm: fix waitqueue_active without memory barrier in virt/kvm/async_pf.c

On Fri, Oct 09, 2015 at 12:21:55PM +, Kosuke Tatsukawa wrote: > + * Memory barrier is required here to make sure change to > + * vcpu->async_pf.done is visible from other CPUs. This memory > + * barrier pairs with prepare_to_wait's set_current_state() That is not how memory

Re: [PATCH 2/5] Documentation: add the binding file for Freescale imx7d ADC driver

On Thu, Oct 8, 2015 at 5:59 AM, Haibo Chen wrote: > The patch adds the binding file for Freescale imx7d ADC driver. > > Signed-off-by: Haibo Chen Acked-by: Rob Herring > --- > .../devicetree/bindings/iio/adc/imx7d-adc.txt | 26 > ++ > 1 file changed, 26

Re: [PATCH v2 07/22] arm64: Keep track of CPU feature registers

On 08/10/15 16:03, Catalin Marinas wrote: On Thu, Oct 08, 2015 at 10:55:11AM +0100, Suzuki K. Poulose wrote: +#define ARM64_FTR_BITS(ftr_strict, ftr_type, ftr_shift, ftr_width, ftr_safe_val) \ You can drop "ftr_" from all the arguments, it makes the macro definition shorter. In fact I

[PATCH v2] HID: hiddev: change hiddev_connect() to return bool

Since hid_connect() only cares about hiddev_connect() succeeding or failing, there is no need for this function to return an int and it can return a bool instead. Suggested-by: Jiri Kosina Signed-off-by: Luis de Bethencourt --- Hi, No idea why my local build did not complain about the obvious

RE: [PATCH 1/1] mm: vmstat: Add OOM kill count in vmstat counter

> -Original Message- > From: Michal Hocko [mailto:mho...@kernel.org] > Sent: Thursday, October 08, 2015 10:01 PM > To: PINTU KUMAR > Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net; > koc...@gmail.com; rient...@google.com; han...@cmpxchg.org; penguin- >

Re: [PATCH v3] mm,thp: reduce ifdef'ery for THP in generic code

On Friday 09 October 2015 05:13 PM, Vineet Gupta wrote: > - pgtable-generic.c: Fold individual #ifdef for each helper into a top > level #ifdef. Makes code more readable > > - Converted the stub helpers for !THP to BUILD_BUG() vs. runtime BUG() > > Signed-off-by: Vineet Gupta Sorry for

Re: [PATCH] netfilter: turn NF_HOOK into an inline function

Hi Arnd, [auto build test ERROR on next-20151009 -- if it's inappropriate base, please ignore] config: i386-randconfig-i0-201540 (attached as .config) reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones prefixed by >>): net/

Re: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation

On Fri, Oct 09, 2015 at 01:51:11PM +0100, Will Deacon wrote: > On Fri, Oct 09, 2015 at 01:12:02PM +0200, Peter Zijlstra wrote: > > On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote: > > > > Which leads me to think I would like to suggest alternative rules for > > > > RELEASE/ACQUIRE (to

Re: [PATCH v2 00/36] x86: Rewrite all syscall entries except native 64-bit

* Andy Lutomirski wrote: > The first two patches are optimizations that I'm surprised we didn't > already have. I noticed them when I was looking at the generated > asm. > > The next two patches are tests and some old stuff. There's a test > that validates the vDSO AT_SYSINFO annotations.

[tip:x86/asm] x86/vdso: Define BUILD_VDSO while building and emit .eh_frame in asm

Commit-ID: f24f910884277aa6824bbc2dda4b5d0418d45c28 Gitweb: http://git.kernel.org/tip/f24f910884277aa6824bbc2dda4b5d0418d45c28 Author: Andy Lutomirski AuthorDate: Mon, 5 Oct 2015 17:47:58 -0700 Committer: Ingo Molnar CommitDate: Fri, 9 Oct 2015 09:41:05 +0200 x86/vdso: Define

[tip:x86/asm] x86/asm: Re-add parts of the manual CFI infrastructure

Commit-ID: 7b956f035a9ef8bd3ef5490f49fc1bd834d8a70a Gitweb: http://git.kernel.org/tip/7b956f035a9ef8bd3ef5490f49fc1bd834d8a70a Author: Andy Lutomirski AuthorDate: Mon, 5 Oct 2015 17:47:57 -0700 Committer: Ingo Molnar CommitDate: Fri, 9 Oct 2015 09:41:05 +0200 x86/asm: Re-add parts of

[tip:x86/asm] x86/vdso: Replace hex int80 CFI annotations with GAS directives

Commit-ID: 29c0ce9508458ed31a9db2ed425f64c0d6d3ddfb Gitweb: http://git.kernel.org/tip/29c0ce9508458ed31a9db2ed425f64c0d6d3ddfb Author: Andy Lutomirski AuthorDate: Mon, 5 Oct 2015 17:47:59 -0700 Committer: Ingo Molnar CommitDate: Fri, 9 Oct 2015 09:41:06 +0200 x86/vdso: Replace hex

[tip:x86/asm] x86/elf/64: Clear more registers in elf_common_init ()

Commit-ID: 7bcdea4d050cbe4912854a68b93494203eec8b24 Gitweb: http://git.kernel.org/tip/7bcdea4d050cbe4912854a68b93494203eec8b24 Author: Andy Lutomirski AuthorDate: Mon, 5 Oct 2015 17:48:00 -0700 Committer: Ingo Molnar CommitDate: Fri, 9 Oct 2015 09:41:06 +0200 x86/elf/64: Clear more

[tip:x86/asm] x86/vdso/32: Save extra registers in the INT80 vsyscall path

Commit-ID: 8242c6c84a644e5f0f721e4ae2bd542f640c89f9 Gitweb: http://git.kernel.org/tip/8242c6c84a644e5f0f721e4ae2bd542f640c89f9 Author: Andy Lutomirski AuthorDate: Mon, 5 Oct 2015 17:48:01 -0700 Committer: Ingo Molnar CommitDate: Fri, 9 Oct 2015 09:41:06 +0200 x86/vdso/32: Save extra

[tip:x86/asm] x86/entry/64/compat: Disable SYSENTER and SYSCALL32 entries

Commit-ID: e62a254a1f93fcc7299497a5c7231639400b8c3c Gitweb: http://git.kernel.org/tip/e62a254a1f93fcc7299497a5c7231639400b8c3c Author: Andy Lutomirski AuthorDate: Mon, 5 Oct 2015 17:48:02 -0700 Committer: Ingo Molnar CommitDate: Fri, 9 Oct 2015 09:41:07 +0200 x86/entry/64/compat:

<    6   7   8   9   10   11   12   13   14   15   >