[PATCH 3/6] security: Introduce security_settime64()

security_settime() returns a timespec, which is not year 2038 safe on 32bit systems. Thus this patch introduces the security_settime64() function with timespec64 type. We also convert the cap_settime() helper function to use the 64bit types. Signed-off-by: Baolin Wang ---

[PATCH 2/6] timekeeping: Introduce current_kernel_time64()

The current_kernel_time() is not year 2038 safe on 32bit systems since it returns a timespec value. Introduce current_kernel_time64() which returns a timespec64 value. Signed-off-by: Baolin Wang --- include/linux/timekeeping.h |9 - kernel/time/timekeeping.c |6 +++--- 2 files

[PATCH 1/6] time: Introduce struct itimerspec64

The struct itimerspec is not year 2038 safe on 32bit systems due to the limitation of the struct timespec members. Introduce itimerspec64 which uses struct timespec64 instead and provide conversion functions. Signed-off-by: Baolin Wang --- include/linux/time64.h | 35

[PATCH 0/6] Introduce 64bit accessors and structures required to address y2038 issues in the posix_clock subsystem

This patch series change the 32-bit time types (timespec/itimerspec) to the 64-bit types (timespec64/itimerspec64), and add new 64bit accessor functions, which are required in order to avoid y2038 issues in the posix_clock subsystem. In order to avoid spamming people too much, I'm only sending

Re: [PATCH v3] [SCSI] mpt2sas, mpt3sas: Abort initialization if no memory I/O resources detected

On Tue, Jul 14, 2015 at 9:49 PM, Sreekanth Reddy wrote: > Driver crashes if the BIOS do not set up at least one > memory I/O resource. This failure can happen if the device is too > slow to respond during POST and is missed by the BIOS, but Linux > then detects the device later in the boot

Re: [PATCH 3/5] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping.

On 2015/7/15 11:33, Tang Chen wrote: > Hi Mika, > > On 07/07/2015 07:14 PM, Mika Penttilä wrote: >> I think you forgot to reserve CPU 0 for BSP in cpuid mask. > > Sorry for the late reply. > > I'm not familiar with BSP. Do you mean in get_cpuid(), > I should reserve 0 for physical cpu0 in BSP

Re: [RFC v4 17/25] powerpc, fbdev: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram_write_byte()

On Tue, 14 Jul 2015, Benjamin Herrenschmidt wrote: > On Tue, 2015-07-14 at 17:58 +1000, Finn Thain wrote: > > Make use of arch_nvram_ops in device drivers so that the nvram_* > > function exports can be removed. > > > > Since they are no longer global symbols, rename the PPC32 nvram_* > >

Re: [PATCH 17/36] PCI: Add support for more than two alt_size under same bridge

On 2015/7/15 13:08, Yinghai Lu wrote: > On Tue, Jul 14, 2015 at 8:07 PM, Yijing Wang wrote: >> On 2015/7/7 7:39, Yinghai Lu wrote: >>> Need to increase size to make sure it could fit all alt entries. >>> >>> So at last, we use 8M/17M as parent bridge alt_align/alt_size. >> >> Tested-by: Yijing

Re: Re: [PATCH 1/3] panic: Disable crash_kexec_post_notifiers if kdump is not available

On 2015/07/15 3:23, Vivek Goyal wrote: > On Tue, Jul 14, 2015 at 01:01:12PM -0500, Eric W. Biederman wrote: >> Vivek Goyal writes: >> >>> On Tue, Jul 14, 2015 at 05:29:53PM +, dwal...@fifo99.com wrote: >>> >>> [..] If a machine is failing, there are high chance it can't deliver you

Re: [PATCH 0/2] CLK: TI: add dpll_clksel_mac_clk node

* Tero Kristo [150714 06:30]: > On 07/14/2015 02:06 PM, Tony Lindgren wrote: > >* Keerthy [150625 06:48]: > >> > >>On Thursday 18 June 2015 02:36 PM, Mugunthan V N wrote: > >>>On Thursday 18 June 2015 01:31 PM, Keerthy wrote: > The series adds the missing clock node needed for cpsw. > >

Re: [PATCH 17/36] PCI: Add support for more than two alt_size under same bridge

On Tue, Jul 14, 2015 at 8:07 PM, Yijing Wang wrote: > On 2015/7/7 7:39, Yinghai Lu wrote: >> Need to increase size to make sure it could fit all alt entries. >> >> So at last, we use 8M/17M as parent bridge alt_align/alt_size. > > Tested-by: Yijing Wang Thanks for testing. > > Hi Yinghai, does

Re: [PATCH v2 05/23] staging: rtl8192e: Remove unused fields from rtllib_stats

On Wed, Jul 15, 2015 at 10:27:20AM +0530, Sudip Mukherjee wrote: > On Tue, Jul 14, 2015 at 10:04:08PM +0200, Mateusz Kulikowski wrote: > > None of them are used in the driver. > > > > Signed-off-by: Mateusz Kulikowski > > --- > > drivers/staging/rtl8192e/rtllib.h | 19 --- > > 1

Re: [PATCH v2 05/23] staging: rtl8192e: Remove unused fields from rtllib_stats

On Tue, Jul 14, 2015 at 10:04:08PM +0200, Mateusz Kulikowski wrote: > None of them are used in the driver. > > Signed-off-by: Mateusz Kulikowski > --- > drivers/staging/rtl8192e/rtllib.h | 19 --- > 1 file changed, 19 deletions(-) > > diff --git

Re: [PATCH RFC] vfs: add a O_NOMTIME flag

On Tue, 14 Jul 2015 15:13:00 +0200 Pavel Machek wrote: > Hi! > > > BTW When you "swap" to a file the mtime doesn't get updated. No one seems > > to > > complain about that. I guess it is a rather narrow use-case though. > > Actually yes, I'd like to complain. > > It was not swap, it was

[PATCH] MAINTAINERS: Update LSILOGIC MPT FUSION DRIVERS (FC/SAS/SPI) maintainers list

Updating maintainers list for the entry LSILOGIC MPT FUSION DRIVERS in MAINTAINERS file Signed-off-by: Sreekanth Reddy --- MAINTAINERS | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 2d3d55c..c3cd5c9 100644 --- a/MAINTAINERS +++

[PATCH v3] [SCSI] mpt2sas, mpt3sas: Abort initialization if no memory I/O resources detected

Driver crashes if the BIOS do not set up at least one memory I/O resource. This failure can happen if the device is too slow to respond during POST and is missed by the BIOS, but Linux then detects the device later in the boot process. Changes in v3: Rearranged the code to remove the code

Re: [PATCH 4/5] staging: sm7xxfb: define new macros

On Tue, Jul 14, 2015 at 08:05:08PM -0700, Greg Kroah-Hartman wrote: > On Tue, Jul 07, 2015 at 01:44:36PM +0530, Sudip Mukherjee wrote: > > +#define mmio_addr 0x00c0 > > +#define seqw17 > > Odd, empty macros are not good, because: > > > -#ifdef __BIG_ENDIAN > > if

[PATCH v2 0/4] Add Broadcom North Star 2 support

This patch series adds Broadcom North Star 2 (NS2) SoC support. NS2 is an ARMv8 based SoC and under the Broadcom iProc family. Sorry for tying this with the Broadcom iProc PCIe driver fixes for ARM64. I have to tie them together because iProc PCIe support is enabled by default when ARCH_BCM_IPROC

[PATCH v2 2/4] PCI: iproc: Fix ARM64 dependency in Kconfig

Allow Broadcom iProc PCIe core driver to be compiled for ARM64 Signed-off-by: Ray Jui Reviewed-by: Vikram Prakash Reviewed-by: Scott Branden --- drivers/pci/host/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/host/Kconfig b/drivers/pci/host/Kconfig

[PATCH v2 3/4] arm64: Add Broadcom iProc family support

This patch adds support to Broadcom's iProc family of arm64 based SoCs in the arm64 Kconfig and defconfig files Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- arch/arm64/Kconfig |5 + arch/arm64/configs/defconfig |2 ++ 2 files changed, 7 insertions(+) diff --git

[PATCH v2 1/4] PCI: iproc: enable arm64 support for iProc PCIe

This patch enables arm64 support to the iProc PCIe driver Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- drivers/pci/host/pcie-iproc.c | 15 --- drivers/pci/host/pcie-iproc.h |8 ++-- 2 files changed, 10 insertions(+), 13 deletions(-) diff --git

[PATCH v2 4/4] arm64: dts: Add Broadcom North Star 2 support

Add Broadcom NS2 device tree binding document. Also add initial device tree dtsi for Broadcom North Star 2 (NS2) SoC and board support for NS2 SVK board Signed-off-by: Jon Mason Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- Documentation/devicetree/bindings/arm/bcm/ns2.txt |9 ++

Re: compile failure linux 3.10 with gcc 4.9.3 for mips

Reinoud Koornstra gmail.com> writes: > > Hi Everyone, > > Did anybody enounter the following compiler problem with linux 3.10.81? > gcc version is 4.9.3 for mips. > > arch/mips/kernel/r4k_fpu.S: Assembler messages: > arch/mips/kernel/r4k_fpu.S:59: Error: opcode not supported on this >

linux-next: Tree for Jul 15

Hi all, Changes since 20150714: New tree: ftrace-fixes The drm-intel tree gained another conflict against the drm-intel-fixes tree. The drm-misc tree lost its build failure. The tip tree gained a build failure so I applied a fix patch. Non-merge commits (relative to Linus' tree): 1971 1793

Re: [Patch V5 00/16] xen: support pv-domains larger than 512GB

On 07/10/2015 03:39 PM, Konrad Rzeszutek Wilk wrote: On Fri, Jul 10, 2015 at 02:47:45PM +0200, Juergen Gross wrote: Support 64 bit pv-domains with more than 512GB of memory. Following test have been done: - 64 bit dom0 on 8GB machine - 64 bit dom0 on 1TB machine (resolving p2m/E820-map

[PATCH v5 05/19] staging: sm750fb: remove space between function name and parenthesis

Fixes checkpatch.pl warning: WARNING: space prohibited between function name and open parenthesis '(' Signed-off-by: Juston Li --- drivers/staging/sm750fb/sm750_accel.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/sm750fb/sm750_accel.c

[PATCH v5 01/19] staging: sm750fb: use tabs for indentation

Replace spaces with tabs for indentation to fix the checkpatch.pl error ERROR: code indent should use tabs where possible WARNING: please, no spaces at the start of a line Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_display.c | 100

[PATCH v5 04/19] staging: sm750fb: add space before open parenthesis

Fixes checkpatch.pl error: ERROR: space required before the open parenthesis '(' Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_display.c | 20 ++-- drivers/staging/sm750fb/ddk750_dvi.c | 2 +- drivers/staging/sm750fb/ddk750_help.c| 2 +-

[PATCH v5 06/19] staging: sm750fb: add space before open brace

Fixes checkpatch.pl error: ERROR: space required before the open brace '{' Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_display.c | 14 +++--- drivers/staging/sm750fb/ddk750_mode.c| 8 drivers/staging/sm750fb/ddk750_power.c | 4 ++--

[PATCH v5 07/19] staging: sm750fb: add space after close brace

Fixes checkpatch.pl error: ERROR: space required after that close brace '}' Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_display.c | 2 +- drivers/staging/sm750fb/ddk750_mode.c| 2 +- drivers/staging/sm750fb/ddk750_power.c | 2 +- drivers/staging/sm750fb/sm750.h |

[PATCH v5 09/19] staging: sm750fb: add space after struct definition

Fixes checkpatch.pl warning: WARNING: missing space after struct definition Signed-off-by: Juston Li --- drivers/staging/sm750fb/sm750.h| 12 ++-- drivers/staging/sm750fb/sm750_hw.h | 6 +++--- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git

[PATCH v5 02/19] staging: sm750fb: remove spacing after open parenthesis

Fixes checkpatch.pl warning: ERROR: space prohibited after that open parenthesis '(' Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_chip.c | 6 +++--- drivers/staging/sm750fb/ddk750_mode.c | 2 +- drivers/staging/sm750fb/ddk750_power.c | 8 3 files changed, 8

[PATCH v5 08/19] staging: sm750fb: add space after enum definition

Fixes checkpatch.pl warning: WARNING: missing space after enum definition Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_display.h | 2 +- drivers/staging/sm750fb/sm750_hw.h | 8 2 files changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH v5 10/19] staging: sm750fb: add space after return type

Fixes checkpatch.pl warning: WARNING: missing space after return type Signed-off-by: Juston Li --- drivers/staging/sm750fb/sm750.h | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/sm750fb/sm750.h b/drivers/staging/sm750fb/sm750.h index

[PATCH v5 12/19] staging: sm750fb: add spaces around operators

Fixes checkpath.pl error: ERROR: spaces required around that operator Note running checkpatch.pl with '--strict' catches more of these errors along with cases where spacing is optional but preferred. Take care of these in a future patch. Signed-off-by: Juston Li ---

[PATCH v5 11/19] staging: sm750fb: consistent spacing around operators

Fixes checkpatch.pl error: ERROR: need consistent spacing around operator Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_chip.c| 4 ++-- drivers/staging/sm750fb/ddk750_display.h | 4 ++-- drivers/staging/sm750fb/sm750.h | 2 +- 3 files changed, 5 insertions(+), 5

[PATCH v5 15/19] staging: sm750fb: remove unnecessary whitespace

Fixes checkpatch.pl warning: WARNING: unnecessary whitespace before a quoted newline Signed-off-by: Juston Li --- drivers/staging/sm750fb/sm750.c| 2 +- drivers/staging/sm750fb/sm750_hw.c | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v5 13/19] staging: sm750fb: add space after semicolon

Fixes checkpatch.pl error: ERROR: space required after that ';' Signed-off-by: Juston Li --- drivers/staging/sm750fb/sm750.h| 2 +- drivers/staging/sm750fb/sm750_cursor.c | 12 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/staging/sm750fb/sm750.h

[PATCH v5 17/19] staging: sm750fb: move while to follow do close brace

Fixes checkpatch.pl error: ERROR: while should follow close brace '}' Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_display.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/staging/sm750fb/ddk750_display.c

[PATCH v5 16/19] staging: sm750fb: fix brace placement

Fix brace placement errors caught by checkpatch.pl ERROR: that open brace { should be on the previous line Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_chip.h| 12 +++ drivers/staging/sm750fb/ddk750_display.c | 56 ++--

[PATCH v5 18/19] staging: sm750fb: remove unnecessary braces

Fixes checkpatch.pl warning: WARNING: braces {} are not necessary for single statement blocks Signed-off-by: Juston Li --- drivers/staging/sm750fb/sm750_accel.c | 9 +++-- drivers/staging/sm750fb/sm750_hw.c| 6 ++ 2 files changed, 5 insertions(+), 10 deletions(-) diff --git

[PATCH v5 03/19] staging: sm750fb: remove space before close parenthesis

Fixes checkpatch.pl error: ERROR: space prohibited before that close parenthesis ')' Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_chip.c | 2 +- drivers/staging/sm750fb/ddk750_mode.c | 2 +- drivers/staging/sm750fb/sm750_accel.c | 2 +- 3 files changed, 3 insertions(+), 3

[PATCH v5 14/19] staging: sm750fb: remove trailing whitespace

Fixes checkpatch.pl error: ERROR: trailing whitespace Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_dvi.c | 2 +- drivers/staging/sm750fb/sm750_accel.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/sm750fb/ddk750_dvi.c

[PATCH v5 19/19] staging: sm750fb: add missing blank line after declarations

Fixes checkpatch.pl WARNING: Missing a blank line after declarations Signed-off-by: Juston Li --- drivers/staging/sm750fb/ddk750_chip.c| 1 + drivers/staging/sm750fb/ddk750_display.c | 2 ++ drivers/staging/sm750fb/ddk750_dvi.c | 1 + drivers/staging/sm750fb/ddk750_mode.c| 3 +++

Re: [patch] checkpatch: Fixes: tag lines are allowed to be long

On Tue, 2015-07-14 at 14:07 +0300, Dan Carpenter wrote: > A lot of the Fixes: tags go over the 75 character limit and that's ok. > > Fixes: 2a076f40d8c9 ('checkpatch, SubmittingPatches: suggest line wrapping > commit messages at 75 columns') > Signed-off-by: Dan Carpenter > --- > The other

[PATCH v5 00/19] staging: sm750fb: checkpatch.pl fixes

This patch set includes 19 patches fixing indentation, spacing, brace placement and missing blank lines from checkpatch.pl warnings/errors in staging/sm750fb. Regards Juston - Changes since v4: * Rebase to current staging-testing Changes since v3: * Fix comment placement 16/19 *

Re: [PATCH] rtc/rtc-opal: Enable alarms only when opal supports tpo

Vaibhav Jain writes: > rtc-opal driver provides support for rtc alarms via > timed-power-on(tpo). However some Power platforms like BML use a fake > rtc clock and don't support tpo. Such platforms are indicated by the > missing 'has-tpo' property in the device tree. > > Current implementation

Re: [PATCH 3/3] zsmalloc: do not take class lock in zs_pages_to_compact()

On (07/11/15 18:45), Sergey Senozhatsky wrote: [..] > We re-do this calculations during compaction on a per class basis > anyway. > > zs_unregister_shrinker() will not return until we have an active > shrinker, so classes won't unexpectedly disappear while > zs_pages_to_compact(), invoked by

Re: [PATCH v2] PM / Sleep: Use workqueue for user space wakeup sources garbage collector

On 2015-07-03 오후 2:03, SungEun Kim(cleaneye@lge.com) wrote: > On 2015-07-03 오전 9:15, Rafael J. Wysocki wrote: >> On Wednesday, July 01, 2015 05:28:48 PM SungEun Kim wrote: >>> From: "SungEun Kim" >>> >>> The synchronous synchronize_rcu in wakeup_source_remove makes user >> process >>> which

Re: [PATCH 3/5] x86, acpi, cpu-hotplug: Introduce apicid_to_cpuid[] array to store persistent cpuid <-> apicid mapping.

Hi Mika, On 07/07/2015 07:14 PM, Mika Penttilä wrote: I think you forgot to reserve CPU 0 for BSP in cpuid mask. Sorry for the late reply. I'm not familiar with BSP. Do you mean in get_cpuid(), I should reserve 0 for physical cpu0 in BSP ? Would you please share more detail ? Thanks.

Re: [PATCH v3 00/11] USB: OTG/DRD Core functionality

On Tue, Jul 14, 2015 at 11:18:30AM -0700, Andrew Bresticker wrote: > Hi Peter, > > On Mon, Jul 13, 2015 at 5:59 PM, Peter Chen wrote: > > On Mon, Jul 13, 2015 at 12:14:43PM -0700, Andrew Bresticker wrote: > >> Hi Roger, > >> > >> On Wed, Jul 8, 2015 at 3:19 AM, Roger Quadros wrote: > >> > Usage

[PATCH 1/2] ASoC: rockchip: Add machine driver for max98090 codec

From: zhengxing The driver is used for rockchip board using a max98090. Reviewed-by: Dylan Reid Signed-off-by: zhengxing --- sound/soc/rockchip/Kconfig | 10 ++ sound/soc/rockchip/Makefile|4 + sound/soc/rockchip/rockchip_max98090.c | 246

[RESEND PATCH 1/1] staging:vt6655: remove checks around dev_kfree_skb

dev_kfree_skb checks for NULL pointer itself, Thus no need of explicit NULL check. Signed-off-by: Maninder Singh --- drivers/staging/vt6655/device_main.c |8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/staging/vt6655/device_main.c

[PATCH 2/2] ASoC: rockchip: Add machine driver for rt5645/rt5650 codec

From: zhengxing The driver is used for rockchip board using a rt5645/rt5650. Reviewed-by: Dylan Reid Signed-off-by: zhengxing --- sound/soc/rockchip/Kconfig |9 ++ sound/soc/rockchip/Makefile |2 + sound/soc/rockchip/rockchip_rt5645.c | 235

[PATCH 0/2] Add codec machine driver for rockchip platform

From: zhengxing Hi, The simple-card is not common at present, soc maybe need own machine driver for jack detection. Add drivers for two families of rockchip-bases chromebooks. These machine drives don't use simplecard because we need custom jack detection plumbing. - use ts3a227e for ext

Re: [RFC PATCH v2 1/4] y2038: add 64bit time_t support in timeval for 32bit architecture

Hi, Arnd On 07/09/2015 06:26 PM, Arnd Bergmann wrote: On Thursday 09 July 2015 17:02:47 Bamvor Zhang Jian wrote: On 07/09/2015 04:09 AM, John Stultz wrote: On Mon, Jun 29, 2015 at 7:23 AM, Bamvor Zhang Jian wrote: +int get_timeval64(struct timeval64 *tv, + const struct

Re: [PATCH 17/36] PCI: Add support for more than two alt_size under same bridge

On 2015/7/7 7:39, Yinghai Lu wrote: > Need to increase size to make sure it could fit all alt entries. > > In the patch, we first select one big size, and then keep reducing > the size and retrying to get the minimum value for alt_size. > > Example: > two bridges: one have 8M/8M, and 1M/1M

Re: [PATCH][RESEND] rts5208:Fix checkpatch warnings

On Wed, Jul 01, 2015 at 12:27:38PM +0530, Ravi Teja Darbha wrote: > else is not generally useful after a break or return, hence removed. > > Signed-off-by: Ravi Teja Darbha > --- > drivers/staging/rts5208/xd.c | 10 -- > 1 file changed, 4 insertions(+), 6 deletions(-) Why resend? What

Re: [PATCH 04/13] pinctrl: tegra: Only set the gpio range if needed

On Tue, Jul 14, 2015 at 5:34 PM, Tomeu Vizoso wrote: > On 13 July 2015 at 22:14, Linus Walleij wrote: >> On Wed, Jun 17, 2015 at 3:42 PM, Tomeu Vizoso >> wrote: >> >>> If the gpio DT node has the gpio-ranges property, the range will be >>> added by the gpio core and doesn't need to be added by

Re: Subject: [v3.19 Regression] x86, irq, acpi: Get rid of special handling of GSI for ACPI SCI

On 2015/7/15 1:22, Joseph Salisbury wrote: > On 07/13/2015 10:42 PM, Jiang Liu wrote: >> On 2015/7/14 3:36, Joseph Salisbury wrote: >>> Hello Jiang, >>> >>> A kernel bug report was opened against Ubuntu [0]. It was found that >>> reverting the following commit resolves this bug: >>> >>> commit

Re: Re: [PATCH 3/3] kexec: Change the timing of callbacks related to "crash_kexec_post_notifiers" boot option

On 2015/07/14 23:42, Vivek Goyal wrote: > On Fri, Jul 10, 2015 at 08:33:31PM +0900, Hidehiro Kawai wrote: >> This patch fixes problems reported by Daniel Walker >> (https://lkml.org/lkml/2015/6/24/44), and also replaces the bug fix >> commits 5375b70 and f45d85f. >> >> If

Re: [RFC PATCH v2] memory-barriers: remove smp_mb__after_unlock_lock()

On Tue, 2015-07-14 at 08:31 +1000, Benjamin Herrenschmidt wrote: > On Mon, 2015-07-13 at 13:15 +0100, Will Deacon wrote: > > smp_mb__after_unlock_lock is used to promote an UNLOCK + LOCK sequence > > into a full memory barrier. > > > > However: > > > > - This ordering guarantee is already

Re: [PATCH 3/5] staging: sm7xxfb: use kernel commandline

On Tue, Jul 07, 2015 at 01:44:35PM +0530, Sudip Mukherjee wrote: > We were only using the kernel commandline to set the mode if this driver > is builtin, but when it is built as a module we were not having any way > to set the mode. Start using commandline even if it is built as a > module. > >

Re: [PATCH 4/5] staging: sm7xxfb: define new macros

On Tue, Jul 07, 2015 at 01:44:36PM +0530, Sudip Mukherjee wrote: > Define and use some new macros to work with different situations > based on little-endian and big-endian. > > Signed-off-by: Sudip Mukherjee > --- > drivers/staging/sm7xxfb/sm7xx.h | 19 >

[PATCH v3 1/8] powerpc/perf/hv-24x7: Whitespace - fix parameter alignment

Fix parameter alignment to be consistent with coding style. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/perf/hv-24x7.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/arch/powerpc/perf/hv-24x7.c b/arch/powerpc/perf/hv-24x7.c index

[PATCH v3 5/8] perf: Split perf_event_read_value()

Move the part of perf_event_read_value() that computes the event counts and event times into a new function, perf_event_compute(). This would allow us to call perf_event_compute() independently. Signed-off-by: Sukadev Bhattiprolu Changelog[v3] Rather than move perf_event_read() into

[PATCH v3 6/8] perf: Rename perf_event_read_{one,group}, perf_read_hw

From: "Peter Zijlstra (Intel)" In order to free up the perf_event_read_group() name: s/perf_event_read_\(one\|group\)/perf_read_\1/g s/perf_read_hw/__perf_read/g Signed-off-by: Peter Zijlstra (Intel) --- kernel/events/core.c | 14 +++--- 1 file changed, 7 insertions(+), 7

[PATCH v3 8/8] powerpc/perf/hv-24x7: Use PMU_TXN_READ interface

The 24x7 counters in Powerpc allow monitoring a large number of counters simultaneously. They also allow reading several counters in a single HCALL so we can get a more consistent snapshot of the system. Use the PMU's transaction interface to monitor and read several event counters at once. The

[PATCH v3 0/8] Implement group-read of events using txn interface

Unlike normal hardware PMCs, the 24x7 counters in Power8 are stored in memory and accessed via a hypervisor call(HCALL). A major aspect of the HCALL is that it allows retireving _several_ counters at once (unlike regular PMCs, which are read one at a time). By reading several counters at once, we

[PATCH v3 2/8] powerpc/perf/hv-24x7: Simplify extracting counter from result buffer

Simplify code that extracts a 24x7 counter from the HCALL's result buffer. Suggested-by: Joe Perches Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/perf/hv-24x7.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/powerpc/perf/hv-24x7.c

[PATCH v3 3/8] perf: Add a flags parameter to pmu txn interfaces

Currently, the PMU interface allows reading only one counter at a time. But some PMUs like the 24x7 counters in Power, support reading several counters at once. To leveage this functionality, extend the transaction interface to support a "transaction type". The first type, PERF_PMU_TXN_ADD,

[PATCH v3 7/8] perf: Define PMU_TXN_READ interface

Define a new PERF_PMU_TXN_READ interface to read a group of counters at once. Note that we use this interface with all PMUs. PMUs that implement this interface use the ->read() operation to _queue_ the counters to be read and use ->commit_txn() to actually read all the queued counters at once.

[PATCH v3 4/8] perf: Split perf_event_read() and perf_event_count()

perf_event_read() does two things: - call the PMU to read/update the counter value, and - compute the total count of the event and its children Not all callers need both. perf_event_reset() for instance needs the first piece but doesn't need the second. Similarly, when we

Re: [PATCH 2/2] staging: speakup: else is not useful after a return

On Thu, Jun 25, 2015 at 02:56:52PM +0200, Luis de Bethencourt wrote: > Correct a checkpatch.pl warning regarding > WARNING: else is not generally useful after a break or return > drivers/staging/speakup/keyhelp.c:185: > > Changing the order of the if blocks, but not the logic, to avoid this >

Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb

On 14.07.2015 22:41, Sergey Senozhatsky wrote: > > sometimes `xset dpms force off' just turns off the panel for a second, > sometimes -- until I generate a `wakeup' event (key press, etc.) FWIW, the former case is because releasing the enter key generates an input event, which changes the DPMS

Re: [RFC 2/3] arm64: refactor save_stack_trace()

On Wed, 15 Jul 2015 09:20:42 +0900 AKASHI Takahiro wrote: > On 07/14/2015 10:31 PM, Steven Rostedt wrote: > > On Tue, 14 Jul 2015 21:47:10 +0900 > > Jungseok Lee wrote: > > > >> Is the below example an unexpected result? > >> Entry 17 and 18 are ftrace_call and ftrace_ops_no_ops, respectively.

Re: [PATCH] Staging:rtl8192u: fixed coding style issues

On Wed, Jun 24, 2015 at 09:05:04PM +0300, Aldo Iljazi wrote: > Fixed the following coding style issues: > r819xU_firmware.c:72: ERROR: space required after that ',' (ctx:VxO) > r819xU_firmware.c:72: ERROR: space required before that '&' (ctx:OxV) > r819xU_firmware.c:72: ERROR: space required after

[PATCH] ACPI: Fix indent for variable declaration

In function acpi_ns_one_complete_parse, the variable declaration aml_length is not correctly indented. Signed-off-by: Zhouyi Zhou --- drivers/acpi/acpica/nsparse.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/acpica/nsparse.c b/drivers/acpi/acpica/nsparse.c

Re: [PATCH v2] staging: rtl8192u: bool tests don't need comparisons

On Tue, Jun 23, 2015 at 03:12:06PM +0200, Luis de Bethencourt wrote: > Remove explicit true/false comparations to bool variables. > > Signed-off-by: Luis de Bethencourt > --- > drivers/staging/rtl8192u/r8192U_core.c | 13 - > drivers/staging/rtl8192u/r8192U_dm.c | 21

Re: [PATCH] drivers: staging: rtl8192u: Fix "space required before the open parenthesis '('" errors

On Sat, Jun 20, 2015 at 03:56:08PM -0500, Greg Donald wrote: > Fix checkpatch.pl "space required before the open parenthesis '('" errors > > Signed-off-by: Greg Donald > --- > .../staging/rtl8192u/ieee80211/rtl819x_HTProc.c| 97 > ++ > 1 file changed, 44 insertions(+),

Re: [PATCHv2] regulator: s2mps11: Added shutdown function to poweroff

hi Krzysztof, On 15 July 2015 at 06:33, Krzysztof Kozlowski wrote: > On 15.07.2015 00:41, Anand Moon wrote: >> Added .shutdown function to s2mps11 to help poweroff the board successfully. > > Which board does not poweroff? The PMIC is used on multiple boards, did > you observed this on all of

Re: [PATCH] ALSA: hda/realtek: Enable HP amp and mute LED on HP Folio 9480m

Takashi Iwai writes: > Thanks for the patch. But this looks suboptimal, unfortunately, since > it keeps the amp always on, and more badly, it would block the power > save of the widget root node. Thanks very much for your feedback; I wasn't sure precisely how this code worked and tried to make

Re: [PATCH 2/7] staging: clocking-wizard: Include clk.h

On Fri, Jul 10, 2015 at 04:03:24PM -0700, Stephen Boyd wrote: > This clock provider uses the consumer API, so include clk.h > explicitly. > > Cc: Sören Brinkmann > Cc: Greg Kroah-Hartman > Signed-off-by: Stephen Boyd > --- > > Please ack so this can go through the clk-tree. > >

[PATCH 1/1] suspend: make sync() on suspend-to-RAM optional

From: Len Brown The Linux kernel suspend path has traditionally invoked sys_sync(). But sys_sync() can be expensive, and some systems do not want to pay the cost of sys_sync() on every suspend. So make sys_sync on suspend optional. Create sysfs attribute /sys/power/pm_suspend_do_sync. When

[PATCH v4 0/1] suspend: make sync() on suspend-to-RAM optional

Based on discussion resulting from... https://lkml.org/lkml/2015/5/8/82 [PATCH 1/1] suspend: delete sys_sync(), this patch makes sys_sync() optional, rather than deleting it entirely. This is an update to the original patch for this issue from Jan, 2014: patch https://lkml.org/lkml/2014/1/23/73

Re: make -jN (n>1) ineffective in 4.2.0-rc on AMD Phenom

GNU Make 4.1 has a problem that causes it to be unable to use the desired level of parallelism. Two people have reported that reverting a commit which changes from fork to vfork "fixes" it. (i'm one of them, unfortunately posting as anonymous in the tracker). Hoewver, if you are also seeing the

RE: [PATCH] rtc/ds3232: fix ds3232 get a WARNING trace in resume function

Thanks Belloni. :) Regards, -Dongsheng > -Original Message- > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com] > Sent: Wednesday, July 15, 2015 6:51 AM > To: Wang Dongsheng-B40534 > Cc: a.zu...@towertech.it; rtc-li...@googlegroups.com; linux- > ker...@vger.kernel.org

[rfc] mm, thp: allow khugepaged to periodically compact memory synchronously

We have seen a large benefit in the amount of hugepages that can be allocated at fault and by khugepaged when memory is periodically compacted in the background. We trigger synchronous memory compaction over all memory every 15 minutes to keep fragmentation low and to offset the lightweight

[PATCH v2 1/6] locking/pvqspinlock: Unconditional PV kick with _Q_SLOW_VAL

The smp_store_release() is not a full barrier. In order to avoid missed wakeup, we may need to add memory barrier around locked and cpu state variables adding to complexity. As the chance of spurious wakeup is very low, it is easier and safer to just do an unconditional kick at unlock time.

[PATCH 0/6 v2] locking/qspinlock: Enhance pvqspinlock performance

v1->v2: - Take out the queued unfair lock patches - Add a patch to simplify the PV unlock code - Move pending bit and statistics collection patches to the front - Keep vCPU kicking in pv_kick_node(), but defer it to unlock time when appropriate. - Change the wait-early patch to use

[PATCH v2 3/6] locking/pvqspinlock: Collect slowpath lock statistics

This patch enables the accumulation of kicking and waiting related PV qspinlock statistics when the new QUEUED_LOCK_STAT configuration option is selected. It also enables the collection of kicking and wakeup latencies which have a heavy dependency on the CPUs being used. The measured latencies

[PATCH v2 4/6] locking/pvqspinlock: Allow vCPUs kick-ahead

Frequent CPU halting (vmexit) and CPU kicking (vmenter) lengthens critical section and block forward progress. This patch implements a kick-ahead mechanism where the unlocker will kick the queue head vCPUs as well as up to four additional vCPUs next to the queue head if they were halted. The

[PATCH v2 2/6] locking/pvqspinlock: Add pending bit support

Like the native qspinlock, using the pending bit when it is lightly loaded to acquire the lock is faster than going through the PV queuing process which is even slower than the native queuing process. It also avoids loading two additional cachelines (the MCS and PV nodes). This patch adds the

[PATCH v2 6/6] locking/pvqspinlock: Queue node adaptive spinning

In an overcommitted guest where some vCPUs have to be halted to make forward progress in other areas, it is highly likely that a vCPU later in the spinlock queue will be spinning while the ones earlier in the queue would have been halted. The spinning in the later vCPUs is then just a waste of

Re: [PATCH 05/10] Staging: fbtft: Set bus specific ops using separate functions

On Tue, Jun 30, 2015 at 08:43:12AM +0200, Fabio Falzoi wrote: > Use two separate functions for spi and platform bus > (flexfb_set_spi_bus_func and flexfb_set_platform_bus_func, > respectively) to set the appropriate write operations. > > This patch corrects the following checkpatch errors: >

[PATCH v2 5/6] locking/pvqspinlock: Opportunistically defer kicking to unlock time

Performing CPU kicking at lock time can be a bit faster if there is no kick-ahead. On the other hand, deferring it to unlock time is preferrable when kick-ahead can be performed or when the VM guest is having too few vCPUs that a vCPU may be kicked twice before getting the lock. This patch

Re: [PATCH 06/10] Staging: fbtft: Use a helper function to set set_addr_win op

On Tue, Jun 30, 2015 at 08:43:13AM +0200, Fabio Falzoi wrote: > Use a helper function to choose which set_addr_win implementation to > use, based on the value of the setaddrwin module parameter. > > Signed-off-by: Fabio Falzoi > --- > drivers/staging/fbtft/flexfb.c | 47 >

Re: [PATCH 03/10] Staging: fbtft: Use a struct to describe each LCD controller

On Tue, Jun 30, 2015 at 08:43:10AM +0200, Fabio Falzoi wrote: > Use a struct flexfb_lcd_controller to holds chip properties, instead of > relying on a long 'if - else if' chain. > This allows to: > - use a simple linear search to verify if a certain LCD controller > model is supported or not. > -

Re: [PATCH 04/10] Staging: fbtft: Use a helper function to set write_register op

On Tue, Jun 30, 2015 at 08:43:11AM +0200, Fabio Falzoi wrote: > Use a helper function to set the correct write_register function, based > on the width of the registers. > > Signed-off-by: Fabio Falzoi > --- > drivers/staging/fbtft/flexfb.c | 36 ++-- > 1 file

Re: [PATCH 1/2] Define find_symbol_in_section_t as function type to simplify the code

On 07/15/15 at 07:22am, Rusty Russell wrote: > Minfei Huang writes: > > From: Minfei Huang > > > > It is not elegance, if we use function directly as the argument, like > > following: > > > > bool each_symbol_section(bool (*fn)(const struct symsearch *arr, > >

  1   2   3   4   5   6   7   8   9   10   >