Re: [PATCH V2] namei: free new_dentry late

On Tue 27-11-18 17:57:12, PanBian wrote: > On Tue, Nov 27, 2018 at 10:25:51AM +0100, Jan Kara wrote: > > On Sun 25-11-18 08:15:23, Pan Bian wrote: > > > After calling dput(new_dentry), new_dentry is passed to fsnotify_move. > > > This may result in a use-after-free bug. This patch moves the put > >

Re: [PATCH 3/3] PCI: imx: Add support for i.MX8MQ

Hi Andrey, Am Montag, den 26.11.2018, 10:24 -0800 schrieb Andrey Smirnov: > On Tue, Nov 20, 2018 at 2:49 AM Leonard Crestez > wrote: > > > > On Sat, 2018-11-17 at 10:12 -0800, Andrey Smirnov wrote: > > > @@ -921,7 +1004,28 @@ static int imx6_pcie_probe(struct platform_device > > > *pdev) > > >

[PATCH v5 0/2] Add Synopsys High-Speed USB PHY driver for Qualcomm SoCs

It's based on a downstream driver from Sriharsha Allenki that uses USB phy framework, and gets rewrote to adpot generic phy framework together with quite some cleanups. Changes for v5: - Drop mb() call from function qcom_snps_hsphy_init_sequence() and qcom_snps_hsphy_por_reset(). Changes fo

Re: [PATCH v2 03/12] drm/sun4i: sun6i_mipi_dsi: Setup burst mode timings

On Tue, Nov 20, 2018 at 09:52:23PM +0530, Jagan Teki wrote: > On Tue, Nov 20, 2018 at 9:15 PM Maxime Ripard > wrote: > > > > On Mon, Nov 19, 2018 at 04:30:37PM +0530, Jagan Teki wrote: > > > On Mon, Nov 19, 2018 at 2:00 PM Maxime Ripard > > > wrote: > > > > > > > > On Fri, Nov 16, 2018 at 10:09

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

It adds Synopsys 28nm Femto High-Speed USB PHY driver support, which is usually paired with Synopsys DWC3 USB controllers on Qualcomm SoCs. Signed-off-by: Shawn Guo --- drivers/phy/qualcomm/Kconfig | 10 + drivers/phy/qualcomm/Makefile | 1 + .../phy/qualcomm/

[PATCH v5 1/2] dt-bindings: phy: Add Qualcomm Synopsys High-Speed USB PHY binding

From: Sriharsha Allenki It adds bindings for Synopsys 28nm femto phy controller that supports LS/FS/HS usb connectivity on Qualcomm chipsets. Signed-off-by: Sriharsha Allenki Signed-off-by: Anu Ramanathan Signed-off-by: Bjorn Andersson Reviewed-by: Rob Herring Signed-off-by: Shawn Guo ---

Re: [PATCH RESEND] tty/sysrq: Do not call sync directly from sysrq_do_reset()

On Tue, Nov 27, 2018 at 09:57:23AM +1300, Mark Tomlinson wrote: > sysrq_do_reset() is called in softirq context, so it cannot call > sync() directly. Instead, call orderly_reboot(), which creates a work > item to run /sbin/reboot, or do emergency_sync and restart if the > command fails. > > Signed

Re: [PATCH 3/3] kvm: introduce manual dirty log reprotect

On 27/11/18 06:04, Junaid Shahid wrote: > There is a subtle point here which might be worth mentioning in a comment. > [...] You're absolutely right, it's subtle and should be mentioned. >> @@ -2945,6 +3012,9 @@ static long >> kvm_vm_ioctl_check_extension_generic(struct kvm *kvm, long arg) >>

Re: [PATCH v2 01/11] clk: mediatek: add new clkmux register API

> > From: Owen Chen > > On both MT8183 & MT6765, there add "set/clr" register for > each clkmux setting, and one update register to trigger value change. > It is designed to prevent read-modify-write racing issue. > The sw design need to add a new API to handle this hw change with > a new mtk_clk

Re: [PATCH V4 2/2] base/drivers/arch_topology: Default dmips-mhz if they are not set in DT

On 27-11-18, 09:09, Quentin Perret wrote: > On Tuesday 27 Nov 2018 at 09:27:35 (+0530), Viresh Kumar wrote: > > On 26-11-18, 13:20, Daniel Lezcano wrote: > > > diff --git a/Documentation/devicetree/bindings/arm/cpu-capacity.txt > > > b/Documentation/devicetree/bindings/arm/cpu-capacity.txt > > > i

Re: [PATCH 0/7] ACPI HMAT memory sysfs representation

On 11/26/2018 11:38 PM, Dan Williams wrote: > On Mon, Nov 26, 2018 at 8:42 AM Dave Hansen wrote: >> >> On 11/23/18 1:13 PM, Dan Williams wrote: A new system call makes total sense to me. I have the same concern about the completeness of what's exposed in sysfs, I just don't see a >>>

Re: [PATCH 3/3] PCI: imx: Add support for i.MX8MQ

On 11/26/18 8:24 PM, Andrey Smirnov wrote: > On Tue, Nov 20, 2018 at 2:49 AM Leonard Crestez > wrote: >> On Sat, 2018-11-17 at 10:12 -0800, Andrey Smirnov wrote: >>> + if (of_property_read_u32_array( >>> + node, "fsl,gpr12-device-type", >>> +

Re: [PATCH 3/4] Drivers: hv: vmbus: Add hooks for per-CPU IRQ

On Tue, Nov 27, 2018 at 07:20:56AM +0100, Greg KH wrote: > On Mon, Nov 26, 2018 at 08:56:50PM +, Michael Kelley wrote: > > From: Greg KH Monday, November 26, 2018 11:57 > > AM > > > > > > > You created "null" hooks that do nothing, for no one in this patch > > > > > series, why? > > > > > >

Re: [PATCH net-next 1/2] br_netfilter: add struct netns_brnf

On Tue, Nov 27, 2018 at 09:23:49AM +0100, Pablo Neira Ayuso wrote: > On Tue, Nov 27, 2018 at 03:20:45AM +0100, Christian Brauner wrote: > > On Tue, Nov 27, 2018 at 01:20:47AM +0100, Pablo Neira Ayuso wrote: > > > Hi, > > > > > > On Wed, Nov 07, 2018 at 02:48:58PM +0100, Christian Brauner wrote: >

[PATCH v6 0/9] Port the FSL QSPI driver to the SPI framework

Now that the SPI memory interface was introduced by Boris, it is possible to move drivers from mtd/spi-nor to the SPI framework in order to use them for different type of SPI memory chips. Patch 1 and 2 removes some unused properties from the devicetree and fixes the reg properties to correctly re

[PATCH v6 5/9] dt-bindings: spi: Adjust the bindings for the FSL QSPI driver

Adjust the documentation of the new SPI memory interface based driver to reflect the new drivers settings. The "old" driver was using the "fsl,qspi-has-second-chip" property to select one of two dual chip setups (two chips on one bus or two chips on separate buses). And it used the order in which

[PATCH v6 8/9] ARM64: dts: ls1046a: Remove fsl,qspi-has-second-chip as it is not used

After switching to the new FSL QSPI driver the property 'fsl,qspi-has-second-chip' is not needed anymore. The driver now uses the 'reg' property to determine the bus and the chipselect. Signed-off-by: Frieder Schrempf --- arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 1 - 1 file changed, 1 d

Re: [PATCH v4 08/26] drm/sun4i: sun6i_mipi_dsi: Fix VBP size calculation

On Tue, Nov 20, 2018 at 09:55:42PM +0530, Jagan Teki wrote: > On Tue, Nov 20, 2018 at 9:27 PM Maxime Ripard > wrote: > > > > On Thu, Nov 15, 2018 at 11:19:53PM +0530, Jagan Teki wrote: > > > On Thu, Nov 15, 2018 at 3:26 PM Maxime Ripard > > > wrote: > > > > > > > > Hi, > > > > > > > > On Tue, N

[PATCH v6 6/9] mtd: fsl-quadspi: Remove the driver as it was replaced by spi-fsl-qspi.c

There's a new driver using the SPI memory interface of the SPI framework at spi/spi-fsl-qspi.c, which can be used together with m25p80.c to replace the functionality of this SPI NOR driver. The new driver is already in use and this code is not compiled anymore, so let's remove it. Signed-off-by:

[PATCH v6 1/9] ARM: dts: Reflect change of FSL QSPI driver and remove unused properties

The FSL QSPI driver will be moved to the SPI framework and it then acts as a SPI controller. Therefore the subnodes need to set spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before. Also the properties 'bus-num', 'fsl,spi-num-chipselects' and 'fsl,spi-flash-chipselects' were never read

Re: [RFC][PATCH 2/2] sched: Enqueue tasks on a cpu with only SCHED_IDLE tasks

Hi Quentin, On 26-11-18, 12:37, Quentin Perret wrote: > On Monday 26 Nov 2018 at 16:50:24 (+0530), Viresh Kumar wrote: > > The scheduler tries to schedule a newly wakeup task on an idle CPU to > > make sure the new task gets chance to run as soon as possible, for > > performance reasons. > > > >

[PATCH v6 9/9] MAINTAINERS: Move the Freescale QSPI driver to the SPI framework

The driver was ported to the SPI framework so it can be used as a generic SPI memory driver and not only for SPI NOR. Reflect this transition in the MAINTAINERS file. Signed-off-by: Frieder Schrempf --- MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINE

[PATCH v6 7/9] ARM: dts: ls1021a: Remove fsl,qspi-has-second-chip as it is not used

After switching to the new FSL QSPI driver the property 'fsl,qspi-has-second-chip' is not needed anymore. The driver now uses the 'reg' property to determine the bus and the chipselect. Signed-off-by: Frieder Schrempf --- arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts | 1 - 1 file changed, 1 dele

[PATCH v6 4/9] dt-bindings: spi: Move the bindings for the FSL QSPI driver

Move the documentation of the old SPI NOR driver to the place of the new SPI memory interface based driver. Signed-off-by: Frieder Schrempf Reviewed-by: Rob Herring --- .../bindings/{mtd/fsl-quadspi.txt => spi/spi-fsl-qspi.txt} | 0 1 file changed, 0 insertions(+), 0 deletions(-) dif

[PATCH v6 2/9] arm64: dts: Reflect change of FSL QSPI driver and remove unused properties

The FSL QSPI driver will be moved to the SPI framework and it then acts as a SPI controller. Therefore the subnodes need to set spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before. Also the properties 'num-cs' and 'bus-num' were never read by the driver and can be removed. The proper

[PATCH v6 3/9] spi: Add a driver for the Freescale/NXP QuadSPI controller

This driver is derived from the SPI NOR driver at mtd/spi-nor/fsl-quadspi.c. It uses the new SPI memory interface of the SPI framework to issue flash memory operations to up to four connected flash chips (2 buses with 2 CS each). The controller does not support generic SPI messages. This patch al

Re: linux-next boot error (2)

Dmitry Vyukov wrote: > Please either use the Reported-by tag (for amended linux-next fixes > Tested-by can make more sense and is recognized too), or tell syzbot > separately: It got folded in as that's better than carrying a separate patch. I'll ask Al how he wants to deal with this since he's

Re: [linux-sunxi] Re: [PATCH v4 08/26] drm/sun4i: sun6i_mipi_dsi: Fix VBP size calculation

On Mon, Nov 26, 2018 at 05:37:09PM +0530, Jagan Teki wrote: > I'm about to send next version by combining with burst mode changes in > one series. Do you have any further inputs on this. I didn't not see > any breakage with 4-lane devices, but has issue with 2-lane w/o this change. I'd rather focu

Re: [PATCH] arm: always update thread_info->syscall

On 11/26/18 9:44 PM, Russell King - ARM Linux wrote: On Mon, Nov 26, 2018 at 11:41:11PM +, Russell King - ARM Linux wrote: On Mon, Nov 26, 2018 at 11:33:03PM +, Russell King - ARM Linux wrote: On Mon, Nov 26, 2018 at 08:53:35PM -0200, Rafael David Tinoco wrote: Right now, only way for

[PATCH] fix dma-buf/udmabuf selftest

This patch fixes the udmabuf selftest. Currently the selftest is broken. I fixed the selftest by setting the F_SEAL_SHRINK seal on the memfd file descriptor which is required by udmabuf and added the test to the selftest Makefile. Signed-off-by: Tom Murphy --- tools/testing/selftests/Makefil

Re: [PATCH V2] namei: free new_dentry late

On Tue, Nov 27, 2018 at 11:05 AM Jan Kara wrote: > > On Tue 27-11-18 17:57:12, PanBian wrote: > > I am not quite sure about the actual execution logic. But I guess new_dentry > > reference may be dropped outside vfs_rename in cocurrent executions. > > Otherwise, there is no need to acquire & drop

Re: [PATCH v3 6/6] ARM: PWM: add allwinner sun8i R40/T3/V40 PWM support.

Hello, On Mon, Nov 26, 2018 at 10:31:58PM +0100, Uwe Kleine-König wrote: > On Mon, Nov 26, 2018 at 12:23:19AM +0800, Hao Zhang wrote: > > The sun8i R40/T3/V40 PWM has 8 PWM channals and divides to 4 PWM pairs, > > each PWM pair built-in 1 clock module, 2 timer logic module and 1 > > programmable d

[PATCH] lzo: fix ip overrun during compress.

It`s possible ip overrun in lzo1x_1_do_compress() when compressed page is point to the end of memory and which virtual address is 0xf000. Leading to a NULL pointer access during the get_unaligned_le32(ip). Fix this panic: [ 2738.034508] Unable to handle kernel NULL pointer dereference

Re: linux-next boot error (2)

On Tue, Nov 27, 2018 at 11:25 AM, David Howells wrote: > Dmitry Vyukov wrote: > >> Please either use the Reported-by tag (for amended linux-next fixes >> Tested-by can make more sense and is recognized too), or tell syzbot >> separately: > > It got folded in as that's better than carrying a separ

Re: [PATCH v2 02/11] clk: mediatek: add new member to mtk_pll_data

> > From: Owen Chen > > 1. pcwibits: The integer bits of pcw for plls is extend to 8 bits, >add a variable to indicate this change and >backward-compatible. > 2. fmin: The pll freqency lower-bound is vary from 1GMhz to >1.5Ghz, add a variable to indicate platform-dependent. The patch

Re: [PATCH v2 08/11] clk: mediatek: Add MT8183 clock support

/linux/commits/Weiyi-Lu/Mediatek-MT8183-clock-and-scpsys-support/20181127-114621 base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next coccinelle warnings: (new ones prefixed by >>) >> drivers/clk/mediatek/clk-mt8183.c:1295:3-8: No need to set .owner here.

[PATCH] clk: mediatek: fix platform_no_drv_owner.cocci warnings

: Add MT8183 clock support") CC: Weiyi Lu Signed-off-by: kbuild test robot --- url: https://github.com/0day-ci/linux/commits/Weiyi-Lu/Mediatek-MT8183-clock-and-scpsys-support/20181127-114621 base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next clk-mt8183.c |1

Re: [PATCH] media: dvb: fix a missing-check bug

Hi Wenwen, On Mon, Oct 29, 2018 at 01:46:04PM -0500, Wenwen Wang wrote: > Hello, > > Can anyone confirm this bug? Thanks! > > Wenwen > > On Fri, Oct 19, 2018 at 9:12 AM Wenwen Wang wrote: > > > > In dvb_audio_write(), the first byte of the user-space buffer 'buf' is > > firstly copied and chec

Re: [PATCH 3/3] PCI: imx: Add support for i.MX8MQ

On 11/27/18 12:06 PM, Lucas Stach wrote: > Hi Andrey, > > Am Montag, den 26.11.2018, 10:24 -0800 schrieb Andrey Smirnov: >> On Tue, Nov 20, 2018 at 2:49 AM Leonard Crestez >> wrote: >>> >>> On Sat, 2018-11-17 at 10:12 -0800, Andrey Smirnov wrote: @@ -921,7 +1004,28 @@ static int imx6_pcie_p

Re: DMA: atmel_serial: Opening and closing the serial device repeatedly causes kmalloc-32 slab leak

Le 27/11/2018 à 10:58, Alexandre Belloni a écrit : > Hello Richard, > > On 27/11/2018 10:51:13+0100, richard.gen...@gmail.com wrote: >> Hi all, >> >> I reproduced the memory leak on my board (at91sam9g35-cm) with a 4.20-rc3. >> >> It triggered an OOM after a couple of hours running a code like thi

Re: [PATCH 3/3] soc: qcom: Add AOSS QMP genpd provider

Hi Bjorn, On 11/12/2018 1:35 PM, Bjorn Andersson wrote: The AOSS QMP genpd provider implements control over power-related resources related to low-power state associated with the remoteprocs in the system as well as control over a set of clocks related to debug hardware in the SoC. Signed-off-b

Re: [PATCH 3/3] gpio: Add reference counting for non-exclusive GPIOs

On Mon, Nov 26, 2018 at 10:53 PM Linus Walleij wrote: > I suspect maybe the lesser evil is to bite the bullet, invent > gpiod_get_from_of_node() which is the missing API (we currently > only have devm_gpiod_get_from_of_node()) and simply > fix up the converted regulator drivers to avoid devm_* >

Re: [PATCH 4.19 000/118] 4.19.5-stable review

On 26 November 2018 4:19:54 PM IST, Greg Kroah-Hartman wrote: >This is the start of the stable review cycle for the 4.19.5 release. >There are 118 patches in this series, all will be posted as a response >to this one. If anyone has any issues with these being applied, please >let me know. > >Res

Re: [PATCHi v2] mm: put_and_wait_on_page_locked() while page is migrated

On Mon, Nov 26, 2018 at 12:53:51PM -0800, Matthew Wilcox wrote: > On Mon, Nov 26, 2018 at 11:27:07AM -0800, Hugh Dickins wrote: > > Waiting on a page migration entry has used wait_on_page_locked() all > > along since 2006: but you cannot safely wait_on_page_locked() without > > holding a reference

Re: [PATCH 1/2] dt-bindings: trivial: add ti,lm3630a binding

On Sat, Nov 24, 2018 at 09:17:02AM -0500, Brian Masney wrote: > Add a trivial binding for the Texas Instruments LM3630A Backlight Chip. It's quite unusual for a backlight device to have a trivial binding. The driver supports fairly extensive parametrization via struct lm3530a_platform_data. It is

Re: [PATCH] arm: always update thread_info->syscall

On Tue, Nov 27, 2018 at 08:30:32AM -0200, Rafael David Tinoco wrote: > On 11/26/18 9:44 PM, Russell King - ARM Linux wrote: > >On Mon, Nov 26, 2018 at 11:41:11PM +, Russell King - ARM Linux wrote: > >>On Mon, Nov 26, 2018 at 11:33:03PM +, Russell King - ARM Linux wrote: > >>>On Mon, Nov 26,

Re: [PATCHi v2] mm: put_and_wait_on_page_locked() while page is migrated

On Mon, Nov 26, 2018 at 11:27:07AM -0800, Hugh Dickins wrote: > Waiting on a page migration entry has used wait_on_page_locked() all > along since 2006: but you cannot safely wait_on_page_locked() without > holding a reference to the page, and that extra reference is enough to > make migrate_page_m

Re: [RFC][PATCH 2/2] sched: Enqueue tasks on a cpu with only SCHED_IDLE tasks

Hi Viresh, On Tuesday 27 Nov 2018 at 15:54:42 (+0530), Viresh Kumar wrote: > Hi Quentin, > > On 26-11-18, 12:37, Quentin Perret wrote: > > On Monday 26 Nov 2018 at 16:50:24 (+0530), Viresh Kumar wrote: > > > The scheduler tries to schedule a newly wakeup task on an idle CPU to > > > make sure the

Re: [Question] atomic_fetch_andnot() in nohz_idle_balance()

On Tue, Nov 27, 2018 at 10:01:24AM +0100, Vincent Guittot wrote: > On Mon, 26 Nov 2018 at 21:44, Andrea Parri > wrote: > > > > On Mon, Nov 26, 2018 at 12:37:00PM +0100, Vincent Guittot wrote: > > > On Mon, 26 Nov 2018 at 10:30, Peter Zijlstra wrote: > > > > > > > > On Wed, Nov 21, 2018 at 11:34:5

Re: [PATCH v6 1/9] ARM: dts: Reflect change of FSL QSPI driver and remove unused properties

Hello, On Tue, Nov 27, 2018 at 10:24:19AM +, Schrempf Frieder wrote: > The FSL QSPI driver will be moved to the SPI framework and it then > acts as a SPI controller. Therefore the subnodes need to set > spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before. > > Also the properties

[PATCH] sched/fair: Clean up comment in nohz_idle_balance()

Concerning the comment associated to the atomic_fetch_andnot() in nohz_idle_balance(), Vincent explains [1]: "[...] the comment is useless and can be removed [...] it was referring to a line code above the comment that was present in a previous iteration of the patchset. This line disappe

Re: [PATCH v7 2/3] x86: add support for Huawei WMI hotkeys.

Some more forgotten bits... On Tue, 27 Nov 2018 03:57:48 +0100, Ayman Bagabas wrote: > --- a/drivers/platform/x86/Kconfig > +++ b/drivers/platform/x86/Kconfig > +config HUAWEI_WMI > + tristate "Huawei WMI hotkeys driver" > + depends on ACPI_WMI > + depends on INPUT > + select

Re: [PATCH] staging: iio: ad7780: Add gain & filter gpio support

On Lu, 2018-11-26 at 17:24 -0200, Giuliano Belinassi wrote: Hi, please see bellow > Hi, thank you for the review > > > > > On Thu, 22 Nov 2018 11:01:00 + > > "Popa, Stefan Serban" wrote: > > > > > > I think that instead of setting the gain directly, we should use > > > the IIO_CHAN_INFO_SC

[PATCH] reorder slow clock source read for clock source watchdog

the clock source watchdog (HPET) in skx is much slower than the clock source TSC. The long latency in the first call may trigger a false postive TSC unstable noise. Let the fast one follows the slow one should fix it. Signed-off-by: Luming Yu Signed-off-by: Yongkai Wu --- kernel/time/clocksourc

[PATCH 1/2] spurious check for user space address

we saw a suspected spurious fault that failed VMA access check but passed spurious check for a user space address access of (rw,execut). The patch is trying to catch the case which might have indicated a stale TLB (software bug found) and a harmful spruious fault. Signed-off-by: Luming Yu Signed-

[PATCH 2/2] spurious check tace point

Add a trace point for debugging spurious fault problem. Signed-off-by: Luming Yu Signed-off-by: Yongkai Wu --- arch/x86/include/asm/trace/exceptions.h | 30 ++ arch/x86/mm/fault.c | 2 ++ 2 files changed, 32 insertions(+) diff --git a/arch/x86/i

Re: [PATCH v3] ALSA: hda/realtek - Add auto-mute quirk for HP Spectre x360 laptop

On Mon, 26 Nov 2018 19:40:46 +0100, Girija Kumar Kasinadhuni wrote: > > This device makes a loud buzzing sound when a headphone is inserted while > playing audio at full volume through the speaker. > > Signed-off-by: Girija Kumar Kasinadhuni > --- > Apologies for the earlier patch not being test

[PATCH] bluetooth: Remove unnecessary smp_mb__after_atomic() barriers

The barriers are redundant because atomic_test_and_clear_bit() already provides the required full ordering for the cases in question (that is, when the bit is cleared). Signed-off-by: Andrea Parri --- drivers/bluetooth/btusb.c | 8 ++-- drivers/bluetooth/hci_intel.c | 16 ---

Re: [PATCH V2 0/5] i2c:ocores: improvements

> This patch set provides improvements to the i2c-ocore driver. > > [V1 -> V2] > - replaced usleep_range() with udelay() so that the polling version can be > used in atomic context. > - added dedicated patch for minor style issues > - fixed delay computation > - use spin_lock_irqsave(), instead

Re: [PATCH v2 0/1] add SPI driver support for mt7629

On Tue, Nov 27, 2018 at 10:29:49AM +0800, Leilk Liu wrote: > From cf719ac350c36cb58e2013b58f73ad04f6981384 Mon Sep 17 00:00:00 2001 > From: Leilk Liu > Date: Tue, 27 Nov 2018 10:18:30 +0800 > Subject: [PATCH v2 0/1] add SPI driver support for mt7629 > > v2: > remove "mediatek,mt7629-spi" compatib

Re: [PATCH 3/3] s390/mm: fix mis-accounting of pgtable_bytes

On 11/26/18 11:34 PM, Heiko Carstens wrote: On Wed, Oct 31, 2018 at 01:36:23PM +0300, Kirill A. Shutemov wrote: On Wed, Oct 31, 2018 at 11:09:44AM +0100, Heiko Carstens wrote: On Wed, Oct 31, 2018 at 07:31:49AM +0100, Martin Schwidefsky wrote: Thanks for testing. Unfortunately Heiko reported a

Re: [PATCH v2 05/13] i2c: acpi: Return error pointers from i2c_acpi_new_device()

On Tue, Nov 27, 2018 at 10:16:25AM +0100, Hans de Goede wrote: > One problem is that i2c_new_device() currently simply returns NULL on all > errors. Andy, you could take a look how much work it is to make that return > an ERR_PTR too, or just check its return value and return ERR_PTR(-ENXIO) if > i

Re: [PATCH] ASoC: max98373: Added max98373_reset for stable amp reset

On Mon, Nov 26, 2018 at 06:46:05PM +, Ryan Lee wrote: > Signed-off-by: Ryan Lee > --- This really needs a changelog to explain what is going on here, and we need some more documentation in the code. It is *extremely* unusual to have to poll for reset like this, and if the failure mode is I/O

Re: linux-next: manual merge of the selinux tree with the vfs tree

Hi Ondrej, On Tue, 27 Nov 2018 09:53:32 +0100 Ondrej Mosnacek wrote: > > Hm... seems that there was some massive overhaul in the VFS code right > at the wrong moment... There are new hooks for mounting now and the The mount changes have been in linux-next since before the last release ... > cod

Re: [PATCH 3/3] s390/mm: fix mis-accounting of pgtable_bytes

On Tue, Nov 27, 2018 at 03:47:13AM -0800, Guenter Roeck wrote: > >E.g. something like the below. If there aren't any objections, I will > >provide a proper patch with changelog, etc. > > > >diff --git a/kernel/fork.c b/kernel/fork.c > >index 07cddff89c7b..d7aeec03c57f 100644 > >--- a/kernel/fork.c

[PATCH v2 1/5] regulator: act8945a-regulator: Implement PM functionalities

From: Boris Brezillon The regulator supports a dedicated suspend mode. Implement the appropriate ->set_suspend_xx() hooks, add support for ->set_mode(), and provide basic PM ops functionalities to setup the regulator in a suspend state when the system is entering suspend. Signed-off-by: Boris Br

[PATCH v2 3/5] regulator: act8945a-regulator: add shutdown function

From: Claudiu Beznea Implement shutdown method to make sure the PMIC will not enter the suspend state when the system is shutdown. This work is based on work done by Borris Brezillon on [1]. [1] https://www.spinics.net/lists/kernel/msg2942960.html Signed-off-by: Claudiu Beznea --- drivers/re

[PATCH v2 4/5] ARM: dts: at91: sama5d2_xplained: Add proper regulator states for suspend-to-mem

From: Boris Brezillon When entering suspend-to-mem, all PMIC outputs are disabled except VDDIODDR which is put in power saving mode, and whose voltage is increased (probably to counter the poor accuracy of power saving mode). Signed-off-by: Boris Brezillon [claudiu.bez...@microchip.com: use reg

[PATCH v2 0/5] add PM functionality for act8945a PMIC

From: Claudiu Beznea This series implements PM functionality for act8945a PMIC and use that support on SAMA5D2 Xplained board. Changes in v2: - split patch 1/1 from previous series in 3 patches: one adding regmap, one adding pm functionality, one adding shutdown functionality - use dev_pm_ops

[PATCH v2 2/5] regulator: act8945a-regulator: fix line over 80 chars warning

From: Claudiu Beznea Fix line over 80 chars checkpatch.pl warning. Signed-off-by: Claudiu Beznea --- drivers/regulator/act8945a-regulator.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/regulator/act8945a-regulator.c b/drivers/regulator/act8945a-regulator.c ind

[PATCH v2 5/5] regulator: add documentation for regulator modes and suspend states

From: Claudiu Beznea Add documentation for regulator modes and suspend states. Signed-off-by: Claudiu Beznea --- .../bindings/regulator/act8945a-regulator.txt | 34 ++ 1 file changed, 34 insertions(+) diff --git a/Documentation/devicetree/bindings/regulator/act8945a-r

Re: [5/6] drivers/i2c: Remove caller signal_pending branch predictions

On Thu, Nov 15, 2018 at 04:27:12PM -0800, Davidlohr Bueso wrote: > This is already done for us internally by the signal machinery. > > Cc: linux-...@vger.kernel.org > Cc: p...@axentia.se > Signed-off-by: Davidlohr Bueso Applied to for-next, thanks! Would have been nice if the cover letter was a

[PATCH 1/3] mfd: cros_ec: Add commands to control codec

Add EC host commands to control codec on EC. Signed-off-by: Cheng-Yi Chiang --- include/linux/mfd/cros_ec_commands.h | 94 1 file changed, 94 insertions(+) diff --git a/include/linux/mfd/cros_ec_commands.h b/include/linux/mfd/cros_ec_commands.h index 07fe4ea0361d3.

Re: [PATCH] module: remove some duplicated includes

+++ Yangtao Li [26/11/18 09:21 -0500]: We include elf.h twice in module.c. It's unnecessary. hence just remove them. Signed-off-by: Yangtao Li --- kernel/module.c | 1 - 1 file changed, 1 deletion(-) diff --git a/kernel/module.c b/kernel/module.c index 49a405891587..438641fc4096 100644 --- a/ke

[PATCH 3/3] ASoC: cros_ec_codec: Add codec driver for Cros EC

Add a codec driver to control ChromeOS EC codec. Use EC Host command to enable/disable I2S recording and control other configurations. Signed-off-by: Cheng-Yi Chiang --- MAINTAINERS | 1 + sound/soc/codecs/Kconfig | 8 + sound/soc/codecs/Makefile| 2 +

[PATCH 2/3] ASoC: Documentation: Add google,cros-ec-codec

Add documentation for Chrome EC codec driver. Signed-off-by: Cheng-Yi Chiang --- .../bindings/sound/google,cros-ec-codec.txt | 24 +++ MAINTAINERS | 5 2 files changed, 29 insertions(+) create mode 100644 Documentation/devicetree/bindin

Re: KASAN: use-after-free Read in kvm_write_guest_offset_cached

On Tue, Nov 27, 2018 at 7:14 AM, Wanpeng Li wrote: > > On Tue, 27 Nov 2018 at 12:51, syzbot > wrote: > > > > Hello, > > Is there beauty C codes? syzbot does not have code like: if (rand() % 2) send_C_repro(); :) > > syzbot found the following crash on: > > > > HEAD commit:442b8cea2477 A

Re: [PATCH v2 1/2] dt-bindings: i2c-stm32: SYSCFG Fast Mode Plus support for I2C STM32F7

On Mon, Nov 19, 2018 at 12:03:31PM +0100, Pierre-Yves MORDRET wrote: > Append optional bindings to update SYSCFG Fast Mode Plus bits if > Fast Mode Plus speed is selected. > > Signed-off-by: Pierre-Yves MORDRET > Reviewed-by: Rob Herring Applied to for-next, thanks! signature.asc Description

Re: [PATCH v2 2/2] i2c: i2c-stm32f7: SYSCFG Fast Mode Plus support for I2C STM32F7

On Mon, Nov 19, 2018 at 12:03:32PM +0100, Pierre-Yves MORDRET wrote: > Read SYSCFG bindings to set Fast Mode Plus bits if Fast Mode Plus > speed is selected. > > Signed-off-by: Pierre-Yves MORDRET Applied to for-next, thanks! signature.asc Description: PGP signature

Re: [PATCH v2] i2c: i2c-stm32f7: add PM Runtime support

On Mon, Nov 19, 2018 at 12:04:24PM +0100, Pierre-Yves MORDRET wrote: > Use PM Runtime API to enable/disable clock > > Signed-off-by: Pierre-Yves MORDRET Looks good but doesn't apply on top of your other patches for me. Can you rebase? signature.asc Description: PGP signature

Health is wealth,Total cure for cancer and infertility

-- To Whom it might Interest: Out of the Mangroove forest and dry vegetation of Africa comes a groundbreaking discovery,a herbal mixture of roots and flower petals [names purposely omitted] comes the cure and prevention to some of man's dreaded diseases including impotency in men and wo

Re: [PATCH v4 4/5] lib/ioremap: Ensure phys_addr actually corresponds to a physical address

On Mon, Nov 26, 2018 at 11:00:10AM -0800, Sean Christopherson wrote: > On Mon, Nov 26, 2018 at 05:07:46PM +, Will Deacon wrote: > > The current ioremap() code uses a phys_addr variable at each level of > > page table, which is confusingly offset by subtracting the base virtual > > address being

Re: [PATCH V5 00/10] x86/KVM/Hyper-v: Add HV ept tlb range flush hypercall support in KVM

On Tue, Nov 27, 2018 at 07:59:22PM +0800, Tianyu Lan wrote: > Gentile Ping... > > On Thu, Nov 8, 2018 at 10:43 PM wrote: > > > > From: Lan Tianyu > > > > Sorry. Some patches was blocked and I try to resend via another account. The patches were still blocked? They didn't show up on driver-devel

Re: [PATCH v2 1/4] mfd: stmpe: Move ADC related defines to header of mfd

On Mon, 19 Nov 2018, Philippe Schenker wrote: > Move defines that are ADC related to the header of the overlying mfd, > so they can be used from multiple sub-devices. > > Signed-off-by: Philippe Schenker > --- > > Changes in v2: > - This is a new added commit. Separate commit for moving the de

[PATCH v3 7/8] platform/chrome: cros_ec_lightbar: instantiate only if the EC has a lightbar.

Due to the way attribute groups visibility work, the function cros_ec_lightbar_attrs_are_visible is called multiple times, once per attribute, and each of these calls makes an EC transaction. For what is worth the EC log reports multiple errors on boot when the lightbar is not available. Instead, c

[PATCH v3 6/8] mfd / platform: cros_ec: instantiate only if th EC has a VBC NVRAM.

The cros-ec-vbc driver is DT-only and there is a DT property that indicates if the EC has the VCB NVRAM, in such case instantiate the driver but don't instantiate on the other cases. To do this move the check code to its parent instead of play with the attribute group visibility. This changes a bi

[PATCH v3 5/8] mfd / platform: cros_ec: move device sysfs attributes to its own driver.

The entire way how cros debugfs attibutes are created is broken. cros_ec_sysfs should be its own driver and its attributes should be associated with the sysfs driver not the mfd driver. The patch also adds the sysfs documentation. Signed-off-by: Enric Balletbo i Serra --- Changes in v3: - Do no

[PATCH v3 4/8] mfd / platform: cros_ec: move debugfs attributes to its own driver.

The entire way how cros debugfs attibutes are created is broken. cros_ec_debugfs should be its own driver and its attributes should be associated with a debugfs driver not the mfd driver. Signed-off-by: Enric Balletbo i Serra --- Changes in v3: None Changes in v2: - Add a "default MFD_CROS_EC_CH

[PATCH v3 0/8] mfd / platform: cros_ec: move cros_ec sysfs attributes to its own drivers.

Hi, This is quick respin of the previous version because I introduced a build problem between patch 3 and 6 due a wrong squash on my side. Sorry about that. I also take this opportunity to do some few cleanups. This is another patchset to try to cleanup a bit more the crossed references for cros-

[PATCH v3 8/8] mfd: cros_ec: add a dev_release empty method.

Devices are required to provide a release method. This patch fixes the following WARN(): [ 47.218707] [ cut here ] [ 47.223901] Device 'cros_ec' does not have a release() function, it is broken and must be fixed. [ 47.234430] WARNING: CPU: 0 PID: 3585 at drivers/base

[PATCH v3 2/8] mfd / platform: cros_ec: move lightbar attributes to its own driver.

The entire way how cros sysfs attibutes are created is broken. cros_ec_lightbar should be its own driver and its attributes should be associated with a lightbar driver not the mfd driver. In order to retain the path, the lightbar attributes are attached to the cros_class. The patch also adds the s

[PATCH v3 3/8] mfd / platform: cros_ec: move vbc attributes to its own driver.

The entire way how cros sysfs attibutes are created is broken. cros_ec_vbc should be its own driver and its attributes should be associated with a vbc driver not the mfd driver. In order to retain the path, the vbc attributes are attached to the cros_class. The patch also adds the sysfs documentat

[PATCH v3 1/8] mfd / platform: cros_ec: use devm_mfd_add_devices.

Use devm_mfd_add_devices() for adding cros-ec core MFD child devices. This reduces the need of remove callback from platform/chrome for removing the MFD child devices. Signed-off-by: Enric Balletbo i Serra --- Changes in v3: - Removed cros_ec_remove from include file. Changes in v2: - Use devm

Re: [PATCH] ARM: dts: imx: Add Y Soft IOTA Draco, Hydra and Ursa boards

On 19.11.2018 15:35, Vokáč Michal wrote: > On 12.11.2018 17:41, Rob Herring wrote: >> On Thu, Nov 01, 2018 at 03:43:26PM +, Vokáč Michal wrote: >>> These are i.MX6S/DL based SBCs embedded in various Y Soft products. >>> All share the same board design but have slightly different HW >>> configur

Re: [PATCH 00/12] ARM: davinci: fix GPIO breakage after v4.19

Hi Bartosz, On 21/11/18 3:05 PM, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > This is the entire set of changes needed to fix the broken GPIO support > for DaVinci boards in legacy mode after certain changes made to the > GPIO driver in 4.19, namely: commits 587f7a694f01 ("gpio: da

Re: [PATCH] i2c-axxia: properly handle master timeout

On Fri, Nov 16, 2018 at 01:24:41PM +, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote: > According to Intel (R) Axxia TM Lionfish Communication Processor > Peripheral Subsystem Hardware Reference Manual, the AXXIA I2C module > have a programmable Master Wait Timer, which among others, checks the

Re: [RFC PATCH RESEND v3 3/3] ptrace: add PTRACE_EVENT_SECCOMP support to PTRACE_GET_SYSCALL_INFO

On 11/27, Elvira Khabirova wrote: > > On Mon, 26 Nov 2018 15:35:24 +0100 > Oleg Nesterov wrote: > > > On 11/25, Elvira Khabirova wrote: > > > > > > Extend PTRACE_GET_SYSCALL_INFO to support PTRACE_EVENT_SECCOMP stops. > > > The information returned is the same as for syscall-enter-stops. > > > > O

Re: [RFC PATCH 00/20] x86/intel_rdt: Start abstraction for a second arch

Hi James, On Fri, Aug 24, 2018 at 11:44:59AM +0100, James Morse wrote: > Hi folks, > > ARM have some upcoming CPU features that are similar to Intel RDT. Resctrl > is the defacto ABI for this sort of thing, but it lives under arch/x86. > > To get existing software working, we need to make resctr

[PATCH] Fix invalid use of sizeof in stm32_sai_add_mclk_provider()

sizeof(mclk) is 4 or 8 as it is the size of a pointer, but we want to reserve space for the pointed data. This issue was detected by using the Coccinelle software. Signed-off-by: Wen Yang CC: Olivier Moysan CC: Arnaud Pouliquen CC: Liam Girdwood CC: Jaroslav Kysela CC: Takashi Iwai CC: Maxim

Re: [PATCH 1/5] perf tools: Add fallback functions for cases where cpumode is insufficient

Em Mon, Nov 26, 2018 at 04:02:17PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Mon, Nov 05, 2018 at 07:53:17PM +, Hunter, Adrian escreveu: > > > From: Arnaldo Carvalho de Melo [mailto:a...@kernel.org] > > > Em Mon, Nov 05, 2018 at 07:21:44PM +, Hunter, Adrian escreveu: > > > > > > +stati

<    1   2   3   4   5   6   7   8   >