[RESEND PATCH] ARM: multi_v7_defconfig: enable CONFIG_UNIPHIER_MDMAC

. So, I am resending it on top of that. The insert context was decided by savedefconfig based on next-20181221. arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 63af623

Re: [PATCH v2 2/2] input: add official Raspberry Pi's touchscreen driver

On Thu, Dec 20, 2018 at 08:12:23PM +0100, Nicolas Saenz Julienne wrote: > On Thu, 2018-12-20 at 10:39 -0800, Eric Anholt wrote: > > Nicolas Saenz Julienne writes: > > > > > Add's support to Raspberry Pi's 7" Touch device. Instead of using a > > > conventional bus all information is copied into a

[PATCH][next] perf trace: use correct SECCOMP prefix spelling, "SECOMP_*" -> "SECCOMP_*"

From: Colin Ian King The spelling of the SECCOMP is incorrect, fix these. Fixes: c65c83ffe904 ("perf trace: Allow asking for not suppressing common string prefixes") Signed-off-by: Colin Ian King --- tools/perf/trace/beauty/seccomp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

Re: [PATCH v2 -next] input: keyboard: remove duplicated include from mtk-pmic-keys.c

On Tue, Dec 11, 2018 at 05:32:00PM +0800, YueHaibing wrote: > alphabetise the header files and remove duplicated include > file linux/kernel.h > > Signed-off-by: YueHaibing Applied, thank you. > --- > v2: alphabetise the header files > --- > drivers/input/keyboard/mtk-pmic-keys.c | 13

Re: [PATCH] Input: elantech - Disable elan-i2c for P52 and P72

On Tue, Dec 18, 2018 at 06:13:43PM +1000, Peter Hutterer wrote: > On Wed, Dec 12, 2018 at 04:42:05PM +0100, Benjamin Tissoires wrote: > > The current implementation of elan_i2c is known to not support those > > 2 laptops. > > > > A proper fix is to tweak both elantech and elan_i2c to transmit the

Re: [linux-sunxi] Re: [PATCH v2 1/8] mfd: axp20x: name voltage ramping define properly

On Fri, Dec 21, 2018 at 08:39:27AM +, Lee Jones wrote: > On Tue, 11 Dec 2018, Priit Laes wrote: > > > From: Olliver Schinagl > > > > The current axp20x names the ramping register 'scal' which probably > > means scaling. Since the register really has nothing to do with > > scaling, but

Re: [PATCH v5] Input: i8042 add i8042_is_mr_coffee() helper to avoid refconut leak

On Sat, Dec 15, 2018 at 04:08:46AM -0500, Yangtao Li wrote: > of_find_node_by_path() acquires a reference to the node returned by > it and that reference needs to be dropped by its caller. Add > i8042_is_mr_coffee() helper to avoid refconut leak. > > Signed-off-by: Yangtao Li > --- > changes in

Re: [PATCH v2 5/8] dt-bindings: mfd: axp20x: Add software based soft_start for AXP209 LDO3

On Tue, 11 Dec 2018, Priit Laes wrote: > From: Olliver Schinagl > > In the past, there have been words on various lists that if LDO3 is > disabled in u-boot, but enabled in the DTS, the axp209 driver would > fail to continue/hang. Several enable/disable patches have been > issues to

Re: [PATCH v2 1/8] mfd: axp20x: name voltage ramping define properly

On Tue, 11 Dec 2018, Priit Laes wrote: > From: Olliver Schinagl > > The current axp20x names the ramping register 'scal' which probably > means scaling. Since the register really has nothing to do with > scaling, but really is the voltage ramp we rename it appropriately. > > Signed-off-by:

general protection fault in ip6_route_output_flags

Hello, syzbot found the following crash on: HEAD commit:a9cd3439e3c6 neighbor: Use nda_policy for validating attri.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=143d3a0d40 kernel config: https://syzkaller.appspot.com/x/.config?x=1f6442435a55ea09

BUG: unable to handle kernel paging request in iptunnel_xmit

Hello, syzbot found the following crash on: HEAD commit:d84e7bc0595a rds: Fix warning. git tree: net console output: https://syzkaller.appspot.com/x/log.txt?x=1461543540 kernel config: https://syzkaller.appspot.com/x/.config?x=c8970c89a0efbb23 dashboard link:

[PATCH 2/5] kconfig: split the lexer out of zconf.y

Compile zconf.lex.c independently of the other files. Signed-off-by: Masahiro Yamada --- scripts/kconfig/Makefile | 8 ++-- scripts/kconfig/lkc.h| 3 +++ scripts/kconfig/zconf.l | 1 + scripts/kconfig/zconf.y | 2 -- 4 files changed, 6 insertions(+), 8 deletions(-) diff --git

[PATCH 5/5] kconfig: surround dbg_sym_flags with #ifdef DEBUG to fix gconf warning

Fix the following warning: no previous prototype for ‘dbg_sym_flags’ [-Wmissing-prototypes] Signed-off-by: Masahiro Yamada --- scripts/kconfig/gconf.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/kconfig/gconf.c b/scripts/kconfig/gconf.c index

[PATCH 4/5] kconfig: split images.c out of qconf.cc/gconf.c to fix gconf warnings

Currently, images.c is included by qconf.cc and gconf.c. qconf.cc uses all of xpm_* arrays, but gconf.c only some of them. Hence, lots of "... defined but not used" warnings are displayed when compiling gconf.c Splitting out images.c fixes the warnings. Signed-off-by: Masahiro Yamada ---

[PATCH 1/5] kconfig: split some C files out of zconf.y

I want to compile each C file independently instead of including all of them from zconf.y. These 4 files are low hanging fruits. Signed-off-by: Masahiro Yamada --- scripts/kconfig/Makefile | 19 +-- scripts/kconfig/confdata.c | 1 + scripts/kconfig/expr.c | 2 ++

[PATCH 3/5] kconfig: add static qualifiers to fix gconf warnings

Add "static" to functions that are locally used in gconf.c This fixes some "no previous prototype for ..." warnings. Signed-off-by: Masahiro Yamada --- scripts/kconfig/gconf.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/scripts/kconfig/gconf.c

[PATCH] PCI: pcie-rockchip: use probe_err helpers instead of open coding

probe_err helpers makes probe error handling easier and less error prone. Signed-off-by: Andrzej Hajda --- Hi all, This is sample conversion of one of drivers to proposed probe_err* helpers. It was created to convince Greg that these helpers are useful. With this helper we gain: - corect error

linux-next: Tree for Dec 21

Hi all, News: there will be no linux-next release until Jan 2. Have a good break. Changes since 20181220: New tree: gpio-brgl The pm tree gained a conflict against the kbuild tree. The bpf-next tree gained a conflict against Linus' tree. The kvm tree gained a conflict against the powerpc

Re: [PATCH v4 3/3] PM/runtime:Replace jiffies based accounting with ktime based accounting

On Thu, 20 Dec 2018 at 23:03, Ulf Hansson wrote: > > On Thu, 20 Dec 2018 at 15:17, Vincent Guittot > wrote: > > > > From: Thara Gopinath > > > > This patch replaces jiffies based accounting for runtime_active_time > > and runtime_suspended_time with ktime base accounting. This makes the > >

Re: [PATCH v4 2/3] drm/i915: Move on the new pm runtime interface

On Thu, 20 Dec 2018 at 23:04, Ulf Hansson wrote: > > On Thu, 20 Dec 2018 at 15:17, Vincent Guittot > wrote: > > > > Use the new pm runtime interface to get the accounted suspended time: > > pm_runtime_accounted_time_get() > > pm_runtime_suspended_time() > > This change also makes quite some nice

Re: [PATCH] touchscreen: elants: fix a missing check of return values

Hi Kangjie, On Fri, Dec 21, 2018 at 12:59:16AM -0600, Kangjie Lu wrote: > elants_i2c_send() may fail, let's check its return values. The fix does > the check and reports an error message upon the failure. > > Signed-off-by: Kangjie Lu > --- > drivers/input/touchscreen/elants_i2c.c | 10

Re: [PATCH v2] media: si2165: fix a missing check of return value

Am 21.12.18 um 05:54 schrieb Kangjie Lu: > si2165_readreg8() may fail. Looking into si2165_readreg8(), we will find > that "val_tmp" will be an uninitialized value when regmap_read() fails. > "val_tmp" is then assigned to "val". So if si2165_readreg8() fails, > "val" will be a random value.

Re: [PATCH v5 2/2] media: usb: pwc: Don't use coherent DMA buffers for ISO transfer

On Thu, Dec 20, 2018 at 12:23:46PM +0900, Tomasz Figa wrote: > I haven't been following the problems with virtually tagged cases, > would you mind sharing some background, so that we can consider it > when adding non-consistent allocations to VB2? The problem exists at least partially with the

Re: [PATCH v6 2/2] phy: qualcomm: Add Synopsys High-Speed USB PHY driver

Hi, On 12/20/2018 4:39 PM, Shawn Guo wrote: > Hi Manu, > > On Thu, Dec 20, 2018 at 09:33:43AM +0530, mgau...@codeaurora.org wrote: >> Hi Shawn, >> >> On 2018-12-20 06:31, Shawn Guo wrote: >>> It adds Synopsys 28nm Femto High-Speed USB PHY driver support, which >>> is usually paired with Synopsys

[PATCH v3] crypto: talitos - fix ablkcipher for CONFIG_VMAP_STACK

[2.364486] WARNING: CPU: 0 PID: 60 at ./arch/powerpc/include/asm/io.h:837 dma_nommu_map_page+0x44/0xd4 [2.373579] CPU: 0 PID: 60 Comm: cryptomgr_test Tainted: GW 4.20.0-rc5-00560-g6bfb52e23a00-dirty #531 [2.384740] NIP: c000c540 LR: c000c584 CTR: [

Re: [PATCH v4 13/18] memory: mtk-smi: Add bus_sel for mt8183

On Fri, 2018-12-21 at 12:47 +0800, Nicolas Boichat wrote: > On Sat, Dec 8, 2018 at 4:43 PM Yong Wu wrote: > > > > There are 2 mmu cells in a M4U HW. we could adjust some larbs entering > > mmu0 or mmu1 to balance the bandwidth via the smi-common register > > SMI_BUS_SEL(0x220)(Each larb occupy 2

Re: [PATCH v4 08/18] iommu/mediatek: Add larb-id remapped support

Hi Nicolas, Thanks for the review of this patchset. On Fri, 2018-12-21 at 11:35 +0800, Nicolas Boichat wrote: > On Sat, Dec 8, 2018 at 4:42 PM Yong Wu wrote: > > > > The larb-id may be remapped in the smi-common, this means the > > larb-id reported in the mtk_iommu_isr isn't the real larb-id, >

Re: [PATCH v4 10/18] iommu/mediatek: Add mt8183 IOMMU support

On Fri, 2018-12-21 at 12:43 +0800, Nicolas Boichat wrote: > On Sat, Dec 8, 2018 at 4:42 PM Yong Wu wrote: > > > > The M4U IP blocks in mt8183 is MediaTek's generation2 M4U which use > > the ARM Short-descriptor like mt8173, and most of the HW registers > > are the same. > > > > Here list main

Re: [PATCH 03/10] SCSI: fcoe: convert to use BUS_ATTR_WO

Looks good, Acked-by: Johannes Thumshirn

<    3   4   5   6   7   8