Re: JBD2: Spotted dirty metadata buffer....

Am Mittwoch, 23. November 2016, 16:40:07 schrieb Andreas Dilger: > On Nov 23, 2016, at 3:43 AM, Wolfgang Walter wrote: > > Am Dienstag, 22. November 2016, 16:02:53 schrieben Sie: > >> On Nov 22, 2016, at 6:56 AM, Wolfgang Walter wrote: > >>> Am Montag, 21. November

Re: [PATCH] vxlan: fix a potential issue when create a new vxlan fdb entry.

On Mon, 28 Nov 2016 15:02:23 +0800, Haishuang Yan wrote: > vxlan_fdb_append may return error, so add the proper check, > otherwise it will cause memory leak. > > Signed-off-by: Haishuang Yan > --- > drivers/net/vxlan.c | 10 +++--- > 1 file changed, 7

[PATCH v2] drm: tilcdc: fix parsing of some DT properties

The DT binding for tildc is not consistent with the driver code: there are two options - 'max-width' and 'max-pixelclock' specified in the documentation which are parsed as 'ti,max-width' and 'ti'max-pixelclock' respectively. Make the driver code consistent with the binding. Signed-off-by:

Re: [PATCH] ARC: mm: PAE40: Cast pfn to pte_t in pfn_pte() macro

Hi Yuriy, Really nice catch! Though a couple of nitpicks below. On Mon, 2016-11-28 at 07:07 +0300, Yuriy Kolerov wrote: > Originally pfn_pte(pfn, prot) macro had this definition: > > __pte(((pfn) << PAGE_SHIFT) | pgprot_val(prot)) > > The value of pfn (Page Frame Number) is shifted to the

[PATCH] Input: joystick: adi - change msleep to usleep_range for small msecs

msleep(1~20) may not do what the caller intends, and will often sleep longer. (~20 ms actual sleep for any value given in the 1~20ms range) This is not the desired behaviour for many cases like device resume time, device suspend time, device enable time, data reading time, etc. Thus, change msleep

Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup

On Mon, Nov 28, 2016 at 01:16:45PM +0200, Jani Nikula wrote: > Using rst we can produce decent HTML pages, and make them available at > [1], in context. You don't have to read that, but it will be a lot more > discoverable for other people, another important quality of good > documentation. And

[PATCH] stmmac: fix comments, make debug output consistent

Fix comments, add some new, and make debugfs output consistent. Signed-off-by: Pavel Machek diff --git a/drivers/net/ethernet/stmicro/stmmac/common.h b/drivers/net/ethernet/stmicro/stmmac/common.h index a61de04..6074d97 100644 ---

Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup

On Mon, Nov 28, 2016 at 09:08:55AM -0200, Mauro Carvalho Chehab wrote: > - use *foo* (for italics) or **foo** (for bold) instead of _foo_; That's daft, and also you're wrong. The normal convention is: /italic/ *bold* _underlined_ >

[PATCH v6 2/3] mfd: lpc_ich: Add support for SPI serial flash host controller

Many Intel CPUs including Haswell, Broadwell and Baytrail have SPI serial flash host controller as part of the LPC device. This will populate an MFD cell suitable for the SPI host controller driver if we know that the LPC device has one. Signed-off-by: Mika Westerberg

[PATCH v6 0/3] spi-nor: Add support for Intel SPI serial flash controller

This is 6th iteration of the series. You can find the previous versions archived on: v5: https://lwn.net/Articles/706363/ v4: https://lwn.net/Articles/703773/ v3: https://lwn.net/Articles/697231/ v2: http://lists.infradead.org/pipermail/linux-mtd/2016-June/068277.html v1:

Re: [GIT PULL] STi defconfig fix for v4.9-rcs

On 11/25/2016 10:40 PM, Arnd Bergmann wrote: > On Wednesday, November 23, 2016 9:59:14 AM CET Patrice Chotard wrote: >> STi defconfig fix: >> >> Enable HVA (Hardware Video Accelerator) video encoder >> driver for STMicroelectronics SoC. > Hi Arnd > Defconfig changes like this don't seem

Re: powernv: Clear SPRN_PSSCR when a POWER9 CPU comes online

On Tue, 2016-11-22 at 18:06:40 UTC, "Gautham R. Shenoy" wrote: > From: "Gautham R. Shenoy" > > Ensure that PSSCR is set to a safe value corresponding to no > state-loss each time a POWER9 CPU comes online. > > Signed-off-by: Gautham R. Shenoy >

Re: powerpc/eeh/of: use builtin_platform_driver

On Wed, 2016-11-23 at 14:58:56 UTC, Geliang Tang wrote: > Use builtin_platform_driver() helper to simplify the code. > > Signed-off-by: Geliang Tang > Acked-by: Russell Currey Applied to powerpc next, thanks.

Re: cxl: drop duplicate header sched.h

On Wed, 2016-11-23 at 15:27:38 UTC, Geliang Tang wrote: > Drop duplicate header sched.h from native.c. > > Signed-off-by: Geliang Tang > Reviewed-by: Andrew Donnellan Applied to powerpc next, thanks.

[PATCH v2 2/2] ARM: dts: da850-lcdk: specify the maximum pixel clock rate for tilcdc

Due to memory throughput constraints any display mode for which the pixel clock rate exceeds the recommended value of 37500 KHz must be filtered out. Specify the max-pixelclock property for the display node for da850-lcdk. Signed-off-by: Bartosz Golaszewski ---

Re: [PATCH] signal: protect SIGNAL_UNKILLABLE from unintentional clearing.

Hi Oleg, On Thu, Nov 17, 2016 at 08:04:20PM +0100, Oleg Nesterov wrote: > On 11/16, Jamie Iles wrote: > > > > This can result in init becoming stoppable/killable after tracing. For > > example, running: > > > > while true; do kill -STOP 1; done & > > strace -p 1 > > > and then stopping

[PATCH 08/11] locking/ww_mutex: Yield to other waiters from optimistic spin

From: Nicolai Hähnle Lock stealing is less beneficial for w/w mutexes since we may just end up backing off if we stole from a thread with an earlier acquire stamp that already holds another w/w mutex that we also need. So don't spin optimistically unless we are sure that

[PATCH 09/11] locking/mutex: Initialize mutex_waiter::ww_ctx with poison when debugging

From: Nicolai Hähnle Help catch cases where mutex_lock is used directly on w/w mutexes, which otherwise result in the w/w tasks reading uninitialized data. Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Maarten Lankhorst

[PATCH 06/11] locking/ww_mutex: Notify waiters that have to back off while adding tasks to wait list

From: Nicolai Hähnle While adding our task as a waiter, detect if another task should back off because of us. With this patch, we establish the invariant that the wait list contains at most one (sleeping) waiter with ww_ctx->acquired > 0, and this waiter will be the

[PATCH] staging: fbtft: remove duplicate entries of ili9225

Signed-off-by: Amitesh Singh --- drivers/staging/fbtft/flexfb.c | 16 1 file changed, 16 deletions(-) diff --git a/drivers/staging/fbtft/flexfb.c b/drivers/staging/fbtft/flexfb.c index ce0d254..182e3c5 100644 --- a/drivers/staging/fbtft/flexfb.c +++

Re: INFO: rcu_sched detected stalls on CPUs/tasks with `kswapd` and `mem_cgroup_shrink_node`

+linux...@kvack.org -linux-...@vger.kernel.org Dear Michal, Thank you for your reply, and for looking at the log files. On 11/28/16 12:04, Michal Hocko wrote: On Sun 27-11-16 10:19:06, Donald Buczek wrote: On 24.11.2016 11:15, Michal Hocko wrote: On Mon 21-11-16 16:35:53, Donald Buczek

[PATCH 07/11] locking/ww_mutex: Wake at most one waiter for back off when acquiring the lock

From: Nicolai Hähnle The wait list is sorted by stamp order, and the only waiting task that may have to back off is the first waiter with a context. The regular slow path does not have to wake any other tasks at all, since all other waiters that would have to back off

Re: linux-next: build warning after merge of the wireless-drivers-next tree

Kalle Valo writes: > Barry Day writes: > >> On Mon, Nov 28, 2016 at 09:25:30AM +0200, Kalle Valo wrote: >>> Stephen Rothwell writes: >>> >>> > Hi all, >>> > >>> > After merging the wireless-drivers-next tree, today's linux-next

[GIT PULL] STi defconfig updates for v4.10 round 3

Hi Olof, Arnd and Kevin, Please consider this third round of multi_v7_defconfig updates for v4.10 : The following changes since commit 57dae748959d0abae2b382ccee68621a82f827c8: ARM: multi_v7_defconfig: Remove ST_THERMAL_SYSCFG Kconfig symbol (2016-10-21 17:05:54 +0200) are available in the

Re: [PATCH 01/22 v2] cpufreq/acpi-cpufreq: Convert to hotplug state machine

On Mon, Nov 28, 2016 at 10:51 AM, Sebastian Andrzej Siewior wrote: > Install the callbacks via the state machine. > > Cc: "Rafael J. Wysocki" > Cc: Viresh Kumar > Cc: linux...@vger.kernel.org > Signed-off-by: Sebastian Andrzej

Re: [PATCH 01/11] drm/vgem: Use ww_mutex_(un)lock even with a NULL context

On Mon, Nov 28, 2016 at 01:42:26PM +0100, Maarten Lankhorst wrote: > > + ww_mutex_lock(>lock.base, NULL); > Yuck, can we rename base to __NEVER_TOUCH_DIRECTLY_OUTSIDE_LOCKING_CORE? > It's harder to get them confused like that, even with a null context it's > illegal to call mutex_lock/unlock

Re: [PATCH 2/2] net: dsa: mv88e6xxx: Add 88E6176 device tree support

> I still wonder (and didn't get an answer back when I asked about this) > why a comment is preferred here. For other devices I know it's usual and > requested by the maintainers to use: > > compatible = "exact name", "earlyer device to match driver"; > > . This is more robust, documents

Re: [PATCH] HID: multitouch: handle external buttons for Precision Touchpads

On Fri, 25 Nov 2016, Benjamin Tissoires wrote: > According to > https://msdn.microsoft.com/en-us/library/windows/hardware/mt604195(v=vs.85).aspx > external buttons have some weird usage mapping: > - Button 2 Indicates Button State for external button for primary > (default left) clicking. > -

Re: Adding a .platform_init callback to sdhci_arasan_ops

On 28/11/16 13:20, Sebastian Frias wrote: > Hi Adrian, > > On 28/11/16 11:30, Adrian Hunter wrote: >> On 28/11/16 09:32, Michal Simek wrote: >>> +Sai for Xilinx perspective. >>> >>> On 25.11.2016 16:24, Sebastian Frias wrote: Hi, When using the Arasan SDHCI HW IP, there is a set of

Re: Kernel Panics on Xen ARM64 for Domain0 and Guest

] Modules linked in: [0.024708] [0.024804] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-rc7-next-20161128 #473 [0.025012] Hardware name: Foundation-v8A (DT) [0.025162] task: 80003d87 task.stack: 80003d844000 [0.025351] PC is at pcpu_alloc+0x88/0x6c0 [0.025490

Re: stmmac ethernet in kernel 4.9-rc6: coalescing related pauses.

Hi! > >> drivers/net/ethernet/stmicro/stmmac/common.h > >> #define STMMAC_COAL_TX_TIMER4 > >> #define STMMAC_MAX_COAL_TX_TICK 10 > >> #define STMMAC_TX_MAX_FRAMES256 > >> > >> If I lower the parameters, delays are gone, but I get netdev watchdog > >> backtrace followed by broken

Re: [PATCH net-next v3 1/4] net: phy: add an option to disable EEE advertisement

Am 28.11.2016 um 10:46 schrieb Jerome Brunet: > This patch adds an option to disable EEE advertisement in the generic PHY > by providing a mask of prohibited modes corresponding to the value found in > the MDIO_AN_EEE_ADV register. > > On some platforms, PHY Low power idle seems to be causing

[PATCH 05/11] locking/ww_mutex: Add waiters in stamp order

From: Nicolai Hähnle Add regular waiters in stamp order. Keep adding waiters that have no context in FIFO order and take care not to starve them. While adding our task as a waiter, back off if we detect that there is a waiter with a lower stamp in front of us. Make

[PATCH 01/11] drm/vgem: Use ww_mutex_(un)lock even with a NULL context

From: Nicolai Hähnle Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Maarten Lankhorst Cc: Daniel Vetter Cc: Chris Wilson Cc: dri-de...@lists.freedesktop.org

[PATCH 11/11] [rfc] locking/ww_mutex: Always spin optimistically for the first waiter

From: Nicolai Hähnle Check the current owner's context once against our stamp. If our stamp is lower, we continue to spin optimistically instead of backing off. This is correct with respect to deadlock detection because while the (owner, ww_ctx) pair may re-appear if

[PATCH 02/11] locking/ww_mutex: Re-check ww->ctx in the inner optimistic spin loop

From: Nicolai Hähnle In the following scenario, thread #1 should back off its attempt to lock ww1 and unlock ww2 (assuming the acquire context stamps are ordered accordingly). Thread #0 Thread #1 - -

[PATCH 03/11] locking/ww_mutex: Extract stamp comparison to __ww_mutex_stamp_after

From: Nicolai Hähnle The function will be re-used in subsequent patches. Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Maarten Lankhorst Cc: Daniel Vetter Cc: Chris Wilson

[PATCH 04/11] locking/ww_mutex: Set use_ww_ctx even when locking without a context

From: Nicolai Hähnle We will add a new field to struct mutex_waiter. This field must be initialized for all waiters if any waiter uses the ww_use_ctx path. So there is a trade-off: Keep ww_mutex locking without a context on the faster non-use_ww_ctx path, at the cost

Re: [PATCH net-next v3 4/4] ARM64: dts: meson: odroidc2: disable advertisement EEE for GbE.

Am 28.11.2016 um 10:46 schrieb Jerome Brunet: > Signed-off-by: Jerome Brunet > --- > arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 16 > 1 file changed, 16 insertions(+) > > diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts >

Re: [PATCH 01/11] drm/vgem: Use ww_mutex_(un)lock even with a NULL context

Op 28-11-16 om 13:20 schreef Nicolai Hähnle: > From: Nicolai Hähnle > > Cc: Peter Zijlstra > Cc: Ingo Molnar > Cc: Maarten Lankhorst > Cc: Daniel Vetter > Cc: Chris Wilson

Re: stmmac ethernet in kernel 4.4: coalescing related pauses?

Hi Pavel, On 23.11.2016 11:51, Pavel Machek wrote: I'm debugging strange delays during transmit in stmmac driver. They seem to be present in 4.4 kernel (and older kernels, too). Workload is burst of udp packets being sent, pause, burst of udp packets, ... Test code is attached, I use these

net/dccp: use-after-free in dccp_invalid_packet

Hi! I've got the following error report while running the syzkaller fuzzer. On commit d8e435f3ab6fea2ea324dce72b51dd7761747523 (Nov 26). dh->dccph_doff is being accessed (line 731) right after skb was freed (line 732) in net/dccp/ipv4.c. A reproducer is attached.

Re: [PATCH] cpuidle/powernv: staticise powernv_idle_driver

On Tue, Nov 22, 2016 at 6:08 AM, Andrew Donnellan wrote: > powernv_idle_driver isn't exported, it can be made static. Found by sparse. > > Signed-off-by: Andrew Donnellan Applied. Thanks, Rafael

Re: [PATCH 0/2] more quirks for hid-sensor-hub

On Fri, 25 Nov 2016, Benjamin Tissoires wrote: > Hi Jiri, > > here are 2 more quirks for the sensor-hub. Applied to for-4.10/microsoft-surface-3; in case you figure out a way how to auto-detect this behavior, please base such patches on top of this. Thanks, -- Jiri Kosina SUSE Labs

[PATCH net v2 1/1] net: macb: fix the RX queue reset in macb_rx()

On macb only (not gem), when a RX queue corruption was detected from macb_rx(), the RX queue was reset: during this process the RX ring buffer descriptor was initialized by macb_init_rx_ring() but we forgot to also set bp->rx_tail to 0. Indeed, when processing the received frames, bp->rx_tail

Re: [PATCH v2 0/3] Support multitouch touchpads in Surface TypeCover

On Fri, 25 Nov 2016, Benjamin Tissoires wrote: > this is mostly a resubmission of v1, with one patch exchanged. Alright, I'd be much happier when a chage such as the one done in 1st patch to hid-input would be done much earlier in the development process so that we'd have much more time for

Re: [PATCH V4 00/10] PM / OPP: Multiple regulator support

On 24 November 2016 at 17:06, Viresh Kumar wrote: > Hi, > > Some platforms (like TI) have complex DVFS configuration for CPU > devices, where multiple regulators are required to be configured to > change DVFS state of the device. This was explained well by Nishanth >

Re: [PATCH 1/1] net: macb: fix the RX queue reset in macb_rx()

Hi David, Le 28/11/2016 à 02:25, David Miller a écrit : > From: Cyrille Pitchen > Date: Fri, 25 Nov 2016 09:49:32 +0100 > >> On macb only (not gem), when a RX queue corruption was detected from >> macb_rx(), the RX queue was reset: during this process the RX ring >>

Re: [GIT PULL]: ARM ARTPEC changes for 4.10

On Mon, Nov 28, 2016 at 01:57:10PM +0100, Arnd Bergmann wrote: > On Monday, November 28, 2016 1:33:31 PM CET Jesper Nilsson wrote: > > > Hi Jesper and Niklas, > > > > > > I just found the old pull request while going through my mail backlog. > > > > > > A few things for you to remember for next

[PATCH v2 1/1] net: macb: ensure ordering write to re-enable RX smoothly

When a hardware issue happened as described by inline comments, the register write pattern looks like the following: + wmb(); There might be a memory barrier between these two write operations, so add wmb to ensure an flip from 0 to 1 for NCR. Signed-off-by: Zumeng Chen

Re: [PATCH v2 0/3] Support multitouch touchpads in Surface TypeCover

On Nov 28 2016 or thereabouts, Jiri Kosina wrote: > On Fri, 25 Nov 2016, Benjamin Tissoires wrote: > > > this is mostly a resubmission of v1, with one patch exchanged. > > Alright, I'd be much happier when a chage such as the one done in 1st > patch to hid-input would be done much earlier in

Re: [PATCH 1/6] perf tool: Add time-based utility functions

On Fri, Nov 25, 2016 at 02:39:54PM -0700, David Ahern wrote: SNIP > diff --git a/tools/perf/util/time-utils.h b/tools/perf/util/time-utils.h > new file mode 100644 > index ..4368a481251d > --- /dev/null > +++ b/tools/perf/util/time-utils.h > @@ -0,0 +1,12 @@ > +#ifndef _TIME_UTILS_H_

Re: [PATCH 1/6] perf tool: Add time-based utility functions

On Fri, Nov 25, 2016 at 02:39:54PM -0700, David Ahern wrote: > From: David Ahern > > Add function to parse a user time string of the form , > where start and stop are time in sec.nsec format. Both start and stop > times are optional. > > Add function to determine if a sample

Re: [PATCH 1/6] perf tool: Add time-based utility functions

On Fri, Nov 25, 2016 at 02:39:54PM -0700, David Ahern wrote: > From: David Ahern > > Add function to parse a user time string of the form , > where start and stop are time in sec.nsec format. Both start and stop > times are optional. > > Add function to determine if a sample

Re: [PATCH v2 1/1] net: macb: ensure ordering write to re-enable RX smoothly

Le 28/11/2016 à 14:55, Zumeng Chen a écrit : > When a hardware issue happened as described by inline comments, the register > write pattern looks like the following: > > > + wmb(); > > > There might be a memory barrier between these two write operations, so add wmb > to ensure an flip from 0

Re: [PATCH] net: fec: turn on device when extracting statistics

From: Nikita Yushchenko Date: Mon, 28 Nov 2016 10:06:31 +0300 > > > 28.11.2016 04:29, David Miller пишет: >> From: Nikita Yushchenko >> Date: Fri, 25 Nov 2016 13:02:00 +0300 >> >>> + int i, ret; >>> + >>> + ret =

Re: [PATCH 5/5] KVM: VMX: Handle RFLAGS.TF in skip_emulated_instruction

On 28/11/2016 05:18, Kyle Huey wrote: > + > + if (unlikely(vmx_get_rflags(vcpu) & X86_EFLAGS_TF)) { > + if (vcpu->guest_debug & KVM_GUESTDBG_SINGLESTEP) { > + vcpu->run->debug.arch.dr6 = DR6_BS | DR6_FIXED_1 | > +

[PATCH v3] crypto: add virtio-crypto driver

This patch introduces virtio-crypto driver for Linux Kernel. The virtio crypto device is a virtual cryptography device as well as a kind of virtual hardware accelerator for virtual machines. The encryption anddecryption requests are placed in the data queue and are ultimately handled by

Re: [RFC PATCH] crypto: Add IV generation algorithms

On Mon, Nov 21, 2016 at 03:40:09PM +0530, Binoy Jayan wrote: > Currently, the iv generation algorithms are implemented in dm-crypt.c. > The goal is to move these algorithms from the dm layer to the kernel > crypto layer by implementing them as template ciphers so they can be used > in relation

Re: [GIT PULL]: ARM ARTPEC changes for 4.10

On Monday, November 28, 2016 1:33:31 PM CET Jesper Nilsson wrote: > > Hi Jesper and Niklas, > > > > I just found the old pull request while going through my mail backlog. > > > > A few things for you to remember for next time: > > > > - please send pull requests "To: a...@kernel.org" so we know

Re: Adding a .platform_init callback to sdhci_arasan_ops

On 28/11/16 12:44, Adrian Hunter wrote: > On 28/11/16 13:20, Sebastian Frias wrote: >> Hi Adrian, >> >> On 28/11/16 11:30, Adrian Hunter wrote: >>> On 28/11/16 09:32, Michal Simek wrote: +Sai for Xilinx perspective. On 25.11.2016 16:24, Sebastian Frias wrote: > Hi, > >

Re: [RFC 1/1] LSM ptags: Add tagging of processes

Jose Bollo wrote: > The fact is that ptags is seat behind the implementation of the special > files in /proc/PID/attr/.. Thus, it has to return an allocated buffer. > I'm not aware of what kind of allocation is possible to use for this > subsystem. Is it possible to use vmalloc? I dont know. If

Re: [PATCH v2] scsi: aic94xx: Add a missing call to kfree

On 25.11.2016 13:23, Quentin Lambert wrote: > Most error branches following the call to kzalloc contain > a call to kfree. This patch add these calls where they are > missing and set the relevant pointers to NULL. > > This issue was found with Hector. > > Signed-off-by: Quentin Lambert

[PATCH] ARM: BCM5301X: Enable UART by default for BCM4708(1) and BCM4709(4)

From: Rafał Miłecki Every device tested so far got UART0 (at 0x18000300) working as serial console. It's most likely part of reference design and all vendors use it that way. It seems to be easier to enable it by default and just disable it if we ever see a device with

Re: [PATCH] orangefs: Axe some dead code

Perhaps we should modify Greg KH's "be-all, end-all document" on "HOWTO do Linux kernel development" then... you've contributed a boatload of work to the kernel since as far back as 2006, but I'm a newbie who just works in an isolated subsystem... people like me need a reliable and authoritative

Re: [PATCH v13 6/8] x86/arch_prctl: Add ARCH_[GET|SET]_CPUID

On Sun, 27 Nov 2016, Kyle Huey wrote: > +DEFINE_PER_CPU(u64, msr_misc_features_shadow); > + > +static void set_cpuid_faulting(bool on) > +{ > + u64 msrval; > + > + DEBUG_LOCKS_WARN_ON(!irqs_disabled()); The arch_prctl code path does not have interrupts disabled and there is no reason why

Re: [PATCH 7/10] mmc: sdhci-xenon: Add support to PHYs of Marvell Xenon SDHC

Hi Ulf, On 2016/11/28 19:13, Ulf Hansson wrote: >> >> As you suggest, I replace mmc_wait_for_cmd() with mmc_send_tuning(), to >> send commands for testing current sampling point set in our host PHY. >> >> According to my test result, it shows that mmc_send_tuning() can only >>

Re: [PATCH v2] Fix objtool with clang

On Sun, Nov 27, 2016 at 09:43:46PM -0500, Peter Foley wrote: > Clang doesn't support multiple arguments being passed to -Wp, so split > them. > > Fixes this error: > HOSTCC tools/objtool/fixdep.o > cat: tools/objtool/.fixdep.o.d: No such file or directory > > v2: > rebased onto perf/core

[PATCH] crypto: caam: check caam_emi_slow instead of re-lookup platform

Signed-off-by: Marcus Folkesson --- Russel King, sorry, I did not see your comment until now. drivers/crypto/caam/ctrl.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/crypto/caam/ctrl.c b/drivers/crypto/caam/ctrl.c index

[PATCH v6 1/3] spi-nor: Add support for Intel SPI serial flash controller

Add support for the SPI serial flash host controller found on many Intel CPUs including Baytrail and Braswell. The SPI serial flash controller is used to access BIOS and other platform specific information. By default the driver exposes a single read-only MTD device but with a module parameter

[PATCH v6 3/3] mfd: lpc_ich: Add support for Intel Apollo Lake SoC

Intel Apollo Lake SoC exposes serial SPI flash through the LPC device. The SPI flash host controller is not discoverable through PCI config cycles because P2SB (function 0 of the device 13) is hidden by the BIOS. We unhide the device briefly in order to read BAR 0 of the SPI host controller.

[PATCH 00/11] locking/ww_mutex: Keep sorted wait list to avoid stampedes

It turns out that the deadlock that I found last week was already implicitly fixed during the lock->owner redesign, by checking the WAITERS bit in the w/w lock fast path. However, since I had already started looking into sorting the wait list, here goes. The basic idea is to make sure that: 1.

Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup

On Mon, 28 Nov 2016, Peter Zijlstra wrote: > On Mon, Nov 28, 2016 at 01:16:45PM +0200, Jani Nikula wrote: >> Using rst we can produce decent HTML pages, and make them available at >> [1], in context. You don't have to read that, but it will be a lot more >> discoverable for

Re: [PATCH net-next v3 4/4] ARM64: dts: meson: odroidc2: disable advertisement EEE for GbE.

On Mon, 2016-11-28 at 13:31 +0100, Andreas Färber wrote: > Am 28.11.2016 um 10:46 schrieb Jerome Brunet: > > > > Signed-off-by: Jerome Brunet > > --- > >  arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 16 > > > >  1 file changed, 16 insertions(+) > >

Re: [PATCH v3] cpufreq: brcmstb-cpufreq: CPUfreq driver for older Broadcom STB SoCs

On Mon, Nov 28, 2016 at 11:14 AM, Arnd Bergmann wrote: > On Tuesday, November 22, 2016 1:32:45 PM CET Markus Mayer wrote: >> From: Markus Mayer >> >> This CPUfreq driver provides basic frequency scaling for older Broadcom >> STB SoCs that do not use AVS

Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup

On Mon, Nov 28, 2016 at 12:54:13PM +0100, Peter Zijlstra wrote: > On Mon, Nov 28, 2016 at 09:08:55AM -0200, Mauro Carvalho Chehab wrote: > > - use *foo* (for italics) or **foo** (for bold) instead of _foo_; > > That's daft, and also you're wrong. The normal convention is: > > /italic/ >

Re: [PATCH 1/1] net: macb: ensure ordering write to re-enable RX smoothly

On 2016年11月28日 17:22, Nicolas Ferre wrote: Le 28/11/2016 à 08:57, Zumeng Chen a écrit : When a hardware issue happened as described by inline comments, the register write pattern looks like the following: + wmb(); There might be a memory barrier between these two write operations,

Re: [PATCH v2 0/3] Support multitouch touchpads in Surface TypeCover

On Mon, 2016-11-28 at 14:58 +0100, Jiri Kosina wrote: > On Mon, 28 Nov 2016, Benjamin Tissoires wrote: > > My current plan is to target 4.10 merge window, but I'll do a bit > more  > stress-testing myself as well. Go ahead. I will test them on Surface Book when I'll be less busy with main

[PATCH net-next] bpf: selftests: include to fix build error

From: Colin Ian King Fix incomplete type build error on struct rlimit by including , fixes: test_lru_map.c:552:9: error: variable ‘r’ has initializer but incomplete type struct rlimit r = {RLIM_INFINITY, RLIM_INFINITY}; ^ test_lru_map.c:552:21: error:

Re: [PATCH] stmmac ethernet: remove cut & paste code

On Thu 2016-11-24 14:27:13, Joe Perches wrote: > On Thu, 2016-11-24 at 22:44 +0100, Pavel Machek wrote: > > On Thu 2016-11-24 12:05:25, Joe Perches wrote: > > > On Thu, 2016-11-24 at 12:05 +0100, Pavel Machek wrote: > > > > Remove duplicate code from _tx routines. > > > > > > trivia: > > > > > >

[RESEND PATCH V4 4/8] mfd: da9061: MFD core support

From: Steve Twiss MFD support for DA9061 is provided as part of the DA9062 device driver. The registers header file adds two new chip variant IDs defined in DA9061 and DA9062 hardware. The core header file adds new software enumerations for listing the valid

Re: [POC/RFC PATCH] overlayfs: constant inode numbers

On Mon, Nov 28, 2016 at 12:35 PM, Miklos Szeredi wrote: > On Mon, Nov 28, 2016 at 10:10 AM, Amir Goldstein wrote: @@ -258,12 +268,12 @@ static int ovl_copy_up_locked(struct den if (err) goto out_cleanup; -

[PATCH] stmmac: reduce code duplication getting basic descriptors

Remove code duplication getting basic descriptors. Signed-off-by: Pavel Machek diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c index f7133d0..ed20668 100644 ---

[PATCH v2 1/2] ARM: dts: da850-lcdk: add the dumb-vga-dac node

Add the dumb-vga-dac node to the board DT together with corresponding ports and vga connector. This allows to retrieve the edid info from the display automatically. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/da850-lcdk.dts | 58

[PATCH v2 0/2] ARM: dts: da850: tilcdc related DT changes

This series contains the last DT changes required for LCDC support on da850-lcdk. The first one adds the dumb-vga-dac nodes, the second limits the maximum pixel clock rate. v1 -> v2: - drop patch 3/3 (already merged) - use max-pixelclock instead of max-bandwidth for display mode limiting Bartosz

Re: [PATCH] Input: joystick: adi - change msleep to usleep_range for small msecs

Hi. ADI_INIT_DELAY/ADI_DATA_DELAY doesn't have to be exact, and a longer sleep doesn't matter. In the initilization sequence - first chunk of your patch - a way too long delay could in theory make the device fail to initialize. What's critical is that the mdelay() calls are precise. One day I'll

[PATCH 10/11] Documentation/locking/ww_mutex: Update the design document

From: Nicolai Hähnle Document the invariants we maintain for the wait list of ww_mutexes. Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Maarten Lankhorst Cc: Daniel Vetter Cc: Chris Wilson

Re: [PATCH net-next v3 3/4] dt: bindings: add ethernet phy eee-broken-modes option documentation

Am 28.11.2016 um 10:46 schrieb Jerome Brunet: > Signed-off-by: Jerome Brunet > --- > Documentation/devicetree/bindings/net/phy.txt | 2 ++ > 1 file changed, 2 insertions(+) Reviewed-by: Andreas Färber Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr.

Re: [PATCH net-next v3 2/4] dt-bindings: net: add EEE capability constants

Am 28.11.2016 um 10:46 schrieb Jerome Brunet: > Signed-off-by: Jerome Brunet > --- > include/dt-bindings/net/mdio.h | 19 +++ > 1 file changed, 19 insertions(+) > create mode 100644 include/dt-bindings/net/mdio.h Tested-by: Andreas Färber

Re: [PATCH net-next] bpf: selftests: include to fix build error

On 11/28/2016 12:45 PM, Colin King wrote: From: Colin Ian King Fix incomplete type build error on struct rlimit by including , fixes: test_lru_map.c:552:9: error: variable ‘r’ has initializer but incomplete type struct rlimit r = {RLIM_INFINITY, RLIM_INFINITY};

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

Hi Will, On Mon, Nov 28, 2016 at 6:52 PM, Will Deacon wrote: > Hi Ming, > > On Mon, Nov 28, 2016 at 11:10:14AM +0800, Ming Lei wrote: >> When I run stress-ng via the following steps on one ARM64 dual >> socket system(Cavium Thunder), the kernel oops[1] can often be >>

4.9-rc: only 3 CPUs out of 4 used

I have a HP ProLiant DL380 G3 server. It has two dual-core 32-bit Xeon CPUs. CONFIG_NR_CPUS=4 and has always been. Now, with 4.9-rc* (earliest tested was 4.9.0-rc2-00138-g14970f2), it only uses 3 CPUs out of 4: [0.00] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:2065

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

On Mon, 2016-11-28 at 11:10 +0800, Ming Lei wrote: > Hi Guys, > > When I run stress-ng via the following steps on one ARM64 dual > socket system(Cavium Thunder), the kernel oops[1] can often be > triggered after running the stress test for several hours(sometimes > it may take longer): > > - git

Re: [PATCH RFC] HID: cp2112: add IRQ chip handling

On Sat, 26 Nov 2016, Antonio Borneo wrote: > > I am currently running this patch in my local tree. > > It allows to attach a SMBus device completely on the CP2112, with a simple > > definition at the end of probe: > > > > { > > struct i2c_client *client; > >

Re: [PATCH V4 00/10] PM / OPP: Multiple regulator support

On Mon, Nov 28, 2016 at 2:41 PM, Viresh Kumar wrote: > On 24 November 2016 at 17:06, Viresh Kumar wrote: >> Hi, >> [cut] > Hi Rafael, > > The first version of this series was sent on 4th of October and its been > ~2 months now that this series

Re: [mdadm PATCH] Add failfast support.

NeilBrown writes: > Allow per-device "failfast" flag to be set when creating an > array or adding devices to an array. > > When re-adding a device which had the failfast flag, it can be removed > using --nofailfast. > > failfast status is printed in --detail and --examine output.

i8042 error at booting an Intel Cherry Trail-based device

Hi Dmitry, I've been testing a small machine with Intel Cherry Trail chipset, and noticed that the kernel spews errors always like: i8042: PNP: No PS/2 controller found. Probing ports directly. i8042: Can't read CTR while initializing i8042 i8042: probe of i8042 failed with error -5

Re: [dm-devel] [RFC PATCH 2/2] mm, mempool: do not throttle PF_LESS_THROTTLE tasks

On Thu 24-11-16 12:10:08, Mikulas Patocka wrote: > > > On Thu, 24 Nov 2016, Michal Hocko wrote: [...] > > Please note that even > > GFP_NOWAIT allocations will wake up kspwad which should clean up that > > The mempool is also using GFP_NOIO allocations - so do you claim that it > should not

Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v3

On Mon, Nov 28, 2016 at 12:00:41PM +0100, Vlastimil Babka wrote: > On 11/27/2016 02:19 PM, Mel Gorman wrote: > > > > 2-socket modern machine > > 4.9.0-rc5 4.9.0-rc5 > > vanilla hopcpu-v3 > > Hmeansend-64

Re: linux-next: build warning after merge of the wireless-drivers-next tree

Barry Day writes: > On Mon, Nov 28, 2016 at 09:25:30AM +0200, Kalle Valo wrote: >> Stephen Rothwell writes: >> >> > Hi all, >> > >> > After merging the wireless-drivers-next tree, today's linux-next build >> > (x86_64 allmodconfig) produced this

  1   2   3   4   5   6   7   8   9   10   >