Re: [PATCH v4 1/2] mmc: sdhci: export sdhci_execute_tuning()

On 05/12/16 04:10, Masahiro Yamada wrote: > Some SDHCI-compat controllers support not only SD, but also eMMC, > but they use different commands for tuning: CMD19 for SD, CMD21 for > eMMC. > > Due to the difference of the underlying mechanism, some controllers > (at least, the Cadence IP is the

Re: [PATCH 02/22] m68k/mac: macints - Modernize printing of kernel messages

On Wed, Dec 7, 2016 at 11:45 PM, Finn Thain wrote: > On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: > >> - Introduce helpers for printing debug messages, incl. dummies for >> validating format strings when debugging is disabled, >> - Convert from printk() to

Re: [PATCH v4 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

Hi Ulf, 2016-12-08 21:32 GMT+09:00 Ulf Hansson : > On 5 December 2016 at 03:10, Masahiro Yamada > wrote: >> Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. >> >> For SD, it basically relies on the SDHCI standard code. >> For

Re: [PATCH 2/5] staging: comedi: usbdux: Split a condition check in usbdux_alloc_usb_buffers()

On Thu, Dec 08, 2016 at 12:34:27PM +0100, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 8 Dec 2016 10:01:54 +0100 > > The functions "kcalloc" and "kzalloc" were called in four cases by the > function "usbdux_alloc_usb_buffers" without checking

Re: [patch] mm, compaction: add vmstats for kcompactd work

On Thu 08-12-16 09:04:12, Vlastimil Babka wrote: > On 12/08/2016 02:50 AM, David Rientjes wrote: > > A "compact_daemon_wake" vmstat exists that represents the number of times > > kcompactd has woken up. This doesn't represent how much work it actually > > did, though. > > > > It's useful to

Lockdep splat from destroy_workqueue() with RT_PREEMPT_FULL

Hi, I am seeing the following splat when stopping btattach on v4.4.30-rt41 with PREEMPT_RT_FULL with lockdep and slub_debug. The bad unlock balance seems to just be an effect of the lock having been overwritten with POISON_FREE, the real issue is that put_pwq_unlocked() is not resuming and

[PATCH v2 2/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

This patch provides an alternative mean to support memory above 16MiB (128Mib) by replacing 3byte address op codes by their associated 4byte address versions. Using the dedicated 4byte address op codes doesn't change the internal state of the SPI NOR memory as opposed to using other means such as

Re: [PATCH] arm64: Work around Falkor erratum 1009

On Thu, Dec 08, 2016 at 11:45:12AM +, Mark Rutland wrote: > On Wed, Dec 07, 2016 at 03:04:31PM -0500, Christopher Covington wrote: > > + asm volatile(ALTERNATIVE( > > +"nop \n" > > +"nop \n", > > +"tlbi vmalle1is \n" > > +"dsb

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

On Thu, Dec 08, 2016 at 01:15:56PM +0100, Geert Uytterhoeven wrote: > On Thu, Dec 8, 2016 at 11:10 AM, Daniel Vetter wrote: > > On Thu, Dec 08, 2016 at 12:01:19PM +1100, Benjamin Herrenschmidt wrote: > >> On Wed, 2016-11-23 at 10:03 +0200, Tomi Valkeinen wrote: > >> > Since the

Re: [PATCH] usbip: fix warning in vhci_hcd_probe/lockdep_init_map

On 12/07/2016 09:12 PM, fx IWATA NOBUO wrote: > Dear Shuah, > >> I noticed that in many places sysfs_attr_init() is called before populating >> the fields such as name etc. However, I don't think the order matters. >> >> sysfs_attr_init() doesn't depend on name or any other fields being set: >>

Re: [PATCH] vfio/pci: Support error recovery

On 12/06/2016 11:35 PM, Alex Williamson wrote: > On Tue, 6 Dec 2016 18:46:04 +0800 > Cao jin wrote: > >> On 12/06/2016 12:59 PM, Alex Williamson wrote: >>> On Tue, 6 Dec 2016 05:55:28 +0200 >>> "Michael S. Tsirkin" wrote: >>> On Mon, Dec 05,

Re: [PATCH] kasan: turn on -fsanitize-address-use-after-scope

On Thu, Dec 8, 2016 at 1:48 PM, Andrey Ryabinin wrote: > In the upcoming gcc7 release release, the -fsanitize=kernel-address option > at first implied new -fsanitize-address-use-after-scope option. > This would cause link errors on older kernels because they don't have >

RE: [RFC PATCH net-next v3 1/2] macb: Add 1588 support in Cadence GEM.

> -Original Message- > From: Richard Cochran [mailto:richardcoch...@gmail.com] > Sent: Wednesday, December 07, 2016 11:04 PM > To: Andrei Pistirica - M16132 > Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm- > ker...@lists.infradead.org; da...@davemloft.net; >

Re: [PATCH v3] kvm: svm: Use the hardware provided GPA instead of page walk

On 29/11/2016 20:38, Brijesh Singh wrote: > > > On 11/29/2016 12:20 PM, Thomas Gleixner wrote: >> On Tue, 29 Nov 2016, Brijesh Singh wrote: >>> --- a/arch/x86/kvm/emulate.c >>> +++ b/arch/x86/kvm/emulate.c >>> @@ -5483,3 +5483,11 @@ void emulator_writeback_register_cache(struct >>>

Re: [patch] mm, compaction: add vmstats for kcompactd work

On 12/08/2016 02:50 AM, David Rientjes wrote: A "compact_daemon_wake" vmstat exists that represents the number of times kcompactd has woken up. This doesn't represent how much work it actually did, though. It's useful to understand how much compaction work is being done by kcompactd versus

Re: [PATCH v5 5/5] ARM: configs: Add I2C support for STM32 defconfig

Hi Alex, 2016-12-08 9:38 GMT+01:00 Alexandre Torgue : > Hi Cedric, > > On 12/08/2016 09:26 AM, M'boumba Cedric Madianga wrote: >> >> Signed-off-by: M'boumba Cedric Madianga >> --- >> arch/arm/configs/stm32_defconfig | 3 +++ >> 1 file changed,

Re: [PATCH] platform: Introduce button support for the Surface 3

On Dec 07 2016 or thereabouts, Dmitry Torokhov wrote: > On Mon, Dec 05, 2016 at 04:10:33PM +0100, Benjamin Tissoires wrote: > > The Surface 3 is not following the ACPI spec for PNP0C40, but nearly. > > The device is connected to a I2C device that might have some magic > > but we don't know about.

Re: [PATCH v5 4/5] ARM: dts: Add I2C1 support for STM32429 eval board

Hi Alex, 2016-12-08 9:39 GMT+01:00 Alexandre Torgue : > Hi Cedric, > > On 12/08/2016 09:26 AM, M'boumba Cedric Madianga wrote: >> >> Signed-off-by: M'boumba Cedric Madianga >> --- >> arch/arm/boot/dts/stm32429i-eval.dts | 6 ++ >> 1 file

Re: [PATCH] doc: Explain light-handed markup preference a bit better

Em Wed, 7 Dec 2016 12:39:24 -0700 Jonathan Corbet escreveu: > On Wed, 7 Dec 2016 16:42:58 +0100 > Daniel Vetter wrote: > > > We already had a super-short blurb, but worth extending it I think: > > We're still pretty far away from anything like a

Re: [PATCH v3 4/6] mfd: dt: Add bindings for the Aspeed LPC Host Controller (LHC)

On Thu, 2016-12-08 at 12:42 +1030, Joel Stanley wrote: > > On Tue, Dec 6, 2016 at 1:23 PM, Andrew Jeffery wrote: > > The LPC bus pinmux configuration on fifth generation Aspeed SoCs depends > > on bits in both the System Control Unit and the LPC Host Controller. > > > > The

Re: [PATCH] x86/smpboot: Make logical package management more robust

On Thu, Dec 08, 2016 at 10:04:25AM +0100, Thomas Gleixner wrote: > @@ -289,16 +293,17 @@ int topology_update_package_map(unsigned > if (test_and_set_bit(pkg, physical_package_map)) > goto found; > > - if (logical_packages_frozen) { > -

Re: Tearing down DMA transfer setup after DMA client has finished

On 08/12/2016 13:03, Geert Uytterhoeven wrote: > Måns Rullgård wrote: > >> Geert Uytterhoeven writes: >> >>> Can you fall back to PIO if requesting a channel fails? >> >> Why are we debating this nonsense? There is an easy fix that doesn't >> require changing the semantics of existing functions

Re: [PATCH v5 2/5] i2c: Add STM32F4 I2C driver

Hi M'boumba, [auto build test WARNING on wsa/i2c/for-next] [also build test WARNING on v4.9-rc8 next-20161208] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/M-boumba-Cedric-Madianga/Add

Re: [PATCH 1/5] staging: comedi: serial2002: Combine four kcalloc() calls into one in serial2002_setup_subdevs()

The original code was simpler. regards, dan carpenter

[PATCH v5 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. For SD, it basically relies on the SDHCI standard code. For eMMC, this driver provides some callbacks to support the hardware part that is specific to this IP design. Signed-off-by: Masahiro Yamada

[PATCH v5 0/2] mmc: sdhci: export sdhci_execute_tuning(), then add Cadence SDHCI driver

1/2 exports sdhci_execute_tuning(), which I want to use for 2/2. 2/2 adds a new driver for Cadence's controller IP. Changes in v2: - Remove unnecessary "select MMC_SDHCI_IO_ACCESSORS" Masahiro Yamada (2): mmc: sdhci: export sdhci_execute_tuning() mmc: sdhci-cadence: add Cadence SD4HC

[PATCH v5 1/2] mmc: sdhci: export sdhci_execute_tuning()

Some SDHCI-compat controllers support not only SD, but also eMMC, but they use different commands for tuning: CMD19 for SD, CMD21 for eMMC. Due to the difference of the underlying mechanism, some controllers (at least, the Cadence IP is the case) provide their own registers for the eMMC tuning.

Re: [PATCH 4/5] staging: comedi: usbduxsigma: Split a condition check in usbduxsigma_alloc_usb_buffers()

On 08/12/16 11:37, SF Markus Elfring wrote: From: Markus Elfring Date: Thu, 8 Dec 2016 11:15:40 +0100 The functions "kcalloc" and "kzalloc" were called in four cases by the function "usbduxsigma_alloc_usb_buffers" without checking immediately if they succeded.

Re: [PATCH] x86/smpboot: Make logical package management more robust

On Thu, 8 Dec 2016, Peter Zijlstra wrote: > On Thu, Dec 08, 2016 at 10:04:25AM +0100, Thomas Gleixner wrote: > > @@ -289,16 +293,17 @@ int topology_update_package_map(unsigned > > if (test_and_set_bit(pkg, physical_package_map)) > > goto found; > > > > - if

Re: [PATCH] x86/smpboot: Make logical package management more robust

On Thu, 8 Dec 2016, Peter Zijlstra wrote: > On Thu, Dec 08, 2016 at 01:49:28PM +0100, Thomas Gleixner wrote: > > > > > > - if (logical_packages > __max_logical_packages) { > > > > - pr_warn("Detected more packages (%u), then computed by > > > > BIOS data (%u).\n", > > > > -

Re: [PATCH 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

Thanks, have changed. Will repost after i386 test is OK. On 12/08/16 at 05:41pm, kbuild test robot wrote: > Hi Baoquan, > > [auto build test ERROR on tip/x86/core] > [also build test ERROR on v4.9-rc8 next-20161208] > [if your patch is applied to the wrong git tree, please

Re: [RFC PATCH 00/19] ide: remove deprecated host drivers (part 1)

Hi, On Friday, July 08, 2016 07:07:46 PM Bartlomiej Zolnierkiewicz wrote: > > Hi Dave, > > What is your opinion on this patchset? Ping.. since there was no negative (or any other) feedback I think that this can be put into -next for some wider exposure.. Best regards, -- Bartlomiej

Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers

On Thu 08-12-16 14:00:20, David Hildenbrand wrote: > Am 08.12.2016 um 11:33 schrieb Michal Hocko: > > From: Michal Hocko > > > > Using kmalloc with the vmalloc fallback for larger allocations is a > > common pattern in the kernel code. Yet we do not have any common helper > >

Re: [PATCH] pci-error-recover: doc cleanup

On Thu, 8 Dec 2016 16:16:14 +0800 Cao jin wrote: > The platform resets the link, and then calls the link_reset() callback > on all affected device drivers. This is a PCI-Express specific state > -and is done whenever a non-fatal error has been detected that can be >

Re: [PATCH v3 6/6] net: smmac: allow configuring lower pbl values

Hi, In subject: s/smmac/stmmac/ Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)

Re: [PATCH v4 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

On 8 December 2016 at 13:52, Masahiro Yamada wrote: > Hi Ulf, > > 2016-12-08 21:32 GMT+09:00 Ulf Hansson : >> On 5 December 2016 at 03:10, Masahiro Yamada >> wrote: >>> Add a driver for the Cadence SD4HC

[PATCH] kasan: turn on -fsanitize-address-use-after-scope

In the upcoming gcc7 release release, the -fsanitize=kernel-address option at first implied new -fsanitize-address-use-after-scope option. This would cause link errors on older kernels because they don't have two new functions required for use-after-scope support. Therefore, gcc7 changed default

Re: [PATCH] MAINTAINERS: clarify that "B:" is the URI where to file bugs

On Thu, 08 Dec 2016, "Rafael J. Wysocki" wrote: > And you can even achieve it with the current definition of entires > like this: > > M: (no bug reports please) I've been told the entries should be machine parseable, without free form text such as that. Also the reason a URI

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

On Thu, 08 Dec 2016, Geert Uytterhoeven wrote: > On Thu, Dec 8, 2016 at 3:02 PM, Daniel Vetter wrote: >> If you're this good at mainting gpu and display subsystems, maybe you >> want to take over? > > No please ;-) Now that is indeed the right answer, and

[PATCH 2/8] x86/efi: Allow invocation of arbitrary runtime services [ver #6]

Provide the ability to perform mixed-mode runtime service calls for x86 in the same way that commit 0a637ee61247bd4bed9b2a07568ef7a1cfc76187 ("x86/efi: Allow invocation of arbitrary boot services") provides the ability to invoke arbitrary boot services. Suggested-by: Lukas Wunner

[PATCH 1/8] efi: use typed function pointers for runtime services table [ver #6]

From: Ard Biesheuvel Instead of using void pointers, and casting them to correctly typed function pointers upon use, declare the runtime services pointers as function pointers using their respective prototypes, for which typedefs are already available. Signed-off-by:

[PATCH v5 5/7] IIO: add bindings for STM32 timer trigger driver

Define bindings for STM32 timer trigger version 4: - remove triggers enumeration from DT - add reg parameter version 3: - change file name - add cross reference with mfd bindings version 2: - only keep one compatible - add DT parameters to set lists of the triggers: one list describe the

[PATCH 3/8] arm/efi: Allow invocation of arbitrary runtime services [ver #6]

efi_call_runtime() is provided for x86 to be able abstract mixed mode support. Provide this for ARM also so that common code work in mixed mode also. Suggested-by: Lukas Wunner Signed-off-by: David Howells --- arch/arm/include/asm/efi.h |1 +

[PATCH 0/8] efi: Pass secure boot mode to kernel [ver #6]

Here's a set of patches that can determine the secure boot state of the UEFI BIOS and pass that along to the main kernel image. This involves generalising ARM's efi_get_secureboot() function and making it mixed-mode safe. Changes: Ver 6: - Removed unnecessary variable init and trimmed

Re: [Lsf-pc] LSF/MM 2017: Call for Proposals

On Thu 08-12-16 13:26:19, Michal Hocko wrote: > On Wed 07-12-16 06:57:06, James Bottomley wrote: > [...] > > Just on this point, since there seems to be a lot of confusion: lsf-pc > > is the list for contacting the programme committee, so you cannot > > subscribe to it. > > > > There is no

Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers

Am 08.12.2016 um 11:33 schrieb Michal Hocko: From: Michal Hocko Using kmalloc with the vmalloc fallback for larger allocations is a common pattern in the kernel code. Yet we do not have any common helper for that and so users have invented their own helpers. Some of them are

Re: [PATCH 08/11] ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel

On Thu, Dec 8, 2016 at 2:11 AM, Dan Williams wrote: > On Tue, Nov 29, 2016 at 11:21 PM, Lv Zheng wrote: >> ACPICA commit cac6790954d4d752a083e610b8a22febcd07 >> >> This patch back ports Linux acpi_get_table_with_size() and >>

Re: linux-next: build failure in the powerpc allyesconfig build

On Monday, December 5, 2016 4:22:04 PM CET Stephen Rothwell wrote: > Hi all, > > After mergeing everything but Andrew's tree, today's linux-next build > (powerpc allyesconfig) failed like this: > > kallsyms failure: relative symbol value 0xc000 out of range in > relative mode > > I

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

On Thu, 8 Dec 2016 11:06:56 + Mel Gorman wrote: > On Thu, Dec 08, 2016 at 11:43:08AM +0100, Jesper Dangaard Brouer wrote: > > > That's expected. In the initial sniff-test, I saw negligible packet loss. > > > I'm waiting to see what the full set of network tests

[PATCH v2 4/6] perf sched timehist: Skip non-idle events when necessary

Sometimes it only focuses on idle-related events like upcoming idle-hist feature. In this case we don't want to see other event to reduce noise. Signed-off-by: Namhyung Kim --- tools/perf/builtin-sched.c | 25 ++--- 1 file changed, 18 insertions(+), 7

[PATCH v2 3/6] perf sched timehist: Save callchain when entering idle

In order to investigate reason of idle, it needs to keep the callchains when entering to idle. This can be identified sched_switch event having next_pid as 0. Signed-off-by: Namhyung Kim --- tools/perf/builtin-sched.c | 29 + 1 file changed, 29

[PATCH v2 5/6] perf sched timehist: Add -I/--idle-hist option

The --idle-hist option is to analyze system idle state so which process makes cpu to go idle. If this option is specified, non-idle events will be skipped and processes switching to/from idle will be shown. This option is mostly useful when used with --summary(-only) option. In the idle-time

[PATCH v2 6/6] perf sched timehist: Show callchains for idle stat

When --idle-hist option is used with --summary, it now shows idle stats with callchains like below: Idle stats by callchain: CPU 0: 902.195 msec Idle time (msec) Count Callchains --

[PATCH v2 1/6] perf sched timehist: Split is_idle_sample()

The is_idle_sample() function actually does more than determining whether sample come from idle task. Split the callchain part into save_task_callchain() to make it clearer. Also checking prev_pid from trace data looks preferred than just checking sample->pid since it's possible, although rare,

[PATCHSET 0/6] perf sched timehist: Introduce --idle-hist option (v2)

Hi, This patchset implements the idle hist feature which analyze reason of system idle. Sometimes I need to investigate what makes CPUs to go idle even though I have jobs to do. It may be due to I/O, waiting on lock or whatever. To identify the reasons it only accounts events related to idle

Re: Tearing down DMA transfer setup after DMA client has finished

Geert Uytterhoeven writes: > On Thu, Dec 8, 2016 at 12:44 PM, Måns Rullgård wrote: >> Vinod Koul writes: >>> On Wed, Dec 07, 2016 at 04:45:58PM +, Måns Rullgård wrote: Vinod Koul writes: > On Tue,

[PATCH v2 0/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

Hi all, this series of patches is based on next-20161208 and can also be applied to the git://github.com/spi-nor/linux.git tree. It has been extracted from the SFDP series and is resent as a standalone series. This series fixes compatibility issue between Linux and many bootloaders when using

Re: Tearing down DMA transfer setup after DMA client has finished

On 08/12/2016 13:20, Måns Rullgård wrote: > The only problem we have is that nobody envisioned hardware where the > dma engine indicates completion slightly too soon. I suspect there's a > fifo or such somewhere, and the interrupt is triggered when the last > byte has been placed in the fifo

Re: [PATCH 01/22] m68k/atari: Modernize printing of kernel messages

On Wed, Dec 7, 2016 at 11:36 PM, Finn Thain wrote: > On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: >> - Convert from printk() to pr_*(), >> - Add missing continuations, to fix user-visible breakage, >> - Drop useless WARNING prefix, >> - Move trailing spaces to

[PATCH v2 1/2] mtd: spi-nor: rename SPINOR_OP_* macros of the 4-byte address op codes

This patch renames the SPINOR_OP_* macros of the 4-byte address instruction set so the new names all share a common pattern: the 4-byte address name is built from the 3-byte address name appending the "_4B" suffix. The patch also introduces new op codes to support other SPI protocols such as SPI

Re: Tearing down DMA transfer setup after DMA client has finished

On 08/12/2016 13:44, Måns Rullgård wrote: > Mason writes: > >> On 08/12/2016 13:20, Måns Rullgård wrote: >> >>> The only problem we have is that nobody envisioned hardware where the >>> dma engine indicates completion slightly too soon. I suspect there's a >>> fifo or such

Re: [PATCH 0/5] staging-COMEDI: Fine-tuning for three functions

On Thu, Dec 08, 2016 at 12:30:20PM +0100, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 8 Dec 2016 11:37:37 +0100 > > Some update suggestions were taken into account > from static source code analysis. > > Markus Elfring (5): > Combine four

Re: [PATCH 2/2] mm, oom: do not enfore OOM killer for __GFP_NOFAIL automatically

On Thu 08-12-16 21:53:44, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Tue 06-12-16 19:38:38, Tetsuo Handa wrote: > > > You are trying to increase possible locations of lockups by changing > > > default behavior of __GFP_NOFAIL. > > > > I disagree. I have tried to explain that it is much more

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

Dear dri-devel folks, My sincere apologies for hitting send on that mail. I got real mad and angry and typed a mail I shouldn't have submitted - pouring oil into flames for shit and giggles just doesn't help anyone, and it detracts from moving things forward and improving the code and drivers and

ATH9 driver issues on ARM64

Hi, Did anyone test Atheros ATH9 driver(drivers/net/wireless/ath/ath9k/) on ARM64. The end point is TP link wifi card with which supports only legacy interrupts. We are trying to test it on ARM64 with (drivers/pci/host/pcie-xilinx-nwl.c) as root port. EP is getting enumerated and able to link

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

Hi Daniel, On Thu, Dec 8, 2016 at 3:02 PM, Daniel Vetter wrote: > On Thu, Dec 08, 2016 at 01:15:56PM +0100, Geert Uytterhoeven wrote: >> On Thu, Dec 8, 2016 at 11:10 AM, Daniel Vetter wrote: >> > On Thu, Dec 08, 2016 at 12:01:19PM +1100, Benjamin Herrenschmidt

Re: [PATCH 2/2 v2] sched: use load_avg for selecting idlest group

On 8 December 2016 at 15:09, Matt Fleming wrote: > On Mon, 05 Dec, at 01:35:46PM, Matt Fleming wrote: >> On Mon, 05 Dec, at 10:27:36AM, Vincent Guittot wrote: >> > >> > Hi Matt, >> > >> > Thanks for the results. >> > >> > During the review, it has been pointed out by

Re: vUDC

Hi Elen, Adding k.opas...@samsung.com On Thu, Dec 8, 2016 at 7:07 AM, Elen Niedermeyer wrote: > Dear Sir or Madam, > > I'm trying to run usbip-vudc since a few days. I want to access my emulated > usb devices over usbip. > I use Ubuntu 16.04.01 and updated my

Re: [PATCH v2] xen/scsifront: don't request a slot on the ring until request is ready

On 12/02/2016 01:15 AM, Juergen Gross wrote: Instead of requesting a new slot on the ring to the backend early, do so only after all has been setup for the request to be sent. This makes error handling easier as we don't need to undo the request id allocation and ring slot allocation.

Re: [PATCH v4 1/2] mmc: sdhci: export sdhci_execute_tuning()

On 08/12/16 13:49, Adrian Hunter wrote: > On 05/12/16 04:10, Masahiro Yamada wrote: >> Some SDHCI-compat controllers support not only SD, but also eMMC, >> but they use different commands for tuning: CMD19 for SD, CMD21 for >> eMMC. >> >> Due to the difference of the underlying mechanism, some

Re: [PATCH v4 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

On 05/12/16 04:10, Masahiro Yamada wrote: > Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. > > For SD, it basically relies on the SDHCI standard code. > For eMMC, this driver provides some callbacks to support the > hardware part that is specific to this IP design. > >

Re: [PATCH v2] rpmsg: qcom_smd: Add support for "label" property

On 2016-12-02 2:06 PM, Bjorn Andersson wrote: Add support for the "label" property, used to give the edge a name other than the one of the DT node. This allows the implementor to provide consistently named edges when using the rpmsg character device. Signed-off-by: Bjorn Andersson

[PATCH v5 4/7] PWM: add PWM driver for STM32 plaftorm

This driver adds support for PWM driver on STM32 platform. The SoC have multiple instances of the hardware IP and each of them could have small differences: number of channels, complementary output, auto reload register size... version 4: - detect at probe time hardware capabilities - fix

[PATCH v5 3/7] PWM: add pwm-stm32 DT bindings

Define bindings for pwm-stm32 version 2: - use parameters instead of compatible of handle the hardware configuration Signed-off-by: Benjamin Gaignard --- .../devicetree/bindings/pwm/pwm-stm32.txt | 33 ++ 1 file changed, 33 insertions(+)

[PATCH v5 7/7] ARM: dts: stm32: add STM32 General Purpose Timer driver in DT

Add General Purpose Timers and it sub-nodes into DT for stm32f4. Define and enable pwm1 and pwm3 for stm32f469 discovery board version 5: - rename gptimer node to timers - re-order timers node par addresses version 4: - remove unwanted indexing in pwm@ and timer@ node name - use "reg" instead of

[PATCH 1/7] dell-led: remove GUID check from dell_micmute_led_set()

As dell_micmute_led_set() no longer uses the dell_wmi_perform_query() method, which was removed in 0c41a08 ("dell-led: use dell_smbios_send_request() for performing SMBIOS calls"), the DELL_APP_GUID check is redundant and thus can be safely removed. Signed-off-by: Michał Kępień

[PATCH 7/7] dell-led: move driver to drivers/platform/x86/dell-wmi-led.c

The dell-led driver handles a specific WMI GUID present on some Dell laptops and as such it belongs in the x86 platform driver subsystem. Source code is moved along with the relevant Kconfig and Makefile entries with some minor modifications: - Kconfig option is renamed from

[PATCH 0/7] Move dell-led to drivers/platform/x86

This patch series moves the dell-led driver from the LED subsystem to the x86 platform driver subsystem. I decided to also CC the sound subsystem contacts for the whole series as sound/pci/hda/dell_wmi_helper.c is also affected. The original motivation behind this effort was to move all code

[PATCH 4/7] dell-led: remove dell_app_wmi_led_set()

All calls to dell_app_wmi_led_set() have been replaced with direct calls to dell_micmute_led_set(), so the former can be safely removed along with its related enum. Signed-off-by: Michał Kępień --- drivers/leds/dell-led.c | 17 - include/linux/dell-led.h | 5

[PATCH 6/7] dell-led: remove code related to mic mute LED

With dell_micmute_led_set() moved to drivers/platform/x86/dell-laptop.c, all remnants of the mic mute LED handling code can be removed from drivers/leds/dell-led.c, restoring it back to the state it was in before db6d8cc ("dell-led: add mic mute led interface"). Signed-off-by: Michał Kępień

[PATCH 5/7] dell-laptop: import dell_micmute_led_set() from drivers/leds/dell-led.c

To ensure all users of dell-smbios are in drivers/platform/x86, move the dell_micmute_led_set() method from drivers/leds/dell-led.c to drivers/platform/x86/dell-laptop.c. Signed-off-by: Michał Kępień --- drivers/leds/dell-led.c| 29 -

[PATCH 3/7] ALSA: hda - use dell_micmute_led_set() instead of dell_app_wmi_led_set()

When the dell_app_wmi_led_set() method was introduced in db6d8cc ("dell-led: add mic mute led interface"), it was implemented as an easily extensible entry point for other modules to set the state of various LEDs. However, almost three years later it is still only used to control the mic mute

Re: [PATCH v2 0/5] kthread: make struct kthread kmalloc'ed

On Tue, Nov 29, 2016 at 06:50:37PM +0100, Oleg Nesterov wrote: > Hello, > > I think that these patches were lost in confusing discussion, let me resend. > The only change is that I added the acks from Thomas and Petr. > > More to come. Acked-by: Peter Zijlstra (Intel)

[PATCH] ASoC: rsnd: don't double free kctrl

From: Colin Ian King On an error, snd_ctl_add already free's kctrl, so calling snd_ctl_free_one to free it again leads to a double free error. Fix this by removing the extraneous snd_ctl_free_one call. Issue found using static analysis with CoverityScan, CID 1372908

Re: Tearing down DMA transfer setup after DMA client has finished

Mason writes: > On 08/12/2016 13:44, Måns Rullgård wrote: > >> Mason writes: >> >>> On 08/12/2016 13:20, Måns Rullgård wrote: >>> The only problem we have is that nobody envisioned hardware where the dma engine indicates completion slightly too

Re: [PATCH 2/2 v2] sched: use load_avg for selecting idlest group

On Mon, 05 Dec, at 01:35:46PM, Matt Fleming wrote: > On Mon, 05 Dec, at 10:27:36AM, Vincent Guittot wrote: > > > > Hi Matt, > > > > Thanks for the results. > > > > During the review, it has been pointed out by Morten that the test condition > > (100*this_avg_load < imbalance_scale*min_avg_load)

Re: [PATCH 03/10] perf sched timehist: Handle zero sample->tid properly

On Wed, Dec 07, 2016 at 11:06:29AM +0900, Namhyung Kim wrote: > On Mon, Dec 05, 2016 at 07:52:57PM -0800, David Ahern wrote: > > On 12/5/16 7:40 PM, Namhyung Kim wrote: > > > Sometimes samples have tid of 0 but non-0 pid. It ends up having a > > > > Any idea how that happens? > > It seems that

[PATCH V1] pinctrl:pxa:pinctrl-pxa2xx:- No need of devm functions

In functions pxa2xx_build_functions, the memory allocated for 'functions' is live within the function only. After the allocation it is immediately freed with devm_kfree. There is no need to allocate memory for 'functions' with devm function so replace devm_kcalloc with kcalloc and devm_kfree with

Re: [PATCH] firwmare: Correct handling of fw_state_wait() return value

On 12/07/2016 02:01 AM, Bjorn Andersson wrote: When request_firmware() finds an already open firmware object it will wait for that object to become fully loaded and then check the status. As __fw_state_wait_common() succeeds the timeout value returned will be truncated in

fs, net: deadlock between bind/splice on af_unix

Hello, I am getting the following deadlock reports while running syzkaller fuzzer on 318c8932ddec5c1c26a4af0f3c053784841c598e (Dec 7). [ INFO: possible circular locking dependency detected ] 4.9.0-rc8+ #77 Not tainted --- syz-executor0/3155 is

Re: ATH9 driver issues on ARM64

[+cc Kalle, ath9k list] On Thu, Dec 08, 2016 at 01:49:42PM +, Bharat Kumar Gogada wrote: > Hi, > > Did anyone test Atheros ATH9 driver(drivers/net/wireless/ath/ath9k/) > on ARM64. The end point is TP link wifi card with which supports > only legacy interrupts. If it works on other arches

[PATCH] usb: gadget: f_fs: Fix possibe deadlock

When system try to close /dev/usb-ffs/adb/ep0 on one core, at the same time another core try to attach new UDC, which will cause deadlock as below scenario. Thus we should release ffs lock before issuing unregister_gadget_item(). [ 52.642225] c1

Re: [GIT PULL] efi: Pass secure boot mode to kernel

On Thu, 08 Dec, at 11:45:17AM, David Howells wrote: > Hi Matt, Ard, > > Is it too late to request this for the upcoming merge window? For something as non-trivial as this, yes, it's too late. We generally close the EFI tree window for new features around -rc5 time. > Also, I've made > Lukas's

Re: Tearing down DMA transfer setup after DMA client has finished

Hi Måns, On Thu, Dec 8, 2016 at 12:47 PM, Måns Rullgård wrote: > Geert Uytterhoeven writes: >> On Thu, Dec 8, 2016 at 11:54 AM, Mason wrote: >>> On 08/12/2016 11:39, Vinod Koul wrote: On Wed, Dec 07, 2016 at 04:45:58PM +, Måns

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

On Thu, Dec 8, 2016 at 11:10 AM, Daniel Vetter wrote: > On Thu, Dec 08, 2016 at 12:01:19PM +1100, Benjamin Herrenschmidt wrote: >> On Wed, 2016-11-23 at 10:03 +0200, Tomi Valkeinen wrote: >> > Since the fbdev framework is in maintenance mode and all new display >> > drivers >> >

Re: [PATCH v4 2/2] mmc: sdhci-cadence: add Cadence SD4HC support

On 5 December 2016 at 03:10, Masahiro Yamada wrote: > Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. > > For SD, it basically relies on the SDHCI standard code. > For eMMC, this driver provides some callbacks to support the > hardware part that is

[PATCH v5 6/7] IIO: add STM32 timer trigger driver

Timers IPs can be used to generate triggers for other IPs like DAC, ADC or other timers. Each trigger may result of timer internals signals like counter enable, reset or edge, this configuration could be done through "master_mode" device attribute. A timer device could be triggered by other

Re: [PATCH v4 1/2] mmc: sdhci: export sdhci_execute_tuning()

On 5 December 2016 at 03:10, Masahiro Yamada wrote: > Some SDHCI-compat controllers support not only SD, but also eMMC, > but they use different commands for tuning: CMD19 for SD, CMD21 for > eMMC. > > Due to the difference of the underlying mechanism, some

[PATCH 4/8] efi: Add SHIM and image security database GUID definitions [ver #6]

Add the definitions for shim and image security database, both of which are used widely in various Linux distros. Signed-off-by: Josh Boyer Signed-off-by: David Howells Reviewed-by: Ard Biesheuvel ---

[PATCH 8/8] efi: Add EFI_SECURE_BOOT bit [ver #6]

From: Josh Boyer UEFI machines can be booted in Secure Boot mode. Add a EFI_SECURE_BOOT bit that can be passed to efi_enabled() to find out whether secure boot is enabled. This will be used by the SysRq+x handler, registered by the x86 arch, to find out whether

  1   2   3   4   5   6   7   8   9   10   >