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

On Mon, Nov 10, 2014 at 06:17:16PM +1100, Stephen Rothwell wrote: > Hi Josh, > > After merging the tiny tree, today's linux-next build (powerpc64 allnoconfig) > failed like this: > > arch/powerpc/kernel/built-in.o: In function `sys_call_table': > (.rodata+0xd58): undefined reference to

Re: Early test: hangs in mm/compact.c w. Linus's 12d7aacab56e9ef185c

On 11/10/2014 07:07 AM, Joonsoo Kim wrote: On Sat, Nov 08, 2014 at 11:18:37PM +0100, Vlastimil Babka wrote: On 11/08/2014 02:11 PM, P. Christeas wrote: Hi, I think I finally found the cause by staring into the code... CCing people from all 4 separate threads I know about this issue. The

crypto: zeroization of sensitive data in af_alg

Hi Herbert, while working on the AF_ALG interface, I saw no active zeroizations of memory that may hold sensitive data that is maintained outside the kernel crypto API cipher handles. I think the following memory segments fall under that category: * message digest * IV

Re: [PATCH v2 01/11] crypto: Documentation - crypto API high level spec

Am Mittwoch, 5. November 2014, 18:15:12 schrieb Tadeusz Struk: Hi Tadeusz, > Hi, > > On 11/02/2014 12:35 PM, Stephan Mueller wrote: > > + * type: > > + - blkcipher for symmetric block ciphers > > blkcipher for synchronous block ciphers > > > + - ablkcipher for asymmetric

Re: [PATCH] n_tty: Add memory barrier to fix race condition in receive path

On Thu, Nov 6, 2014 at 9:56 PM, Greg Kroah-Hartman wrote: > On Thu, Nov 06, 2014 at 08:49:01PM +, Måns Rullgård wrote: >> Greg Kroah-Hartman writes: >> >> > On Thu, Nov 06, 2014 at 12:39:59PM +0100, Christian Riesch wrote: >> >> The current implementation of put_tty_queue() causes a race

Re: [f2fs-dev] [PATCH] f2fs: implement -o dirsync

On Sun, Nov 09, 2014 at 10:24:22PM -0800, Jaegeuk Kim wrote: > If a mount option has dirsync, we should call checkpoint for all the directory > operations. > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/namei.c | 24 > 1 file changed, 24 insertions(+) > > diff --git

Re: [PATCH] mfd: qcom-spmi-pmic: Add support for more chips versions

Hi Gilad, On Fri, 2014-11-07 at 17:08 -0700, Gilad Avidov wrote: > On 11/6/2014 12:54 AM, Ivan T. Ivanov wrote: > > On Wed, 2014-11-05 at 17:36 -0800, Bjorn Andersson wrote: > > > On Wed, Nov 5, 2014 at 10:31 AM, Ivan T. Ivanov > > > wrote: > > > > On Wed, 2014-11-05 at 10:11 -0800, Bjorn

Re: typo of the comment

* john_gong wrote: > hi Paolo, > i find a typo of the comment. > > > From 09d5df31f0930e8e3eb10ad60a3debc53d6ce992 Mon Sep 17 00:00:00 2001 > From: john_gong > Date: Fri, 7 Nov 2014 07:32:17 +0800 > Subject: [PATCH] modify a typo of the comment > > Signed-off-by: john_gong > --- >

Re: [PATCH 1/3] perf tools: Allow vmlinux to fallback to kallsyms on NO_LIBELF=1

Hi David, On Fri, 07 Nov 2014 08:21:16 -0700, David Ahern wrote: > On 11/6/14, 10:20 PM, Namhyung Kim wrote: >> It worked w/o libelf, but recent change to use vmlinux for kernel >> symbols break it. > > Do you know the recent change (commit id) that broke it? Nope. I tried to find it but failed

Re: [f2fs-dev] [PATCH 4/5] f2fs: write node pages if checkpoint is not doing

On Sat, Nov 08, 2014 at 11:36:08PM -0800, Jaegeuk Kim wrote: > It needs to write node pages if checkpoint is not doing in order to avoid > memory pressure. > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/node.c | 10 ++ > 1 file changed, 6 insertions(+), 4 deletions(-) > > diff --git

Re: [PATCH v5 00/24] AMDKFD Kernel Driver

On 11/10/2014 04:34 AM, Dave Airlie wrote: On 9 November 2014 04:37, Oded Gabbay wrote: Hi, Here is the v5 patch set of amdkfd. This version is released several days ahead of the release of AMD's HSA Runtime library as Open Source. Coupled with the modification that Thomas Stellard did for

Re: [PATCH 1/4] inet: Add skb_copy_datagram_iter

From: Al Viro Date: Mon, 10 Nov 2014 06:58:17 + > On Mon, Nov 10, 2014 at 12:20:20AM -0500, David Miller wrote: >> From: Al Viro >> Date: Sun, 9 Nov 2014 21:19:08 + >> >> > 1) does sparc64 access_ok() need to differ for 32bit and 64bit tasks? >> >> sparc64 will just fault no matter

[PATCH v2 4/5] power: rt5033_charger: Add RT5033 charger device driver

This patch add device driver of Richtek RT5033 PMIC. The driver support switching charger. rt5033 charger provide three charging mode. Three charging mode are pre charge mode, fast cahrge mode and constant voltage mode. They are have vary charge rate, charge parameters. The charge parameters can

[PATCH v2 0/5] mfd: rt5033: Add Richtek RT5033 drivers

This patchset adds driver for Richtek rt5033 chip The chip contains switching charge mode Li-Ion/Li-Polymer battery charger, fuelgauge, regulators. This patchset provides common support for accessing the device. This patchset have been tested base on exynos board. Changes in v2: - Remove

[PATCH v2 1/5] mfd: rt5033: Add Richtek RT5033 driver core.

This patch adds a new driver for Richtek RT5033 driver. RT5033 is a Multifunction device which includes battery charger, fuel gauge, flash LED current source, LDO and synchronous Buck converter. It is interfaced to host controller using I2C interface. Cc: Samuel Ortiz Cc: Lee Jones

Re: [PATCH] ALSA: korg1212: cleanup of printk

hi Takashi, I have a doubt regarding this korg1212. snd_korg1212_free_pcm is just making korg1212->pcm as NULL. But are we not supposed to release the allocated memory ? in snd_pcm_new we are allocating memory. thanks sudip -- To unsubscribe from this list: send the line "unsubscribe

[PATCH v2 2/5] regulator: rt5033: Add RT5033 Regulator device driver

This patch add device driver of Richtek RT5033 PMIC. The driver support multiple regulator like LDO and synchronous Buck. The integrated synchronous buck converter is designed to provide 0.6 A application with high efficiency. Two LDOs are integrated. One safe LDO is for 60mA and the other one LDO

[PATCH v2 3/5] power: rt5033_battery: Add RT5033 Fuel gauge device driver

This patch adds device driver of Richtek PMIC. The driver support battery fuel gange. Fuel gauge calculates and determines the battery state of charge(SOC) according to battery open circuit voltage(OCV). Also, this driver provides battery average voltage, voltage and bettery present property. Cc:

[PATCH v2 5/5] Documentation: Add documentation for rt5033 multifunction device

This patch device tree binding documentation for rt5033 multifunction device. Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian campbell Cc: Kumar Gala Signed-off-by: Beomho Seo Acked-by: Chanwoo Choi --- Changes in v2: - Revise binding documentation. ---

[PATCH] Input: xpad - update docs to reflect current state

The last time this documentation was accurate was just over 8 years ago. In this time we've added support for two new generations of Xbox console controllers and dozens of third-party controllers. This patch unifies terminology and makes it explicit which model of controller a sentence refers to.

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

Hi Josh, After merging the tiny tree, today's linux-next build (powerpc64 allnoconfig) failed like this: arch/powerpc/kernel/built-in.o: In function `sys_call_table': (.rodata+0xd58): undefined reference to `.compat_sys_adjtimex' arch/powerpc/kernel/built-in.o: In function `sys_call_table':

[PATCH] Makefile: allow building selected tests with non-NPTL toolchain

Some architectures are still stuck with non-NPTL toolchains. These are for example ARC, Blackfin, Xtensa etc. Still rt-tests are very good benchmarks and it would be good to enable use of at least selected (those that will be built) tests on those architectures. This change makes it possible to

[PATCH] ALSA: korg1212: cleanup of printk

replaced all references of the debug messages via printk with dev_* macro (mostly dev_dbg). one reference was changed to pr_err as there the card might have been uninitialized. while compiling after these modifications, we are getting three warnings in function snd_korg1212_create: 2301: warning:

[PATCH] slab: Fix compilation error in case of !CONFIG_NUMA

Move the definition of slab_free() outside of #ifdef CONFIG_NUMA since it is used by code which is not NUMA specific. Fixes the following error introduced by the following commit: 5da1c3c725ab slab: recharge slab pages to the allocating memory cgroup CC mm/slab.o

Re: [NOHZ] Remove scheduler_tick_max_deferment

On 6 November 2014 22:54, Christoph Lameter wrote: > We did not need to housekeeper in the dynticks idle case. What is so > different about dynticks busy? We do have a running task here and so the stats are important.. > I may not have the complete picture of the timer tick processing in my >

A recommendation from Support

Hello, Hey Friend, As you know, I’m always on the lookout for real ways to make decent money. Not just a measly $20 or $30 a day; I mean real money. $20,000 or $30,000 A DAY?!?! Now THAT is… DAMN GOOD REAL MONEY! His 6 figure

Re: [alsa-devel] [PATCH 1/3] ASoC: twl4030: don't report EBUSY if no change requested.

On 11/10/2014 01:45 AM, NeilBrown wrote: diff --git a/sound/soc/codecs/twl4030.c b/sound/soc/codecs/twl4030.c index b6b0cb399599..613b61cee081 100644 --- a/sound/soc/codecs/twl4030.c +++ b/sound/soc/codecs/twl4030.c @@ -957,6 +957,16 @@ static int snd_soc_put_twl4030_opmode_enum_double(struct

Re: [PATCH 1/4] inet: Add skb_copy_datagram_iter

On Mon, Nov 10, 2014 at 12:20:20AM -0500, David Miller wrote: > From: Al Viro > Date: Sun, 9 Nov 2014 21:19:08 + > > > 1) does sparc64 access_ok() need to differ for 32bit and 64bit tasks? > > sparc64 will just fault no matter what kind of task it is. > > It is impossible for a user task

Re: [PATCH 1/3] perf tools: Allow vmlinux to fallback to kallsyms on NO_LIBELF=1

On Fri, 7 Nov 2014 12:29:31 -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Nov 07, 2014 at 02:20:04PM +0900, Namhyung Kim escreveu: >> When libelf is not used, perf cannot not show symbol names since it >> doesn't access the ELF symbol table. But kernel is different as it >> can fallback to

Re: [Gta04-owner] [PATCH 2/3] ASoC: twl4030: allow voice port to be connected externally.

Am 10.11.2014 um 00:25 schrieb NeilBrown : > On Sat, 8 Nov 2014 09:26:22 + Mark Brown wrote: > >> On Sat, Nov 08, 2014 at 11:38:03AM +1100, NeilBrown wrote: >> >>> If voice port on twl4030 is not connected to a McBSP (or similar) >>> then we cannot configure the format the way we normally

Re: [rfc patch] mm: vmscan: invoke slab shrinkers for each lruvec

On Thu, Nov 06, 2014 at 06:50:28PM -0500, Johannes Weiner wrote: > The slab shrinkers currently rely on the reclaim code providing an > ad-hoc concept of NUMA nodes that doesn't really exist: for all > scanned zones and lruvecs, the nodes and available LRU pages are > summed up, only to have the

[PATCH] tty: pr_warning->pr_warn and logging neatening

Convert the pr_warning to the more common pr_warn. Other miscellanea: o Convert unusual PR_FMT define and uses to pr_fmt o Remove unnecessary OOM message o Fix grammar in an error message o Convert a pr_warning with a KERN_ERR to pr_err Signed-off-by: Joe Perches ---

Re: [PATCH 1/3] SMBUS: Add DeviceIDs for SunrisePoint LP

Hi Devin, On Fri, 07 Nov 2014 17:55:43 -0500, Devin Ryles wrote: > From 8386c61977dce52fcdfe7fb279692606f47650bc Mon Sep 17 00:00:00 2001 > From: Devin Ryles > Date: Wed, 5 Nov 2014 16:30:03 -0500 > Subject: [PATCH 1/3] SMBUS: Add DeviceIDs for SunrisePoint LP > > This patch adds the DeviceIDs

[PATCH 03/13] KVM: Add KVM_CAP_PI to detect VT-d Posted-Interrtups

This patch adds KVM_CAP_PI to detect VT-d Posted-Interrtups feature for QEMU. Signed-off-by: Feng Wu --- arch/x86/kvm/x86.c |4 include/uapi/linux/kvm.h |1 + 2 files changed, 5 insertions(+), 0 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index

[PATCH 04/13] iommu/vt-d: Adjust 'struct irte' to better suit for VT-d Posted-Interrupts

This patch adjusts the definition of 'struct irte', so that we can add the VT-d Posted-Interrtups format in this structure later. Signed-off-by: Feng Wu --- drivers/iommu/intel_irq_remapping.c | 35 +++ include/linux/dmar.h|4 ++-- 2 files

[PATCH 00/13] Add VT-d Posted-Interrupts support for KVM

VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt. With VT-d Posted-Interrupts enabled, external interrupts from direct-assigned devices can be delivered to guests without VMM intervention when guest is running in non-root mode. You can find the VT-d Posted-Interrtups Spec. in

[PATCH 10/13] KVM: Add the handler for Wake-up Vector

When VCPU is blocked and an external interrupts from assigned devices is delivered to it, VT-d Posted-Interrupts mechanism will deliver a interrrupt to the associated physical CPU with Wake-up Vector. In its handler, we find the destination VCPU and wake up it. Signed-off-by: Feng Wu ---

[PATCH 02/13] KVM: Initialize VT-d Posted-Interrtups Descriptor

This patch initialize the VT-d Posted-interrupt Descritpor. Signed-off-by: Feng Wu --- arch/x86/include/asm/irq_remapping.h |1 + arch/x86/kernel/apic/apic.c |1 + arch/x86/kvm/vmx.c | 56 - 3 files changed, 56 insertions(+),

[PATCH 01/13] iommu/vt-d: VT-d Posted-Interrupts feature detection

VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt. With VT-d Posted-Interrupts enabled, external interrupts from direct-assigned devices can be delivered to guests without VMM intervention when guest is running in non-root mode. This patch adds feature detection logic for VT-d

[PATCH 12/13] iommu/vt-d: No need to migrating irq for VT-d Posted-Interrtups

We don't need to migrate the irqs for VT-d Posted-Interrtups here. When 'pst' is set in IRTE, the associated irq will be posted to guests instead of interrupt remapping. The destination of the interrupt is set in Posted-Interrupts Descriptor, and the migration happens during VCPU scheduling.

[PATCH 05/13] KVM: Update IRTE according to guest interrupt configuration changes

When guest changes its interrupt configuration (such as, vector, etc.) for direct-assigned devices, we need to update the associated IRTE with the new guest vector, so external interrupts from the assigned devices can be injected to guests without VM-Exit. The current method of handling guest

[PATCH 11/13] KVM: Suppress posted-interrupt when 'SN' is set

Currently, we don't support urgent interrupt, all interrupts are recognized as non-urgent interrupt, so we cannot send posted-interrupt when 'SN' is set. Signed-off-by: Feng Wu --- arch/x86/kvm/vmx.c | 11 +-- 1 files changed, 9 insertions(+), 2 deletions(-) diff --git

[PATCH 09/13] KVM: Change NDST field after VCPU scheduling

This patch changes the NDST filed of Posted-Interrupts Descriptor after VCPU is scheduled to another physical CPU. Signed-off-by: Feng Wu --- arch/x86/kvm/vmx.c | 25 + 1 files changed, 25 insertions(+), 0 deletions(-) diff --git a/arch/x86/kvm/vmx.c

[PATCH 07/13] x86, irq: Define a global vector for VT-d Posted-Interrupts

Currently, we use a global vector as the Posted-Interrupts Notification Event for all the VCPUs in the system. We need to introduce another global vector for VT-d Posted-Interrtups, which will be used to wakeup the sleep VCPU when an external interrupt from a direct-assigned device happens for

Re: [RFC] ptrace: add generic SET_SYSCALL request

On 11/07/2014 09:27 PM, Will Deacon wrote: On Fri, Nov 07, 2014 at 12:03:00PM +, Arnd Bergmann wrote: On Friday 07 November 2014 11:55:51 Will Deacon wrote: On Fri, Nov 07, 2014 at 09:30:53AM +, Arnd Bergmann wrote: On Friday 07 November 2014 16:47:23 AKASHI Takahiro wrote: This

[PATCH 06/13] KVM: Add some helper functions for Posted-Interrupts

This patch adds three helper functions to manipulate the Posted- Interrtups Decriptor. Signed-off-by: Feng Wu --- arch/x86/kvm/vmx.c | 18 ++ 1 files changed, 18 insertions(+), 0 deletions(-) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index ae91b72..f4f 100644

[PATCH 08/13] KVM: Update Posted-Interrupts descriptor during VCPU scheduling

Update Posted-Interrupts descriptor according to the following rules: - Before VCPU block, set 'NV' to POSTED_INTR_WAKEUP_VECTOR - After VCPU block, set 'NV' back to POSTED_INTR_VECTOR Signed-off-by: Feng Wu --- arch/x86/include/asm/kvm_host.h |5 ++ arch/x86/kvm/vmx.c | 83

Re: [PATCH 2/3] perf symbol: Implement a very simple ELF symbol parser

Hi Arnaldo, On Fri, 7 Nov 2014 12:26:18 -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Nov 07, 2014 at 02:20:05PM +0900, Namhyung Kim escreveu: >> It'll be used to show (userspace) symbol names when libelf isn't (or >> cannot be) linked. > > Does this deals with prelink, etc? I believe so. :)

[PATCH 13/13] iommu/vt-d: Add a command line parameter for VT-d posted-interrupts

Enable VT-d Posted-Interrtups and add a command line parameter for it. Signed-off-by: Feng Wu --- drivers/iommu/irq_remapping.c |9 - 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/drivers/iommu/irq_remapping.c b/drivers/iommu/irq_remapping.c index 0e36860..3cb9429

linux-next: manual merge of the pinctrl tree with the arm-soc tree

Hi Linus, Today's linux-next merge of the pinctrl tree got a conflict in arch/arm/boot/dts/ste-nomadik-stn8815.dtsi between commit 2096eb80e446 ("ARM: nomadik: move GPIO I2C to S8815 board file") and 43c4034963d6 ("ARM: nomadik: set up MCDATDIR2") from the arm-soc tree and commits 68d41f23ce8d

Re: [PATCH 1/3] perf tools: Allow vmlinux to fallback to kallsyms on NO_LIBELF=1

Hi Peter, On Fri, 7 Nov 2014 18:37:18 +0100, Peter Zijlstra wrote: > On Fri, Nov 07, 2014 at 11:57:39PM +0900, Namhyung Kim wrote: > >> > Why does this live in the minimal implementation; should we not always >> > discard ELF files with 0 symbols? >> > >> > Suppose I have a vmlinux but removed

linux-next: manual merge of the pinctrl tree with the driver-core tree

Hi Linus, Today's linux-next merge of the pinctrl tree got a conflict in drivers/pinctrl/pinctrl-rockchip.c between commit 9198f509c888 ("pinctrl: rockchip: add suspend/resume functions") from the driver-core tree and commit 5c759d73b022 ("pinctrl: drop owner assignment from platform_drivers")

RE: linux-next: build failure after merge of the scsi tree

Fix for this was sent out on thursday itself, but does not seem to be applied yet : http://marc.info/?l=linux-scsi=141529629911520=2 From: Stephen Rothwell [s...@canb.auug.org.au] Sent: Sunday, November 09, 2014 10:15 PM To: James Bottomley Cc:

[PATCH] f2fs: implement -o dirsync

If a mount option has dirsync, we should call checkpoint for all the directory operations. Signed-off-by: Jaegeuk Kim --- fs/f2fs/namei.c | 24 1 file changed, 24 insertions(+) diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c index 6312dd2..db3ee09 100644 ---

Re: [PATCH] cpufreq: respect the min/max settings from user space

Hi Viresh, Just sent v2 with your ACK. :) Hi Rafael, Could you please apply the v2? Thanks! Vince On 11/10/2014 01:09 PM, Viresh Kumar wrote: On 28 October 2014 08:55, Vince Hsu wrote: Hi Viresh, Could you remind me where can I find this patch upstream? It seems this was missed? Rafael

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

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/cxgbi/cxgb4i/cxgb4i.c: In function 'do_abort_req_rss': drivers/scsi/cxgbi/cxgb4i/cxgb4i.c:942:3: error: too many arguments to function 'send_tx_flowc_wr'

[PATCH V2] cpufreq: respect the min/max settings from user space

When the user space tries to set scaling_(max|min)_freq through sysfs, the cpufreq_set_policy() asks other driver's opinions for the max/min frequencies. Some device drivers, like Tegra CPU EDP which is not upstreamed yet though, may constrain the CPU maximum frequency dynamically because of board

Re: [PATCH 14/18] perf tools: Make vmlinux short name more like kallsyms short name

Hi Jiri, On Sun, 9 Nov 2014 08:51:26 +0100, Jiri Olsa wrote: > On Thu, Nov 06, 2014 at 06:04:35PM -0300, Arnaldo Carvalho de Melo wrote: >> From: Namhyung Kim >> >> The previous patch changed kernel dso name from '[kernel.kallsyms]' to >> vmlinux. However it might add confusion to old users

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

On Mon, Nov 10, 2014 at 04:53:16PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the char-misc tree got a conflict in > drivers/Makefile between commit 83e0abae ("staging: android: > binder: move to the "real" part of the kernel") from the staging tree and > commit

Re: Early test: hangs in mm/compact.c w. Linus's 12d7aacab56e9ef185c

On Sat, Nov 08, 2014 at 11:18:37PM +0100, Vlastimil Babka wrote: > On 11/08/2014 02:11 PM, P. Christeas wrote: > > On Thursday 06 November 2014, Vlastimil Babka wrote: > >>> On Wednesday 05 November 2014, Vlastimil Babka wrote: > Can you please try the following patch? > -

Re: AMR: sun7i: CPU hotplug support?

On 2014-11-10 00:17, Maxime Ripard wrote: > Hi Jan, > > On Sun, Nov 09, 2014 at 08:35:49PM +0100, Jan Kiszka wrote: >> did anyone already happen to look into enabling CPU hotplug for the >> Allwinner A20 in upstream? I'm currently running the sunxi-next branch >> on Banana Pi, and echo 0 >

[PATCH 2/2] ARM: multi_v7_defconfig: Enable Broadcom Cygnus

From: Ray Jui Enable Broadcom Cygnus platform support in multi_v7_defconfig Signed-off-by: Ray Jui Signed-off-by: Scott Branden --- arch/arm/configs/multi_v7_defconfig | 18 ++ 1 file changed, 18 insertions(+) diff --git a/arch/arm/configs/multi_v7_defconfig

[PATCH 1/2] ARM: multi_v7_defconfig: remove one level of menu from Kconfig

remove menu "Broadcom Mobile SoC Selection" This requires: - selecting ARCH_BCM_MOBILE based on SoC selections - fixup multi_v7_defconfig to work with new menu levels of mach-bcm. Signed-off-by: Scott Branden --- arch/arm/configs/multi_v7_defconfig | 3 ++- 1 file changed, 2 insertions(+), 1

[LKP] [sched] 9597d64116d: -16.1% hackbench.throughput

FYI, we noticed the below changes on https://git.linaro.org/people/mturquette/linux.git eas-next commit 9597d64116d0d441dea32e7f5f05fa135d16f44b ("sched: replace capacity_factor by usage") b57a1e0afff2cbac 9597d64116d0d441dea32e7f5f testbox/testcase/testparams

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

Hi all, Today's linux-next merge of the char-misc tree got a conflict in drivers/Makefile between commit 83e0abae ("staging: android: binder: move to the "real" part of the kernel") from the staging tree and commit a06ae8609b3d ("coresight: add CoreSight core layer framework") from the

Re: [arc-linux-dev] Re: ARC backport for stable 3.14

On Monday 10 November 2014 08:55 AM, Greg Kroah-Hartman wrote: > On Wed, Oct 15, 2014 at 09:26:55AM +, Vineet Gupta wrote: >> Hi, >> >> Can you please apply the following mainline commits to 3.14 stable (in the >> order below) >> >> c3441edd2dea ARC: [SMP] General Fixes > That commit doesn't

[RFC 1/2] sched/fair: Add cumulative average of load_avg_contrib to a task

This patch aims to identify a suitable metric which can define the nature of the task as CPU intensive or non-intensive. This metric's value will be used to optimize the logic to scale CPU frequency during an idle wakeup scenario i.e., to make the cpufreq governor to scale the frequency optimized

[RFC 2/2] cpufreq: governor: CPU frequency scaled from task's cumulative-load on an idle wakeup

"18b46a cpufreq: governor: Be friendly towards latency-sensitive bursty workloads" patch by Srivatsa tried to solve a problem in cpufreq governor's CPU load calculation logic. The fix is to detect wakeup from cpuidle scenario and to start the workload at reasonably high frequency and thus avoiding

[RFC 0/2] CPU frequency scaled from a task's load on an idle wakeup

This patch set aims to solve a problem in cpufreq governor's CPU load calculation logic when the CPU wakes up after an idle period. In the current logic when a CPU wakes up from an idle state the 'previous load' of the CPU is used as its current load on the alternate wakeups. A

Re: [PATCH 5/5] Documentation: Add documentation for rt5033 multifunction device

Thank you for your advice. I'll fix them and send v2 patch soon. On 11/07/2014 07:34 PM, Mark Brown wrote: > On Fri, Nov 07, 2014 at 11:52:07AM +0900, Beomho Seo wrote: > >> +Required properties: >> +- compatible = Must be "richtek,rt5033-regulator" >> + >> +regulators { >> +

[LKP] [sunrpc] WARNING: CPU: 1 PID: 1890 at lib/list_debug.c:36 __list_add+0xcb/0xd0()

FYI, we noticed a wraning changes on git://git.samba.org/jlayton/linux svc-pool-lock commit 3a41085d37f2374f6ae6539f5dca3d1d53e50431 ("sunrpc: search for a thread under RCU") <5>[ 21.635477] Key type id_legacy registered <4>[ 21.638149] [ cut here ] <4>[ 21.638359]

[no subject]

3.5% WONGA LOANS OFFER.pdf Description: Adobe PDF document

[LKP] [x86, irq] BUG: kernel boot hang

FYI, we noticed the below changes on https://github.com/jiangliu/linux.git irqdomain/p4v1 commit e530b4be849e7c865c95f25008eb52b72ec96341 ("x86, irq: Use cached IOAPIC entry instead of reading from hardware") +--+++ | |

Re: linux-next: manual merge of the driver-core tree with the sound-asoc tree

On Mon, Nov 10, 2014 at 03:51:42PM +1100, Stephen Rothwell wrote: > Hi Greg, > > On Mon, 10 Nov 2014 13:38:53 +0900 Greg KH wrote: > > > > On Mon, Nov 10, 2014 at 03:31:32PM +1100, Stephen Rothwell wrote: > > > > > > Today's linux-next merge of the driver-core tree got a conflict in > > >

Re: linux-next: manual merge of the tty tree with the tty.current tree

On Mon, Nov 10, 2014 at 03:49:58PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the tty tree got a conflict in > drivers/tty/serial/8250/8250_mtk.c between commit cd92208f6996 ("tty: > serial: 8250_mtk: Fix quot calculation") from the tty.current tree and > commit

[PATCH] AHCI: Add generic MSI-X interrupt support to SATA PCI driver

From: Sunil Goutham This patch adds generic support for MSI-X interrupts to the SATA PCI driver. Only single interrupt support is implemented. Thus, per-port interrupts can not yet be enabled. The driver now checks the device for the existence of MSI-X and tries to enable the interrupt.

Re: [PATCH/RFC] workqueue: allow rescuer thread to do more work.

On Fri, 7 Nov 2014 11:03:40 +0800 Lai Jiangshan wrote: > > > On 11/07/2014 12:58 AM, Dongsu Park wrote: > > Hi Tejun & Neil, > > > > On 04.11.2014 09:22, Tejun Heo wrote: > >> On Thu, Oct 30, 2014 at 10:19:32AM +1100, NeilBrown wrote: > Given that workder

RE: [PATCH net-next v2 2/3] r8152: cleartheflagofSCHEDULE_TASKLETintasklet

Francois Romieu [mailto:rom...@fr.zoreil.com] > Sent: Sunday, November 09, 2014 6:12 AM [...] > The performance explanation leaves me a bit unconvinced. Without any > figure one could simply go for the always locked clear_bit because of: > 1. the "I'm racy" message that the open-coded test + set

Re: [PATCH 1/4] inet: Add skb_copy_datagram_iter

From: Al Viro Date: Sun, 9 Nov 2014 21:19:08 + > 1) does sparc64 access_ok() need to differ for 32bit and 64bit tasks? sparc64 will just fault no matter what kind of task it is. It is impossible for a user task to generate a reference to a kernel virtual address, as kernel and user

Re: [f2fs-dev] [PATCH 3/5] f2fs: control the memory footprint used by ino entries

On Mon, Nov 10, 2014 at 12:28:34PM +0900, Changman Lee wrote: > On Sat, Nov 08, 2014 at 11:36:07PM -0800, Jaegeuk Kim wrote: > > This patch adds to control the memory footprint used by ino entries. > > This will conduct best effort, not strictly. > > > > Signed-off-by: Jaegeuk Kim > > --- > >

Re: [PATCH v8 4/8] ARM: dts: Enable Broadcom Cygnus SoC

On 14-11-09 12:38 PM, Arnd Bergmann wrote: On Sunday 09 November 2014 09:23:11 Greg Kroah-Hartman wrote: On Sat, Nov 08, 2014 at 10:49:09PM -0800, Olof Johansson wrote: +/* + * Copyright 2014 Broadcom Corporation. All rights reserved. + * + * Unless you and Broadcom execute a separate written

Re: [RFC] Add of_path property for all devices with a node

On Fri, 2014-11-07 at 17:35 +1100, Benjamin Herrenschmidt wrote: > On Fri, 2014-11-07 at 17:33 +1100, Benjamin Herrenschmidt wrote: > > > So I came up with this patch, > > And here is the actual patch, which might help :-) It's pretty trivial > and small... So not much reactions here .. a bit

Re: [PATCH] mmc: wmt-sdmmc: fix unmatched release_mem_region

2014-11-10 1:18 GMT+03:00 lautriv : > On 11/09/2014 10:55 PM, Fabio Estevam wrote: >> >> On Sun, Nov 9, 2014 at 7:12 PM, Alexey Charkov wrote: >> >>> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); >>> + if (!res) { >>> + ret = -ENODEV; >>> + goto

Re: [PATCH v2 6/6] drivers: soc: samsung: Add support for Exynos7 pmu

On Sat, Nov 8, 2014 at 11:05 PM, Pankaj Dubey wrote: > Hi Amit, > > On 8 November 2014 18:46, Amit Daniel Kachhap wrote: >> Add PMU settings for exynos7. This is required for future suspend-to-ram, >> cpuidle and power domain support. >> >> Note: In this patch some static declarations lines are

Re: [PATCH] cpufreq: respect the min/max settings from user space

On 28 October 2014 08:55, Vince Hsu wrote: > Hi Viresh, > > Could you remind me where can I find this patch upstream? It seems this was > missed? Rafael hasn't picked it up. You can normally look at the tree Rafael manages: git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git Can

linux-next: manual merge of the usb-gadget tree with the driver-core tree

Hi Felipe, Today's linux-next merge of the usb-gadget tree got a conflict in drivers/usb/gadget/udc/pxa27x_udc.c between commit 6d3f5f2d895b ("usb: gadget: udc: drop owner assignment from platform_drivers") from the driver-core tree and commit 1803fe15ad54 ("usb: gadget: pxa27x_udc: add

Re: [PATCH v2 2/6] drivers: soc: Add support for Exynos PMU driver

On Sat, Nov 8, 2014 at 10:45 PM, Pankaj Dubey wrote: > Hi Amit, > > On 8 November 2014 18:46, Amit Daniel Kachhap wrote: >> This patch moves Exynos PMU driver implementation from "arm/mach-exynos" >> to "drivers/soc/samsung". This driver is mainly used for setting misc bits of >> register from

Re: linux-next: build failure after merge of the slave-dma tree

On Mon, Nov 10, 2014 at 11:58:46AM +1100, Stephen Rothwell wrote: > Hi Vinod, > > After merging the slave-dma tree, today's linux-next build (x86_64 > allmodconfig) > failed like this: > > drivers/dma/at_xdmac.c: In function 'at_xdmac_off': > drivers/dma/at_xdmac.c:317:2: error: implicit

Re: [PATCH 1/1] perf tools: perf diff for different binaries

Hi Kan, On Thu, 6 Nov 2014 14:16:23 +, Kan Liang wrote: > The diff code doesn’t define event_op mmap2, so it fails to get the symbol. Looks like a bug in perf diff code. (It's too easy to miss... :-/ ) > You are right, it’s ip address. The meaning of symbol for diff and report > should >

Re: [PATCH v2 3/6] drivers: soc: samsung: Fix a spelling mistake

On Sat, Nov 8, 2014 at 9:26 PM, Pankaj Dubey wrote: > Hi Amit, > > > On 8 November 2014 18:46, Amit Daniel Kachhap wrote: >> This patches changes the name of exynos5_list_diable_wfi_wfe to >> exynos5_list_disable_wfi_wfe. >> > > Same change I have posted earlier [1] and Kukjin has taken same in

Re: [PATCH] cpufreq: qoriq: Make the driver usable on all QorIQ platforms

On 27 October 2014 09:09, Yuantian Tang wrote: > Do we have a conclusion yet? No. You can keep your initial duplication of Kconfig entries for the time being. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More

Re: [PATCH] x86, kvm, vmx: Always use LOAD_IA32_EFER if available

Hi Andy, On Fri, Nov 07, 2014 at 06:25:18PM -0800, Andy Lutomirski wrote: >At least on Sandy Bridge, letting the CPU switch IA32_EFER is much >faster than switching it manually. > >I benchmarked this using the vmexit kvm-unit-test (single run, but >GOAL multiplied by 5 to do more iterations): >

Re: linux-next: manual merge of the driver-core tree with the pm tree

On Mon, Nov 10, 2014 at 03:18:56PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the driver-core tree got a conflict in > drivers/input/keyboard/gpio_keys_polled.c between commit b26d4e2283b6 > ("input: gpio_keys_polled: Make use of device property API") from the > pm

Re: linux-next: manual merge of the driver-core tree with the l2-mtd tree

On Mon, Nov 10, 2014 at 03:28:01PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the driver-core tree got a conflict in > drivers/mtd/devices/docg3.c between commit a59459f29fb7 ("mtd: docg3: > add device-tree support") from the l2-mtd tree and commit c37c1e160546 >

Re: linux-next: manual merge of the driver-core tree with the mfd tree

On Mon, Nov 10, 2014 at 03:24:26PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the driver-core tree got a conflict in > drivers/mfd/syscon.c between commit d4ad08b424c1 ("mfd: syscon: > Decouple syscon interface from platform devices") from the mfd tree and > commit

Re: linux-next: manual merge of the driver-core tree with the tree

On Mon, Nov 10, 2014 at 03:21:25PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the driver-core tree got a conflict in > drivers/leds/leds-gpio.c between commit a43f2cbbb009 ("leds: leds-gpio: > Make use of device property API") from the tree and commit >

Re: [PATCH v5 12/16] cpufreq: tegra: Rename tegra-cpufreq to tegra20-cpufreq

On 24 October 2014 20:09, Mikko Perttunen wrote: > From: Tuomas Tynkkynen > > The Tegra124 will use a different driver for frequency scaling, so > rename the old driver (which handles only Tegra20) appropriately. > > Signed-off-by: Tuomas Tynkkynen > Signed-off-by: Mikko Perttunen > --- >

Re: linux-next: manual merge of the driver-core tree with the sound-asoc tree

Hi Greg, On Mon, 10 Nov 2014 13:38:53 +0900 Greg KH wrote: > > On Mon, Nov 10, 2014 at 03:31:32PM +1100, Stephen Rothwell wrote: > > > > Today's linux-next merge of the driver-core tree got a conflict in > > sound/soc/intel/sst-haswell-pcm.c between commit 2e4f75919e5a ("ASoC: > > Intel: Add PM

Re: linux-next: manual merge of the driver-core tree with the sound-asoc tree

On Mon, Nov 10, 2014 at 03:31:32PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the driver-core tree got a conflict in > sound/soc/intel/sst-haswell-pcm.c between commit 2e4f75919e5a ("ASoC: > Intel: Add PM support to HSW/BDW PCM driver") from the sound-asoc tree >

linux-next: manual merge of the tty tree with the tty.current tree

Hi Greg, Today's linux-next merge of the tty tree got a conflict in drivers/tty/serial/8250/8250_mtk.c between commit cd92208f6996 ("tty: serial: 8250_mtk: Fix quot calculation") from the tty.current tree and commit 2a768264eef0 ("tty: serial: Fix mediatek UART driver setting baudrate issue")

  1   2   3   4   5   6   7   8   >