Re: [PATCH] clk: at91: fix num_parents test in at91sam9260 slow clk implementation

Quoting Boris BREZILLON (2014-09-02 08:27:51) > The slow clk block provided by at91sam9260 and derived SoCs should always > have 2 parents. > > Signed-off-by: Boris BREZILLON > --- > > Hello Mike, > > Could you take this fix for the next 3.17 rc ? > Without this fix you won't be able to use

[PATCH 00/26] tty/serial flow control fixes

Hi Greg, This patch series reworks the internals of tty and serial flow control to fix multiple races in both START/STOP flow control and RTS/CTS flow control. The main changes in this series are: Patch 1 Backs out the UPF_HARD_FLOW kludge for 8250. This revert should be for mainline and

[PATCH 04/26] serial: core: Fix x_char race

The UART driver is expected to clear port->x_char after transmission while holding the port->lock. However, the serial core fails to take the port->lock before assigning port->xchar. This allows for the following race CPU 0 | CPU 1 |

[PATCH 03/26] serial: imx: Fix x_char handling and tx flow control

The serial core expects the UART driver to transmit x_char (START/STOP chars) even if tx is stopped and before data already in the tx ring buffer if possible. Also, sending x_char must not cause additional data in the tx ring buffer to transmit if tx is stopped. Cause x_char to be transmitted

[PATCH 06/26] serial: Fix send_xchar() handlers

START_CHAR() & STOP_CHAR() can be disabled if set to '\0' (__DISABLED_CHAR). UART drivers which define a send_xchar() handler must not transmit __DISABLED_CHAR. Document requirement. Affected drivers: sunsab sunhv cc: David S. Miller cc: Signed-off-by: Peter Hurley ---

Re: [PATCH net-next v2] net: bpf: make eBPF interpreter images read-only

On Tue, Sep 2, 2014, at 23:40, Eric Dumazet wrote: > On Tue, 2014-09-02 at 14:31 -0700, Alexei Starovoitov wrote: > > > > +static inline void bpf_prog_unlock_ro(struct bpf_prog *fp) > > > +{ > > > + set_memory_rw((unsigned long)fp, fp->pages); > > > > why rw is needed? > > since fp is

Re: [patch] mm: clean up zone flags

On Tue, 2 Sep 2014, Johannes Weiner wrote: > diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h > index 318df7051850..48bf12ef6620 100644 > --- a/include/linux/mmzone.h > +++ b/include/linux/mmzone.h > @@ -521,13 +521,13 @@ struct zone { > atomic_long_t

[PATCH 05/26] serial: core: Remove unsafe x_char optimization

uart_unthrottle() attempts to avoid sending START and the previous x_char if the previous x_char has not yet been sent. However, this optimization could leave the sender in a throttled state; for example, if the sender is throttled and this unthrottle coincides with a manual tcflow(TCION) from

[PATCH 07/26] serial: mpc52xx: Use default serial core x_char handler

mpc52xx_uart_send_xchar() is _identical_ to the default serial core x_char handling behavior in uart_send_xchar(). Remove mpc52xx_uart_send_xchar(). Signed-off-by: Peter Hurley --- drivers/tty/serial/mpc52xx_uart.c | 17 - 1 file changed, 17 deletions(-) diff --git

[PATCH v3 8/9] ARM: tegra: jetson-tk1: Add xHCI support

Assign USB ports previously owned by the EHCI controllers to the xHCI controller. There is a mini-PCIe USB port (UTMI port 1) and a USB A connector (UTMI port 2, USB3 port 0). PCIe lane 0 is used for USB3 port 0. Signed-off-by: Andrew Bresticker --- Changes from v2: - Updated VBUS power

[PATCH 01/26] Revert "serial: uart: add hw flow control support configuration"

This reverts commit 06aa82e498c144c7784a6f3d3b55458b272d6146. This commit purports to enable auto CTS flow control for the 8250 UART driver. However, the 8250 UART driver already supports auto CTS flow control via UART_CAP_AFE and UART_CAP_EFR. Indeed, this patch introduces another DT attribute

Re: [PATCH net-next v2] net: bpf: make eBPF interpreter images read-only

On Tue, 2014-09-02 at 14:31 -0700, Alexei Starovoitov wrote: > > +static inline void bpf_prog_unlock_ro(struct bpf_prog *fp) > > +{ > > + set_memory_rw((unsigned long)fp, fp->pages); > > why rw is needed? > since fp is allocated with vmalloc, vfree doesn't need > to touch the pages to free

[PATCH 08/26] serial: sunsab: Don't enable tx if tx stopped

The serial core may call the UART driver's start_tx() even if tx is stopped; the UART driver must verify tx should be enabled before transmitting. Reported-by: Sam Ravnborg cc: David S. Miller cc: Signed-off-by: Peter Hurley --- drivers/tty/serial/sunsab.c | 2 +- 1 file changed, 1

[PATCH 09/26] serial: blackfin: Fix missing gpio.h

If CONFIG_SERIAL_BFIN_CTSRTS is set, compile fails because of missing declarations for the gpio_* api. Include necessary header. Signed-off-by: Peter Hurley --- drivers/tty/serial/bfin_sport_uart.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/tty/serial/bfin_sport_uart.c

Re: [PATCH V4 1/8] namespaces: assign each namespace instance a serial number

On 14/08/28, Eric W. Biederman wrote: > Richard Guy Briggs writes: > > On 14/08/23, Eric W. Biederman wrote: > >> Richard Guy Briggs writes: > >> > >> > Generate and assign a serial number per namespace instance since boot. > >> > > >> > Use a serial number per namespace (unique across one boot

[PATCH 02/26] serial: Style fix

Unwrap if() conditional; no functional change. Signed-off-by: Peter Hurley --- drivers/tty/serial/serial_core.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c index 261e49e..87cde4c 100644 ---

[PATCH v3 3/9] of: Update Tegra XUSB pad controller binding for USB

Add new bindings used for USB support by the Tegra XUSB pad controller. This includes additional PHY types, USB-specific pinconfig properties, etc. Signed-off-by: Andrew Bresticker --- Changes from v2: - Added nvidia,otg-hs-curr-level-offset property. - Dropped "-otg" from VBUS supplies. -

[PATCH v3 4/9] pinctrl: tegra-xusb: Add USB PHY support

In addition to the PCIe and SATA PHYs, the XUSB pad controller also supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a single PCIe or SATA lane and is mapped to one of the three UTMI ports. The xHCI controller will also send messages intended for the PHY driver, so request and listen

[PATCH v3 2/9] mailbox: Add NVIDIA Tegra XUSB mailbox driver

The Tegra xHCI controller's firmware communicates requests to the host processor through a mailbox interface. While there is only a single physical channel, messages sent by the controller can be divided into two groups: those intended for the PHY driver and those intended for the host-controller

[PATCH v3 5/9] of: Add NVIDIA Tegra xHCI controller binding

Add device-tree binding documentation for the xHCI controller present on Tegra124 and later SoCs. Signed-off-by: Andrew Bresticker --- Changes from v2: - Added mbox-names property. Changes from v1: - Updated to use common mailbox bindings. - Added remaining XUSB-related clocks and resets. -

[PATCH v3 7/9] ARM: tegra: Add Tegra124 XUSB mailbox and xHCI controller

Add nodes for the Tegra XUSB mailbox and Tegra xHCI controller and add the PHY mailbox channel to the XUSB padctl node. Signed-off-by: Andrew Bresticker --- Changes from v2: - Dropped channel specifier from mailbox bindings. - Added mbox-names properties. Changes from v1: - Updated to use

[PATCH v3 6/9] usb: xhci: Add NVIDIA Tegra xHCI host-controller driver

Add support for the on-chip xHCI host controller present on Tegra SoCs. The driver is currently very basic: it loads the controller with its firmware, starts the controller, and is able to service messages sent by the controller's firmware. The hardware also supports device mode as well as

Re: [PATCH v11 06/19] irqchip: gic: Provide support for interrupt grouping

On 2 Sep 2014, at 20:33, Russell King - ARM Linux wrote: > On Tue, Sep 02, 2014 at 02:00:40PM +0100, Daniel Thompson wrote: >> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c >> index 4b959e6..423707c 100644 >> --- a/drivers/irqchip/irq-gic.c >> +++ b/drivers/irqchip/irq-gic.c

[PATCH v3 0/9] Tegra xHCI support

This series adds support for xHCI on NVIDIA Tegra SoCs. This includes: - patches 1 and 2: adding a driver for the mailbox used to communicate with the xHCI controller's firmware, - patches 3 and 4: extending the XUSB pad controller driver to support the USB PHY types (UTMI, HSIC, and

Re: [PATCH net-next v2] net: bpf: make eBPF interpreter images read-only

On Tue, Sep 2, 2014, at 23:31, Alexei Starovoitov wrote: > On Tue, Sep 2, 2014 at 1:53 PM, Hannes Frederic Sowa > wrote: > > From: Daniel Borkmann > > > > With eBPF getting more extended and exposure to user space is on it's way, > > hardening the memory range the interpreter uses to steer its

[PATCH v3 1/9] of: Add NVIDIA Tegra XUSB mailbox binding

Add device-tree bindings for the Tegra XUSB mailbox which will be used for communication between the Tegra xHCI controller's firmware and the host processor. Signed-off-by: Andrew Bresticker --- Changes from v2: - Dropped channel specifier. - Added pointer to mailbox documentation. Changes

[PATCH v3 9/9] ARM: tegra: venice2: Add xHCI support

Assign ports previously owned by the EHCI controllers to the xHCI controller. There are two external USB ports (UTMI ports 0/2 and USB3 ports 0/1) and an internal USB port (UTMI port 1). PCIe lanes 0 and 1 are used by the USB3 ports. Signed-off-by: Andrew Bresticker --- Changes from v2: -

Re: [PATCH] ACPICA: ACPI 5.1: Add support for runtime validation of _DSD package.

On Friday, August 29, 2014 09:32:42 AM Lv Zheng wrote: > From: Mika Westerberg > > Adds ACPICA kernel runtime support to validate contents/format > of the _DSD package, similar to the iASL support. Ported by > Mika Westerberg. > > Signed-off-by: Mika Westerberg > Signed-off-by: Bob Moore >

Re: [PATCH] ACPI/EC: Add msi quirk for Clevo W350etq

On Friday, August 29, 2014 10:50:08 AM Lan Tianyu wrote: > Clevo W350etq's EC will not produce GPE interrupt some time after > booting. The ACPI notify event won't trigger when the issue takes > place. After debugging, adding msi quirk for the machine can fix > the issue. This patch is to add msi

Re: [PATCH net-next v2] net: bpf: make eBPF interpreter images read-only

On Tue, Sep 2, 2014 at 1:53 PM, Hannes Frederic Sowa wrote: > From: Daniel Borkmann > > With eBPF getting more extended and exposure to user space is on it's way, > hardening the memory range the interpreter uses to steer its command flow > seems appropriate. This patch moves the to be

Re: [PATCH] Revert "leds: convert blink timer to workqueue"

On Tue, 2 Sep 2014, Bryan Wu wrote: > On Tue, Sep 2, 2014 at 2:03 AM, Jiri Kosina wrote: > > This reverts commit 8b37e1bef5a6b60e949e28a4db3006e4b00bd758. > > > > It's broken as it changes led_blink_set() in a way that it can now sleep > > (while synchronously waiting for workqueue to be

[PATCH v2 2/9] Documentation: devicetree: Add binding for Synopsys DDR controller

Signed-off-by: Soren Brinkmann --- .../devicetree/bindings/memory-controllers/synopsys.txt | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 Documentation/devicetree/bindings/memory-controllers/synopsys.txt diff --git

[PATCH v2 0/9] Zynq PM updates

Hi all, here is v2 of this series. It's mostly the same and most changes are related to reformatting comments. The only functional change is in 'ARM: zynq: PM: Enable DDR clock stop' which does no longer enable self-refresh too. It seems self-refresh is inflicting a non-negligible amount of

[PATCH v2 3/9] ARM: zynq: DT: Add DDRC node

Add the DDR controller to the Zynq devicetree. Signed-off-by: Soren Brinkmann --- arch/arm/boot/dts/zynq-7000.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/zynq-7000.dtsi b/arch/arm/boot/dts/zynq-7000.dtsi index 6cc83d4c6c76..587cadcf7001 100644 ---

[PATCH v2 1/9] ARM: zynq: PM: Enable A9 internal clock gating feature

Signed-off-by: Soren Brinkmann --- v2: - make comments comply to kernel-doc format --- arch/arm/mach-zynq/common.c | 6 ++ arch/arm/mach-zynq/common.h | 11 +++ arch/arm/mach-zynq/platsmp.c | 13 + 3 files changed, 30 insertions(+) diff --git

[PATCH v2 5/9] ARM: zynq: Remove invalidate cache for cpu die

From: Daniel Lezcano As there is no Power management unit on this board, it is not possible to power down a core, just WFI is allowed. There is no point to invalidate the cache and exit coherency. Signed-off-by: Daniel Lezcano Reviewed-and-tested-by: Soren Brinkmann ---

[PATCH v2 6/9] ARM: zynq: cpuidle: Remove pointless code

From: Daniel Lezcano The core is not powered down, it is pointless to call the cpu_pm notifiers and switch to the global timer. Signed-off-by: Daniel Lezcano Reviewed-and-tested-by: Soren Brinkmann --- drivers/cpuidle/cpuidle-zynq.c | 10 +- 1 file changed, 1 insertion(+), 9

[PATCH v2 8/9] ARM: zynq: Remove hotplug.c

The hotplug code contains only a single function, which is an SMP function. Move that to platsmp.c where all other SMP runctions reside. That allows removing hotplug.c and declaring the cpu_die function static. Signed-off-by: Soren Brinkmann --- v2: - don't add function prototype a second time

[PATCH v2 7/9] ARM: zynq: Synchronise zynq_cpu_die/kill

Avoid races and add synchronisation between the arch specific kill and die routines. The same synchronisation issue was fixed on IMX platform by this commit: "ARM: imx: fix sync issue between imx_cpu_die and imx_cpu_kill" (sha1: 2f3edfd7e27ad4206acbc2ae99c9df5f46353024) Signed-off-by: Soren

[PATCH v2 9/9] ARM: zynq: Rename 'zynq_platform_cpu_die'

Match the naming pattern of all other SMP ops and rename zynq_platform_cpu_die --> zynq_cpu_die. Signed-off-by: Soren Brinkmann --- v2: - make comments comply to kernel-doc format --- arch/arm/mach-zynq/platsmp.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git

[PATCH v2 4/9] ARM: zynq: PM: Enable DDR clock stop

The DDR controller can detect idle periods and leverage low power features clock stop. When new requests occur, the DDRC resumes normal operation. Signed-off-by: Soren Brinkmann --- v2: - properly document return value for zynq_pm_ioremap - change zynq_pm_late_init signature to return void -

Re: [PATCH] semaphore: Resolve some shadow warnings

On Sep 1, 2014, at 4:41 PM, Jeff Kirsher wrote: > On Mon, 2014-09-01 at 14:02 +0200, Peter Zijlstra wrote: >> On Thu, Aug 28, 2014 at 05:19:26AM -0700, Jeff Kirsher wrote: >>> From: Mark Rustad >>> >>> Resolve some shadow warnings resulting from using the name >>> jiffies, which is a

Re: [RFC] dynticks: dynticks_idle is only modified locally use this_cpu ops

On Tue, Sep 02, 2014 at 03:47:55PM -0500, Christoph Lameter wrote: > On Tue, 2 Sep 2014, Paul E. McKenney wrote: > > > But yes, in theory, something like this can work if appropriate memory > > barriers are put in place. In practice, this sort of change needs > > profound testing on multiple

Re: [PATCH v3 2/4] Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro

On Thu, Aug 28, 2014 at 11:00:27AM +0100, Juri Lelli wrote: > Section 4 intro was still describing the old interface. Rewrite it. > > Signed-off-by: Juri Lelli > Signed-off-by: Luca Abeni > Cc: Randy Dunlap > Cc: Peter Zijlstra > Cc: Ingo Molnar > Cc: Henrik Austad > Cc: Dario Faggioli >

[PATCH] drivers: staging: lustre: Fix "space prohibited after that open parenthesis '('" errors

Fix checkpatch.pl "space prohibited after that open parenthesis '('" errors Signed-off-by: Greg Donald --- drivers/staging/lustre/lustre/lmv/lmv_internal.h | 2 +- .../lustre/lustre/obdclass/linux/linux-module.c| 4 ++-- drivers/staging/lustre/lustre/obdclass/obdo.c | 28

Re: [PATCH v3 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity

On Thu, Aug 28, 2014 at 11:00:26AM +0100, Juri Lelli wrote: > From: Luca Abeni > > Several small changes regarding SCHED_DEADLINE documentation that fix > terminology and improve clarity and readability: > > - "current runtime" becomes "remaining runtime" > > - readablity of an equation is

[tip:x86/platform] x86/iosf: Add debugfs support

Commit-ID: 8dc12f933c9d732c5bbfb233daf27377893b109c Gitweb: http://git.kernel.org/tip/8dc12f933c9d732c5bbfb233daf27377893b109c Author: David E. Box AuthorDate: Wed, 27 Aug 2014 14:40:40 -0700 Committer: H. Peter Anvin CommitDate: Wed, 27 Aug 2014 14:48:36 -0700 x86/iosf: Add debugfs

[tip:x86/platform] x86/iosf: Add Kconfig prompt for IOSF_MBI selection

Commit-ID: aa8e4f22ab7773352ba3895597189b8097f2c307 Gitweb: http://git.kernel.org/tip/aa8e4f22ab7773352ba3895597189b8097f2c307 Author: David E. Box AuthorDate: Wed, 27 Aug 2014 14:40:39 -0700 Committer: H. Peter Anvin CommitDate: Wed, 27 Aug 2014 14:48:33 -0700 x86/iosf: Add Kconfig

Re: [RFC v2 0/9] KVM-VFIO IRQ forward control

On Mon, 2014-09-01 at 14:52 +0200, Eric Auger wrote: > This RFC proposes an integration of "ARM: Forwarding physical > interrupts to a guest VM" (http://lwn.net/Articles/603514/) in > KVM. > > It enables to transform a VFIO platform driver IRQ into a forwarded > IRQ. The direct benefit is that,

Compat sysinfo syscall (kernel/sys.c) relying on undefined behavior?

am getting acquainted with the linux kernel and to do so I've been browsing the source. In the compat version of sysinfo, kernel/sys.c we see the following: COMPAT_SYSCALL_DEFINE1(sysinfo, struct compat_sysinfo __user *, info) { struct sysinfo s; do_sysinfo(); /* Check to see if

Re: rcu: Remove rcu_dynticks * parameters when they are always this_cpu_ptr(_dynticks)

On Tue, Sep 02, 2014 at 03:13:44PM -0500, Christoph Lameter wrote: > For some functions in kernel/rcu/tree* the rdtp parameter is always > this_cpu_ptr(rdtp). > Remove the parameter if constant and calculate the pointer in function. > > This will have the advantage that it is obvious that the

Re: regression caused by cgroups optimization in 3.17-rc2

I, of course, forgot to include the most important detail. This appears to be pretty run-of-the-mill spinlock contention in the resource counter code. Nearly 80% of the CPU is spent spinning in the charge or uncharge paths in the kernel. It is apparently spinning on res_counter->lock in both

Re: [PATCH v3 3/4] irq: Allow multiple clients to register for irq affinity notification

On Tue, 2 Sep 2014, Lina Iyer wrote: > On Wed, Aug 27 2014 at 14:56 -0600, Thomas Gleixner wrote: > > On Wed, 27 Aug 2014, Lina Iyer wrote: > > > > All you are describing is the fact, that there is only a single > > notifier possible right now, but you completely miss to describe WHY > > you need

[PATCH net-next v2] net: bpf: make eBPF interpreter images read-only

From: Daniel Borkmann With eBPF getting more extended and exposure to user space is on it's way, hardening the memory range the interpreter uses to steer its command flow seems appropriate. This patch moves the to be interpreted bytecode to read-only pages. In case we execute a corrupted BPF

Re: [PATCH] ethernet: nvidia: Remove extra parens

From: David Wood Date: Mon, 1 Sep 2014 15:31:55 -0700 > Remove unnecessary double parenthesis around if statement. > > Signed-off-by: David Wood Applied, thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org

Re: [RFC] dynticks: dynticks_idle is only modified locally use this_cpu ops

On Tue, 2 Sep 2014, Paul E. McKenney wrote: > But yes, in theory, something like this can work if appropriate memory > barriers are put in place. In practice, this sort of change needs > profound testing on multiple architectures. Ok how can we move forward? I just looked further and it seems a

[PATCH net-next] net: bpf: make eBPF interpreter images read-only

From: Daniel Borkmann With eBPF getting more extended and exposure to user space is on it's way, hardening the memory range the interpreter uses to steer its command flow seems appropriate. This patch moves the to be interpreted bytecode to read-only pages. In case we execute a corrupted BPF

Re: [PATCH] platform/x86: toshiba: re-enable acpi hotkeys after suspend to disk

On Tue, 2014-09-02 at 14:04 -0400, Benjamin Tissoires wrote: > we noticed this problem on a Toshiba Z40. I kind of brute-forced the thing, > and > I ended up that calling "ENAB" was making the keys working again > (rmmod/insmod > the driver was sufficient, and the only command which was

Re: [PATCH 15/15] tty: serial: 8250: omap: add dma support

On Tue, Sep 02, 2014 at 01:15:37PM -0700, Tony Lindgren wrote: > * Sebastian Andrzej Siewior [140902 11:40]: > > On 09/01/2014 07:47 PM, Sebastian Andrzej Siewior wrote: > > > Comparing it with serial-omap I see the same thing: I takes approx the > > > same amount of data until the first one is

Re: [RFC] dynticks: dynticks_idle is only modified locally use this_cpu ops

On Tue, Sep 02, 2014 at 03:14:43PM -0500, Christoph Lameter wrote: > > Since dynticks_idle is only ever modified by the local cpu we do > not need to use an atomic there. The weak "atomicity" of this_cpu > ops is sufficient since there is no other cpu modifying the variable. > > [This is a

Re: [PATCH] PM / sleep: Fix test_suspend= command line option

On Tuesday, September 02, 2014 09:43:49 AM Srinivas Pandruvada wrote: > On Tue, 2014-09-02 at 01:37 +0200, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > After commit d431cbc53cb7 (PM / sleep: Simplify sleep states sysfs > > interface code) the pm_states[] array is not populated

[RFC PATCH v6] tpm_tis: verify interrupt during init

On Tue, 2 Sep 2014, Jason Gunthorpe wrote: > On Sat, Aug 30, 2014 at 11:23:56PM +, Scot Doyle wrote: >> The output is now >> [1.526798] tpm_tis 00:08: 1.2 TPM (device-id 0xB, rev-id 16) >> [5.914732] tpm_tis 00:08: [Firmware Bug]: TPM interrupt not working, >> polling instead > >

Re: [PATCH] net: calxedaxgmac: fix driver dependencies

From: Bartlomiej Zolnierkiewicz Date: Mon, 01 Sep 2014 17:39:04 +0200 > Calxeda 1G/10G XGMAC Ethernet support should be available only on > Calxeda ECX-1000/2000 (Highbank/Midway) platforms. > > Signed-off-by: Bartlomiej Zolnierkiewicz > Acked-by: Kyungmin Park Applied. -- To unsubscribe

Re: [PATCH v2] net: sh_eth: fix driver dependencies

From: Bartlomiej Zolnierkiewicz Date: Mon, 01 Sep 2014 16:25:35 +0200 > Renesas SuperH Ethernet support should be available only on > Renesas ARM SoCs and SuperH architecture. > > Signed-off-by: Bartlomiej Zolnierkiewicz > Acked-by: Kyungmin Park Applied. -- To unsubscribe from this list:

Re: [PATCH] net: lpc_eth: Fix crash on ip link up

From: sti...@antcom.de Date: Mon, 1 Sep 2014 13:46:46 +0200 > From: Roland Stigge > > When a link is already up, the following sequence makes the kernel > block completely: > > ip link set dev eth0 down > ip link set dev eth0 up > > This is because on suspended phy, the following lines >

Re: linux-next: Tree for Aug 23

On Tue, Sep 02, 2014 at 12:04:45PM -0700, Guenter Roeck wrote: > I provided qemu images and instructions as follows. > http://server.roeck-us.net/qemu/mipsel/ MIPS 32 bit, little > endian > http://server.roeck-us.net/qemu/mips64el/ MIPS 64 bit, little > endian > > Let

Re: regression caused by cgroups optimization in 3.17-rc2

On 09/02/2014 12:05 PM, Dave Hansen wrote: > It does not revert cleanly because of the hunks below. The code in > those hunks was removed, so I tried running without properly merging > them and it spews warnings because counter->usage is seen going negative. > > So, it doesn't appear we can

Re: [PATCH 15/15] tty: serial: 8250: omap: add dma support

* Sebastian Andrzej Siewior [140902 11:40]: > On 09/01/2014 07:47 PM, Sebastian Andrzej Siewior wrote: > > Comparing it with serial-omap I see the same thing: I takes approx the > > same amount of data until the first one is displayed. After a lot of > > "long" writes which wake the chip up from

[no subject]

This version addresses Sergei's comments. o Fixed description and added Reported-by o Removed NULL check for kfree() -- 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

[RFC] dynticks: dynticks_idle is only modified locally use this_cpu ops

Since dynticks_idle is only ever modified by the local cpu we do not need to use an atomic there. The weak "atomicity" of this_cpu ops is sufficient since there is no other cpu modifying the variable. [This is a cautious patch that leaves the barriers in place] Signed-off-by: Christoph Lameter

rcu: Remove rcu_dynticks * parameters when they are always this_cpu_ptr(_dynticks)

For some functions in kernel/rcu/tree* the rdtp parameter is always this_cpu_ptr(rdtp). Remove the parameter if constant and calculate the pointer in function. This will have the advantage that it is obvious that the address are all per cpu offsets and thus it will enable the use of this_cpu_ops

Re: [PATCH] pci/pci-sysfs: Set pci interface in uppercase

On Tue, Sep 2, 2014 at 1:22 PM, Ricardo Ribalda Delgado wrote: > Hej Bjorn > > I have seen that you have updated your pci tree without this patch. Is > there something wrong with it? > > If you are already considering it, sorry for the mail, but I wanted to > make sure that it is in 3.17 and then

[PATCH] VMXNET3: Check for map error in vmxnet3_set_mc

We should check if the map of the table actually succeeds, and also free resources accordingly. Version bumped to 1.2.1.0 Acked-by: Shelley Gong Acked-by: Bhavesh Davda Signed-off-by: Andy King Reported-by: Tetsuo Handa --- drivers/net/vmxnet3/vmxnet3_drv.c | 15 ---

[PATCH v3] hwspinlock: qcom: Add support for Qualcomm HW Mutex block

From: Kumar Gala Add driver for Qualcomm Hardware Mutex block that exists on newer Qualcomm SoCs. Cc: Jeffrey Hugo Cc: Eric Holmberg Cc: Courtney Cavin Signed-off-by: Kumar Gala [bjorn: added pm_runtime calls, from Courtney, added sfpb-mutex compatible, updated DT binding

Re: [PATCH] VMXNET3: Check for map error in vmxnet3_set_mc

Hello. On 09/02/2014 08:30 PM, Andy King wrote: We should check if the map of the table actually succeeds, and also free resources accordingly. This fixes the kernel panic reported by Tetsuo Handa. There's "Reported-by:" line for that. Version bumped to 1.2.1.0 Acked-by: Shelley Gong

Re: [PATCH v7 0/5] Add rockchip RK808 pmic driver

Am Montag, 1. September 2014, 17:07:43 schrieb Chris Zhong: > This is the initial version of the RK808 PMIC. This is a power management IC > for multimedia products. > > It provides regulators that are able to supply power to processor cores > and other components. The chip provides other modules

Re: [PATCH] locks: Ability to test for flock presence on fd

On Tue, 2 Sep 2014 15:43:00 -0400 "J. Bruce Fields" wrote: > On Tue, Sep 02, 2014 at 11:07:14PM +0400, Pavel Emelyanov wrote: > > On 09/02/2014 10:44 PM, J. Bruce Fields wrote: > > > On Tue, Sep 02, 2014 at 09:17:34PM +0400, Pavel Emelyanov wrote: > > >> Hi, > > >> > > >> There's a problem with

Re: How is pivot_root intended to be used?

On 09/01/2014 02:19 PM, Steven Stewart-Gallus wrote: Hello, I am not confused about how I can currently use pivot_root for containers on my kernel (version 3.13). Currently a sequence like: if (-1 == syscall(__NR_pivot_root, ".", ".")) { perror("pivot_root"); return

Re: [PATCH 0/2] Add input supplies to rk808 regulator

Heiko, On Tue, Sep 2, 2014 at 12:48 PM, Heiko Stübner wrote: > Am Dienstag, 2. September 2014, 09:14:27 schrieb Doug Anderson: >> We want to specify the input supplies to the rk808 regulator. This >> patch series adds them to the driver. Note that the bindings are >> based atop Chris's most

Re: [PATCH 0/2] Add input supplies to rk808 regulator

Am Dienstag, 2. September 2014, 09:14:27 schrieb Doug Anderson: > We want to specify the input supplies to the rk808 regulator. This > patch series adds them to the driver. Note that the bindings are > based atop Chris's most recent version at > . If

Re: [PATCH] locks: Ability to test for flock presence on fd

On Tue, Sep 02, 2014 at 11:07:14PM +0400, Pavel Emelyanov wrote: > On 09/02/2014 10:44 PM, J. Bruce Fields wrote: > > On Tue, Sep 02, 2014 at 09:17:34PM +0400, Pavel Emelyanov wrote: > >> Hi, > >> > >> There's a problem with getting information about who has a flock on > >> a specific file. The

Re: [PATCH v11 11/19] irqchip: vic: Add support for FIQ management

On Tue, Sep 02, 2014 at 02:00:45PM +0100, Daniel Thompson wrote: > diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c > index bda5a91..8821160 100644 > --- a/drivers/irqchip/irq-gic.c > +++ b/drivers/irqchip/irq-gic.c > @@ -502,13 +502,17 @@ static void __init gic_init_fiq(struct

Re: [PATCH 03/12] of: Add binding document for MIPS GIC

On Tue, Sep 2, 2014 at 10:27 AM, David Daney wrote: > On 08/29/2014 03:14 PM, Andrew Bresticker wrote: >> >> The Global Interrupt Controller (GIC) present on certain MIPS systems >> can be used to route external interrupts to individual VPEs and CPU >> interrupt vectors. It also supports a timer

Re: [PATCH v11 07/19] irqchip: gic: Add support for FIQ management

On Tue, Sep 02, 2014 at 02:00:41PM +0100, Daniel Thompson wrote: > +static void gic_enable_fiq(struct irq_data *d) > +{ > + gic_set_group_irq(d, 0); > +} > + > +static void gic_disable_fiq(struct irq_data *d) > +{ > + gic_set_group_irq(d, 1); > +} I think both the above functions should

Re: [RFC PATCH 1/1] drivers: introduce ARM SBSA generic UART driver

On Tuesday 02 September 2014 12:38:23 Rob Herring wrote: > On Tue, Sep 2, 2014 at 8:48 AM, Arnd Bergmann wrote: > > On Tuesday 02 September 2014 08:20:53 Rob Herring wrote: > >> >> > >> >> This alone is not okay. There is no such implementation of hardware. > >> > > >> > But the SBSA explicitly

Re: [PATCH v11 06/19] irqchip: gic: Provide support for interrupt grouping

On Tue, Sep 02, 2014 at 02:00:40PM +0100, Daniel Thompson wrote: > diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c > index 4b959e6..423707c 100644 > --- a/drivers/irqchip/irq-gic.c > +++ b/drivers/irqchip/irq-gic.c > @@ -41,6 +41,9 @@ > #include > > #include > +#ifdef

Re: [PATCH] pci/probe: Enable CRS for Intel Haswell root ports

On Mon, Sep 1, 2014 at 9:14 PM, Bjorn Helgaas wrote: > > I'm not a fan of adding a whitelist for devices that work correctly. > I don't think that's a maintainable solution. Since we haven't had > many systems yet that care about CRS, some kind of "enable CRS on > machines newer than X" might

Re: [REGRESSION] "efi: efistub: Convert into static library" and preparation patches

On Tue, 02 Sep, at 05:25:58PM, Maarten Lankhorst wrote: > Hey, > > My macbook pro 8.2 fails to do a efi stub boot with these patches. > > Commit f23cf8bd5c1f49 "efi/x86: efistub: Move shared dependencies to > " > causes the first break, but this can be averted by changing > > struct efi_config

[PATCH] staging: android: use braces on all arms of if

Signed-off-by: Grzegorz Swirski --- drivers/staging/android/sync.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/android/sync.c b/drivers/staging/android/sync.c index 0d37495..c5255dc 100644 --- a/drivers/staging/android/sync.c +++

Re: [PATCH] pci/pci-sysfs: Set pci interface in uppercase

Hej Bjorn I have seen that you have updated your pci tree without this patch. Is there something wrong with it? If you are already considering it, sorry for the mail, but I wanted to make sure that it is in 3.17 and then back ported. Thanks!! On Wed, Aug 27, 2014 at 10:51 PM, Greg KH wrote:

Re: [Xen-devel] [PATCH] Solved the Xen PV/KASLR riddle

On Mon, Sep 01, 2014 at 06:03:06AM +0200, Juergen Gross wrote: > On 08/29/2014 04:55 PM, Konrad Rzeszutek Wilk wrote: > >On Fri, Aug 29, 2014 at 03:44:06PM +0100, Jan Beulich wrote: > >On 29.08.14 at 16:27, wrote: > >>>Sure. Btw, someone also contacted me saying they have the same problem >

Re: RTNL: assertion failed at net/ipv6/addrconf.c (1699)

On Tue, Sep 2, 2014 at 12:02 PM, Hannes Frederic Sowa wrote: > > If fixes tag is well researched, it won't point to the addition of > ASSERT_RTNL() but your patch would help to discover a bug somewhere else > in the stack. > > I think for this patch a fixes-tag is hard to find because it is hard

Re: [PATCH] init/Kconfig: move RCU_NOCB_CPU dependencies to choice

On Tue, Sep 02, 2014 at 08:05:48PM +0200, Stefan Hengelein wrote: > 2014-09-02 19:07 GMT+02:00 Paul E. McKenney : > > On Fri, Aug 29, 2014 at 03:08:20PM +0200, Stefan Hengelein wrote: > >> Every choice item of the "Build-forced no-CBs CPUs" choice had a > >> dependency to RCU_NOCB_CPU. It's more

[PATCH -v2] x86: only load initrd above 4g on second try

Mantas found that after commit 4bf7111f5016 ("x86/efi: Support initrd loaded above 4G"), the kernel freezes at the earliest possible moment when trying to boot via UEFI on Asus laptop. Revert to old way to load initrd under 4G on first try, second try will use above 4G buffer when initrd is too

Re: Race condition in HR timers that cause double insertion and hard lockup -- all latest versions

On Tue, 2 Sep 2014, Linus Torvalds wrote: > On Tue, Sep 2, 2014 at 8:45 AM, Itzcak Pechtalt > wrote: > > > > I opened a bug in https://bugzilla.kernel.org/show_bug.cgi?id=83601 for > > this subject with full description. > > There is also a short fix patch for kernel/hrtimer.c file. > > Even

Re: RTNL: assertion failed at net/ipv6/addrconf.c (1699)

On 09/02/2014 02:15 PM, Cong Wang wrote: > On Tue, Sep 2, 2014 at 11:11 AM, Eric Dumazet wrote: >> On Tue, 2014-09-02 at 11:04 -0700, Cong Wang wrote: >>> On Tue, Sep 2, 2014 at 10:58 AM, Hannes Frederic Sowa >> I definitely don't have a problem cleaning this up in net-next. I wanted a

Re: [PATCH] locks: Ability to test for flock presence on fd

On 09/02/2014 10:44 PM, J. Bruce Fields wrote: > On Tue, Sep 02, 2014 at 09:17:34PM +0400, Pavel Emelyanov wrote: >> Hi, >> >> There's a problem with getting information about who has a flock on >> a specific file. The thing is that the "owner" field, that is shown in >> /proc/locks is the pid of

regression caused by cgroups optimization in 3.17-rc2

I'm seeing a pretty large regression in 3.17-rc2 vs 3.16 coming from the memory cgroups code. This is on a kernel with cgroups enabled at compile time, but not _used_ for anything. See the green lines in the graph: https://www.sr71.net/~dave/intel/regression-from-05b843012.png The

Re: linux-next: Tree for Aug 23

On Tue, Sep 02, 2014 at 11:55:53AM +0200, Peter Zijlstra wrote: > On Tue, Sep 02, 2014 at 11:40:16AM +0200, Peter Zijlstra wrote: > > On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote: > > > On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote: > > > > Yes, the problem is

Re: RTNL: assertion failed at net/ipv6/addrconf.c (1699)

On Di, 2014-09-02 at 11:40 -0700, Cong Wang wrote: > On Tue, Sep 2, 2014 at 11:18 AM, Hannes Frederic Sowa > wrote: > > Those ASSERT_RTNLs were misplaced and only caught the callers mostly > > from addrconf.c. I don't mind getting reports from stable kernel users > > and fixing those, too (or

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