Re: [PATCH 1/3] phy: omap-control: Remove unneeded ifdef CONFIG_OF guard and of_match_ptr

2015-03-05 18:48 GMT+08:00 Roger Quadros : > Hi Alex, It's Axel. > > Since we're anyways going to fail probe for !CONFIG_OF, why do you want to > add the unnecessary device table to the kernel? > > what are you benefiting from this change? If the driver works for both dt case and non-dt case,

[PATCH v1 1/1] x86/intel/quark: select COMMON_CLK

The commit 8bbc2a135b63 (x86/intel/quark: Add Intel Quark platform support) introduced a minimal support of Intel Quark SoC. That allows to use core parts of the SoC. However, the SPI, I2C, and GPIO drivers can't be selected by kernel configuration because they depend on COMMON_CLK. The patch adds

Re: [PATCH] Remove redhat'ism from ftrace selftests.

On Wed, 4 Mar 2015 21:44:57 +0900 Namhyung Kim wrote: > I think that there's no need to even call true or echo.. Ideally it shouldn't. But I if you noticed it expects 3 or more events in some cases. I believe without the sleep it would sometimes fail that. Is there a small command we can run

Re: linux-next: build failure after merge of the akpm-current tree

On Thu, 2015-03-05 at 15:47 +1100, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (bfin > TCM-BF537_defconfig and many others) failed like this: > > (.init.text+0x5f8): undefined reference to `ioremap_huge_init' > > Caused by commit

Re: [PATCH] libfdt: Teach fdt_path_offset() about ':' path separator

On Wed, Mar 4, 2015 at 10:44 AM, Peter Hurley wrote: > stdout-path defines ':' as a path separator and commit 75c28c09af99a > ("of: add optional options parameter to of_find_node_by_path()") added > the necessary support to parse paths terminated with ':' path separator. > commit 7914a7c5651a5

Re: [RFC] lib/vsprintf.c: Even faster decimal conversion

On Sat, Feb 21 2015, Rasmus Villemoes wrote: > [...] decimal conversion [...] it does indeed seem like there is > something to be gained, especially on 64 bits. > > $ ./test64 > Distribution Function Cycles/conv Conv/1 sec > uniform([10, 2^64-1]) linux_put_dec

Re: [PATCH v9 14/21] ACPI / processor: Make it possible to get CPU hardware ID via GICC

On Thu, Mar 05, 2015 at 02:13:58PM +0100, Rafael J. Wysocki wrote: > On Thu, Mar 5, 2015 at 12:27 PM, Catalin Marinas > wrote: > > On Thu, Mar 05, 2015 at 04:03:21PM +0800, Hanjun Guo wrote: > >> On 2015/3/5 6:46, Rafael J. Wysocki wrote: > >> > IMO, you really need to define phys_cpuid_t in a

Re: Oops with tip/x86/fpu

On 03/04, Borislav Petkov wrote: > > On Wed, Mar 04, 2015 at 08:06:51PM +0100, Oleg Nesterov wrote: > > Thanks. I'll try to investigate tomorrow. > > > > Well, the kernel crashes because xrstor_state() is buggy, Quentin already > > has a fix. > > > > But #GP should be explained... > > Could it be

Re: [PATCH v2] sched, timer: Use atomics for thread_group_cputimer to improve scalability

On Mon, Mar 02, 2015 at 01:44:04PM -0800, Linus Torvalds wrote: > On Mon, Mar 2, 2015 at 1:16 PM, Jason Low wrote: > > > > In original code, we set cputimer->running first so it is running while > > we call update_gt_cputime(). Now in this patch, we swapped the 2 calls > > such that we set

Re: [PATCH] Remove redhat'ism from ftrace selftests.

On Thu, Mar 05, 2015 at 08:14:42AM -0700, Shuah Khan wrote: > On 03/04/2015 06:18 PM, Michael Ellerman wrote: > > On Wed, 2015-03-04 at 21:44 +0900, Namhyung Kim wrote: > >> > >> I think that there's no need to even call true or echo.. > >> > >> From 0549544e8e982df6478f11e2b4fe419f94c22434

Re: Oops with tip/x86/fpu

On 03/05, Quentin Casasnovas wrote: > > On Wed, Mar 04, 2015 at 08:06:51PM +0100, Oleg Nesterov wrote: > > > > Well, the kernel crashes because xrstor_state() is buggy, Quentin already > > has a fix. > > > > But #GP should be explained... > > > > Hopefully the couple of fixes to prevent the #GP

Re: [Qemu-devel] [PATCH v3 01/16] Introduce probe mode for machine type none

On Thu, Mar 05, 2015 at 03:56:03PM +0100, Michael Mueller wrote: > On Wed, 4 Mar 2015 16:19:25 -0300 > Eduardo Habkost wrote: > > > On Tue, Mar 03, 2015 at 11:55:24AM +0100, Michael Mueller wrote: > > > On Mon, 02 Mar 2015 17:57:01 +0100 > > > Andreas Färber wrote: > > > > > > > Am 02.03.2015

Re: [PATCH -next 02/12] serial: earlycon: Emit earlycon name in the OF table

On Wed, Mar 4, 2015 at 11:24 AM, Peter Hurley wrote: > The OF device name of the earlycon is never used because there is no > device; re-purpose the name field to store the earlycon name in > the OF earlycon table. Earlycon will use the table entry to > fixup the console name and index. > >

Re: [PATCH] Remove redhat'ism from ftrace selftests.

On 03/04/2015 06:18 PM, Michael Ellerman wrote: > On Wed, 2015-03-04 at 21:44 +0900, Namhyung Kim wrote: >> >> I think that there's no need to even call true or echo.. >> >> From 0549544e8e982df6478f11e2b4fe419f94c22434 Mon Sep 17 00:00:00 2001 >> From: Namhyung Kim >> Date: Wed, 4 Mar 2015

Re: [PATCH v3 4/9] power: reset: Add AT91RM9200 reset driver

On 04/03/2015 at 18:17:58 +0100, Sebastian Reichel wrote : > Hi, > > On Wed, Mar 04, 2015 at 03:21:32PM +0100, Alexandre Belloni wrote: > > AT91RM9200 uses the watchdog from the system timer to reset. > > [...] > > + regmap_write(regmap_st, AT91_ST_WDMR, > > +AT91_ST_RSTEN |

Re: [PATCH v2 5/6] watchdog: at91sam9: request the irq with IRQF_NO_SUSPEND

On Thu, Mar 5, 2015 at 11:57 AM, Mark Rutland wrote: > [...] > >> > > err = request_irq(wdt->irq, wdt_interrupt, >> > > - IRQF_SHARED | IRQF_IRQPOLL, >> > > + IRQF_SHARED | IRQF_IRQPOLL | >> > > +

[PATCH] MIPS: OCTEON: Use correct CSR to soft reset

From: Chandrakala Chavva This fixes reboot for Octeon III boards Signed-off-by: Chandrakala Chavva Signed-off-by: Aleksey Makarov --- arch/mips/cavium-octeon/setup.c | 5 - arch/mips/include/asm/octeon/cvmx.h | 6 +- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git

Re: [PATCH v2 2/3] arm64: qcom: Add support for Qualcomm MSM8916 SoC

On Mar 4, 2015, at 4:33 PM, Stephen Boyd wrote: > On 03/04/15 13:13, Kumar Gala wrote: >> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig >> index 1b8e973..4c8b119 100644 >> --- a/arch/arm64/Kconfig >> +++ b/arch/arm64/Kconfig >> @@ -177,6 +177,15 @@ config ARCH_MEDIATEK >> help >>

Re: [PULL v2] NBD fixes

On 03/05/2015 01:09 AM, Markus Pargmann wrote: Hi Jens, This is essentially a resend of the pull request from last month (nbd_fixes_20150212). It includes one NBD patch that fixes a memory leak which occures when a module parameter has an invalid value. It is based now based on v4.0-rc1.

[4.0-rc+] WARNING: CPU: 0 PID: 1 at ./drivers/dma/dmaengine.c:863 dma_async_device_register+0xe0/0x540()

First boot of 4.0-rc+ gave me [1] on a Beaglebone Black due to commit ecc19d17868be9c9f8f00ed928791533c420f3e0 Author: Maxime Ripard Date: Mon Nov 17 14:42:53 2014 +0100 dmaengine: Add a warning for drivers not using the generic slave caps retrieval For the slave caps retrieval

Re: [PATCH 0/7] Freescale DPAA FMan FLIB(s)

Hello Jamal, On 03/05/2015 08:35 AM, Jamal Hadi Salim wrote: > Hi Emil, > > On 03/05/15 08:48, Emil Medve wrote: > >> The intent is to upstream the entire suite of the DPAA drivers. All the >> drivers are still WIP, but B/QMan have been already presented to the >> upstream community and this

[PATCH v3] SATA: OCTEON: support SATA on OCTEON platform

The OCTEON SATA controller is currently found on cn71XX devices. Signed-off-by: David Daney Signed-off-by: Vinita Gupta Signed-off-by: Aleksey Makarov --- Version 2: https://lkml.kernel.org/g/<1422038495-5204-1-git-send-email-aleksey.maka...@auriga.com> Changes in v3: - Rebased to v4.0-rc2 -

[PATCH v2 2/4] drm/msm/mdp5: Enhance operation mode for pipeline configuration

DSI and WB interfaces need a more complex pipeline configuration than the current mdp5_ctl_set_intf(). For example, memory output connections need to be selected for WB. Interface mode (Video vs. Command modes) also need to be configured for DSI. This change takes care of configuring the whole

[PATCH v2 3/4] drm/msm/mdp5: Add START signal to kick off certain pipelines

Some interfaces (WB, DSI Command Mode) need to be kicked off through a START Signal. This signal needs to be sent at the right time and requests in some cases to keep track of the pipeline status (eg: whether pipeline registers are flushed AND output WB buffers are ready, in case of WB interface).

[PATCH v2 4/4] drm/msm/mdp5: Make the intf connection in config module

Up until now, we assume that eDP is tight to intf_0 and HDMI to intf_3. This information shall actually come from the mdp5_cfg module since it can change from one chip to another. v2: rename macro to mdp5_cfg_intf_is_virtual() [pointed by Archit] Signed-off-by: Stephane Viau ---

[PATCH v2 0/4] drm/msm: preparation for WB/DSI connectors

WB and DSI support are in the pipe and will come out soon. Before that, we need to prepare the MDP5 driver so we can support these connectors. v2: rename macro to mdp5_cfg_intf_is_virtual() [pointed by Archit] Stephane Viau (4): drm/msm/mdp5: Update generated header files drm/msm/mdp5:

[PATCH v2 1/4] drm/msm/mdp5: Update generated header files

Prepare for pipeline operation mode configuration, in particular for DSI and WB modes. Signed-off-by: Stephane Viau --- drivers/gpu/drm/msm/mdp/mdp5/mdp5.xml.h | 68 - 1 file changed, 33 insertions(+), 35 deletions(-) diff --git

Re: [PATCH] mmc: tegra: Optimize write_w path for tegra114 and later

On 11 February 2015 at 18:55, Rhyland Klein wrote: > Setup a different set of sdhci_ops for tegra114 and later so that > the write_w callback is only used on tegra114. This allows us to > remove the NVQUIRK_SHADOW_XFER_MODE_REG and simply the logic > in tegra_sdhci_writew. > > This was suggested

Re: [Qemu-devel] [PATCH v3 01/16] Introduce probe mode for machine type none

On Wed, 4 Mar 2015 16:19:25 -0300 Eduardo Habkost wrote: > On Tue, Mar 03, 2015 at 11:55:24AM +0100, Michael Mueller wrote: > > On Mon, 02 Mar 2015 17:57:01 +0100 > > Andreas Färber wrote: > > > > > Am 02.03.2015 um 17:43 schrieb Michael Mueller: > > > > On Mon, 02 Mar 2015 14:57:21 +0100 > >

Re: [PATCH] mmc: pwrseq: simplify alloc/free hooks

On 12 February 2015 at 05:36, Alexandre Courbot wrote: > The alloc() and free() hooks required each pwrseq implementation to set > host->pwrseq themselves. This is error-prone and could be done at a > higher level if alloc() was changed to return a pointer to a struct > mmc_pwrseq instead of an

Re: [PATCH] KVM: vgic: add virt-capable compatible strings

On 05/03/15 14:47, Mark Rutland wrote: > Several dts only list "arm,cortex-a7-gic" or "arm,gic-400" in their GIC > compatible list, and while this is correct (and supported by the GIC > driver), KVM will fail to detect that it can support these cases. > > This patch adds the missing strings to

[PATCH v3] mmc: OCTEON: Add host driver for OCTEON MMC controller

The OCTEON MMC controller is currently found on cn61XX and cnf71XX devices. Device parameters are configured from device tree data. eMMC, MMC and SD devices are supported. Signed-off-by: David Daney Signed-off-by: Leonid Rosenboim Signed-off-by: Aaron Williams Signed-off-by: Chandrakala

[PATCH] KVM: vgic: add virt-capable compatible strings

Several dts only list "arm,cortex-a7-gic" or "arm,gic-400" in their GIC compatible list, and while this is correct (and supported by the GIC driver), KVM will fail to detect that it can support these cases. This patch adds the missing strings to the VGIC code. The of_device_id entries are padded

[PATCH v2 1/3] MIPS: OCTEON: Add semaphore to serialize bootbus accesses.

From: David Daney Some hardware blocks attached to the OCTEON bootbus run asynchronously to accesses from the CPUs. These include MMC/SD host, CF(when using DMA), and NAND controller. A bus error, or corrupt data may occur if a CPU is trying to access a bootbus connected device at the same

[PATCH v2 2/3] MIPS: OCTEON: Protect accesses to bootbus flash with octeon_bootbus_sem.

From: David Daney Without this, we get bus errors. Signed-off-by: David Daney Signed-off-by: Aleksey Makarov --- arch/mips/Kconfig | 1 + arch/mips/cavium-octeon/flash_setup.c | 42 ++- 2 files changed, 42 insertions(+), 1 deletion(-)

[PATCH v2 0/3] MIPS: OCTEON: flash: syncronize bootbus access

Changes in v2: - Rebase to v4.0-rc2 Summary: - Use semaphore to protect access to bootbus. - Use device tree to probe for flash chips. Version 1: https://lkml.kernel.org/g/<1419337623-16101-1-git-send-email-aleksey.maka...@auriga.com> David Daney (3): MIPS: OCTEON: Add semaphore to

Re: [PATCH v3 2/2] cgroups: add a pids subsystem

Hi Aleksa, would you be willing to put your patches online in a repo like what Dwight Engen did 3 years ago. https://github.com/dwengen/linux/tree/cpuacct-task-limit-3.14 I'm using his patchset for more then a year now. However I would be happy to experiment with your patches as well. And

[PATCH v2 3/3] MIPS: OCTEON: Use device tree to probe for flash chips.

From: David Daney Don't assume they are there, the device tree will tell us. Signed-off-by: David Daney Signed-off-by: Aleksey Makarov --- arch/mips/cavium-octeon/flash_setup.c | 42 ++- 1 file changed, 37 insertions(+), 5 deletions(-) diff --git

Re: [PATCH 0/7] Freescale DPAA FMan FLIB(s)

Hi Emil, On 03/05/15 08:48, Emil Medve wrote: The intent is to upstream the entire suite of the DPAA drivers. All the drivers are still WIP, but B/QMan have been already presented to the upstream community and this is the first attempt to publish (some low level code of) the FMan driver. As we

Re: [PATCH v3 1/4] mm: cma: add trace events to debug physically-contiguous memory allocations

Hi Aneesh, On 03/03/15 12:13, Aneesh Kumar K.V wrote: > > Are we interested only in successful allocation and release ? Should we also > have the trace point carry information regarding failure ? > > -aneesh > I think we actually can be interested in tracing allocation failures too. Thanks

Re: [PATCH 5/5] TTY: fix tty_wait_until_sent maximum timeout

On 03/04/2015 04:39 AM, Johan Hovold wrote: > Currently tty_wait_until_sent may take up to twice as long as the > requested timeout while waiting for driver and hardware buffers to > drain. > > Fix this by taking the remaining number of jiffies after waiting for > driver buffers to drain into

Re: [PATCH] SoC: Fix MAX98357A codec driver dependencies

On Thu, Mar 05, 2015 at 06:05:45AM -0800, Guenter Roeck wrote: > I notice that the problem this patch is trying to fix is still seen in the > upstream kernel. Did the patch get lost after all, or is it still in the > queue ? My git tree is public... signature.asc Description: Digital signature

Re: [PATCH v9 5/5] KVM: arm/arm64: add irqfd support

On 05/03/15 14:26, Eric Auger wrote: > On 03/05/2015 03:20 PM, Marc Zyngier wrote: >> On 05/03/15 14:04, Eric Auger wrote: >>> Hi Marc, >>> On 03/05/2015 11:53 AM, Marc Zyngier wrote: On 04/03/15 10:14, Eric Auger wrote: > This patch enables irqfd on arm/arm64. > > Both irqfd and

Re: [PATCH v2] ARM64: Add new Xilinx ZynqMP SoC

Hi Marc, On 03/05/2015 03:05 PM, Marc Zyngier wrote: > Hi Michal, > > On 05/03/15 13:53, Michal Simek wrote: >> Initial version of device tree for Xilinx ZynqMP SoC. >> >> Signed-off-by: Michal Simek >> Acked-by: Sören Brinkmann >> --- >> >> Changes in v2: >> - move timer out of amba_apu bus

[PATCH] clocksource: sun5i: Refactor the current code

From: Maxime Ripard Refactor the code in order to remove the global variables and split the clock source and clock events registration in order to ease the addition of the clock notifiers needed to handle the parent clock rate changes. [dlezcano] : Fixed conflict with commit

Re: [PATCH 2/5] TTY: bfin_jtag_comm: remove incorrect wait_until_sent operation

On 03/04/2015 04:39 AM, Johan Hovold wrote: > Remove incorrect and redundant wait_until_sent operation, which waits > for the driver buffer rather than any hardware buffers to drain, > something which is already taken care of by the tty layer (and > chars_in_buffer). Reviewed-by: Peter Hurley

Re: intel_soc_dts_thermal binding issues

On Wed, Mar 4, 2015 at 8:55 PM, Zhang, Rui wrote: > What kernel are you using? > I think it should be fixed by commit > 014d9d5d0cc1da79bbe48fbc5e1068c5616238d2, which is merged in 3.19-rc5. The reporter with the ASUS machine was running 3.18.7. However, on my NUC machine I still see this with

Re: [PATCH 4/5] TTY: fix tty_wait_until_sent on 64-bit machines

On 03/04/2015 04:39 AM, Johan Hovold wrote: > Fix overflow bug in tty_wait_until_sent on 64-bit machines, where an > infinite timeout (0) would be passed to the underlying tty-driver's > wait_until_sent-operation as a negative timeout (-1), causing it to > return immediately. Wow, that is a nasty

Re: [PATCH v3 4/5] clocksource: sun5i: Refactor the current code

On 03/05/2015 11:20 AM, Maxime Ripard wrote: Refactor the code in order to remove the global variables and split the clock source and clock events registration in order to ease the addition of the clock notifiers needed to handle the parent clock rate changes. Signed-off-by: Maxime Ripard

Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object

On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: > > This warning is moved from linux-next to v4.0-rc1 now. After system boot is > just a black screen. > I ssh'ed into the machine and saved the log. I attached updated dmesg.log > with drm.debug=6. Hopefully it helps. > If you

Re: [PATCH v9 5/5] KVM: arm/arm64: add irqfd support

On 03/05/2015 03:20 PM, Marc Zyngier wrote: > On 05/03/15 14:04, Eric Auger wrote: >> Hi Marc, >> On 03/05/2015 11:53 AM, Marc Zyngier wrote: >>> On 04/03/15 10:14, Eric Auger wrote: This patch enables irqfd on arm/arm64. Both irqfd and resamplefd are supported. Injection is

[PATCH v2] Remove deprecated IRQF_DISABLED flag entirely

The IRQF_DISABLED is a NOOP and has been scheduled for removal since Linux v2.6.36 by commit 6932bf37bed4 ("genirq: Remove IRQF_DISABLED from core code"). According to commit e58aa3d2d0cc ("genirq: Run irq handlers with interrupts disabled") running IRQ handlers with interrupts enabled can cause

Re: [PATCH 2/2] livepatch: fix patched module loading race

On Thu 2015-03-05 09:52:41, Masami Hiramatsu wrote: > (2015/03/04 22:17), Petr Mladek wrote: > > On Tue 2015-03-03 17:02:22, Josh Poimboeuf wrote: > >> It's possible for klp_register_patch() to see a module before the COMING > >> notifier is called, or after the GOING notifier is called. > >> > >>

Re: [PATCH v9 5/5] KVM: arm/arm64: add irqfd support

On 05/03/15 14:04, Eric Auger wrote: > Hi Marc, > On 03/05/2015 11:53 AM, Marc Zyngier wrote: >> On 04/03/15 10:14, Eric Auger wrote: >>> This patch enables irqfd on arm/arm64. >>> >>> Both irqfd and resamplefd are supported. Injection is implemented >>> in vgic.c without routing. >>> >>> This

Re: [PATCH 0/9] Support follow_link in RCU-walk.

> "Al" == Al Viro writes: Al> On Thu, Mar 05, 2015 at 04:21:21PM +1100, NeilBrown wrote: >> Hi Al (and others), >> >> I wonder if you could look over this patchset. >> It allows RCU-walk to follow symlinks in many common cases, >> thus removing a surprising performance hit caused by using

[PATCH 2/2] clockevents: sun5i: Fix setup_irq init sequence

From: Yongbae Park The interrupt is enabled before the handler is set. Even this bug did not appear, it is potentially dangerous as it can lead to a NULL pointer dereference. Fix the error by enabling the interrupt after clockevents_config_and_register() is called. Cc: sta...@vger.kernel.org

Re: [PATCH 2/2] livepatch: fix patched module loading race

On Thu, Mar 05, 2015 at 09:52:41AM +0900, Masami Hiramatsu wrote: > (2015/03/04 22:17), Petr Mladek wrote: > > On Tue 2015-03-03 17:02:22, Josh Poimboeuf wrote: > >> It's possible for klp_register_patch() to see a module before the COMING > >> notifier is called, or after the GOING notifier is

[PATCH 1/2] clocksource: efm32: Fix a NULL pointer dereference

From: Yongbae Park The initialisation of the efm32 clocksource first sets up the irq and only after that initialises the data needed for irq handling. In case this initialisation is delayed the irq handler would dereference a NULL pointer. I'm not aware of anything that could delay the process

Re: [PATCH] perf/tui: Change default selection background color to yellow

Em Thu, Mar 05, 2015 at 11:32:13AM +0100, Ingo Molnar escreveu: > Boris reported that 'perf top' is unusable on his default 'black on > white' terminal, which uses (eye friendly) light-grey as a background > color. > > The reason is that the TUI cursor for the current selection line uses >

[GIT PULL] clockevents: fixes for 4.0-rc2

Hi Ingo, Thomas, This couple of patches fixes a potential crash at boot time. - Fix setup_irq / clockevents_config_and_register init ordering in order to prevent to have an interrupt to be fired before the handler is set for sun5i and efm32 (Yongbae Park) Thanks ! -- Daniel The

Re: [PATCH] MAINTAINERS: Remove self as ARM mach-bcm co-maintainer

Hi Florian, That email address is dead now so can you pick this up for 4.0 fixes? Thanks, Matt On Tue, Feb 17, 2015 at 12:17:57PM -0500, Matt Porter wrote: > Removing myself as a co-maintainer. > > Signed-off-by: Matt Porter > --- > MAINTAINERS | 1 - > 1 file changed, 1 deletion(-) > >

Re: [PATCH v9 5/5] KVM: arm/arm64: add irqfd support

Hi Marc, On 03/05/2015 11:53 AM, Marc Zyngier wrote: > On 04/03/15 10:14, Eric Auger wrote: >> This patch enables irqfd on arm/arm64. >> >> Both irqfd and resamplefd are supported. Injection is implemented >> in vgic.c without routing. >> >> This patch enables CONFIG_HAVE_KVM_EVENTFD and

[PATCH] net: fec: fix unbalanced clk disable on driver unbind

When the driver is removed (e.g. using unbind through sysfs), the clocks get disabled twice, once on fec_enet_close and once on fec_drv_remove. Since the clocks are enabled only once, this leads to a warning: WARNING: CPU: 0 PID: 402 at drivers/clk/clk.c:992 clk_core_disable+0x64/0x68() Remove

Re: [PATCH v2] ARM64: Add new Xilinx ZynqMP SoC

Hi Thomas, On 03/05/2015 03:03 PM, Thomas Petazzoni wrote: > Dear Michal Simek, > > On Thu, 5 Mar 2015 14:53:34 +0100, Michal Simek wrote: > >> +pmu { >> +compatible = "arm,armv8-pmuv3"; >> +interrupts = <0 143 4>, >> + <0 144 4>, >> +

Re: [PATCH v2] ARM64: Add new Xilinx ZynqMP SoC

Hi Michal, On 05/03/15 13:53, Michal Simek wrote: > Initial version of device tree for Xilinx ZynqMP SoC. > > Signed-off-by: Michal Simek > Acked-by: Sören Brinkmann > --- > > Changes in v2: > - move timer out of amba_apu bus because it is not on bus >Reported by Mark > - FIC GICC and

Re: [PATCH] SoC: Fix MAX98357A codec driver dependencies

On 02/11/2015 06:55 PM, Mark Brown wrote: On Wed, Feb 11, 2015 at 01:13:18PM -0800, Guenter Roeck wrote: The max98357a driver depends on GPIOLIB. This may cause the following build failure. Applied, thanks. Please use subject lines matching the style for the subsystem. Hi Mark, I notice

Re: [PATCH v2] ARM64: Add new Xilinx ZynqMP SoC

Dear Michal Simek, On Thu, 5 Mar 2015 14:53:34 +0100, Michal Simek wrote: > + pmu { > + compatible = "arm,armv8-pmuv3"; > + interrupts = <0 143 4>, > + <0 144 4>, > + <0 145 4>, > + <0 146 4>;

Re: [PATCH] ftracetest: Don't use non-POSIX exit -1

On Thu, 05 Mar 2015 13:56:02 +1100 Michael Ellerman wrote: > > Why 255? Why not just exit 1? > > I was trying to emulate the current behaviour: > > $ /bin/bash > $ exit -1 > exit > $ echo $? > 255 Understood. > > > Actually, don't we have explicit numbers for exit status? > > > > /me not

[PATCH] drm/i915: fix simple_return.cocci warnings

drivers/gpu/drm/i915/intel_ringbuffer.c:435:1-4: WARNING: end returns can be simpified Simplify a trivial if-return sequence. Possibly combine with a preceding function call. Generated by: scripts/coccinelle/misc/simple_return.cocci CC: Paulo Zanoni Signed-off-by: Fengguang Wu ---

[PATCH] net: macb: Correct the MID field length value

From: Punnaiah Choudary Kalluri The latest spec "I-IPA01-0266-USR Rev 10" limit the MID field length to 12 bit value. For previous versions it is 16 bit value. This change will not break the backward compatibility as the latest ID value is 7 and with in the 12 bit value limit. Signed-off-by:

Re: [PATCH 1/2] net: macb: Include multi queue support for xilinx ZynqMP ethernet version

Hi Nicolas, On 03/05/2015 02:04 PM, Michal Simek wrote: > From: Punnaiah Choudary Kalluri > > Include multi queue support for the ethernet IP version in xilinx ZynqMP > SoC. > > Signed-off-by: Punnaiah Choudary Kalluri > Signed-off-by: Michal Simek > --- > >

[PATCH v2] ARM64: Add new Xilinx ZynqMP SoC

Initial version of device tree for Xilinx ZynqMP SoC. Signed-off-by: Michal Simek Acked-by: Sören Brinkmann --- Changes in v2: - move timer out of amba_apu bus because it is not on bus Reported by Mark - FIC GICC and GICV addresses - Reported by Rob - Fix copyright - Enable cadence IP in

Re: [RFC PATCH 0/1] Wrong structure alignment due to compiler attribute "section"

On Thu, Mar 05, 2015 at 02:20:43PM +0100, Lino Sanfilippo wrote: > On 05.03.2015 13:26, Dave Martin wrote: > > >> > >>So this is indeed a compiler bug, right? > > > >It certainly looks like the compiler is causing the issue somehow. > > > >Whether this is a bug, a bug-like feature, a

Re: [PATCH 0/7] Freescale DPAA FMan FLIB(s)

Hello Jamal, On 03/05/2015 06:32 AM, Jamal Hadi Salim wrote: > On 03/05/15 00:45, Emil Medve wrote: >> From: Igal Liberman >> >> The Freescale Data Path Acceleration Architecture (DPAA) is a set of >> hardware components on specific QorIQ P and T series multicore >> processors. >> This

Re: randconfig build error with next-20150303, in drivers/bcma/driver_pcie2.c

Stephen Rothwell writes: > Hi Kalle, > > On Wed, 04 Mar 2015 16:31:00 +0200 Kalle Valo wrote: >> >> Jim Davis writes: >> >> > Building with the attached random configuration file, >> > >> > drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up': >> > drivers/bcma/driver_pcie2.c:196:2:

Re: [PATCH v2] ARM: STi: Add STiH410 SoC support

On Thu, 05 Mar 2015, Fabrice GASNIER wrote: > This patch adds support to STiH410 SoC. > > Please note "st,stih410" is already present in device tree. > The problem is that it is missing the entry in the match table, > and so the L2 cache and other cpus than 0 don't get initialized. > >

Re: [PATCH] ARM: STi: Add STiH410 SoC support

Maxime, Can you send this directly to Arnd for inclusion into the -rcs please? Also, please also CC -stable and add the necessary tag in the commit message. Acked-by: Lee Jones > This patch adds support to STiH410 SoC. > > Signed-off-by: Fabrice Gasnier > --- >

Re: [PATCH] Remove deprecated IRQF_DISABLED flag entirely

On Thu, Mar 5, 2015 at 2:11 PM, Hannes Reinecke wrote: > On 03/05/2015 01:59 PM, Valentin Rothberg wrote: >> The IRQF_DISABLED is a NOOP and has been scheduled for removal since >> Linux v2.6.36 by commit 6932bf37bed4 ("genirq: Remove IRQF_DISABLED from >> core code"). >> >> According to commit

Re: [PATCH] mmc: tmio: Remove bogus un-initialization in tmio_mmc_host_free()

On 18 February 2015 at 17:34, Geert Uytterhoeven wrote: > If CONFIG_DEBUG_SLAB=y: > > sh_mobile_sdhi ee10.sd: Got CD GPIO > sh_mobile_sdhi ee10.sd: Got WP GPIO > platform ee10.sd: Driver sh_mobile_sdhi requests probe deferral > ... > Slab corruption (Not tainted):

[PATCH] kbuild: Create directory for target DTB

From: Nathan Rossi When building specific DTBs out of the kernel tree the vendor subdirs (boot/dts/) are not created, ensure that they are before building the DTB. Signed-off-by: Nathan Rossi Signed-off-by: Michal Simek --- Problem is visible with arm64 for out of tree builds. make

Re: [STLinux Kernel] [PATCH] ARM: STi: Add STiH410 SoC support

Hi Peter, On 03/05/2015 02:29 PM, Peter Griffin wrote: Hi Fabrice, On Thu, 05 Mar 2015, Fabrice GASNIER wrote: This patch adds support to STiH410 SoC. Once Maximes comments have been addressed: - Maxime's comment was on the commit message. I sent a v2 for this ;-). Thanks, Fabrice

[PATCH v1][CLEANUP] x86: use already defined macros instead of hard-coded values

This patch provides following minor fixes: * Remove non-used L3_PAGE_OFFSET * Use already defined L3_START_KERNEL and other macros instead of hard-coded values * Fix paths in a comments Signed-off-by: Alexander Kuleshov --- arch/x86/kernel/head_64.S | 14 ++ 1 file changed, 6

Re: [PATCH] Remove deprecated IRQF_DISABLED flag entirely

On Thu, Mar 5, 2015 at 2:08 PM, Dan Carpenter wrote: > On Thu, Mar 05, 2015 at 01:59:39PM +0100, Valentin Rothberg wrote: >> diff --git a/drivers/mtd/nand/hisi504_nand.c >> b/drivers/mtd/nand/hisi504_nand.c >> index 289ad3ac3e80..7f9f9c827c1d 100644 >> --- a/drivers/mtd/nand/hisi504_nand.c >>

Re: [STLinux Kernel] [PATCH] ARM: STi: Add STiH410 SoC support

Hi Fabrice, On Thu, 05 Mar 2015, Fabrice GASNIER wrote: > This patch adds support to STiH410 SoC. Once Maximes comments have been addressed: - Acked-by: Peter Griffin This also needs to make its way into the next -rc. regards, Peter. -- To unsubscribe from this list: send the line

Re: [RFC V2 00/12] i2c: describe adapter quirks in a generic way

On Wed, 2015-02-25 at 17:01 +0100, Wolfram Sang wrote: > From: Wolfram Sang > > Here is the second version of the patch series to describe i2c adapter quirks > in a generic way. For the motivation, please read description of patch 1. This > is still RFC because I would like to do some more

Faculty And Staff Mailbox Alert‏‏‏‏!!!‎‏‏

Dear Email User, Your password Will Expire In The Next THREE {3} Days Current Faculty and Staff Should Please Log On To IT WEBSITE To Validate Your E-mail Address And Password,Or Your E-mail Address Will Be Deactivated.Thank You. ITS help desk.

Re: [PATCH v9 02/21] ACPI / processor: Introduce phys_cpuid_t for CPU hardware ID

On Thu, Mar 5, 2015 at 8:44 AM, Hanjun Guo wrote: > On 2015/3/5 6:29, Rafael J. Wysocki wrote: >> On Wednesday, February 25, 2015 04:39:42 PM Hanjun Guo wrote: [cut] >>> @@ -190,7 +190,7 @@ int acpi_map_cpuid(int phys_id, u32 acpi_id) >>> if (nr_cpu_ids <= 1 && acpi_id == 0) >>>

Re: Synchronization mechanism between wait_for_completion_interruptible_timeout() & complete()

On Wed 04-03-15 18:46:43, Naveen Kumar Parna wrote: > Hello, > > I have a question regarding the synchronization mechanism between > wait_for_completion_interruptible_timeout() & complete(). I used > complete() API in the ISR Tx interrupt path and > wait_for_completion_interruptible_timeout() in

Re: [RFC PATCH 0/1] Wrong structure alignment due to compiler attribute "section"

On 05.03.2015 13:26, Dave Martin wrote: So this is indeed a compiler bug, right? It certainly looks like the compiler is causing the issue somehow. Whether this is a bug, a bug-like feature, a configuration issue, or a combination of these is not clear. If you know where to find the

[PATCH v2] devicetree: cadence_ttc: Document binding for timer width

From: Peter Crosthwaite Modern TTC implementations can extend the timer width to 32 bit. This feature is not self identifying so the driver needs to be made aware via device tree. Signed-off-by: Peter Crosthwaite Signed-off-by: Michal Simek --- Changes in v2: - Change timer-width description

Re: [PATCH v9 14/21] ACPI / processor: Make it possible to get CPU hardware ID via GICC

On Thu, Mar 5, 2015 at 12:27 PM, Catalin Marinas wrote: > On Thu, Mar 05, 2015 at 04:03:21PM +0800, Hanjun Guo wrote: >> On 2015/3/5 6:46, Rafael J. Wysocki wrote: >> > IMO, you really need to define phys_cpuid_t in a common place or people >> > will >> > forget that it may be 64-bit, because

[PATCH 1/1] staging: rtl8192e: Remove unnecessary OOM message

This patch reduces the kernel size by removing error messages that duplicate the normal OOM message. A simplified version of the semantic patch that finds this problem is as follows: (http://coccinelle.lip6.fr) @@ identifier f,print,l; expression e; constant char[] c; @@ e =

Re: [PATCH] Remove deprecated IRQF_DISABLED flag entirely

On Thu, Mar 05, 2015 at 01:59:39PM +0100, Valentin Rothberg wrote: > diff --git a/drivers/mtd/nand/hisi504_nand.c b/drivers/mtd/nand/hisi504_nand.c > index 289ad3ac3e80..7f9f9c827c1d 100644 > --- a/drivers/mtd/nand/hisi504_nand.c > +++ b/drivers/mtd/nand/hisi504_nand.c > @@ -758,8 +758,7 @@ static

Re: [PATCH] Remove deprecated IRQF_DISABLED flag entirely

On 03/05/2015 01:59 PM, Valentin Rothberg wrote: > The IRQF_DISABLED is a NOOP and has been scheduled for removal since > Linux v2.6.36 by commit 6932bf37bed4 ("genirq: Remove IRQF_DISABLED from > core code"). > > According to commit e58aa3d2d0cc ("genirq: Run irq handlers with > interrupts

[RESENT PATCH] spi: xilinx: Use standard num-cs binding

Use standard num-cs binding property and setup "xlnx,num-ss-bits" as deprecated. Signed-off-by: Michal Simek --- drivers/spi/spi-xilinx.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/spi/spi-xilinx.c b/drivers/spi/spi-xilinx.c index

Re: [PATCH v3 5/9] mtd: pxa3xx_nand: add support for the Marvell Berlin nand controller

Thomas, On Thu, Mar 05, 2015 at 02:00:00PM +0100, Thomas Petazzoni wrote: > On Thu, 5 Mar 2015 12:31:21 +0100, Antoine Tenart wrote: > > > struct pxa3xx_nand_host { > > @@ -253,6 +258,12 @@ static struct pxa3xx_nand_flash builtin_flash_types[] > > = { > > { "512MiB 8-bit", 0xdc2c, 64,

Re: [PATCH] drivers: platform: parse IRQ flags from resources

Greg Kroah-Hartman writes: > On Wed, Feb 18, 2015 at 05:12:18PM +0100, Linus Walleij wrote: >> This fixes a regression from the net subsystem: >> After commit d52fdbb735c36a209f36a628d40ca9185b349ba7 >> "smc91x: retrieve IRQ and trigger flags in a modern way" >> a regression would appear on some

[PATCH v2] ARM: STi: Add STiH410 SoC support

This patch adds support to STiH410 SoC. Please note "st,stih410" is already present in device tree. The problem is that it is missing the entry in the match table, and so the L2 cache and other cpus than 0 don't get initialized. Signed-off-by: Fabrice Gasnier Acked-by: Maxime Coquelin ---

Re: [PATCH -next] cpuset: initialize cpuset a bit early

On Wed, Mar 04, 2015 at 05:09:33PM +0800, Zefan Li wrote: > Now we call ss->bind() in cgroup_init(), so cgroup_init() will > call cpuset_bind() and then the latter will access top_cpuset's > cpumask, which is NULL, because cpuset_init() is called after > cgroup_init() > > The simplest fix is to

[PATCH v3 wq/for-4.0-fixes] workqueue: fix hang involving racing cancel[_delayed]_work_sync()'s for PREEMPT_NONE

cancel[_delayed]_work_sync() are implemented using __cancel_work_timer() which grabs the PENDING bit using try_to_grab_pending() and then flushes the work item with PENDING set to prevent the on-going execution of the work item from requeueing itself. try_to_grab_pending() can always grab PENDING

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