Re: [PATCH V2] AHCI: Workaround for ThunderX Errata#22536

Hello, Tirumalesh. On Sun, Feb 14, 2016 at 07:36:18PM -0800, Tirumalesh Chalamarla wrote: > There is no need for special Driver, AHCI is sufficient for ThunderX, the > file only contains this interrupt handler, > is it preferable if this interrupt handler in libahci.c with others, instead > of

Re: [PATCH] regulator: vexpress: rename vexpress regulator implementation

On 15/02/16 18:10, Mark Brown wrote: On Wed, Feb 10, 2016 at 06:49:54PM +, Sudeep Holla wrote: On 29/01/16 17:37, Sudeep Holla wrote: The vexpress regulator implementation is currently just called vexpress. This is a problem because it clashes with another module with the same name in

Re: [RFC][PATCH 00/12] various perf fixes

On Mon, Feb 15, 2016 at 7:01 PM, Peter Zijlstra wrote: > On Mon, Feb 15, 2016 at 06:45:59PM +0100, Dmitry Vyukov wrote: >> However, you need to add getpid and gettid syscalls to the list of >> enabled syscalls in config (they are required for perf_event_open): >> >>

[PATCH 1/1 v2] MIPS: DTS: cavium-octeon: provide model attribute

Downstream packages like Debian flash-kernel rely on /proc/device-tree/model to determine how to install an updated kernel image. Most dts files provide this property. This patch adds a model attribute Octeon CPUs. v2: Use vendor prefix defined in vendor-prefixes.txt. Separate

Applied "regulator: max77686: Fix MAINTAINER entry to match driver" to the regulator tree

The patch regulator: max77686: Fix MAINTAINER entry to match driver has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Re: [BUG] random kernel crashes after THP rework on s390 (maybe also on PowerPC and ARM)

On Mon, 15 Feb 2016 13:31:59 +0200 "Kirill A. Shutemov" wrote: > On Sat, Feb 13, 2016 at 12:58:31PM +0100, Sebastian Ott wrote: > > > > On Sat, 13 Feb 2016, Kirill A. Shutemov wrote: > > > Could you check if revert of fecffad25458 helps? > > > > I reverted fecffad25458 on

Re: [PATCH 1/1] MIPS: DTS: cavium-octeon: provide model attribute

Hi, On Mon, Feb 15, 2016 at 06:52:20PM +0100, Heinrich Schuchardt wrote: > On 02/15/2016 12:16 PM, Sergei Shtylyov wrote: > > On 2/15/2016 8:26 AM, Heinrich Schuchardt wrote: > >> Downstream packages like Debian flash-kernel rely on > >> /proc/device-tree/model > >> to determine how to install an

Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'

On 15/02/16 18:12, Guenter Roeck wrote: [...] I added some debugging on top of your patch, and get: platform basic-mmio-gpio.1.auto: Device node exists [/smb/motherboard/iofpga@7,/sysreg@0/sys_led@08], of_driver_match_device() failed platform basic-mmio-gpio.1.auto:

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

Sudeep Holla writes: > 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

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

Sudeep Holla writes: > SCPI specification v1.1 adds support for energy sensors. This patch > adds support for the same. > > Cc: Punit Agrawal Reviewed-by: Punit Agrawal > Signed-off-by: Sudeep Holla

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

On Mon, Feb 15, 2016 at 6:05 PM, Guenter Roeck <li...@roeck-us.net> wrote: > Rafael, Hi, Thanks for the report! > I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace > timers with utilization update callbacks' with next-20160215. An example > crash log

[PATCH 1/3] drm/amdgpu: use post-decrement in error handling

We need to use post-decrement to get the pci_map_page undone also for i==0, and to avoid some very unpleasant behaviour if pci_map_page failed already at i==0. Signed-off-by: Rasmus Villemoes --- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 2 +- 1 file changed, 1

[PATCH v1] tty: serial: 8250: Cleanup p->em485 in serial8250_unregister_port

Formally, currently there is no memory leak, but if serial8250_ports[line] is reused with other 8250 driver, then em485 will be already activated and it will cause issues. Fixes: e490c9144cfa ("tty: Add software emulated RS485 support for 8250") Signed-off-by: Matwey V. Kornilov

[PATCH 2/3] drm/nouveau: use post-decrement in error handling

We need to use post-decrement to get the dma_map_page undone also for i==0, and to avoid some very unpleasant behaviour if dma_map_page failed already at i==0. Signed-off-by: Rasmus Villemoes --- drivers/gpu/drm/nouveau/nouveau_bo.c | 2 +- 1 file changed, 1

[PATCH 3/3] drm/radeon: use post-decrement in error handling

We need to use post-decrement to get the pci_map_page undone also for i==0, and to avoid some very unpleasant behaviour if pci_map_page failed already at i==0. Signed-off-by: Rasmus Villemoes --- drivers/gpu/drm/radeon/radeon_ttm.c | 2 +- 1 file changed, 1

[PATCH 0/3] drm: more pre-decrement fixes

A few more cases where one should use post-decrement when unwinding, this time found where the unwinding is done inside the setup loop instead of after an error label. Rasmus Villemoes (3): drm/amdgpu: use post-decrement in error handling drm/nouveau: use post-decrement in error handling

[PATCHv2 2/4] slub: Fix/clean free_debug_processing return paths

Since 19c7ff9ecd89 ("slub: Take node lock during object free checks") check_object has been incorrectly returning success as it follows the out label which just returns the node. Thanks to refactoring, the out and fail paths are now basically the same. Combine the two into one and just use a

[PATCHv2 4/4] slub: Relax CMPXCHG consistency restrictions

When debug options are enabled, cmpxchg on the page is disabled. This is because the page must be locked to ensure there are no false positives when performing consistency checks. Some debug options such as poisoning and red zoning only act on the object itself. There is no need to protect other

[PATCHv2 3/4] slub: Convert SLAB_DEBUG_FREE to SLAB_CONSISTENCY_CHECKS

SLAB_DEBUG_FREE allows expensive consistency checks at free to be turned on or off. Expand its use to be able to turn off all consistency checks. This gives a nice speed up if you only want features such as poisoning or tracing. Credit to Mathias Krause for the original work which inspired this

[PATCHv2 0/4] Improve performance for SLAB_POISON

Hi, This is a follow up to my previous series (http://lkml.kernel.org/g/<1453770913-32287-1-git-send-email-labb...@fedoraproject.org>) This series takes the suggestion of Christoph Lameter and only focuses on optimizing the slow path where the debug processing runs. The two main optimizations in

[PATCHv2 1/4] slub: Drop lock at the end of free_debug_processing

Currently, free_debug_processing has a comment "Keep node_lock to preserve integrity until the object is actually freed". In actuallity, the lock is dropped immediately in __slab_free. Rather than wait until __slab_free and potentially throw off the unlikely marking, just drop the lock in

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

e to 'cpufreq: governor: Replace >> timers with utilization update callbacks' with next-20160215. An example >> crash log and bisect results are attached below. >> >> Please let me know if there is anything I can do to help tracking down >> the problem. > > It looks

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

; timers with utilization update callbacks' with next-20160215. An example >> crash log and bisect results are attached below. >> >> Please let me know if there is anything I can do to help tracking down >> the problem. > > It looks like we've uncovered some nastiness

Re: [PATCH 4.3 041/200] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

On Mon, Feb 15, 2016 at 10:15:08AM -0800, Greg Kroah-Hartman wrote: > On Sun, Feb 14, 2016 at 09:08:50PM -0600, Michael Welling wrote: > > On Sun, Feb 14, 2016 at 03:17:36PM -0800, Greg Kroah-Hartman wrote: > > > On Sun, Feb 14, 2016 at 04:50:47PM -0600, Michael Welling wrote: > > > > On Sun, Feb

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

report! >> >>> I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace >>> timers with utilization update callbacks' with next-20160215. An example >>> crash log and bisect results are attached below. >>> >>> Please let me know

[PATCH] thermal: remove a pointless check

The state in devfreq_cooling_state2power is unsigned so removed the < 0 check. Signed-off-by: Alan Cox --- drivers/thermal/devfreq_cooling.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/thermal/devfreq_cooling.c

Re: [PATCH] xfs: fix format specifier , should be %llx and not %llu

On Sat, Feb 13, 2016 at 08:26:22PM +, Colin King wrote: > From: Colin Ian King > > busyp->bno is printed with a %llu format specifier when the > intention is to print a hexadecimal value. Trivial fix to > use %llx instead. Found with smatch static analysis: > >

[PATCH v5 RESEND 0/8] Staging: rts5208: Fix coding style

This set of patches fixes the coding style issues in rtsx_transport.c. Changes since v4 * Moved a declaration to the beginning of an if branch Changes since v3 * Removed the extraneous SCSI comment in the first patch * Removed the last patch (Staging: rts5208: Add missing dma_mapping_error)

[PATCH v5 RESEND 3/8] Staging: rts5208: rtsx_transport.c: Remove spaces after casts

This patch removes all spaces after casts in rtsx_transport.c, as reported by checkpatch.pl: CHECK: No space is necessary after a cast Signed-off-by: Shaun Ren --- drivers/staging/rts5208/rtsx_transport.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v5 RESEND 1/8] Staging: rts5208: rtsx_transport.c: Cleanup comments

This patch fixes all multiline comments to conform to the coding style, which states that multiline comments should start with "/*" and end with "*/" on a separate line. Also cleans up some comments to make them more clear and/or reflect what the code is doing. Signed-off-by: Shaun Ren

[PATCH v5 RESEND 6/8] Staging: rts5208: rtsx_transport.c: Fix label naming convention

This patch fixes the following naming convention issue in rtsx_transport.c, as reported by checkpatch.pl: CHECK: Avoid CamelCase: Signed-off-by: Shaun Ren --- drivers/staging/rts5208/rtsx_transport.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH v5 RESEND 8/8] Staging: rts5208: rtsx_transport.c: Fix comparisons to NULL

This patch changes all comparsions to NULL with !..., as reported by checkpatch.pl. Signed-off-by: Shaun Ren --- drivers/staging/rts5208/rtsx_transport.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/rts5208/rtsx_transport.c

[PATCH v5 RESEND 7/8] Staging: rts5208: rtsx_transport.c: Remove unnecessary parentheses

This patch removes all unnecessary parentheses found by checkpatch.pl. Signed-off-by: Shaun Ren --- Changes since v3 * Fixed patch conflicts due to commit 9a66d05d82db ("Staging: rts5208: fix check for dma mapping error"), and commit b3232842dbef ("Staging:

Re: [lkp] [workqueue] 82607adcf9: BUG: workqueue lockup - pool cpus=0 flags=0x4 nice=0 stuck for 42s!

Hello, On Sun, Feb 14, 2016 at 09:07:04AM +0800, kernel test robot wrote: > FYI, we noticed the below changes on > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > commit 82607adcf9cdf40fb7b5331269780c8f70ec6e35 ("workqueue: implement lockup > detector") > > > [

[PATCH v5 RESEND 4/8] Staging: rts5208: rtsx_transport.c: Add spaces around -

This patch fixes the following styling issue in rtsx_transport.c as reported by checkpatch.pl: CHECK: spaces preferred around that '-' (ctx:VxV) Signed-off-by: Shaun Ren --- drivers/staging/rts5208/rtsx_transport.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCH v5 RESEND 5/8] Staging: rts5208: rtsx_transport.c: Remove extra newlines

This patch fixes the following issues in rtsx_transport.c as reported by checkpatch.pl: CHECK: Blank lines aren't necessary after an open brace '{' CHECK: Please don't use multiple blank lines Signed-off-by: Shaun Ren --- drivers/staging/rts5208/rtsx_transport.c | 3 --- 1

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

Replace > > timers with utilization update callbacks' with next-20160215. An example > > crash log and bisect results are attached below. > > > > Please let me know if there is anything I can do to help tracking down > > the problem. > > It looks l

[PATCH v5 RESEND 2/8] Staging: rts5208: rtsx_transport.c: Align to open parenthesis

This patch fixes the alignment issue reported by checkpatch.pl: CHECK: Alignment should match open parenthesis Add a unsigned char *sgbuffer in rtsx_stor_access_xfer_buffer to make the following memcpy logic easier to read. Add a struct scatterlist *sg in the use_sg branch of

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

On Mon, Feb 15, 2016 at 07:41:21PM +0100, Rafael J. Wysocki wrote: > Since this is ARM, arch_send_call_function_single_ipi() looks like this: > > void arch_send_call_function_single_ipi(int cpu) > { > smp_cross_call(cpumask_of(cpu), IPI_CALL_FUNC_SINGLE); > } > > so I'm not sure how the

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

gt;> Rafael, >>> >>> Hi, >>> >>> Thanks for the report! >>> >>>> I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace >>>> timers with utilization update callbacks' with next-20160215. An example >>>> c

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

On Thu, Feb 11, 2016 at 05:16:00PM -0800, Andy Lutomirski wrote: > Are you running 32-bit userspace by any chance? Sure, that's a 32-bit kernel testing partition. :) > I'm guessing you're hitting this in __fpu_restore_sig: Yeah, I was looking at that too. > fpu__drop(fpu); > if

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

On Mon, Feb 15, 2016 at 07:54:26PM +0100, Rafael J. Wysocki wrote: > On Mon, Feb 15, 2016 at 7:49 PM, Marc Zyngier wrote: > > Given that OMAP3 is a UP system, there is zero chance that it has > > registered the magic hook that delivers IPIs (its interrupt controller > > is

Re: [PATCH v4 21/23] arm64: hw_breakpoint: Allow EL2 breakpoints if running in HYP

On Mon, Feb 15, 2016 at 05:46:56PM +, Will Deacon wrote: > On Thu, Feb 11, 2016 at 06:40:02PM +, Marc Zyngier wrote: > > With VHE, we place kernel {watch,break}-points at EL2 to get things > > like kgdb and "perf -e mem:..." working. > > > > This requires a bit of repainting in the

Re: [PATCH] gpio/sysfs: Add ID parameter for GPIO lines

On Thu, Dec 17, 2015 at 5:48 PM, Ricardo Ribalda Delgado wrote: > On named GPIOs there is currently no find out their numerical id. > > Because of this, a GPIO pin named like: > /sys/class/gpio/PROG_B > > cannot be unexported by an application different than the one

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

; On Mon, Feb 15, 2016 at 6:05 PM, Guenter Roeck <li...@roeck-us.net> wrote: >>>>> Rafael, >>>> >>>> Hi, >>>> >>>> Thanks for the report! >>>> >>>>> I see crashes in various arm qemu tests due to 'cp

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

On Fri, Feb 12, 2016 at 06:00:10PM +0100, Borislav Petkov wrote: > Something for me to try when I get a chance. Ok, so I wanted to know what happens in detail. Here's some ftracing (debug patch at the end). Now pay attention to this udevadm thing [3.816977] rcu_pree-7 0d..2 4058241us

Re: [PATCH 1/1] MIPS: DTS: cavium-octeon: provide model attribute

On 02/15/2016 07:38 PM, Aaro Koskinen wrote: > Hi, > > On Mon, Feb 15, 2016 at 06:52:20PM +0100, Heinrich Schuchardt wrote: >> On 02/15/2016 12:16 PM, Sergei Shtylyov wrote: >>> On 2/15/2016 8:26 AM, Heinrich Schuchardt wrote: Downstream packages like Debian flash-kernel rely on

Re: [PATCH] irqchip/ts4800: Make ts4800_ic_ops static const

On Sun, Feb 14, 2016 at 09:50:04PM +0800, Axel Lin wrote: > ts4800_ic_ops is only referenced in this driver, so make it static. > In additional, it's never get modified thus also make it const. > > Signed-off-by: Axel Lin Reviewed-by: Damien Riegel

Re: [PART1 RFC 5/9] svm: Add VMEXIT handlers for AVIC

2016-02-12 16:38+0100, Paolo Bonzini: > On 12/02/2016 14:59, Suravee Suthikulpanit wrote: >> +case AVIC_INCMP_IPI_ERR_TARGET_NOT_RUN: >> +kvm_lapic_reg_write(apic, APIC_ICR2, icrh); >> +kvm_lapic_reg_write(apic, APIC_ICR, icrl); > > Wouldn't this cause a double

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

On Mon, Feb 15, 2016 at 07:03:33PM +, Marc Zyngier wrote: > On 15/02/16 18:54, Rafael J. Wysocki wrote: > > That would explain it, thanks. > > > > So it looks like we should always use irq_work_queue() on UP even if > > CONFIG_SMP is set, shouldn't we? > > Something like that, yes.

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

t; >>>> Thanks for the report! > >>>> > >>>>> I see crashes in various arm qemu tests due to 'cpufreq: governor: > >>>>> Replace > >>>>> timers with utilization update callbacks' with next-20160215. An exampl

Re: [PATCH nf] netfilter: nfnetlink: correctly validate length of batch messages

On Tue, Feb 02, 2016 at 01:36:45PM -0500, phil.turnb...@oracle.com wrote: > From: Phil Turnbull > > If nlh->nlmsg_len is zero then an infinite loop is triggered because > 'skb_pull(skb, msglen);' pulls zero bytes. > > The calculation in nlmsg_len() underflows if

Re: [RFC] component: Fix: Unassign components' masters if bringing up master fails

On Thu, 2016-02-11 at 15:05 +0530, Archit Taneja wrote: > component_master_add_with_match can fail if the master's bind op doesn't > go through successfully. In such a scenario, all the components in the > master's match array have their 'master' pointer set to the given master. > These pointers

[PATCH -next] PM / OPP: Fix crash seen if CPU clock has no voltage regulator

omap3 overo boots crash with Unable to handle kernel NULL pointer dereference at virtual address 0030 pgd = c0204000 [0030] *pgd= Internal error: Oops: 17 [#1] SMP ARM ... [] (regulator_set_voltage) from [] (_set_opp_voltage+0x34/0x90) [] (_set_opp_voltage) from []

Re: [PATCH 4.3 041/200] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

On Mon, Feb 15, 2016 at 12:50:41PM -0600, Michael Welling wrote: > On Mon, Feb 15, 2016 at 10:15:08AM -0800, Greg Kroah-Hartman wrote: > > On Sun, Feb 14, 2016 at 09:08:50PM -0600, Michael Welling wrote: > > > On Sun, Feb 14, 2016 at 03:17:36PM -0800, Greg Kroah-Hartman wrote: > > > > On Sun, Feb

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

nor: Replace timers with utilization update callbacks' with next-20160215. An example crash log and bisect results are attached below. Please let me know if there is anything I can do to help tracking down the problem. It looks like we've uncovered some nastiness in the arch ARM code (see b

Re: [PATCH v3 1/5] arm64/perf: Rename Cortex A57 events

On Wed, Feb 03, 2016 at 06:11:56PM +0100, Jan Glauber wrote: > The implemented Cortex A57 events are not A57 specific. > They are recommended by ARM and can be found on other > ARMv8 SOCs like Cavium ThunderX too. Therefore move > these events to the common PMUv3 table. I can't find anything in

Re: [PATCH 1/1] MIPS: DTS: cavium-octeon: provide model attribute

Hi, On Mon, Feb 15, 2016 at 08:21:33PM +0100, Heinrich Schuchardt wrote: > flash-kernel has a database /usr/share/flash-kernel/db/all.db with > entries like: > > Machine: LeMaker Banana Pi > Kernel-Flavors: armmp armmp-lpae > Boot-Script-Path: /boot/boot.scr > DTB-Id: sun7i-a20-bananapi.dtb >

Re: [PATCH] pinctrl: coh901: fix initconst annotation

On Mon, Feb 8, 2016 at 3:29 PM, Arnd Bergmann wrote: > Clang correctly points out that the section attribute for u300_gpio_confdata > is in the wrong place: > > drivers/pinctrl/pinctrl-coh901.c:130:37: error: '__section__' attribute only > applies to functions and global

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

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.5.0-rc4-next-20160215-2-g08cd608 #895 Hardware name: Generic OMAP4 (Flattened Device Tree) task: ee87 ti: ee85e000 task.ti: ee85e000 PC is at regulator_set_voltage+0x10/0x54 LR is at _set_opp_voltage+0x30/0x98 pc : []lr : []psr: 0113 sp

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

On Mon, Feb 15, 2016 at 11:42:27AM -0800, Tony Lindgren wrote: > * Rafael J. Wysocki [160215 11:28]: > > > > Guenter, Tony, > > > > Below is a patch to try, on top of linux-next. > > Fixes the issue on UP for me: > > Tested-by: Tony Lindgren > > >

Re: [PATCH 1/1] MIPS: DTS: cavium-octeon: provide model attribute

On 02/15/2016 08:40 PM, Aaro Koskinen wrote: > Hi, > > On Mon, Feb 15, 2016 at 08:21:33PM +0100, Heinrich Schuchardt wrote: >> flash-kernel has a database /usr/share/flash-kernel/db/all.db with >> entries like: >> >> Machine: LeMaker Banana Pi >> Kernel-Flavors: armmp armmp-lpae >>

Re: [PATCH] Bluetooth: hci_uart: Support firmware download for Marvell

Hi Ganapathi, [auto build test WARNING on bluetooth-next/master] [also build test WARNING on v4.5-rc4 next-20160215] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Amitkumar-Karwar/Bluetooth

Re: [PATCH v3 4/5] arm64/perf: Enable PMCR long cycle counter bit

On Wed, Feb 03, 2016 at 06:11:59PM +0100, Jan Glauber wrote: > With the long cycle counter bit (LC) disabled the cycle counter is not > working on ThunderX SOC (ThunderX only implements Aarch64). > Also, according to documentation LC == 0 is deprecated. > > To keep the code simple the patch does

Injection magnets for your Automation

Dear, Good day. May I have your attention?We are a professional manufacturer of magnet and magnetic products located in Shenzhen China,with two production line the annual capacity exceeds 1,000 tons. Thanks to skilled workers and engineers,some of them having more than 15 years

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

* Guenter Roeck [160215 11:47]: > On Mon, Feb 15, 2016 at 11:42:27AM -0800, Tony Lindgren wrote: > > * Rafael J. Wysocki [160215 11:28]: > > > > > > Guenter, Tony, > > > > > > Below is a patch to try, on top of linux-next. > > > > Fixes the issue on UP

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

* Guenter Roeck <li...@roeck-us.net> [160215 11:41]: > On 02/15/2016 11:01 AM, Tony Lindgren wrote: > > > >https://kernelci.org/boot/all/job/next/kernel/next-20160215/ > > > >The SMP ones seem to fail with some regulator issues? > > > > There is anothe

Re: [PATCH 1/1] MIPS: DTS: cavium-octeon: provide model attribute

Hi, On Mon, Feb 15, 2016 at 08:50:48PM +0100, Heinrich Schuchardt wrote: > On 02/15/2016 08:40 PM, Aaro Koskinen wrote: > > On Mon, Feb 15, 2016 at 08:21:33PM +0100, Heinrich Schuchardt wrote: > >> flash-kernel has a database /usr/share/flash-kernel/db/all.db with > >> entries like: > >> > >>

Re: [PATCH V6] netfilter: h323: avoid potential attack

On Tue, Feb 02, 2016 at 09:40:04PM +0800, Zhouyi Zhou wrote: > diff --git a/net/netfilter/nf_conntrack_h323_main.c > b/net/netfilter/nf_conntrack_h323_main.c > index 9511af0..8d24c4b 100644 > --- a/net/netfilter/nf_conntrack_h323_main.c > +++ b/net/netfilter/nf_conntrack_h323_main.c > @@ -110,6

[PATCH v2] phy: marvell: Fix and unify reg-init behavior

For the Marvell 88E1510, marvell_of_reg_init was called too late, in the config_aneg function. Since commit 113c74d83eef ("net: phy: turn carrier off on phy attach"), this lead to the link not coming up at boot anymore, due to the phy state machine being stuck at waiting for interrupts (off by

[Patch] media: ti-vpe: cal: Fix syntax check warnings

Fix the following sparse warnings: ti-vpe/cal.c:387:26: warning: incorrect type in return expression (different address spaces) ti-vpe/cal.c:459:26: warning: incorrect type in return expression (different address spaces) ti-vpe/cal.c:503:27: warning: incorrect type in argument 6 (different

Re: [PATCH 00/33] Compile-time stack metadata validation

On Mon, Feb 15, 2016 at 08:56:21AM -0800, Linus Torvalds wrote: > On Feb 15, 2016 8:31 AM, "Josh Poimboeuf" wrote: > > > > So is the goal to optimize for size? If I replace the calls to > > __preempt_schedule[_notrace]() with real C calls and remove the thunks, > > it only

Re: [PATCH 00/33] Compile-time stack metadata validation

> > There are two ways to fix the warnings: > > > > 1. get rid of the thunks and call the C functions directly; or > > No. Not until gcc learns about per-function callibg conventions (so that it > can > be marked as not clobbering registers). It does already for static functions in 5.x (with

Re: [PATCH 4.3 041/200] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

On Mon, Feb 15, 2016 at 11:36:13AM -0800, Greg Kroah-Hartman wrote: > On Mon, Feb 15, 2016 at 12:50:41PM -0600, Michael Welling wrote: > > On Mon, Feb 15, 2016 at 10:15:08AM -0800, Greg Kroah-Hartman wrote: > > > On Sun, Feb 14, 2016 at 09:08:50PM -0600, Michael Welling wrote: > > > > On Sun, Feb

Re: [PATCH v3 5/5] arm64/perf: Extend event mask for ARMv8.1

On Wed, Feb 03, 2016 at 06:12:00PM +0100, Jan Glauber wrote: > ARMv8.1 increases the PMU event number space. Detect the > presence of this PMUv3 type and extend the event mask. > > The event mask is moved to struct arm_pmu so different event masks > can exist, depending on the PMU type. > >

Re: [PATCH 0/3] OOM detection rework v4

On Sun 07-02-16 13:09:33, Tetsuo Handa wrote: [...] > FYI, I again hit unexpected OOM-killer during genxref on linux-4.5-rc2 source. > I think current patchset is too fragile to merge. > > [ 3101.626995] smbd invoked oom-killer: >

Re: [PATCH v3 1/5] arm64/perf: Rename Cortex A57 events

On Mon, Feb 15, 2016 at 07:40:37PM +, Will Deacon wrote: > On Wed, Feb 03, 2016 at 06:11:56PM +0100, Jan Glauber wrote: > > The implemented Cortex A57 events are not A57 specific. > > They are recommended by ARM and can be found on other > > ARMv8 SOCs like Cavium ThunderX too. Therefore move

Re: [PATCH 1/4] block: bio: introduce helpers to get the 1st and last bvec

Cc Kent and Keith. Follows another version which should be more efficient. Kent and Keith, I appreciate much if you may give a review on it. diff --git a/include/linux/bio.h b/include/linux/bio.h index 56d2db8..ef45fec 100644 --- a/include/linux/bio.h +++ b/include/linux/bio.h @@ -278,11

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

From: Буди Романто, AreMa Inc Signed-off-by: Буди Романто, AreMa Inc --- drivers/media/pci/Kconfig | 2 +- drivers/media/pci/Makefile | 2 +- drivers/media/pci/ptx/Kconfig | 21 ++ drivers/media/pci/ptx/Makefile | 8 +

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

On 02/15/2016 11:58 AM, Tony Lindgren wrote: * Guenter Roeck <li...@roeck-us.net> [160215 11:41]: On 02/15/2016 11:01 AM, Tony Lindgren wrote: https://kernelci.org/boot/all/job/next/kernel/next-20160215/ The SMP ones seem to fail with some regulator issues? There is another p

Re: [PATCH 5/5] mm, oom_reaper: implement OOM victims queuing

On Sun 07-02-16 00:33:38, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Sat 06-02-16 14:54:24, Tetsuo Handa wrote: > > > Michal Hocko wrote: > > > > > But if we consider non system-wide OOM events, it is not very > > > > > unlikely to hit > > > > > this race. This queue is useful for

Re: [PATCH] branch tracer: fix freak link error

On Monday 15 February 2016 12:47:46 Steven Rostedt wrote: > On Fri, 12 Feb 2016 22:26:42 +0100 > Arnd Bergmann wrote: > > > In my randconfig tests, I came across a bug that involves several > > components: > > > > > > [..] > > > > > This patch avoids the problem by changing

Re: [PATCH 1/4] gpio: remove broken irq_to_gpio() interface

On Monday 15 February 2016 17:01:09 Lars-Peter Clausen wrote: > On 02/15/2016 04:46 PM, Arnd Bergmann wrote: > > +static inline __deprecated int irq_to_gpio(unsigned int irq) > > +{ > > + /* this has clearly not worked for a long time */ > > + return -EINVAL; > > +} > > + > > #define

Re: [PATCH] branch tracer: fix freak link error

On Mon, 15 Feb 2016 21:15:39 +0100 Arnd Bergmann wrote: > Do you also want to add a 'Cc: sta...@vger.kernel.org' tag? > I currently have this in the Tags: Acked-by: Nicolas Pitre Fixes: ab3c9c686e22 ("branch tracer, intel-iommu: fix build with

Applied "regulator: axp20x: Use of_match name as default regulator name" to the regulator tree

The patch regulator: axp20x: Use of_match name as default regulator name has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Applied "regmap: irq: add devm apis for regmap_{add,del}_irq_chip" to the regmap tree

The patch regmap: irq: add devm apis for regmap_{add,del}_irq_chip has been applied to the regmap tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Re: About support XZ-compressed kernel on x86

On 2016-02-14 Baoquan He wrote: > On 02/13/16 at 08:57pm, Lasse Collin wrote: > > The long comment in arch/x86/boot/compressed/misc.c explains the > > need for the offset for gzip/Deflate. A similar comment in > > lib/decompress_unxz.c explains it for XZ/LZMA2. > > Thank you so much, Lasse. You

Re: [PATCH 2/4] block: check virt boundary in bio_will_gap()

diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index 4571ef1..b8ff6a3 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -1388,7 +1388,7 @@ static inline bool bvec_gap_to_prev(struct request_queue *q, static inline bool bio_will_gap(struct request_queue *q,

[PATCH v2 1/4] dma: mmp_pdma: Add the #dma-requests DT property documentation

For pxa based platforms, the number of requestor lines should be specified, so that the driver can check if the flow control should be activated (when a requestor line is asked for) or not. Signed-off-by: Robert Jarzmik --- Since v1: rename of property to #dma-requests

Applied "regulator: hi655x: enable regulator for hi655x PMIC" to the regulator tree

The patch regulator: hi655x: enable regulator for hi655x PMIC has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: hi655x: Document for hi655x regulator" to the regulator tree

The patch regulator: hi655x: Document for hi655x regulator has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Hi lkml

Good morning lkml http://www.drewlin.me/pitch.php?cause=1va2u3y80rqgv Badari Pulavarty

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

On Mon, Feb 15, 2016 at 8:58 PM, Tony Lindgren <t...@atomide.com> wrote: > * Guenter Roeck <li...@roeck-us.net> [160215 11:41]: >> On 02/15/2016 11:01 AM, Tony Lindgren wrote: >> > >> >https://kernelci.org/boot/all/job/next/kernel/next-20160215/ >&

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

; >>>> >>>> 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

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

On Monday 15 February 2016 21:56:42 Viresh Kumar wrote: > We are currently required to do two checks for regulator pointer: > IS_ERR() and IS_NULL(). > > And multiple instances are reported, about both of these not being used > consistently and so resulting in crashes. > > Fix that by

[PATCH 3.1/5] oom: make oom_reaper freezable

Andrew, this can be either folded into 3/5 patch or go as a standalone one. I would be inclined to have it standalone for the record (the description should be pretty clear about the intention) and because the issue is highly unlikely. OOM during the PM freezer doesn't happen in 99% cases. On Sat

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

On Mon, Feb 15, 2016 at 8:23 PM, Russell King - ARM Linux wrote: > On Mon, Feb 15, 2016 at 07:03:33PM +, Marc Zyngier wrote: >> On 15/02/16 18:54, Rafael J. Wysocki wrote: >> > That would explain it, thanks. >> > >> > So it looks like we should always use

Re: [PATCH 3/5] oom: clear TIF_MEMDIE after oom_reaper managed to unmap the address space

On Sat 06-02-16 20:23:43, Tetsuo Handa wrote: > Michal Hocko wrote: [...] > By always waking the OOM reaper up, we can delegate the duty of unlocking > the OOM killer (by clearing TIF_MEMDIE or some other means) to the OOM > reaper because the OOM reaper is tracking all TIF_MEMDIE tasks. And

Re: [PATCH 1/5] mm, oom: introduce oom reaper

On Sat 06-02-16 22:22:20, Tetsuo Handa wrote: > Michal Hocko wrote: > > There is one notable exception to this, though, if the OOM victim was > > in the process of coredumping the result would be incomplete. This is > > considered a reasonable constrain because the overall system health is > >

Re: [PATCH 1/4] Drivers: hv: vmbus: don't loose HVMSG_TIMER_EXPIRED messages

2016-02-12 16:42+0100, Vitaly Kuznetsov: > We must handle HVMSG_TIMER_EXPIRED messages in the interrupt context > and we offload all the rest to vmbus_on_msg_dpc() tasklet. This functions > loops to see if there are new messages pending. In case we'll ever see > HVMSG_TIMER_EXPIRED message there

<    1   2   3   4   5   6   7   8   9   10   >