Re: [PATCH v4 0/5] pinctrl: mediatek: add pinctrl/GPIO/EINT driver for mt2701

On Wed, Jan 27, 2016 at 2:24 AM, Biao Huang wrote: > Change in v4: > 1. create a sperate patch for direction setting of input-enable/disalbe and > input-schmitt-enable/disable. So I've merged the patches affecting drivers/pinctrl on the special devel-mt2701 branch, so

Re: [PATCH v2 2/2] lightnvm: add non-continuous lun target creation support

OK, I see. Will include these changes in next version. 2016-01-28 17:09 GMT+08:00 Matias Bjørling : > On 01/28/2016 09:50 AM, Wenwei Tao wrote: >> 2016-01-27 17:44 GMT+08:00 Matias Bjørling : >>> On 01/26/2016 01:33 PM, Wenwei Tao wrote: When create a

Re: [PATCH] net/mac80211/agg-rx.c: fix use of uninitialised values

On Thu, 28 Jan 2016, Julian Calaby wrote: > Hi Johannes, > > On Thu, Jan 28, 2016 at 8:48 PM, Johannes Berg > wrote: > > On Thu, 2016-01-28 at 10:27 +1100, Julian Calaby wrote: > >> I'd prefer to just set ->removed to false right after we set > >> ->auto_seq as that

Re: [PATCH V4 3/5] pinctrl: max77620: add pincontrol driver for MAX77620/MAX20024

On Thursday 28 January 2016 03:34 PM, Linus Walleij wrote: On Tue, Jan 19, 2016 at 11:19 AM, Laxman Dewangan wrote: MAXIM Semiconductor's PMIC, MAX77620/MAX20024 has 8 GPIO pins which also act as the special function in alternate mode. Also there is configuration like

Re: [PATCH] pinctrl: pxa: guard sub-directory with CONFIG_PINCTRL_PXA

On Sat, Jan 23, 2016 at 4:31 PM, Masahiro Yamada wrote: > CONFIG_PINCTRL_PXA is more suitable than CONFIG_ARCH_PXA > to guard the drivers/pinctrl/pxa/ directory. > > Signed-off-by: Masahiro Yamada Patch applied. Yours, Linus

Re: [PATCH v6 0/7] cpufreq: add generic cpufreq driver support for Exynos542x/5800 platforms

On 16.12.2015 11:14, Viresh Kumar wrote: > On 15-12-15, 18:33, Bartlomiej Zolnierkiewicz wrote: >> Hi, >> >> This patch series adds generic cpufreq-dt driver support for >> Exynos542x/5800 (using the new CPU clock type which allows it). >> >> It has been tested on Exynos5422 based ODROID-XU3 Lite

[patch added to 3.12-stable] veth: don’t modify ip_summed; doing so treats packets with bad checksums as good.

From: Vijay Pandurangan This patch has been added to the 3.12 stable tree. If you have any objections, please let us know. === [ Upstream commit ce8c839b74e3017996fad4e1b7ba2e2625ede82f ] Packets that arrive from real hardware devices have ip_summed ==

Re: [PATCH v4] lib/spinlock_debug.c: prevent a recursive cycle in the debug code

two small corrections. On (01/28/16 19:41), Sergey Senozhatsky wrote: [..] > > Unfortunately, it's not reproduced anymore. > > > > If it's clearly a spinlock caller's bug as you said, modifying the > > spinlock debug code does not help it at all. But I found there's a > > possiblity in the debug

Re: [PATCH] mm: polish virtual memory accounting

On Thu, Jan 28, 2016 at 12:45:44PM +0300, Konstantin Khlebnikov wrote: > * add VM_STACK as alias for VM_GROWSUP/DOWN depending on architecture > * always account VMAs with flag VM_STACK as stack (as it was before) > * cleanup classifying helpers > * update comments and documentation > >

Re: [PATCH] arm64: Allow vmalloc regions to be set with set_memory_*

On Thu, Jan 28, 2016 at 09:47:20AM +0800, Xishi Qiu wrote: > On 2016/1/18 19:56, Mark Rutland wrote: > > On Wed, Jan 13, 2016 at 05:10:31PM +0100, Ard Biesheuvel wrote: > >> Something along these lines, perhaps? > >> > >> diff --git a/arch/arm64/mm/pageattr.c b/arch/arm64/mm/pageattr.c > >> index

Re: [RFC PATCH v2 1/3] getcpu_cache system call: cache CPU number of running thread

On Wed, Jan 27, 2016 at 10:47:37PM +, Mathieu Desnoyers wrote: > - On Jan 27, 2016, at 5:11 PM, Josh Triplett j...@joshtriplett.org wrote: > > > On Wed, Jan 27, 2016 at 09:34:35PM +, Mathieu Desnoyers wrote: > >> - On Jan 27, 2016, at 12:37 PM, Thomas Gleixner t...@linutronix.de

Re: [PATCH v3 3/4] x86/efi: print size in binary units in efi_print_memmap

On Thu, 2016-01-28 at 09:29 +, Matt Fleming wrote: > On Tue, 26 Jan, at 01:59:26PM, Andy Shevchenko wrote: > > On Tue, 2016-01-26 at 11:50 +, Matt Fleming wrote: > > > On Mon, 25 Jan, at 08:37:58PM, Elliott, Robert (Persistent > > > Memory) > > > wrote: > > > > > > > > For the UEFI memory

Re: [PATCH 3/2] oom: clear TIF_MEMDIE after oom_reaper managed to unmap the address space

Michal Hocko wrote: > On Mon 18-01-16 13:35:44, Tetsuo Handa wrote: > [...] > > (1) Make the OOM reaper available on CONFIG_MMU=n kernels. > > > > I don't know about MMU, but I assume we can handle these errors. > > What is the usecase for this on !MMU configurations? Why does it make >

[PATCH 0/6] Support for systems without AArch32 state

This series add checks to make sure that the AArch32 state is supported before we process the 32bit ID registers. Also checks the same for COMPAT binary execution. This series applies on top of 4.5-rc1 + Early CPU feature verification [1] + Handle sign bit for CPU Features [2], even though review

[PATCH 4/6] arm64: cpufeature: Check availability of AArch32

On ARMv8 support for AArch32 state is optional. Hence it is not safe to check the AArch32 ID registers for sanity, which could lead to false warnings. This patch makes sure that the AArch32 state is implemented before we keep track of the 32bit ID registers. As per ARM ARM (D.1.21.2 - Support for

Re: [PATCH] clk: Move vendor's Kconfig into CCF menu section

On Thursday 28 January 2016 00:36:56 Stephen Boyd wrote: > On 01/27, Arnd Bergmann wrote: > > On Wednesday 27 January 2016 17:56:18 James Liao wrote: > > > > > > > > I think you should include this change in your patch, or as a > > > > preparation. > > > > All other samsung platforms already

[PATCH 6/6] arm64: compat: Check for AArch32 state

Make sure we have AArch32 state available for running COMPAT binaries. Signed-off-by: Yury Norov [ Added checks for ELF HWCAP, Use cap bit in cap_hwcaps ] Signed-off-by: Suzuki K Poulose --- arch/arm64/include/asm/elf.h |3 ++-

[PATCH 2/6] arm64: HWCAP: Split COMPAT HWCAP table entries

In order to handle systems which do not support 32bit at EL0, split the COMPAT HWCAP entries into a separate table which can be processed, only if the support is available. Signed-off-by: Suzuki K Poulose --- arch/arm64/kernel/cpufeature.c | 78

[PATCH 3/6] arm64: Add helpers for detecting AArch32 support at EL0

Adds a helper to extract the support for AArch32 at EL0 Signed-off-by: Suzuki K Poulose --- arch/arm64/include/asm/cpufeature.h |7 +++ arch/arm64/include/asm/sysreg.h |1 + 2 files changed, 8 insertions(+) diff --git

Re: [PATCH] arm64: Disallow combination of ARCH_XGENE and 16K page size

On 28/01/16 11:30, Ard Biesheuvel wrote: On 28 January 2016 at 12:27, Suzuki K. Poulose wrote: On 28/01/16 11:08, Will Deacon wrote: I thought there was also a suggestion that we could fail gracefully in the EFI stub if we detected an unsupported page size? Yes,

[PATCH 1/6] arm64: hwcaps: Cleanup naming

We use hwcaps for referring to ELF hwcaps capability information. However this can be confusing with 'cpu_hwcaps' which stands for the CPU capability bit field. This patch cleans up the names to make it a bit more readable. Signed-off-by: Suzuki K Poulose ---

Re: [PATCH v7 6/6] cpufreq: powernv: Add sysfs attributes to show throttle stats

On 28-01-16, 12:55, Shilpasri G Bhat wrote: > Create sysfs attributes to export throttle information in > /sys/devices/system/cpu/cpufreq/chipN. The newly added sysfs files are as > follows: > > 1)/sys/devices/system/cpu/cpufreq/chip0/throttle_frequencies > This gives the throttle stats for

Re: [PATCH v8 0/5] mfd: tps65912: Driver rewrite with DT support

On Thu, Jan 28, 2016 at 06:41:49AM +, Lee Jones wrote: > Just need your stamp for this to go in. Please be more specific? What is it that you are looking for beyond the review I already did for the regulator driver? signature.asc Description: PGP signature

Re: mm: another VM_BUG_ON_PAGE(PageTail(page))

On Thu, Jan 28, 2016 at 11:55:14AM +0100, Dmitry Vyukov wrote: > On Thu, Jan 28, 2016 at 11:51 AM, Kirill A. Shutemov > wrote: > > On Thu, Jan 28, 2016 at 11:27:11AM +0100, Dmitry Vyukov wrote: > >> Hello, > >> > >> The following program triggers

Re: [PATCH] arm64: Allow vmalloc regions to be set with set_memory_*

On 2016/1/28 18:51, Mark Rutland wrote: > On Thu, Jan 28, 2016 at 09:47:20AM +0800, Xishi Qiu wrote: >> On 2016/1/18 19:56, Mark Rutland wrote: >>> On Wed, Jan 13, 2016 at 05:10:31PM +0100, Ard Biesheuvel wrote: Something along these lines, perhaps? diff --git

Re: [PATCH] cputime: Fix timeval-->cputime conversion

On Thursday 28 January 2016 09:22:04 Thomas Gleixner wrote: > Cc'ing Arnd > > On Thu, 28 Jan 2016, zengtao wrote: > > > The structure: > > struct timeval { > > __kernel_time_t tv_sec; /* seconds */ > > __kernel_suseconds_ttv_usec;/* microseconds */ > > };

Re: [PATCH] drm/amdgpu: fix non-ANSI declaration of amdgpu_amdkfd_gfx_*_get_functions()

On Fri, Jan 22, 2016 at 7:35 PM, Colin King wrote: > From: Colin Ian King > > amdgpu_amdkfd_gfx_7_get_functions and amdgpu_amdkfd_gfx_8_0_get_functions > have no parameters, so use the normal void parameter convention to make > them match

Re: [RFC PATCH 4/6] iommu/arm-smmu: Add support for IOMMU_DOMAIN_DMA in SMMUv1/SMMUv2 driver

On Thu, Jan 28, 2016 at 05:28:30PM +, Robin Murphy wrote: > On 27/01/16 05:21, Anup Patel wrote: > >To allow use of large memory (> 4Gb) with 32bit devices we need to use > >some kind of iommu for such 32bit devices. > > > >This patch extends SMMUv1/SMMUv2 driver to support DMA domains which >

Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE

Hi Arnd, On Wed, Jan 27, 2016 at 10:44 AM, Arnd Bergmann wrote: > - in some configurations, you end up without any boards selected, hitting > an #error in the final link FWIW, I have a similar problem with m68k+MMU=y randconfig... Gr{oetje,eeting}s,

Re: [PATCH v2 5/5] arm64/perf: Extend event mask for ARMv8.1

Hi Jan, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.5-rc1 next-20160128] [cannot apply to tip/perf/core] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Jan-Glauber

[PATCH v2 0/9] arm64: apq8016: dt patches.

Hi Andy, Here are the reworked regulator patches with some additional dt patches for spi. Changes since v1: - Moved regulators under smd_rpm_regulators label. - Added few spi related fixes thanks, srini Srinivas Kandagatla (9): arm64: dts: qcom: remove redundant spi cs pins

[PATCH v2 2/9] arm64: dts: qcom: add correct drive strenght on cs pins

2mA drive strenght is not enough to drive chipselect low on hardware configurations with level shifters, 16mA should give good range to allow such configurations to work. This issue was noticed while testing spi on db410c with sensor board. Signed-off-by: Srinivas Kandagatla

[PATCH v2 1/9] arm64: dts: qcom: remove redundant spi cs pins from pinconf

This patch removes redundant pins from spi pinconf as these are already specified in pinconf_cs. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/msm8916-pins.dtsi | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH v2 3/9] arm64: dts: apq8016-sbc: Add aliases to spi device.

This patch adds aliases to spi device so that it can get proper bus number rather than a random number. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [PATCH 6/7] usb: musb: use %pad format string from dma_addr_t

* Arnd Bergmann [160128 08:26]: > The musb driver prints DMA addresses in a few places, using the > 0x%x format string. This is wrong on 64-bit architectures (which > need %lx) and 32-bit ARM with CONFIG_LPAE set (which needs > %llx), otherwise we print the wrong data, as gcc

Re: [RFC PATCH 1/3] lib/list_batch: A simple list insertion/deletion batching facility

On Thu, Jan 28, 2016 at 11:45:40AM -0500, Waiman Long wrote: > Using xchg_release() looks OK to me. As this feature is enabled on x86 only > for this patch, we can make the change and whoever enabling it for other > architectures that have a real release function will have to test it. Ah, I was

[PATCH v1 1/1] tools/perf: try to make output directory

Instead of just complaining and fail try to create output directory fisrt like it's done in main Linux kernel Makefile. Signed-off-by: Andy Shevchenko --- tools/build/Makefile | 2 +- tools/perf/Makefile | 3 +++ 2 files changed, 4 insertions(+), 1

Re: [PATCH v5 4/5] x86: use mb() around clflush

On Thu, Jan 28, 2016 at 07:02:51PM +0200, Michael S. Tsirkin wrote: > commit f8e617f4582995f7c25ef25b4167213120ad122b ("sched/idle/x86: > Optimize unnecessary mwait_idle() resched IPIs") adds > memory barriers around clflush, but this seems wrong > for UP since barrier() has no effect on clflush.

Re: [PATCH v3 3/3] pci: dra7xx: use pdata callbacks to perform reset

* Suman Anna [160127 15:17]: > On 01/27/2016 12:56 PM, Tony Lindgren wrote: > > * Suman Anna [160127 10:17]: > >> On 01/27/2016 11:31 AM, Tony Lindgren wrote: > >>> Why do you need another reset here? Can't you just implement PM runtime > >>> in the driver and do

Re: [PATCH v9 3/6] arm64/arm, numa, dt: adding numa dt binding implementation for arm64 platforms.

On Thu, Jan 28, 2016 at 10:42:17PM +0530, Ganapatrao Kulkarni wrote: > On Thu, Jan 28, 2016 at 8:09 PM, Will Deacon wrote: > > On Tue, Jan 26, 2016 at 02:36:04PM -0600, Bjorn Helgaas wrote: > >> Subject is "arm64/arm, numa, dt: adding ..." What is the significance > >> of

[PATCH 0/2] Fix BTT data corruptions after crash

Data corruption issues were observed in tests which initiated a system crash/reset while accessing BTT devices. This problem is reproducible. The BTT driver calls pmem_rw_bytes() to update data in pmem devices. This interface calls __copy_user_nocache(), which uses non-temporal stores so that

[PATCH 1/2] x86/lib/copy_user_64.S: Handle 4-byte uncached copy

Data corruption issues were observed in tests which initiated a system crash while accessing BTT devices. This problem is reproducible. The BTT driver calls pmem_rw_bytes() to update data in pmem devices. This interface calls __copy_user_nocache(), which uses non-temporal stores so that the

[PATCH 2/2] pmem: Flush cache on unaligned request

arch_memcpy_to_pmem() calls __copy_user_nocache() to copy data via non-temporal stores. However, __copy_user_nocache() still performs cached copy when a request is not naturally aligned or is less then 4 bytes. Call clflush_cache_range() to flush destination when a request leads to cached copy.

Re: [PATCH V4 2/2] regulator: mt6323: Add support for MT6323 regulator

On 27/01/2016 15:41, Mark Brown wrote: > On Wed, Jan 27, 2016 at 01:00:59PM +0100, John Crispin wrote: > >> +/* Constrain board-specific capabilities according to what >> + * this driver and the chip itself can actually do. >> + */ >> +c =

Re: [PATCH v5 04/21] usb: dwc2: host: Set host_perio_tx_fifo_size to 304 for rk3066

Kever, On Wed, Jan 27, 2016 at 10:41 PM, Kever Yang wrote: > Hi Doug, > > We are in HOST mode, we only need to receive data from USB camera > with RX FIFO, and no need to use TX FIFO for USB webcam, right? :) > > Any way, I think we need to NAK this patch after look

[PATCH 3.19.y-ckt 137/210] xfs: log mount failures don't wait for buffers to be released

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Dave Chinner commit 85bec5460ad8e05e0a8d70fb0f6750eb719ad092 upstream. Recently I've been seeing xfs/051 fail on

[PATCH 3.19.y-ckt 135/210] ALSA: control: Avoid kernel warnings from tlv ioctl with numid 0

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Takashi Iwai commit c0bcdbdff3ff73a54161fca3cb8b6cdbd0bb8762 upstream. When a TLV ioctl with numid zero is handled, the

Re: [PATCH 0/2] reboot: Introduce emergency_poweroff function

Hi Alan, On Thursday 28 January 2016 06:54 PM, One Thousand Gnomes wrote: On Thu, 28 Jan 2016 18:36:27 +0530 Keerthy wrote: The series introduces a new function emergency_poweroff which shuts down the system after a configurable period of time. emergency_poweroff is

[PATCH 3.19.y-ckt 131/210] crypto: af_alg - Forbid bind(2) when nokey child sockets are present

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Herbert Xu commit a6a48c565f6f112c6983e2a02b1602189ed6e26e upstream. This patch forbids the calling of

[PATCH 3.19.y-ckt 136/210] ARM: debug-ll: fix BCM63xx entry for multiplatform

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Arnd Bergmann commit 6c54809977de3c9e2ef9e9934a2c6625f7e161e7 upstream. During my randconfig build testing, I found

[PATCH 3.19.y-ckt 116/210] ocfs2/dlm: ignore cleaning the migration mle that is inuse

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: xuejiufei commit bef5502de074b6f6fa647b94b73155d675694420 upstream. We have found that migration source will

[PATCH 3.19.y-ckt 118/210] zram/zcomp: use GFP_NOIO to allocate streams

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Sergey Senozhatsky commit 3d5fe03a3ea013060ebba2a811aeb0f23f56aefa upstream. We can end up allocating a

[PATCH 3.19.y-ckt 119/210] zram: try vmalloc() after kmalloc()

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kyeongdon Kim commit d913897abace843bba20249f3190167f7895e9c3 upstream. When we're using LZ4 multi compression

[PATCH 3.19.y-ckt 114/210] dma-debug: switch check from _text to _stext

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Laura Abbott commit ea535e418c01837d07b6c94e817540f50bfdadb0 upstream. In include/asm-generic/sections.h:

[PATCH 3.19.y-ckt 120/210] mm: soft-offline: check return value in second __get_any_page() call

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Naoya Horiguchi commit d96b339f453997f2f08c52da3f41423be48c978f upstream. I saw the following BUG_ON

RE: [PATCH v10 1/1] efi: a misc char interface for user to update efi firmware

> -Original Message- > From: Matt Fleming [mailto:m...@codeblueprint.co.uk] > Sent: Thursday, January 28, 2016 8:16 PM > > On Tue, 26 Jan, at 03:10:03AM, Kweh Hock Leong wrote: > > > > > > This mutex is not needed. It doesn't protect anything in your code. > > > > This is to

[PATCH 3.19.y-ckt 104/210] ALSA: timer: Fix double unlink of active_list

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Takashi Iwai commit ee8413b01045c74340aa13ad5bdf905de32be736 upstream. ALSA timer instance object has a couple of

[PATCH 3.19.y-ckt 102/210] drm/i915: intel_hpd_init(): Fix suspend/resume reprobing

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Lyude commit 2dc2f761dea65069485110d24eaa5b0d5d808b07 upstream. This fixes reprobing of display connectors on

[PATCH 3.19.y-ckt 105/210] dmaengine: dw: fix cyclic transfer setup

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Mans Rullgard commit df3bb8a0e619d501cd13334c3e0586edcdcbc716 upstream. Commit 61e183f83069 ("dmaengine/dw_dmac:

[PATCH 3.19.y-ckt 099/210] powerpc/module: Handle R_PPC64_ENTRY relocations

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Ulrich Weigand commit a61674bdfc7c2bf909c4010699607b62b69b7bec upstream. GCC 6 will include changes to

[PATCH 3.19.y-ckt 100/210] ALSA: hda - fix the headset mic detection problem for a Dell laptop

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Hui Wang commit 0a1f90a982e85f4921bed606a6b41a24f4de2ae1 upstream. The machine uses codec alc255, and the pin

[PATCH 3.19.y-ckt 093/210] ALSA: seq: Fix missing NULL check at remove_events ioctl

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Takashi Iwai commit 030e2c78d3a91dd0d27fef37e91950dde333eba1 upstream. snd_seq_ioctl_remove_events() calls

[PATCH 3.19.y-ckt 089/210] xfs: handle dquot buffer readahead in log recovery correctly

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Dave Chinner commit 7d6a13f023567d573ac362502bb702eda716e654 upstream. When we do dquot readahead in log

[PATCH 3.19.y-ckt 080/210] uml: fix hostfs mknod()

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Vegard Nossum commit 9f2dfda2f2f1c6181c3732c16b85c59ab2d195e0 upstream. An inverted return value check in

[PATCH 3.19.y-ckt 077/210] locks: fix unlock when fcntl_setlk races with a close

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Jeff Layton commit 7f3697e24dc3820b10f445a4a7d914fc356012d1 upstream. Dmitry reported that he was able to

[PATCH 3.19.y-ckt 088/210] xfs: inode recovery readahead can race with inode buffer creation

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Dave Chinner commit b79f4a1c68bb99152d0785ee4ea3ab4396cdacc6 upstream. When we do inode readahead in log

[PATCH 3.19.y-ckt 075/210] PCI: host: Mark PCIe/PCI (MSI) IRQ cascade handlers as IRQF_NO_THREAD

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Grygorii Strashko commit 8ff0ef996ca00028519c70e8d51d32bd37eb51dc upstream. On -RT and if kernel is booting

[PATCH 3.19.y-ckt 073/210] drm/dp/mst: fix in RAD element access

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Mykola Lysenko commit 7a11a334aa6af4c65c6a0d81b60c97fc18673532 upstream. This is needed to receive correct

[PATCH 3.19.y-ckt 068/210] udf: Prevent buffer overrun with multi-byte characters

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Andrew Gabbasov commit ad402b265ecf6fa22d04043b41444cdfcdf4f52d upstream. udf_CS0toUTF8 function stops the

[PATCH 3.19.y-ckt 074/210] PCI: Fix minimum allocation address overwrite

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Christoph Biedl commit 3460baa620685c20f5ee19afb6d99d26150c382c upstream. Commit 36e097a8a297

[PATCH 3.19.y-ckt 072/210] drm/dp/mst: fix in MSTB RAD initialization

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Mykola Lysenko commit 75af4c8c4c0f60d7ad135419805798f144e9baf9 upstream. This fix is needed to support more

[PATCH 3.19.y-ckt 070/210] drm/dp/mst: process broadcast messages correctly

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Mykola Lysenko commit bd9343208704fcc70a5b919f228a7d26ae472727 upstream. In case broadcast message received in

[PATCH 3.19.y-ckt 066/210] libxfs: pack the agfl header structure so XFS_AGFL_SIZE is correct

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: "Darrick J. Wong" commit 96f859d52bcb1c6ea6f3388d39862bf7143e2f30 upstream. Because struct xfs_agfl is 36

[PATCH 3.19.y-ckt 064/210] wlcore/wl12xx: spi: fix NULL pointer dereference (Oops)

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Uri Mashiach commit e47301b06d5a65678690f04c2248fd181db1e59a upstream. Fix the below Oops when trying to

[PATCH 3.19.y-ckt 054/210] NFS: Fix attribute cache revalidation

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Trond Myklebust commit ade14a7df796d4e86bd9d181193c883a57b13db0 upstream. If a NFSv4 client uses the

[PATCH 3.19.y-ckt 058/210] bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing device

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Zheng Liu commit fecaee6f20ee122ad75402c53d8278f9bb142ddc upstream. This bug can be reproduced by the following

[PATCH 3.19.y-ckt 065/210] Input: i8042 - add Fujitsu Lifebook U745 to the nomux list

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: =?UTF-8?q?Aur=C3=A9lien=20Francillon?= commit dd0d0d4de582a6a61c032332c91f4f4cb2bab569 upstream. Without

[PATCH 3.19.y-ckt 056/210] bcache: fix a livelock when we cause a huge number of cache misses

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Zheng Liu commit 2ef9ccbfcb90cf84bdba320a571b18b05c41101b upstream. Subject : [PATCH v2] bcache: fix a

[PATCH 3.19.y-ckt 059/210] bcache: fix a leak in bch_cached_dev_run()

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Al Viro commit 4d4d8573a8451acc9f01cbea24b7e55f04a252fe upstream. Signed-off-by: Al Viro

[PATCH 3.19.y-ckt 030/210] arm64: kernel: enforce pmuserenr_el0 initialization and restore

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Lorenzo Pieralisi commit 60792ad349f3c6dc5735aafefe5dc9121c79e320 upstream. The pmuserenr_el0 register

[PATCH 3.19.y-ckt 019/210] wlcore/wl12xx: spi: fix oops on firmware load

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Uri Mashiach commit 9b2761cb72dc41e1948c8a5512b4efd384eda130 upstream. The maximum chunks used by the

[PATCH 3.19.y-ckt 027/210] dm thin: fix race condition when destroying thin pool workqueue

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Nikolay Borisov commit 18d03e8c25f173f4107a40d0b8c24defb6ed69f3 upstream. When a thin pool is being destroyed delayed

[PATCH 3.19.y-ckt 029/210] arm64: mdscr_el1: avoid exposing DCC to userspace

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Will Deacon commit d8d23fa0f27f3b2942a7bbc7378c7735324ed519 upstream. We don't want to expose the DCC to

[PATCH 3.19.y-ckt 032/210] drm/radeon: clean up fujitsu quirks

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Alex Deucher commit 0eb1c3d4084eeb6fb3a703f88d6ce1521f8fcdd1 upstream. Combine the two quirks. bug:

[PATCH 3.19.y-ckt 031/210] drm/radeon: Fix off-by-one errors in radeon_vm_bo_set_addr

3.19.8-ckt14 -stable review patch. If anyone has any objections, please let me know. ---8< From: Felix Kuehling commit 42ef344c0994cc453477afdc7a8eadc578ed0257 upstream. eoffset is sometimes treated as the

[PATCH v6 19/22] usb: dwc2: host: Add dwc2_hcd_get_future_frame_number() call

As we start getting more exact about our scheduling it's becoming more and more important to know exactly how far through the current frame we are. This lets us make decisions about whether there's still time left to start a new transaction in the current frame. We'll add

[PATCH v6 22/22] usb: dwc2: host: If using uframe scheduler, end splits better

The microframe scheduler figured out exactly how many transfers we need for a split transaction. Let's use this knowledge to know when to end things. Without this I found that certain devices would just keep responding with tons of NYET resonses on their INT_IN endpoint. These would just keep

Re: [PATCH V2 1/4] mfd: f81504-core: Add Fintek F81504/508/512 PCIE-to-UART/GPIO core support

Hi Alan, One Thousand Gnomes 於 2016/1/28 下午 06:04 寫道: + Please bulit-in kernel if you need early console support. This driver needs to be built into the kernel to use early console support. ok + switch (dev->device) { + case FINTEK_F81504: /* 4 ports */ +

[PATCH v6 21/22] usb: dwc2: host: Totally redo the microframe scheduler

This totally reimplements the microframe scheduler in dwc2 to attempt to handle periodic splits properly. The old code didn't even try, so this was a significant effort since periodic splits are one of the most complicated things in USB. I've attempted to keep the old "don't use the microframe"

[PATCH v6 20/22] usb: dwc2: host: Properly set even/odd frame

When setting up ISO and INT transfers dwc2 needs to specify whether the transfer is for an even or an odd frame (or microframe if the controller is running in high speed mode). The controller appears to use this as a simple way to figure out if a transfer should happen right away (in the current

[PATCH v6 01/22] usb: dwc2: rockchip: Make the max_transfer_size automatic

Previously we needed to set the max_transfer_size to explicitly be 65535 because the old driver would detect that our hardware could support much bigger transfers and then would try to do them. This wouldn't work since the DMA alignment code couldn't support it. Later in commit e8f8c14d9da7

[PATCH v6 09/22] usb: dwc2: host: Giveback URB in tasklet context

In commit 94dfd7edfd5c ("USB: HCD: support giveback of URB in tasklet context") support was added to give back the URB in tasklet context. Let's take advantage of this in dwc2. This speeds up the dwc2 interrupt handler considerably. Note that this requires the change ("usb: dwc2: host: Add a

[PATCH v6 07/22] usb: dwc2: host: Add scheduler tracing

In preparation for future changes to the scheduler let's add some tracing that makes it easy for us to see what's happening. By default this tracing will be off. By changing "core.h" you can easily trace to ftrace, the console, or nowhere. Signed-off-by: Douglas Anderson

[PATCH v6 0/22] usb: dwc2: host: Fix and speed up all the stuff, especially with splits

This is a bit of catchall series for all the bug fix and performance patches I've been working on over the last few months. Note that for dwc2 we need to do LOTS in software and need super low interrupt latency, so most performance improvements actually fix real bugs. Patches are structured to

[PATCH v6 06/22] usb: dwc2: host: fix split transfer schedule sequence

We're supposed to keep outstanding splits in order. Keep track of a list of the order of splits and process channel interrupts in that order. Without this change and the following setup: * Rockchip rk3288 Chromebook, using port ff54 -> Pluggable 7-port Hub with Charging (powered) ->

[PATCH v6 04/22] usb: dwc2: host: Avoid use of chan->qh after qh freed

When poking around with USB devices with slub_debug enabled, I found another obvious use after free. Turns out that in dwc2_hc_n_intr() I was in a state when the contents of chan->qh was filled with 0x6b, indicating that chan->qh was freed but chan still had a reference to it. Let's make sure

[PATCH v6 03/22] usb: dwc2: host: Set host_rx_fifo_size to 525 for rk3066

As documented in dwc2_calculate_dynamic_fifo(), host_rx_fifo_size should really be: 2 * ((Largest Packet size / 4) + 1 + 1) + n with n = number of host channel. We have 9 host channels, so 2 * ((1024/4) + 2) + 9 = 516 + 9 = 525 We've got 960 / 972 total_fifo_size on rk3288 (and presumably on

[PATCH v6 02/22] usb: dwc2: host: Get aligned DMA in a more supported way

All other host controllers who want aligned buffers for DMA do it a certain way. Let's do that too instead of working behind the USB core's back. This makes our interrupt handler not take forever and also rips out a lot of code, simplifying things a bunch. This also has the side effect of

[PATCH v5 07/10] virtio_mmio: Use the DMA API if enabled

This switches to vring_create_virtqueue, simplifying the driver and adding DMA API support. Signed-off-by: Andy Lutomirski --- drivers/virtio/virtio_mmio.c | 67 ++-- 1 file changed, 15 insertions(+), 52 deletions(-) diff --git

[PATCH v5 09/10] vring: Use the DMA API on Xen

Signed-off-by: Andy Lutomirski --- drivers/virtio/virtio_ring.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index c169c6444637..305c05cc249a 100644 --- a/drivers/virtio/virtio_ring.c +++

<    4   5   6   7   8   9   10   11   12   13   >