Re: [patch 00/13] irqchip: spear_shirq: Cleanup the bitrot

On Fri, Jun 20, 2014 at 2:50 PM, Viresh Kumar wrote: > For 1-7, 10 & 11 > > Acked-by: Viresh Kumar This is applicable to 8-9, 12-13 as well. I couldn't find any documentation which has Ack registers for SPEAr320.. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the

Build regressions/improvements in v3.16-rc2

Below is the list of build error/warning regressions/improvements in v3.16-rc2[1] compared to v3.15-rc8[2]. Summarized: - build errors: +80/-6 - build warnings: +94/-70 JFYI, when comparing v3.16-rc2[1] to v3.16-rc1[3], the summaries are: - build errors: +1/-6 - build warnings: +26/-313

Re: [PATCH 2/4] Documentation: devicetree: Fix s2mps11 example syntax

On Mon, 23 Jun 2014, Andreas Färber wrote: > It's <1>, not 1. > > Signed-off-by: Andreas Färber > --- > Documentation/devicetree/bindings/mfd/s2mps11.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Applied, thanks. > diff --git a/Documentation/devicetree/bindings/mfd/s2mps11.txt

Re: [PATCH 1/4] Documentation: devicetree: Fix s2mps11 and s5m8767 typos

On Mon, 23 Jun 2014, Andreas Färber wrote: > It's LDO2, not LD02. > > Signed-off-by: Andreas Färber > --- > Documentation/devicetree/bindings/mfd/s2mps11.txt | 2 +- > Documentation/devicetree/bindings/regulator/s5m8767-regulator.txt | 2 +- > 2 files changed, 2 insertions(+), 2

[PATCH V2 4/5] hrtimer: Kick lowres dynticks targets on timer enqueue

In lowres mode, hrtimers are serviced by the tick instead of a clock event. It works well as long as the tick stays periodic but we must also make sure that the hrtimers are serviced in dynticks mode targets, pretty much like timer list timers do. Note that all dynticks modes are concerned: get_no

Re: [PATCH 1/2] perf/x86: update Haswell PEBS event constraints

On Mon, Jun 23, 2014 at 9:14 AM, Peter Zijlstra wrote: > On Thu, Jun 19, 2014 at 11:00:28AM -0700, Andi Kleen wrote: >> However these days I'm actually thinking of just getting >> rid of the detailed table except for PREC_DIST. All the PEBS >> controls should be noops if the event does not support

Re: [PATCH 2/2] drivers/net/usb/asix_devices.c: inline ax88772_unbind

On Fri, 2014-06-20 at 22:40 +0200, Fabian Frederick wrote: > inline this one line function used in driver_info structure That precisely is this the reason not to inline this. It is used as a function pointer. gcc must generate a non-inlined version of the function. Your patch has zero effect and

[PATCH] crypto: caam - Add definition of rd/wr_reg64 for little endian platform

CAAM IP has certain 64 bit registers . 32 bit architectures cannot force atomic-64 operations. This patch adds definition of these atomic-64 operations for little endian platforms. The definitions which existed previously were for big endian platforms. Signed-off-by: Ruchika Gupta --- Tested on

Re: [PATCH net-next] hyperv: Add handler for RNDIS_STATUS_NETWORK_CHANGE event

On Fri, Jun 20, Haiyang Zhang wrote: > This command ("/etc/init.d/network restart") exists on our supported distros > currently. We will also look into some better ways to refresh the network for > the distros without this command. I have tried setting IF_OPER_DORMANT then > IF_OPER_UP, but not w

[PATCH 4/7] tools lib traceevent: Fix and cleanup kvm_nested_vmexit tracepoints

From: Jan Kiszka Fix several issues of kvm_nested_vmexit[_inject]: field width aren't supported with pevent_print, rip was printed twice/incorrectly, SVM ISA was hard-coded, we don't use ':' to separate field names. Link: http://lkml.kernel.org/r/8e6c02b22ea8136c139a91c69d6cc73b8c5c184b.1388855

[PATCH 3/7] tools lib traceevent: Add back in kvm plugins nested_vmexit events

From: "Steven Rostedt (Red Hat)" The nested vmexit events were removed from the backport from trace-cmd because they were considered buggy. They have since been updated in trace-cmd but are still missing from the traceevent library. Add back in the buggy version to be able to backport the fixes.

[GIT PULL 0/7] perf/core improvements and fixes

hi Ingo, please consider pulling thanks, jirka The following changes since commit 4ba96195051be30160af6d5f5f83f9a055ab1f23: Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf into perf/core (2014-06-13 08:19:06 +0200) are available in the git reposi

[PATCH 7/7] tools lib traceevent: Clean up format of args in jbd2 plugin

From: Steven Rostedt While synchronizing what's in trace-cmd vs what's in perf, I came across a change that was made when entering the jbd2 plugin into the tools/lib/traceevent directory. For example, one of the function prototypes went from: unsigned long long process_jbd2_dev_to_name(struct tr

[PATCH 2/7] tools lib traceevent: Factor out print_exit_reason in kvm plugin

From: Jan Kiszka We will reuse it for nested vmexit tracepoints. Link: http://lkml.kernel.org/r/619c418c8af87f03027b8c8013b0443996605700.1388855989.git.jan.kis...@web.de Acked-by: Namhyung Kim Signed-off-by: Jan Kiszka Signed-off-by: Steven Rostedt Signed-off-by: Jiri Olsa --- tools/lib/t

[PATCH 5/7] tools lib traceevent: Fix format in plugin_kvm

From: Steven Rostedt The format field argument passed to the format in pevent_print_num_field() will be of type long long. That means that %ll must be used instead of %l. Acked-by: Namhyung Kim Reported-by: Namhyung Kim Signed-off-by: Steven Rostedt Link: http://lkml.kernel.org/r/201406131031

[PATCH 6/7] tools lib traceevent: Clean up format of args in cfg80211 plugin

From: Steven Rostedt While synchronizing what's in trace-cmd vs what's in perf, I came across a change that was made when entering the cfg80211 plugin into the tools/lib/traceevent directory. The function prototype went from: static unsigned long long process___le16_to_cpup(struct trace_seq *s,

[PATCH 1/7] tools lib traceevent: Report unknown VMX exit reasons with code

From: Jan Kiszka Allows to parse the result even if the KVM plugin does not yet understand a specific exit code. Link: http://lkml.kernel.org/r/5207446f.1090...@web.de Acked-by: Namhyung Kim Signed-off-by: Jan Kiszka Signed-off-by: Steven Rostedt Signed-off-by: Jiri Olsa --- tools/lib/trac

Re: [PATCH] ARM: mvebu: rename ARM_ERRATA_753970

On Fri, 2014-06-20 at 17:10 -0400, Jason Cooper wrote: > On Fri, Jun 20, 2014 at 10:42:57PM +0200, Paul Bolle wrote: > > Jason Cooper schreef op vr 20-06-2014 om 16:21 [-0400]: > > > It looks like rmk just added a patch to fixing the selection of the > > > erratas. Could you please take a look and

[PATCH 06/11] usb: dwc2/gadget: ensure that all fifos have correct memory buffers

From: Marek Szyprowski Print warning if FIFOs are configured in such a way that they don't fit into the SPRAM available on the s3c hsotg module. Signed-off-by: Marek Szyprowski Signed-off-by: Robert Baldyga --- drivers/usb/dwc2/core.h | 1 + drivers/usb/dwc2/gadget.c | 15 ++-

Re: [PATCH -tip v2 2/3] ftrace, kprobes: Support IPMODIFY flag to find IP modify conflict

(2014/06/20 11:48), Steven Rostedt wrote: > On Tue, 17 Jun 2014 11:04:49 + > Masami Hiramatsu wrote: > >> Introduce FTRACE_OPS_FL_IPMODIFY to avoid conflict among >> ftrace users who may modify regs->ip to change the execution >> path. This also adds the flag to kprobe_ftrace_ops, since >> ft

[PATCH 2/2] perf symbols: Get kernel start address by symbol name

From: Simon Que The function machine__get_kernel_start_addr() was taking the first symbol of kallsyms as the start address. This is incorrect in certain cases where the first symbol is something at 0, while the actual kernel functions begin at a later point (e.g. 0x8020). This patch fixes ma

[PATCH 11/11] usb: dwc2/gadget: disable clock when it's not needed

When device is stopped or suspended clock is not needed so we can disable it for this time. Signed-off-by: Robert Baldyga --- drivers/usb/dwc2/gadget.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c index 2a7c014..0523bc3 100644

[GIT PULL 0/2] perf/urgent fixes

hi Ingo, please consider pulling thanks, jirka The following changes since commit cf230918cda19532e4a5cc4f0d5c82fa7e5e94f6: Merge branch 'perf/core' into perf/urgent, to pick up the latest fixes (2014-06-14 14:10:08 +0200) are available in the git repository at: git://git.kernel.org/pub

[PATCH 09/11] usb: dwc2/gadget: delay enabling irq once hardware is configured properly

From: Marek Szyprowski This patch fixes kernel panic/interrupt storm/etc issues if bootloader left s3c-hsotg module in enabled state. Now interrupt handler is enabled only after proper configuration of hardware registers. Signed-off-by: Marek Szyprowski Signed-off-by: Robert Baldyga --- drive

[PATCH 10/11] usb: dwc2/gadget: assign TX FIFO dynamically

Because we have not enough memory to have each TX FIFO of size at least 3072 bytes (the maximum single packet size), we create four FIFOs of lenght 1024, and four of length 3072 bytes, and assing them to endpoints dynamically according to maxpacket size value of given endpoint. Signed-off-by: Robe

[PATCH 08/11] usb: dwc2/gadget: do not call disconnect method in pullup

From: Marek Szyprowski This leads to potential spinlock recursion in composite framework, other udc drivers also don't call it directly from pullup method. Signed-off-by: Marek Szyprowski Signed-off-by: Robert Baldyga --- drivers/usb/dwc2/gadget.c | 1 - 1 file changed, 1 deletion(-) diff --

[PATCH 07/11] usb: dwc2/gadget: break infinite loop in endpoint disable code

From: Marek Szyprowski This patch fixes possible freeze caused by infinite loop in interrupt context. Signed-off-by: Marek Szyprowski Signed-off-by: Robert Baldyga --- drivers/usb/dwc2/gadget.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/ga

[PATCH 1/2] perf tools: Fix segfault in cumulative.callchain report

When cumulative callchain mode is on, we could get samples with with no actual hits. This breaks the assumption of the annotation code, that each sample has annotation counts allocated and leads to segfault. Fixing this by additional checks for annotation stats. Acked-by: Namhyung Kim Acked-by:

Re: [PATCH 1/2] SCHED: remove proliferation of wait_on_bit action functions.

Acked-by: David Howells (fscache, keys) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] ARM: dts: exynos5410: Fill in CPU clock-frequency

On 06/22/2014 11:49 PM, Andreas Färber wrote: It's 1.6 GHz for the Cortex-A15. Avoids warnings like "/cpus/cpu@0 missing clock-frequency property". Signed-off-by: Andreas Färber --- arch/arm/boot/dts/exynos5410.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/e

[PATCH 05/11] usb: dwc2/gadget: hide some not really needed debug messages

From: Marek Szyprowski Some DWC2/s3c-hsotg debug messages are really useless for typical user, so hide them behind dev_dbg(). Signed-off-by: Marek Szyprowski Signed-off-by: Robert Baldyga --- drivers/usb/dwc2/gadget.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dri

[PATCH 04/11] usb: dwc2/gadget: Fix comment text

From: Andrzej Pietrasiewicz Adjust the debug text to the name of the printed variable. Signed-off-by: Andrzej Pietrasiewicz Signed-off-by: Robert Baldyga --- drivers/usb/dwc2/gadget.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/d

[PATCH 02/11] usb: dwc2/gadget: fix phy initialization sequence

From: Kamil Debski In the Generic PHY Framework a NULL phy is considered to be a valid phy thus the "if (hsotg->phy)" check does not give us the information whether the Generic PHY Framework is used. In addition to the above this patch also removes phy_init from probe and phy_exit from remove. T

[PATCH 03/11] usb: dwc2/gadget: move phy bus legth initialization

From: Kamil Debski This patch moves the part of code that initializes the PHY bus width. This results in simpler code and removes the need to check whether the Generic PHY Framework is used. Signed-off-by: Kamil Debski Signed-off-by: Marek Szyprowski Signed-off-by: Robert Baldyga --- drivers

[PATCH 00/11] usb: dwc2/gadget: fix series

Hello, This patchset contains fixes for dwc2 gadget driver. It touches PHY, FIFO configuration, initialization sequence and adds many other small fixes. Best regards Robert Baldyga Samsung R&D Institute Poland Andrzej Pietrasiewicz (1): usb: dwc2/gadget: Fix comment text Kamil Debski (3): u

[PATCH 01/11] usb: dwc2/gadget: fix phy disable sequence

From: Kamil Debski When the driver is removed s3c_hsotg_phy_disable is called three times instead of once. This results in decreasing of the phy reference counter below zero and thus consecutive inserts of the module fails. This patch removes calls to s3c_hsotg_phy_disable from s3c_hsotg_remove

Re: [patch 1/4] mm: vmscan: remove remains of kswapd-managed zone->all_unreclaimable

On Fri 20-06-14 12:33:47, Johannes Weiner wrote: > shrink_zones() has a special branch to skip the all_unreclaimable() > check during hibernation, because a frozen kswapd can't mark a zone > unreclaimable. > > But ever since 6e543d5780e3 ("mm: vmscan: fix do_try_to_free_pages() > livelock"), deter

[regression] fix 32-bit breakage in block device read(2) (was Re: 32-bit bug in iovec iterator changes)

On Sun, Jun 22, 2014 at 07:50:07AM -0400, Theodore Ts'o wrote: > On Sun, Jun 22, 2014 at 02:00:32AM +0100, Al Viro wrote: > > > > PS: I agree that it's worth careful commenting, obviously, but > > before sending it to Linus (*with* comments) I want to get a > > confirmation that this one-liner act

Re: [PATCH 1/2] perf/x86: update Haswell PEBS event constraints

On Thu, Jun 19, 2014 at 01:40:41PM -0700, Andi Kleen wrote: > On Thu, Jun 19, 2014 at 10:31:29PM +0200, Stephane Eranian wrote: > > On Thu, Jun 19, 2014 at 10:18 PM, Andi Kleen wrote: > > >> I don't quite understand that. > > >> You need to know which events support PEBS. You need a table > > > >

[PATCH 0/2] ARM: tegra: roth: pinmux fixes

Two small but important fixes to SHIELD's pinmux configuration. The use of invalid properties caused the pinmux to not be applied at all. Also the setting for sdmmc clock lines resulted in random errors or even the impossibility to probe attached devices. Alexandre Courbot (2): ARM: tegra: roth:

[PATCH 1/2] ARM: tegra: roth: fix unsupported pinmux properties

The pinmux subsystem complained that the nvidia,low-power-mode property is not supported by the sdio1, sdio3 and gma drive groups. In addition gma also does not support nvidia,drive-type. Remove these properties so the pinmux configuration can properly be applied. Signed-off-by: Alexandre Courbot

[PATCH 2/2] ARM: tegra: roth: enable input on mmc clock pins

Input had been disabled by mistake on these pins, leading to issues with SDIO devices like the Wifi module not being probed or random errors occuring on the SD card. Signed-off-by: Alexandre Courbot --- arch/arm/boot/dts/tegra114-roth.dts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(

Re: [patch 2/4] mm: vmscan: rework compaction-ready signaling in direct reclaim

On Fri 20-06-14 16:24:49, Johannes Weiner wrote: [...] > From cd48b73fdca9e23aa21f65e9af1f850dbac5ab8e Mon Sep 17 00:00:00 2001 > From: Johannes Weiner > Date: Wed, 11 Jun 2014 12:53:59 -0400 > Subject: [patch] mm: vmscan: rework compaction-ready signaling in direct > reclaim > > Page reclaim fo

Re: [PATCH V3 16/16] irqchip: crossbar: allow for quirky hardware with direct hardwiring of GIC

Hi Jason, On Saturday 21 June 2014 08:27 AM, Jason Cooper wrote: > On Mon, Jun 16, 2014 at 04:53:16PM +0530, Sricharan R wrote: >> From: Nishanth Menon >> >> On certain platforms such as DRA7, SPIs 0, 1, 2, 3, 5, 6, 10, 131, >> 132, 133 are direct wired to hardware blocks bypassing crossbar. >> T

Re: [PATCH V3 03/16] irqchip: crossbar: introduce ti,irqs-skip to skip

On Saturday 21 June 2014 08:03 AM, Jason Cooper wrote: > Sricharan, > > Your subject line seems truncated: > > "irqchip: crossbar: introduce ti,irqs-skip to skip" > > maybe "... Introduce DT property to skip hardwired irqs" ? > > Also note that you need to correct the subject line for *every*

Re: [PATCH v6 1/9] efi: Use early_mem*() instead of early_io*()

>>> On 20.06.14 at 23:29, wrote: > --- a/drivers/firmware/efi/efi.c > +++ b/drivers/firmware/efi/efi.c > @@ -298,7 +298,7 @@ int __init efi_config_init(efi_config_table_type_t > *arch_tables) > if (table64 >> 32) { > pr_cont("\n"); >

Re: [PATCH 1/2] perf/x86: update Haswell PEBS event constraints

On Thu, Jun 19, 2014 at 11:00:28AM -0700, Andi Kleen wrote: > However these days I'm actually thinking of just getting > rid of the detailed table except for PREC_DIST. All the PEBS > controls should be noops if the event does not support PEBS I had something like the below stuck on the 'look more

Re: [PATCH] arch,locking: Ciao arch_mutex_cpu_relax()

Hi Peter, On Monday 23 June 2014 12:24 PM, Peter Zijlstra wrote: > On Fri, Jun 20, 2014 at 11:21:13AM -0700, Davidlohr Bueso wrote: >> diff --git a/arch/arc/include/asm/processor.h >> b/arch/arc/include/asm/processor.h >> index d99f9b3..8e1bf6b 100644 >> --- a/arch/arc/include/asm/processor.h >>

[PATCH v2] DRBG: simplify ordering of linked list in drbg_ctr_df

This patch superseeds and replaces the initial fix submitted with [1]. After careful analysis of the code, the anticipated NULL pointer deference is caught in drbg_ctr_update which only invokes drbg_ctr_df when addtl is not NULL. This patch is tested with CAVS testing and the test set provided in

Re: [PATCH 1/2] perf/x86: update Haswell PEBS event constraints

On Thu, Jun 19, 2014 at 05:58:28PM +0200, Stephane Eranian wrote: > + INTEL_EVENT_CONSTRAINT(0xd1, 0xf), /* MEM_LOAD_UOPS_RETIRED.* */ > + /* MEM_LOAD_UOPS_LLC_HIT_RETIRED.* */ > + INTEL_EVENT_CONSTRAINT(0xd2, 0xf), > + /* MEM_LOAD_UOPS_LLC_MISS_RETIRED.* */ > + INTEL_EVENT_CONS

[PATCH v2] DRBG: simplify ordering of linked list in drbg_ctr_df

As reported by a static code analyzer, the code for the ordering of the linked list can be simplified. Reported-by: kbuild test robot Signed-off-by: Stephan Mueller --- crypto/drbg.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/crypto/drbg.c b/crypto/drbg.c ind

Re: scsi-mq

On Sat, Jun 21, 2014 at 12:52:22AM +, Elliott, Robert (Server Storage) wrote: > Some of those context switches might be from scsi_end_request(), > which always schedules the scsi_requeue_run_queue() function via the > requeue_work workqueue for scsi-mq. That causes lots of context > switche

Re: [PATCH 10/14] scsi: only maintain target_blocked if the driver has a target queue limit

On Sat, Jun 21, 2014 at 10:10:14PM +, Elliott, Robert (Server Storage) wrote: > > not_ready: > > /* > > * lock q, handle tag, requeue req, and decrement device_busy. We > > There's an extra & in that if statement. Indeed, this crept in during a rebase and a later patch fixes it.

Re: [PATCH v3] lockdep: restrict the use of recursive read_lock with qrwlock

On Fri, Jun 20, 2014 at 03:22:46PM -0400, Waiman Long wrote: > v2->v3: > - Add a new read mode (3) for rwlock (used in >lock_acquire_shared_cond_recursive()) to avoid conflict with other >use cases of lock_acquire_shared_recursive(). > > v1->v2: > - Use less conditional & make it easier

<    5   6   7   8   9   10