Applied "spi: gpio: Make sure spi_master_put() is called in every error path" to the spi tree

The patch spi: gpio: Make sure spi_master_put() is called in every error path has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "spi-summary: document set_cs_timing" to the spi tree

The patch spi-summary: document set_cs_timing has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "spi: gpio: Use devm_spi_register_master()" to the spi tree

The patch spi: gpio: Use devm_spi_register_master() has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "spi: tegra114: add 3 wire transfer mode support" to the spi tree

The patch spi: tegra114: add 3 wire transfer mode support has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "spi: bitbang: Introduce spi_bitbang_init()" to the spi tree

The patch spi: bitbang: Introduce spi_bitbang_init() has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "spi: add a method for configuring CS timing" to the spi tree

The patch spi: add a method for configuring CS timing has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "spi: document tx/rx clock delay properties" to the spi tree

The patch spi: document tx/rx clock delay properties has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: ab8500: add range to usleep_range" to the regulator tree

The patch ASoC: ab8500: add range to usleep_range has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "regulator: bd718x7: Use rdev_get_id() to get regulator id" to the regulator tree

The patch regulator: bd718x7: Use rdev_get_id() to get regulator id has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "regulator: s2mpa01: Convert to use simplified DT parsing" to the regulator tree

The patch regulator: s2mpa01: Convert to use simplified DT parsing has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "ASoC: fsl-dma: Switch to SPDX identifier" to the asoc tree

The patch ASoC: fsl-dma: Switch to SPDX identifier has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: stm32: fix sai driver name initialisation" to the asoc tree

The patch ASoC: stm32: fix sai driver name initialisation has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Re: [RESENT PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

On Mon, Apr 08, 2019 at 12:07:17PM +0800, zhong jiang wrote: > When adding the memory by probing memory block in sysfs interface, there is an > obvious issue that we will unlock the device_hotplug_lock when fails to takes > it. > > That issue was introduced in Commit 8df1d0e4a265 >

Applied "ASoC: mpc5200_dma: Switch to SPDX identifier" to the asoc tree

The patch ASoC: mpc5200_dma: Switch to SPDX identifier has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: mpc5200_psc_ac97: Switch to SPDX identifier" to the asoc tree

The patch ASoC: mpc5200_psc_ac97: Switch to SPDX identifier has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: p1022_rdk: Switch to SPDX identifier" to the asoc tree

The patch ASoC: p1022_rdk: Switch to SPDX identifier has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Re: [PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

://github.com/0day-ci/linux/commits/zhong-jiang/mm-memory_hotplug-Do-not-unlock-when-fails-to-take-the-device_hotplug_lock/20190408-142325 config: x86_64-randconfig-x007-201914 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree

Applied "ASoC: wm1133-ev1: Switch to SPDX identifier" to the asoc tree

The patch ASoC: wm1133-ev1: Switch to SPDX identifier has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: phycore-ac97: Switch to SPDX identifier" to the asoc tree

The patch ASoC: phycore-ac97: Switch to SPDX identifier has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "ASoC: Intel: bytcht_es8316: Add quirk for the Teclast X98+ II" to the asoc tree

The patch ASoC: Intel: bytcht_es8316: Add quirk for the Teclast X98+ II has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

RE: [PATCH 1/2] dt-bindings: rtc: add battery-low-hw-alarm property

HI, > On 06/04/2019 01:07:13-0500, Rob Herring wrote: > > On Wed, Apr 03, 2019 at 04:52:44PM +0200, Flavio Suligoi wrote: > > > Some RTC devices have a battery-low automatic detection circuit. > > > The battery-low event is usually reported with: > > > > > > - a bit change in a RTC status

Re: [PATCH V2 19/20] DT bindings: spi: document tx/rx clock delay properties

On Thu, Apr 04, 2019 at 05:14:18PM -0700, Sowjanya Komatineni wrote: > Tegra SPI controller has TX and RX trimmers to tuning the delay of > SPI master clock with respect to the data. Please use subject lines matching the style for the subsystem. This makes it easier for people to identify

[REGRESSION] AppArmor module parameter layout changed with c5459b829b716

Hi A recent commit changed how `/sys/module/apparmor/parameters/enabled` looks. It was "Y"/"N" before, now it is an integer. I *think* the commit that changed this was: commit c5459b829b716dafd226ad270f25c9a3050f7586 Author: Kees Cook Date: Thu Sep 13 22:28:48 2018 -0700 LSM: Plumb

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

On 08.04.2019 9:05, Hugh Dickins wrote: On Fri, 5 Apr 2019, Konstantin Khlebnikov wrote: On 05.04.2019 5:12, Hugh Dickins wrote: Hi Alex, could you please give the patch below a try? It fixes a problem, but I'm not sure that it's your problem - please let us know. I've not yet written up the

Re: WARN_ON_ONCE() hit at kernel/events/core.c:330

On 4/4/19 3:03 PM, Peter Zijlstra wrote: > On Thu, Apr 04, 2019 at 01:09:09PM +0200, Peter Zijlstra wrote: > >> That is not entirely the scenario I talked about, but *groan*. >> >> So what I meant was: >> >> CPU-0 CPU-n >> >>

Re: [PATCH] soundwire: fix pm_runtime_get_sync return code checks

> On 5 Apr 2019, at 17:04, Pierre-Louis Bossart > wrote: > > On 4/5/19 2:26 AM, Jan Kotas wrote: >> >> >> ret = pm_runtime_get_sync(slave->bus->dev); >> -if (ret < 0) >> +if (ret < 0 && ret != -EACCES) >> > There was a patch submitted on 3/28 by Srinivas Kandagatla who

Re: [PATCH] s390/mm: Silence compiler warning when compiling without CONFIG_PGSTE

On 07.04.19 14:55, Thomas Huth wrote: > If CONFIG_PGSTE is not set (e.g. when compiling without KVM), GCC complains: > > CC arch/s390/mm/pgtable.o > arch/s390/mm/pgtable.c:413:15: warning: ‘pmd_alloc_map’ defined but not > used [-Wunused-function] > static pmd_t *pmd_alloc_map(struct

Re: [RESENT PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

On 08.04.19 06:07, zhong jiang wrote: > When adding the memory by probing memory block in sysfs interface, there is an > obvious issue that we will unlock the device_hotplug_lock when fails to takes > it. > > That issue was introduced in Commit 8df1d0e4a265 > ("mm/memory_hotplug: make

Re: [RFC PATCH 2/9] cpufreq: qcom: Re-organise kryo cpufreq to use it for other nvmem based qcom socs

Hi Niklas, On 4/4/2019 10:39 AM, Niklas Cassel wrote: > From: Sricharan R > > The kryo cpufreq driver reads the nvmem cell and uses that data to > populate the opps. There are other qcom cpufreq socs like krait which > does similar thing. Except for the interpretation of the read data, > rest

[net] 97cdcf37b5: BUG:using__this_cpu_read()in_preemptible[#]code:systemd-timesyn

FYI, we noticed the following commit (built with gcc-7): commit: 97cdcf37b57e3f204be3000b9eab9686f38b4356 ("net: place xmit recursion in softnet data") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master in testcase: trinity with following parameters: runtime: 300s

Re: Regression in suspend-to-ram (TPM related) with 5.1-rc1 (BISECTED)

On Sun, Apr 7, 2019 at 10:53 PM Martin Kepplinger wrote: > > On 21.03.19 14:41, Jarkko Sakkinen wrote: > > On Tue, Mar 19, 2019 at 04:03:37PM -0700, Paul Zimmerman wrote: > >> So I bisected this down to: > >> > >> # first bad commit: [a3fbfae82b4cb3ff9928e29f34c64d0507cad874] tpm: > >> take TPM

[PATCH 1/3] ntb_hw_switchtec: Remove redundant steps of switchtec_ntb_reinit_peer() function

From: Joey Zhang When a re-initialization is caused by a link event, the driver will re-setup the shared memory window. But at that time, the shared memory is still valid, and it's unnecessary to free, reallocate and then initialize it again. We only need to reconfigure the hardware registers.

[PATCH 2/3] ntb_hw_switchtec: Skip unnecessary re-setup of shared memory window for crosslink case

In case of NTB crosslink topology, the setting of shared memory window in the virtual partition doesn't reset on peer's reboot. So skip the unnecessary re-setup of shared memory window for that case. Signed-off-by: Wesley Sheng --- drivers/ntb/hw/mscc/ntb_hw_switchtec.c | 3 +++ 1 file changed,

[PATCH 3/3] ntb_hw_switchtec: Fix setup MW with failure bug

From: Joey Zhang Switchtec does not support setting multiple MWs simultaneously. The driver takes a hardware lock to ensure that two peers are not doing this simultaneously and it fails if someone else takes the lock. In most cases, this is fine as clients only setup the MWs once on one side of

Re: [patch V2 28/29] x86/irq/64: Remap the IRQ stack with guard pages

On Sun, 7 Apr 2019, Andy Lutomirski wrote: > On Sun, Apr 7, 2019 at 3:44 PM Thomas Gleixner wrote: > > Actually we have: save_stack_trace() > > > > Like I did here: > > https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=WIP.x86/stackguards Kinda, but what that code wants is

[PATCH 0/3] Redundant steps removal and bug fix of ntb_hw_switchtec

Hi, Everyone, This patch series remove redundant steps and fix one bug of the ntb_hw_switchtec module. When a re-initialization is caused by a link event, the driver will re-setup the shared memory windows. But at that time, the shared memory is still valid, and it's unnecessary to free,

Re: [PATCH V2 10/20] Documentation: devicetree: spi: add spi-lsbyte-first propery

On Thu, Apr 04, 2019 at 05:14:09PM -0700, Sowjanya Komatineni wrote: > spi-lsbyte-first optional property allows SPI slaves to choose byte > order of little endian for transfers. Why make this a DT property - surely it's either a fixed property of the relevant devices if they are LSB first (in

Re: [PATCH V2 11/20] spi: expand mode support and add LSBYTE_FIRST mode

On Thu, Apr 04, 2019 at 05:14:10PM -0700, Sowjanya Komatineni wrote: > Some SPI Master controllers support configuring Least significant byte > first or Most significant byte first order for transfers. Also some SPI > slave devices expect bytes to be in Least significant first order and > some

Re: [PATCH v2 1/3] ASoC: rt5677: allow multiple interrupt sources

On Fri, Apr 05, 2019 at 02:42:55PM -0600, Fletcher Woodruff wrote: > This patch allows headphone plug detect and mic present > detect to be enabled at the same time. This patch implements > an irq_chip with irq_domain directly instead of using > regmap_irq, so that interrupt source line

Re: [PATCH V2 14/20] spi: tegra114: add support for gpio based cs

On Thu, Apr 04, 2019 at 05:14:13PM -0700, Sowjanya Komatineni wrote: > + if (cstate->cs_gpio_valid) { > + int val = (spi->mode & SPI_CS_HIGH) ? 1 : 0; > + > + gpio_set_value(spi->cs_gpio, val); > + } This is adding new usage of the

[PATCH 0/2] Fix two bugs of switchtec module

Hi, Everyone, This patch series fix two bugs of switchtec module. The first is introduced by device spec definition issue: the maximum supported PCIe function number by hardware should be 255 instead of the false number of 48. Rectify it in driver and for backward compatible, a new ioctl and

[PATCH 2/2] switchtec: Fix unintended mask of MRPC event

When running application tool switchtec-user's `firmware update` and `event wait` commands concurrently, sometimes the firmware update speed reduced evidently. It is because when the MRPC event happened right after MRPC event occurrence check but before event mask loop reach to its header

[PATCH 1/2] switchtec: Fix false maximum supported PCIe function number issue

The hardware supports up to 255 PFFs and the driver only supports 48, so this patch updates the driver to support them all. To be backward compatible, a new ioctl and corresponding data structure are created, while keep the deprecated one. Signed-off-by: Wesley Sheng ---

Hello Beautiful

Hi Dear, my name is Jack and i am seeking for a relationship in which i will feel loved after a series of failed relationships. I am hoping that you would be interested and we could possibly get to know each other more if you do not mind. I am open to answering questions from you as i think

Re: [PATCH] alarmtimer: return correct remaining time

On 4/8/2019 9:45 AM, Andrei Vagin wrote: To calculate a remaining time, we need to subtract the current time from the expiration time. Currently, arguments of ktime_sub are swapped. Signed-off-by: Andrei Vagin --- kernel/time/alarmtimer.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

On Fri, 5 Apr 2019, Konstantin Khlebnikov wrote: > On 05.04.2019 5:12, Hugh Dickins wrote: > > Hi Alex, could you please give the patch below a try? It fixes a > > problem, but I'm not sure that it's your problem - please let us know. > > > > I've not yet written up the commit description, and

Re: [PATCH 1/2] arm64: dts: allwinner: a64-amarula-relic: Add GT5663 CTP node

On Mon, Apr 8, 2019 at 1:54 PM Jagan Teki wrote: > > Add Goodix GT5663 capacitive touch controller node on > Amarula A64-Relic board. > > The CTP connected to board with, > - SDA, SCK from i2c1 > - GPIO-LD0 as AVDD28 supply > - PH4 gpio as interrupt pin > - PH8 gpio as reset pin > - X axis is

Re: [PATCH 6/6] arm64/mm: Enable ZONE_DEVICE

On 04/08/2019 09:33 AM, Ira Weiny wrote: > On Sun, Apr 07, 2019 at 03:11:00PM -0700, Dan Williams wrote: >> On Thu, Apr 4, 2019 at 2:47 AM Robin Murphy wrote: >>> >>> On 04/04/2019 06:04, Dan Williams wrote: On Wed, Apr 3, 2019 at 9:42 PM Anshuman Khandual wrote: > > >

Re: [PATCH] x86/reboot: Use efi reboot for Acer TravelMate X514-51T

Thomas Gleixner 於 2019年4月6日 週六 上午5:14寫道： > > On Mon, 1 Apr 2019, Jian-Hong Pan wrote: > > +/* > > + * Some machines require the "reboot=e" commandline options > > + */ > > +static int __init set_efi_reboot(const struct dmi_system_id *d) > > +{ > > + if (reboot_type != BOOT_EFI) { > > +

<    3   4   5   6   7   8