[PATCH v2 6/6] spi: sun4i: add DMA transfers support

DMA transfers are now available for sun4i-family SoCs. The DMA mode is used automatically as soon as requested transfer length is more than FIFO length. Changes in v2: 1) Debug log enhancements. Signed-off-by: Sergey Suloev --- drivers/spi/spi-sun4i.c | 299

[PATCH v2 0/6] spi: Add support for DMA transfers in sun4i SPI driver

The following patchset provides corrections for PIO-mode and support for DMA transfers in sun4i SPI driver. Changes in v2: 1) Restored processing of 3/4 FIFO full interrupt. 2) Debug log enhancements. Sergey Suloev (6): spi: core: handle timeout error from transfer_one() spi: sun4i:

[PATCH v2 2/6] spi: sun4i: restrict transfer length in PIO-mode

There is no need to handle the 3/4 FIFO empty interrupt as the maximum supported transfer length in PIO mode is 64 bytes. As long as a problem was reported previously with filling FIFO on A10s we want to stick with 63 bytes depth. Changes in v2: 1) Restored processing of 3/4 FIFO full interrupt.

Re: [PATCH v3 2/4] mfd: add Gateworks System Controller core driver

On Wed, Mar 28, 2018 at 8:14 AM, Tim Harvey wrote: > The Gateworks System Controller (GSC) is an I2C slave controller > implemented with an MSP430 micro-controller whose firmware embeds the > following features: > - I/O expander (16 GPIO's) using PCA955x protocol > - Real

Re: [PATCH v2 1/6] spi: core: handle timeout error from transfer_one()

On Tue, Apr 03, 2018 at 06:29:00PM +0300, Sergey Suloev wrote: > As long as sun4i/sun6i SPI drivers have overriden the default > "wait for completion" procedure then we need to properly > handle -ETIMEDOUT error from transfer_one(). Why is this connected to those drivers specifically?

Re: [PATCH v2] f2fs: remain written times to update inode during fsync

On 04/03, Chao Yu wrote: > On 2018/4/3 13:23, Jaegeuk Kim wrote: > > On 04/03, Chao Yu wrote: > >> On 2018/3/31 0:30, Jaegeuk Kim wrote: > >>> Change log from v1: > >>> - add more description > >>> > >>> This fixes xfstests/generic/392. > >>> > >>> The failure was caused by different times

Re: [PATCH v2] x86/xen/efi: Initialize UEFI secure boot state during dom0 boot

On Tue, Apr 03, 2018 at 08:44:41AM -0700, James Bottomley wrote: > On Tue, 2018-04-03 at 16:39 +0200, Daniel Kiper wrote: > > Initialize UEFI secure boot state during dom0 boot. Otherwise the > > kernel > > may not even know that it runs on secure boot enabled platform. > > > > Signed-off-by:

Re: [GIT PULL] Kernel lockdown for secure boot

On Tue, Apr 3, 2018 at 8:41 AM, Alexei Starovoitov wrote: > On Tue, Apr 03, 2018 at 08:11:07AM -0700, Andy Lutomirski wrote: >> > >> >> "bpf: Restrict kernel image access functions when the kernel is locked >> >> down": >> >> This patch just sucks in general. >> >

Re: [LINUX PATCH v8 2/2] memory: pl353: Add driver for arm pl353 static memory controller

Hello- On Wed, Mar 14, 2018 at 04:14:34PM +0530, nagasureshkumarre...@gmail.com wrote: > From: Naga Sureshkumar Relli I'm pleased to see this patchset revived and resubmitted! It would be easier to follow if you constructed your two patchsets with git format-patch

Re: [PATCH v6 3/9] pinctrl: actions: Add Actions S900 pinctrl driver

Hi Andy, On Sat, Mar 31, 2018 at 12:16:49AM +0300, Andy Shevchenko wrote: > On Wed, Mar 28, 2018 at 8:46 PM, Manivannan Sadhasivam > wrote: > > Add pinctrl driver for Actions Semi S900 SoC. The driver supports > > pinctrl, pinmux and pinconf functionalities

KASAN: global-out-of-bounds Write in string

Hello, syzbot hit the following crash on upstream commit 642e7fd23353e22290e3d51719fcb658dc252342 (Tue Apr 3 04:22:12 2018 +) Merge branch 'syscalls-next' of git://git.kernel.org/pub/scm/linux/kernel/git/brodo/linux syzbot dashboard link:

Re: NO_HZ_FULL and tick running within a reasonable amount of time

On Tue, Apr 03, 2018 at 01:41:31PM +0200, Frederic Weisbecker wrote: > On Mon, Apr 02, 2018 at 03:04:38PM -0700, Paul E. McKenney wrote: > > Hello! > > > > I am hitting the following on today's mainline under rcutorture, but > > only on scenarios built with CONFIG_NO_HZ_FULL=y: > > > >

[PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

The touch sensor buttons on Sony VAIO VGN-CS series laptops (e.g. VGN-CS31S) are a separate PS/2 device. As the MUX is disabled for all VAIO machines by the nomux blacklist, the data from touch sensor buttons and touchpad are combined. The protocol used by the buttons is probably similar to the

Re: [PATCH 4/8] dma-buf: add peer2peer flag

On Tue, Apr 03, 2018 at 11:09:09AM +0200, Daniel Vetter wrote: > On Thu, Mar 29, 2018 at 01:34:24PM +0200, Christian König wrote: > > Am 29.03.2018 um 08:57 schrieb Daniel Vetter: > > > On Sun, Mar 25, 2018 at 12:59:56PM +0200, Christian König wrote: > > > > Add a peer2peer flag noting that the

Re: [PATCH v2] locks: change POSIX lock ownership on execve when files_struct is displaced

Jeff Layton writes: > On Thu, 2018-03-22 at 00:36 -0500, Eric W. Biederman wrote: >> ebied...@xmission.com (Eric W. Biederman) writes: >> >> > Jeff Layton writes: >> > >> > > From: Jeff Layton >> > > >> > > POSIX mandates that open

[PATCH 2/2] kfree_rcu() should use kfree_bulk() interface

From: Rao Shoaib kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures as it is more efficient. Signed-off-by: Rao Shoaib --- include/linux/mm.h | 5 ++ include/linux/rcupdate.h | 4 +- include/linux/rcutiny.h

[PATCH 1/2] Move kfree_call_rcu() to slab_common.c

From: Rao Shoaib kfree_call_rcu does not belong in linux/rcupdate.h and should be moved to slab_common.c Signed-off-by: Rao Shoaib --- include/linux/rcupdate.h | 43 +++ include/linux/rcutree.h | 2 --

Re: [GIT PULL] siginfo fix for v4.16-rc5

On Apr 3, 2018, at 10:27 AM, Eric W. Biederman wrote: > Geert Uytterhoeven writes: > >> On Mon, Apr 2, 2018 at 10:17 PM, Eric W. Biederman >> wrote: >> >>> A 2-byte alignment for 4 byte pointers. That is a new one to me.

Re: [PATCH v2 3/6] i2c: i2c-stm32f7: Add initial SMBus protocols support

> >> All SMBus protocols are implemented except SMBus-specific protocols. > > > > What does that mean? > > It miss SMBus Host Notification and SMBBus Alert. They are almost ready but > I'm > struggling to put them back to operational state after recent changes related > to > SMBust Host

[GIT] Sparc

1) Add support for ADI (Application Data Integrity) found in more recent sparc64 cpus. Essentially this is keyed based access to virtual memory, and if the key encoded in the virual address is wrong you get a trap. The mm changes were reviewed by Andrew Morton and others. Work by

Re: [PATCH 02/15] ARM: pxa: add dma slave map

On Tue, Apr 3, 2018 at 5:18 PM, Robert Jarzmik wrote: > Arnd Bergmann writes: > >>> + { "smc911x.0", "rx", PDMA_FILTER_PARAM(LOWEST, -1) }, >>> + { "smc911x.0", "tx", PDMA_FILTER_PARAM(LOWEST, -1) }, >>> + { "smc91x.0", "data",

Re: [PATCH v2 5/6] i2c: i2c-stm32f7: Add DMA support

> +#define STM32F7_I2C_DMA_LEN_MIN 0x1 ... > + if (i2c_dev->dma && f7_msg->count >= STM32F7_I2C_DMA_LEN_MIN) { Are you using DMA for every message with a length >= 1? The setup of that might be more expensive than the DMA gain, if so. signature.asc Description: PGP

Re: [alsa-devel] [PATCH] ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"

On Tue, 2018-04-03 at 15:45 +0200, Ladislav Michl wrote: > On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote: > > From: Colin Ian King > > Hello Colin, > > > Trivial fix to spelling mistake in pr_debug message text > > would you mind making this patch a bit

Re: call/normal switch was Re: omap4-droid4: voice call support was

Hi! > > OK thanks for checking. So probably only n_gsm channel 1 is for normal > > Qualcomm at commands, and then channel 2 and others are commands > > implemented by Motorola on the mdm6600. > > > > I guess we'd have to add support for reading and writing to > > /dev/gsmtty2 at least as it

Re: [PATCH] usbip: vhc_hcd: prevent module being removed while device are attached

On 04/03/2018 12:56 AM, Greg KH wrote: > On Mon, Apr 02, 2018 at 02:52:31PM -0600, Shuah Khan wrote: >> vhci_hcd module can be removed even when devices are attached. Fix to >> prevent module removal when devices are still attached. >> >> Signed-off-by: Shuah Khan >> ---

Re: [PATCH v5 3/3] MIPS: use generic GCC library routines from lib/

On Tue, Apr 03, 2018 at 10:24:26AM +0100, Matt Redfearn wrote: > From: Antony Pavlov > > The commit b35cd9884fa5 ("lib: Add shared copies of some GCC library > routines") makes it possible to share generic GCC library routines by > several architectures. > > This commit

RE: [PATCH v5 03/14] PCI: Add pcie_bandwidth_capable() to compute max supported link bandwidth

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: Tuesday, April 03, 2018 7:06 AM > To: Jacob Keller > Cc: Tal Gilboa ; Tariq Toukan ; > Keller, Jacob E ; Ariel Elior >

[PATCH 2/3] Documentation/features/core: Add arch support status files for 'cBPF-JIT' and 'eBPF-JIT'

Signed-off-by: Andrea Parri --- .../features/core/BPF-JIT/arch-support.txt | 31 -- .../features/core/cBPF-JIT/arch-support.txt| 5 .../features/core/eBPF-JIT/arch-support.txt| 5 3 files changed, 10

[PATCH 3/3] Documentation/features: Refresh and auto-generate the arch support status files in place

Signed-off-by: Andrea Parri --- .../features/core/cBPF-JIT/arch-support.txt| 27 ++ .../features/core/eBPF-JIT/arch-support.txt| 27 ++ .../core/generic-idle-thread/arch-support.txt | 3 ++-

[PATCH 1/3] Documentation/features: Add script that refreshes the arch support status files in place

Suggested-by: Ingo Molnar Signed-off-by: Andrea Parri --- Documentation/features/scripts/features-refresh.sh | 55 ++ 1 file changed, 55 insertions(+) create mode 100755 Documentation/features/scripts/features-refresh.sh

[RFC PATCH 0/3] Documentation/features: Provide and apply "features-refresh.sh"

In Ingo's words [1]: "[...] what should be done instead is to write a script that refreshes all the arch-support.txt files in-place. [...] It's OK for the script to have various quirks for weirdly implemented features and exceptions: i.e. basically whenever it gets a feature wrong,

Re: [RFC PATCH v1] fw_lockdown: new micro LSM module to prevent loading unsigned firmware

On Mon, Apr 02, 2018 at 05:42:22PM -0700, Andy Lutomirski wrote: > On 11/10/2017 01:02 PM, Mimi Zohar wrote: > > If the kernel is locked down and IMA-appraisal is not enabled, prevent > > loading of unsigned firmware. > > > diff --git a/security/fw_lockdown/Kconfig b/security/fw_lockdown/Kconfig

Re: [PATCH net] net: dsa: mt7530: Use NULL instead of plain integer

On 04/02/2018 07:18 PM, Sean Wang wrote: > On Mon, 2018-04-02 at 16:24 -0700, Florian Fainelli wrote: >> We would be passing 0 instead of NULL as the rsp argument to >> mt7530_fdb_cmd(), fix that. >> > > Acked-by: Sean Wang > > BTW, does the part of the commit message

[RFC PATCH 2/4] acpi: apei: Swap ghes_print_queued_estatus and ghes_proc_in_irq

Move ghes_print_queued_estatus() above ghes_proc_in_irq(). In a subsequent patch, the NMI handler will be updated, and the print functionality will be used in ghes_proc_in_irq. This simply makes the subsequent diff look sane. Signed-off-by: Alexandru Gagniuc ---

[RFC PATCH 4/4] acpi: apei: Warn when GHES marks correctable errors as "fatal"

There seems to be a culture amongst BIOS teams to want to crash the OS when an error can't be handled in firmware. Marking GHES errors as "fatal" is a very common way to do this. However, a number of errors reported by GHES may be fatal in the sense a device or link is lost, but are not fatal to

[RFC PATCH 0/4] acpi: apei: Improve error handling with firmware-first

Hi, I'm helping out Dell work out through the issues related to PCIe and NVMe hotplug. Although hot-plug generally works, there are corner cases such as pin bounce, drives failing and surprise removal that are not 100% worked out. Because of this, NVMe is not yet on feature parity with SCSI and

[RFC PATCH 3/4] acpi: apei: Do not panic() in NMI because of GHES messages

BIOSes like to send NMIs for a number of silly reasons often deemed to be "fatal". For example pin bounce during a PCIE hotplug/unplug might cause the link to go down and retrain, with fatal PCI errors being generated while the link is retraining. Instead of panic()ing in NMI context, pass fatal

Re: [PATCH v6 3/9] pinctrl: actions: Add Actions S900 pinctrl driver

On Tue, Apr 03, 2018 at 07:03:46PM +0200, Andreas Färber wrote: > Hi Mani, > > Am 03.04.2018 um 19:00 schrieb Manivannan Sadhasivam: > > On Sat, Mar 31, 2018 at 12:16:49AM +0300, Andy Shevchenko wrote: > >> On Wed, Mar 28, 2018 at 8:46 PM, Manivannan Sadhasivam > >>

Re: How to get lockref patch merged?

On Tue, Apr 03, 2018 at 01:13:00PM +0200, Andreas Gruenbacher wrote: > Hello, > > what's the best way to get the following lockref patch merged? The > maintainers file doesn't list a maintainer. Should we go straight to > Linus? Does one of you want to take it? Andrew normally takes lib/

Re: [PATCH v2 11/17] kvm: arm64: Configure VTCR per VM

On 03/04/18 15:58, James Morse wrote: Hi Suzuki, On 27/03/18 14:15, Suzuki K Poulose wrote: We set VTCR_EL2 very early during the stage2 init and don't touch it ever. This is fine as we had a fixed IPA size. This patch changes the behavior to set the VTCR for a given VM, depending on its

Re: [PATCH v2] x86/xen/efi: Initialize UEFI secure boot state during dom0 boot

On Tue, 2018-04-03 at 16:39 +0200, Daniel Kiper wrote: > Initialize UEFI secure boot state during dom0 boot. Otherwise the > kernel > may not even know that it runs on secure boot enabled platform. > > Signed-off-by: Daniel Kiper > --- >  arch/x86/xen/efi.c   

Re: [PATCH] memcg, thp: do not invoke oom killer on thp charges

On Tue 03-04-18 10:58:53, Johannes Weiner wrote: > On Wed, Mar 21, 2018 at 09:59:28PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > David has noticed that THP memcg charge can trigger the oom killer > > since 2516035499b9 ("mm, thp: remove __GFP_NORETRY from

Re: [PATCH v17 01/10] LIB: Introduce a generic PIO mapping method

+int logic_pio_register_range(struct logic_pio_hwaddr *new_range) +{ + struct logic_pio_hwaddr *range; + resource_size_t start = new_range->hw_start; + resource_size_t end = new_range->hw_start + new_range->size; + resource_size_t mmio_sz = 0; + resource_size_t

Re: [PATCH 1/1] taging: fbtft: fix memory leak

On Tue, 2018-04-03 at 21:33 +0800, Xidong Wang wrote: > From: Xidong Wang <2711406...@qq.com> > > In function fbtft_framebuffer_alloc(), the memory allocated by > framebuffer_alloc() is not released on the error path that txbuflen > 0 > and txbuf, which holds the return value of devm_kzalloc(),

Re: [GIT PULL] Kernel lockdown for secure boot

On Tue, Apr 3, 2018 at 8:11 AM Andy Lutomirski wrote: > Can you explain that much more clearly? I'm asking why booting via > UEFI Secure Boot should enable lockdown, and I don't see what this has > to do with kexec. And "someone blacklist[ing] your key in the > bootloader"

Re: [PATCH net 1/2] net: bcmgenet: Fix sparse warnings in bcmgenet_put_tx_csum()

On Mon, Apr 02, 2018 at 03:58:55PM -0700, Florian Fainelli wrote: > skb->protocol is a __be16 which we would be calling htons() against, > while this is not wrong per-se as it correctly results in swapping the > value on LE hosts, this still upsets sparse. Adopt a similar pattern to > what other

Re: [PATCH net 1/2] net: bcmgenet: Fix sparse warnings in bcmgenet_put_tx_csum()

On Tue, Apr 03, 2018 at 12:33:05PM -0400, David Miller wrote: > Yes Al, however the pattern choosen here is probably cheaper on little endian: > > __beXX val = x; > switch (val) { > case htons(ETH_P_FOO): >... > } > > This way only the compiler byte swaps the

Re: [GIT PULL] Kernel lockdown for secure boot

On Tue, Apr 3, 2018 at 9:29 AM, Matthew Garrett wrote: > On Tue, Apr 3, 2018 at 8:11 AM Andy Lutomirski wrote: >> Can you explain that much more clearly? I'm asking why booting via >> UEFI Secure Boot should enable lockdown, and I don't see what this has >> to

Re: Looking for way to program external MMU from userspace (or viable alternative)

On Tue, Apr 03, 2018 at 01:27:36AM +, Simon Que wrote: > Hi kernel community, > > We have an external PCIe board with a custom coprocessor on it. We also > have code for a kernel driver for it. We have thought about upstreaming it, > but we realized that we can instead convert the driver to a

Re: 4.15.14 crash with iscsi target and dvd

On Sun, 2018-04-01 at 14:27 -0400, Wakko Warner wrote: > Wakko Warner wrote: > > Wakko Warner wrote: > > > I tested 4.14.32 last night with the same oops. 4.9.91 works fine. > > > From the initiator, if I do cat /dev/sr1 > /dev/null it works. If I mount > > > /dev/sr1 and then do find -type f |

Re: [PATCH v17 01/10] LIB: Introduce a generic PIO mapping method

On 03/04/2018 17:37, Thierry Reding wrote: On Tue, Apr 03, 2018 at 05:01:37PM +0100, John Garry wrote: +int logic_pio_register_range(struct logic_pio_hwaddr *new_range) +{ + struct logic_pio_hwaddr *range; + resource_size_t start = new_range->hw_start; + resource_size_t end =

Re: [PATCH 0/5] memory-barriers.txt: Applies upstream changes to the Korean version

On Tue, Apr 03, 2018 at 06:20:22PM +0900, SeongJae Park wrote: > This patchset applies upstream changes for memory-barriers.txt to the Korean > version of it. > > SeongJae Park (5): > kokr/doc: READ_ONCE() now implies smp_barrier_depends() > kokr/doc: De-emphasize smp_read_barrier_depends >

Re: [PATCH v2 2/6] i2c: i2c-stm32f7: Add slave support

On Mon, Mar 26, 2018 at 10:41:51AM +0200, Pierre Yves MORDRET wrote: > > > On 03/25/2018 08:16 PM, Wolfram Sang wrote: > > On Wed, Mar 21, 2018 at 05:48:56PM +0100, Pierre-Yves MORDRET wrote: > >> This patch adds slave support for I2C controller embedded in STM32F7 SoC > >> > >> Signed-off-by:

Re: [PATCH 14/15] ARM: pxa: change SSP devices allocation

Arnd Bergmann writes: chop chop ... removed several mail recipients to leave only the ASoC / PXA subset ... > On Mon, Apr 2, 2018 at 4:26 PM, Robert Jarzmik wrote: > >> >> +static struct pxa_ssp_info pxa_ssp_infos[] = { >> + { .dma_chan_rx_name =

[PATCH v2 0/2] iio: add unit converter

Hi! This driver implements support for voltage dividers and current sense circuits. It's pretty generic and should be easily adaptable to other linear scaling purposes... The driver is still named "unit converter", because it was not clear to me that there was a real problem with the driver

[PATCH v2 1/2] dt-bindings: iio: afe: add current-sense-cuicuit and voltage-divider

An ADC is often used to measure other quantities indirectly. These bindings describe two cases, a current through a sense resistor, and a "big" voltage measured with the help of a voltage divider. Signed-off-by: Peter Rosin --- .../bindings/iio/afe/current-sense-circuit.txt

[PATCH v2 2/2] iio: afe: unit-converter: new driver

If an ADC channel measures the midpoint of a voltage divider, the interesting voltage is often the voltage over the full resistance. E.g. if the full voltage is too big for the ADC to handle. Likewise, if an ADC channel measures the voltage across a resistor, the interesting value is often the

Re: [GIT PULL] Kernel lockdown for secure boot

On Tue, Apr 03, 2018 at 08:11:07AM -0700, Andy Lutomirski wrote: > > > >> "bpf: Restrict kernel image access functions when the kernel is locked > >> down": > >> This patch just sucks in general. > > > > Yes - but that's what Alexei Starovoitov specified. bpf kind of sucks since > > it gives you

[PATCH v3 6/6] spi: sun6i: add DMA transfers support

DMA transfers are now available for sun6i and sun8i SoCs. The DMA mode is used automatically as soon as requested transfer length is more than FIFO length. Changes in v3: 1) Debug log enhancements. Signed-off-by: Sergey Suloev --- drivers/spi/spi-sun6i.c | 331

[PATCH v3 5/6] spi: sun6i: introduce register set/unset helpers

Two helper functions were added in order to set/unset specified flags in registers. Signed-off-by: Sergey Suloev --- drivers/spi/spi-sun6i.c | 37 - 1 file changed, 16 insertions(+), 21 deletions(-) diff --git a/drivers/spi/spi-sun6i.c

[PATCH] rapidio: use a reference count for struct mport_dma_req

Once the dma request is passed to the DMA engine, the DMA subsystem would hold a pointer to this structure and could call the completion callback after do_dma_request() has timed out. The current code deals with this by putting timed out SYNC requests to a pending list and freeing them later,

[PATCH v3 0/6] spi: Add support for DMA transfers in sun6i SPI driver

The following patchset provides corrections for PIO-mode and support for DMA transfers in sun6i SPI driver. Changes in v2: 1) Fixed issue with misplacing a piece of code that requires access to the transfer structure into sun6i_spi_prepare_message() function where the transfer structure is not

[PATCH v3 4/6] spi: sun6i: use completion provided by SPI core

As long as the completion is already provided by the SPI core then there is no need to waste extra-memory on this. Also a waiting function was added to avoid code duplication. Changes in v2: 1) Fixed issue with passing an invalid argument into devm_request_irq() function. Signed-off-by: Sergey

[PATCH v3 3/6] spi: sun6i: restrict transfer length in PIO-mode

There is no need to handle 3/4 empty interrupt as the maximum supported transfer length in PIO mode is equal to FIFO depth, i.e. 128 bytes for sun6i and 64 bytes for sun8i SoCs. Changes in v3: 1) Restored processing of 3/4 FIFO full interrupt. Signed-off-by: Sergey Suloev

Re: [PATCH 14/15] ARM: pxa: change SSP devices allocation

On Tue, Apr 3, 2018 at 5:32 PM, Robert Jarzmik wrote: > Arnd Bergmann writes: > > chop chop ... removed several mail recipients to leave only the ASoC / PXA > subset ... > >> On Mon, Apr 2, 2018 at 4:26 PM, Robert Jarzmik >> wrote:

Re: [PATCH V3 4/4] genirq/affinity: irq vector spread among online CPUs as far as possible

On Tue, Apr 03, 2018 at 03:32:21PM +0200, Thomas Gleixner wrote: > On Thu, 8 Mar 2018, Ming Lei wrote: > > 1) before 84676c1f21 ("genirq/affinity: assign vectors to all possible > > CPUs") > > irq 39, cpu list 0 > > irq 40, cpu list 1 > > irq 41, cpu list 2 > > irq 42, cpu list 3

Re: [PATCH v2 1/6] spi: core: handle timeout error from transfer_one()

On 04/03/2018 06:52 PM, Mark Brown wrote: On Tue, Apr 03, 2018 at 06:29:00PM +0300, Sergey Suloev wrote: As long as sun4i/sun6i SPI drivers have overriden the default "wait for completion" procedure then we need to properly handle -ETIMEDOUT error from transfer_one(). Why is this connected to

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Tue 03-04-18 10:17:53, Steven Rostedt wrote: > On Tue, 3 Apr 2018 15:56:07 +0200 > Michal Hocko wrote: [...] > > I simply do not see the difference between the two. Both have the same > > deadly effect in the end. The direct OOM has an arguable advantage that > > the effect

Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()

On Tue, Apr 03, 2018 at 08:03:56AM -0700, Paul E. McKenney wrote: > On Tue, Apr 03, 2018 at 04:43:00PM +0200, Peter Zijlstra wrote: > > On Tue, Apr 03, 2018 at 07:17:18AM -0700, Paul E. McKenney wrote: > > > Suggestions for a fix? Clearly great care is required when using it > > > in things like

Re: stable-rc build: 4 warnings 0 failures (stable-rc/v4.15.15)

On Tue, Apr 03, 2018 at 04:47:31PM +0200, Arnd Bergmann wrote: > On Sat, Mar 31, 2018 at 7:49 PM, Olof's autobuilder wrote: > > > Warnings: > > > > arm64.allmodconfig: > > WARNING: modpost: missing MODULE_LICENSE() in > > drivers/phy/qualcomm/phy-qcom-ufs.o > > This

Re: [PATCH net 1/2] net: bcmgenet: Fix sparse warnings in bcmgenet_put_tx_csum()

From: Al Viro Date: Tue, 3 Apr 2018 17:29:33 +0100 > On Mon, Apr 02, 2018 at 03:58:55PM -0700, Florian Fainelli wrote: >> skb->protocol is a __be16 which we would be calling htons() against, >> while this is not wrong per-se as it correctly results in swapping the >>

Re: [PATCH v4 13/14] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu

Hi Viresh, On 4/3/2018 9:53 AM, Viresh Kumar wrote: > On 03-04-18, 08:11, Sricharan R wrote: >> Right, i was adding a similar one for krait cores [1]. There is code common >> in the >> init sequence across both (little). Do you suggest to make them common ? > > It may make sense as we are

Re: [PATCH v3 2/4] mfd: add Gateworks System Controller core driver

On Tue, Apr 03, 2018 at 08:48:27AM -0700, Tim Harvey wrote: > On Wed, Mar 28, 2018 at 8:14 AM, Tim Harvey wrote: > > The Gateworks System Controller (GSC) is an I2C slave controller > > implemented with an MSP430 micro-controller whose firmware embeds the > > following

Re: [PATCH v2] x86/xen/efi: Initialize UEFI secure boot state during dom0 boot

On Tue, 2018-04-03 at 18:07 +0200, Daniel Kiper wrote: > On Tue, Apr 03, 2018 at 08:44:41AM -0700, James Bottomley wrote: > > > > On Tue, 2018-04-03 at 16:39 +0200, Daniel Kiper wrote: > > > > > > Initialize UEFI secure boot state during dom0 boot. Otherwise the > > > kernel may not even know

KASAN: use-after-free Read in xfs_inobt_init_key_from_rec

Hello, syzbot hit the following crash on upstream commit 642e7fd23353e22290e3d51719fcb658dc252342 (Tue Apr 3 04:22:12 2018 +) Merge branch 'syscalls-next' of git://git.kernel.org/pub/scm/linux/kernel/git/brodo/linux syzbot dashboard link:

[RFC PATCH 1/4] acpi: apei: Return severity of GHES messages after handling

The policy currently is to simply panic() on GHES fatal errors. Oftentimes we may correct fatal errors i.e. "Fatal" PCIe errors can be corrected via AER When these errors are corrected, it doesn't make sense to panic(). Update ghes_do_proc() to return the severity of the worst error, while

Re: [GIT PULL] siginfo fix for v4.16-rc5

On Apr 03 2018, Josh Juran wrote: > On Apr 3, 2018, at 10:27 AM, Eric W. Biederman wrote: > >> Geert Uytterhoeven writes: >> >>> On Mon, Apr 2, 2018 at 10:17 PM, Eric W. Biederman >>> wrote: >>> A

Re: [alsa-devel] [PATCH] ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"

On Tue, Apr 03, 2018 at 08:49:57AM -0700, Joe Perches wrote: > On Tue, 2018-04-03 at 15:45 +0200, Ladislav Michl wrote: > > On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote: > > > From: Colin Ian King > > > > Hello Colin, > > > > > Trivial fix to spelling

Re: [GIT PULL] x86/build changes for v4.17

On Tue, Apr 3, 2018 at 1:59 AM, Peter Zijlstra wrote: > > It's not just spectre, I believe you yourself wanted to use asm-goto > somewhere in the x86 code: Absolutely. But I don't want to make it impossible for clang people to get their work done. Linus

Re: [PATCH] memcg, thp: do not invoke oom killer on thp charges

On Tue, Apr 03, 2018 at 05:55:09PM +0200, Michal Hocko wrote: > On Tue 03-04-18 10:58:53, Johannes Weiner wrote: > > On Wed, Mar 21, 2018 at 09:59:28PM +0100, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > David has noticed that THP memcg charge can trigger the oom

[PATCH 0/3] SPDX to btrfs

Switch fs/btrfs/*.[ch] and fs/btrfs/tests/*.[ch] to SPDX. I've briefly verified that there are no exceptions to GPL-2.0 (ie. no 'or later'). The changes match what I've seen in other patches and I don't think ther's more needed to be done. If there are no objections I'm going to add the patches to

[PATCH 1/3] btrfs: replace GPL boilerplate by SPDX -- headers

Remove GPL boilerplate text (long, short, one-line) and keep the rest, ie. personal, company or original source copyright statements. Add the SPDX header. Unify the include protection macros to match the file names. Signed-off-by: David Sterba --- fs/btrfs/async-thread.h

Re: [alsa-devel] [PATCH] ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"

On Tue, 2018-04-03 at 19:30 +0200, Ladislav Michl wrote: > On Tue, Apr 03, 2018 at 08:49:57AM -0700, Joe Perches wrote: > > On Tue, 2018-04-03 at 15:45 +0200, Ladislav Michl wrote: > > > On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote: > > > > From: Colin Ian King

[v6 1/6] mm/memory_hotplug: enforce block size aligned range check

Start qemu with the following arguments: -m 64G,slots=2,maxmem=66G -object memory-backend-ram,id=mem1,size=2G Which boots machine with 64G and adds a device mem1 with 2G that can be hotplugged later. Also make sure that .config has the following options turned on: CONFIG_MEMORY_HOTPLUG

[v6 6/6] mm/memory_hotplug: optimize memory hotplug

During memory hotplugging we traverse struct pages three times: 1. memset(0) in sparse_add_one_section() 2. loop in __add_section() to set do: set_page_node(page, nid); and SetPageReserved(page); 3. loop in memmap_init_zone() to call __init_single_pfn() This patch removes the first two loops,

Re: [PATCH] ARM64: dts: meson-axg: enable the eMMC controller

Hi Nan, Thank you for the patch! Yet something to improve: [auto build test ERROR on next-20180403] [cannot apply to robh/for-next v4.16 v4.16-rc7 v4.16-rc6 v4.16] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [virtio-dev] [pci PATCH v7 2/5] virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices

On Tue, Apr 03, 2018 at 10:32:00AM -0700, Alexander Duyck wrote: > On Tue, Apr 3, 2018 at 6:12 AM, Michael S. Tsirkin wrote: > > On Fri, Mar 16, 2018 at 09:40:34AM -0700, Alexander Duyck wrote: > >> On Fri, Mar 16, 2018 at 9:34 AM, Michael S. Tsirkin > >>

Re: [PATCH 2/2] efi: Add embedded peripheral firmware support

In your next patches please Cc the folks I added for future review as well. We don't have a mailing list for the firmware API so I just tend to Cc who I think should help review when needed. On Tue, Apr 03, 2018 at 10:33:25AM +0200, Hans de Goede wrote: > Hi Luis, > > Thank you for the review. >

Re: [PATCH 1/6] x86/intel_rdt/mba_sc: Add documentation for MBA software controller

On Tue, 3 Apr 2018, Thomas Gleixner wrote: On Thu, 29 Mar 2018, Vikas Shivappa wrote: +Memory bandwidth(b/w) in MegaBytes +-- + +Memory bandwidth is a core specific mechanism which means that when the +Memory b/w percentage is specified in the schemata per

Re: Please add 21035965f60b ("bitmap: fix memset optimization on big-endian systems") to the stable tree

On Tue, Apr 3, 2018 at 11:14 AM, Omar Sandoval wrote: > Just wanted to make sure this doesn't get missed because I misspelled > the stable email address in the patch. It applies to v4.13+. The "sta...@kernel.org" address for a stable cc is actually better than stable@vger"

Re: [alsa-devel][PATCH 1/3 v3] ASoC: TSCS42xx: Shorten lines and other cleanup

On Mon, Apr 02, 2018 at 04:23:35PM +0100, Mark Brown wrote: > I only seem to have patches 1 and 2 here (and they aren't threaded with > each other which is a bit odd too). I seem to recall this has been > happening quite a bit with your patches - in general if you're sending > things you should

Re: [GIT PULL] Kernel lockdown for secure boot

> On Apr 3, 2018, at 10:16 AM, David Howells wrote: > > Andy Lutomirski wrote: > >>> A kernel that allows users arbitrary access to ring 0 is just an >>> overfeatured bootloader. Why would you want secure boot in that case? >> >> To get a chain of trust. > >

Re: [GIT PULL] Kernel lockdown for secure boot

On Tue, Apr 3, 2018 at 11:45 AM, Kees Cook wrote: > On Tue, Apr 3, 2018 at 9:45 AM, Andy Lutomirski wrote: >> On Tue, Apr 3, 2018 at 9:29 AM, Matthew Garrett wrote: >>> On Tue, Apr 3, 2018 at 8:11 AM Andy Lutomirski

[BUG] checkpatch.pl: false positive: space prohibited before open square bracket

This patch leads to errors "space prohibited before open square bracket '['" for the asm statement. In the inline assembler statement the bracket is not used for an index. Adding a space after a colon or a comma should be allowable. Signed-off-by: Heinrich Schuchardt ---

[PATCH v10 0/2] fpga: Lattice MachXO2 Slave SPI FPGA Manager support

Hi all, this series adds support for the Lattice MachXO2 FPGA chip, programmed over slave SPI. Tested on a raspberry pi3, beaglebone black (little endian mode) and imx6 hummingboard (big endian mode) + bugblat's pif2 fpga hat (machxo2 7000HC) or tinyfpga A1/A2 (machxo2 256HC / 1200HC), in SPI

Re: [PATCH v9 06/24] mm: make pte_unmap_same compatible with SPF

On Tue, Mar 13, 2018 at 06:59:36PM +0100, Laurent Dufour wrote: > pte_unmap_same() is making the assumption that the page table are still > around because the mmap_sem is held. > This is no more the case when running a speculative page fault and > additional check must be made to ensure that the

Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850

Am Mon, 2 Apr 2018 08:34:35 -0400 schrieb Jason Andryuk : > The HP EliteBook G3 850 has a weird bug where a subsequent cold boot > hangs while plugged in if Linux enables the Host Notify features of > i2c-i801. The cold boot hang depends on how the system boots. It > does

[RFC][PATCH] tracing, printk: Force no hashing when trace_printk() is used

While debugging an issue I needed to see if the pointers were being processed correctly with trace_printk() and after using "%p" and triggering my bug and trace output, I was disappointed that all my pointers were random garbage and didn't produce anything useful for me. I had to rewrite all the

Re: [PATCH v9 15/24] mm: Introduce __vm_normal_page()

On Tue, Mar 13, 2018 at 06:59:45PM +0100, Laurent Dufour wrote: > When dealing with the speculative fault path we should use the VMA's field > cached value stored in the vm_fault structure. > > Currently vm_normal_page() is using the pointer to the VMA to fetch the > vm_flags value. This patch

[PATCH v2 1/6] spi: core: handle timeout error from transfer_one()

As long as sun4i/sun6i SPI drivers have overriden the default "wait for completion" procedure then we need to properly handle -ETIMEDOUT error from transfer_one(). Signed-off-by: Sergey Suloev --- drivers/spi/spi.c | 5 +++-- 1 file changed, 3 insertions(+), 2

<    1   2   3   4   5   6   7   8   9   10   >