Re: [PATCH v3 3/3] ALSA: hda: Disabled unused audio controller for Dell platforms with Switchable Graphics

at 6:59 PM, Pali Rohár wrote: On Thursday 12 April 2018 12:50:02 Takashi Iwai wrote: +#if IS_ENABLED(CONFIG_DELL_LAPTOP) +static bool check_dell_switchable_gfx(struct pci_dev *pdev) +{ + bool (*dell_switchable_gfx_is_enabled_func)(void); + bool enabled; + +

Re: [PATCH v2 04/13] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On 04/12/2018 10:06 AM, Will Deacon wrote: > On Wed, Apr 11, 2018 at 03:53:16PM -0400, Waiman Long wrote: >>> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c >>> index 396701e8c62d..a8fc402b3f3a 100644 >>> --- a/kernel/locking/qspinlock.c >>> +++ b/kernel/locking/qspinlock.c

Re: [PATCH 4/4] dt-bindings: Document the DT bindings for lan78xx

On Thu, Apr 12, 2018 at 03:10:57PM +0100, Phil Elwell wrote: > Hi Andrew, > > On 12/04/2018 15:04, Andrew Lunn wrote: > > On Thu, Apr 12, 2018 at 02:55:36PM +0100, Phil Elwell wrote: > >> The Microchip LAN78XX family of devices are Ethernet controllers with > >> a USB interface. Despite being

Re: [PATCH 08/14] ARM: OMAP2: Add functions to save and restore pinctrl context.

Hi, * Keerthy [180412 03:56]: > From: Russ Dill > > This adds a pair of context save/restore functions to save/restore the > state of a set of pinctrl registers. This simplifies some of the AM33XX > PM code as some of the pinctrl registers are lost when

[PATCH v2 10/13] y2038: powerpc: extend sysvipc data structures

powerpc, uses a nonstandard variation of the generic sysvipc data structures, intended to have the padding moved around so it can deal with big-endian 32-bit user space that has 64-bit time_t. powerpc has the same definition as parisc and sparc, but now also supports little-endian mode, which is

[PATCH v2 00/13] y2038: convert IPC syscalls

This is an update of a series I posted a long time ago [1], updating the IPC subsystem to pass down 64-bit time stamps to user space. In particular, for sys_msgctl, sys_semctl and sys_shmctl, I do not introduce a completely new set of replacement system calls, but instead extend the existing ones

[PATCH v2 08/13] y2038: parisc: extend sysvipc data structures

parisc, uses a nonstandard variation of the generic sysvipc data structures, intended to have the padding moved around so it can deal with big-endian 32-bit user space that has 64-bit time_t. Unlike most architectures, parisc actually succeeded in defining this right for big-endian CPUs, but as

Re: [PATCH 24/24] debugfs: Restrict debugfs when the kernel is locked down

On Thu, Apr 12, 2018 at 1:23 AM, Greg KH wrote: > On Wed, Apr 11, 2018 at 07:54:12PM -0700, Andy Lutomirski wrote: >> On Wed, Apr 11, 2018 at 1:33 PM, Greg KH wrote: >> > On Wed, Apr 11, 2018 at 09:09:16PM +0100, David Howells wrote: >> >> Greg KH

[PATCH v2 01/13] y2038: asm-generic: extend sysvipc data structures

Most architectures now use the asm-generic copy of the sysvipc data structures (msqid64_ds, semid64_ds, shmid64_ds), which use 32-bit __kernel_time_t on 32-bit architectures but have padding behind them to allow extending the type to 64-bit. Unfortunately, that fails on all big-endian

[PATCH v2 12/13] y2038: ipc: use ktime_get_real_seconds consistently

In some places, we still used get_seconds() instead of ktime_get_real_seconds(), and I'm changing the remaining ones now to all use ktime_get_real_seconds() so we use the full available range for timestamps instead of overflowing the 'unsigned long' return value in year 2106 on 32-bit kernels.

[PATCH v2 11/13] y2038: xtensa: extend sysvipc data structures

xtensa, uses a nonstandard variation of the generic sysvipc data structures, intended to have the padding moved around so it can deal with big-endian 32-bit user space that has 64-bit time_t. xtensa tries hard to define the structures so they work in both big-endian and little-endian systems with

[PATCH v2 04/13] y2038: s390: remove unneeded ipc uapi header files

The s390 msgbuf/sembuf/shmbuf header files are all identical to the version from asm-generic. This patch removes the files and replaces them with 'generic-y' statements, to avoid having to modify each copy when we extend sysvipc to deal with 64-bit time_t in 32-bit user space. Note that unlike

[PATCH v2 06/13] y2038: mips: extend sysvipc data structures

MIPS is the weirdest case for sysvipc, because each of the three data structures is done differently: * msqid64_ds has padding in the right place so we could in theory extend this one to just have 64-bit values instead of time_t. As this does not work for most of the other combinations, we

Re: [PATCH 10/14] gpio: omap: Drop the concept of gpio banks not being able to lose context.

* Keerthy [180412 03:56]: > From: Russ Dill > --- a/drivers/gpio/gpio-omap.c > +++ b/drivers/gpio/gpio-omap.c > @@ -68,7 +68,7 @@ struct gpio_bank { > bool dbck_enabled; > bool is_mpuio; > bool dbck_flag; > - bool loses_context; > + >

[PATCH v2 07/13] y2038: x86: extend sysvipc data structures

This extends the x86 copy of the sysvipc data structures to deal with 32-bit user space that has 64-bit time_t and wants to see timestamps beyond 2038. Fortunately, x86 has padding for this purpose in all the data structures, so we can just add extra fields. With msgid64_ds and shmid64_ds, the

buffer sharing across VMs - xen-zcopy and hyper_dmabuf discussion

(changed subject and decoupling from udmabuf thread) On Wed, Apr 11, 2018 at 08:59:32AM +0300, Oleksandr Andrushchenko wrote: > On 04/10/2018 08:26 PM, Dongwon Kim wrote: > >On Tue, Apr 10, 2018 at 09:37:53AM +0300, Oleksandr Andrushchenko wrote: > >>On 04/06/2018 09:57 PM, Dongwon Kim wrote: >

Re: [PATCH 3/4] lan78xx: Read LED modes from Device Tree

Hi Andrew, On 12/04/2018 15:26, Andrew Lunn wrote: > On Thu, Apr 12, 2018 at 02:55:35PM +0100, Phil Elwell wrote: >> Add support for DT property "microchip,led-modes", a vector of two >> cells (u32s) in the range 0-15, each of which sets the mode for one >> of the two LEDs. Some possible values

Re: [PATCH 04/10] KVM: Introduce a new guest mapping API

Coming back to this (nice) series. On 21/02/2018 18:47, KarimAllah Ahmed wrote: > +bool kvm_vcpu_map(struct kvm_vcpu *vcpu, gfn_t gfn, struct kvm_host_map *map) > +{ > + kvm_pfn_t pfn; > + void *kaddr = NULL; Can we s/kaddr/hva/ since that's the standard nomenclature? > + struct

Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system

On 4/12/2018 10:06 AM, Bjorn Helgaas wrote: > [+cc Alex because of his interest in device reset] > > For context, here's the part of the patch we're discussing: > static void dpc_work(struct work_struct *work) { struct dpc_dev *dpc = container_of(work, struct dpc_dev,

[PATCH] doc: Add vendor prefix for Kaohsiung

The 'kao' entry has been added to vendor-prefixes.txt to indicate products from Kaohsiung Opto-Electronics Inc. Signed-off-by: Lukasz Majewski --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH 3/4] lan78xx: Read LED modes from Device Tree

> @@ -2097,6 +2098,25 @@ static int lan78xx_phy_init(struct lan78xx_net *dev) > (void)lan78xx_set_eee(dev->net, ); > } > > + if (!of_property_read_u32_array(dev->udev->dev.of_node, > + "microchip,led-modes", > +

Re: [PATCH 06/10] KVM/nVMX: Use kvm_vcpu_map when mapping the virtual APIC page

On 21/02/2018 18:47, KarimAllah Ahmed wrote: > + > + if (kvm_vcpu_map(vcpu, > gpa_to_gfn(vmcs12->virtual_apic_page_addr), map)) > + vmcs_write64(VIRTUAL_APIC_PAGE_ADDR, > gfn_to_gpa(map->pfn)); This should in principle be pfn_to_hpa. However, pfn_to_hpa is

Applied "ASoC: Intel: atom: fix ACPI/PCI Kconfig" to the asoc tree

The patch ASoC: Intel: atom: fix ACPI/PCI Kconfig 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: fsl_esai: Fix divisor calculation failure at lower ratio" to the asoc tree

The patch ASoC: fsl_esai: Fix divisor calculation failure at lower ratio 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 3/3] ARM: dts: sun7i: Add support for the Ainol AW1 tablet

On Thu, Apr 12, 2018 at 01:08:51AM +0200, Paul Kocialkowski wrote: > > > + backlight: backlight { > > > + compatible = "pwm-backlight"; > > > + pinctrl-names = "default"; > > > + pinctrl-0 = <_enable_pin>; > > > > You don't need any of the pinctrl nodes for the GPIOs > >

[PATCH] memcg: Remove memcg_cgroup::id from IDR on mem_cgroup_css_alloc() failure

In case of memcg_online_kmem() fail, memcg_cgroup::id remains hashed in mem_cgroup_idr even after memcg memory is freed. This leads to leak of ID in mem_cgroup_idr. This patch adds removing into mem_cgroup_css_alloc(), which fixes the problem. For better readability, it adds generic helper, which

[PATCH v3] selftests/livepatch: introduce tests

Add a few livepatch modules and simple target modules that the included regression suite can run tests against. Signed-off-by: Joe Lawrence --- Documentation/livepatch/callbacks.txt | 487 - lib/Kconfig.debug

[PATCH v3] Add livepatch kselftests

Tests run on top of Petr's v11 atomic replace feature and v2 of the shadow variable enhancement patchsets: [PATCH 0/8] livepatch: Atomic replace feature https://lkml.kernel.org/r/20180323120028.31451-1-pmla...@suse.com [PATCH v2 0/2] livepatch: Allocate and free shadow variables more

Re: [PATCH 3/5] net: stmmac: dwmac-sun8i: Allow getting syscon regmap from device

On Wed, Apr 11, 2018 at 10:16:39PM +0800, Icenowy Zheng wrote: > From: Chen-Yu Tsai > > On the Allwinner R40 SoC, the "GMAC clock" register is in the CCU > address space; on the A64 SoC this register is in the SRAM controller > address space, and with a different offset. > > To

[PATCH 3/4] lan78xx: Read LED modes from Device Tree

Add support for DT property "microchip,led-modes", a vector of two cells (u32s) in the range 0-15, each of which sets the mode for one of the two LEDs. Some possible values are: 0=link/activity 1=link1000/activity 2=link100/activity 3=link10/activity

[PATCH 4/4] dt-bindings: Document the DT bindings for lan78xx

The Microchip LAN78XX family of devices are Ethernet controllers with a USB interface. Despite being discoverable devices it can be useful to be able to configure them from Device Tree, particularly in low-cost applications without an EEPROM or programmed OTP. Document the supported properties in

Re: [PATCH v2 04/13] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On Wed, Apr 11, 2018 at 03:53:16PM -0400, Waiman Long wrote: > > diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c > > index 396701e8c62d..a8fc402b3f3a 100644 > > --- a/kernel/locking/qspinlock.c > > +++ b/kernel/locking/qspinlock.c > > @@ -162,6 +162,17 @@ struct __qspinlock {

Re: [PATCH v3 2/2] vfio: platform: Add generic DT reset support

On Thu, 2018-04-12 at 15:12 +0200, Geert Uytterhoeven wrote: > Hi Sinan, > > On Thu, Apr 12, 2018 at 2:36 PM, Sinan Kaya wrote: > > On 4/12/2018 7:49 AM, Auger Eric wrote: > > > On 12/04/18 13:32, Geert Uytterhoeven wrote: > > > > On Thu, Apr 12, 2018 at 12:31 PM, Auger

Re: [PATCH v2 2/2] slab: __GFP_ZERO is incompatible with a constructor

On Wed, 11 Apr 2018, Matthew Wilcox wrote: > > I don't see how that works ... can you explain a little more? > > I see ___slab_alloc() is called from __slab_alloc(). And I see > slab_alloc_node does this: > > object = c->freelist; > page = c->page; > if (unlikely(!object

Re: [PATCH 2/4] lan78xx: Read initial EEE setting from Device Tree

On Thu, Apr 12, 2018 at 02:55:34PM +0100, Phil Elwell wrote: > Add two new Device Tree properties: > * microchip,eee-enabled - a boolean to enable EEE > * microchip,tx-lpi-timer - time in microseconds to wait after TX goes >idle before entering the low power state >

Re: [PATCH 1/4] lan78xx: Read MAC address from DT if present

Hi Andrew, On 12/04/2018 15:06, Andrew Lunn wrote: > Hi Phil > >> -ret = lan78xx_write_reg(dev, RX_ADDRL, addr_lo); >> -ret = lan78xx_write_reg(dev, RX_ADDRH, addr_hi); >> +mac_addr = of_get_mac_address(dev->udev->dev.of_node); > > It might be

Re: [PATCH v2 04/13] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On Thu, Apr 12, 2018 at 10:16:55AM -0400, Waiman Long wrote: > On 04/12/2018 10:06 AM, Will Deacon wrote: > > On Wed, Apr 11, 2018 at 03:53:16PM -0400, Waiman Long wrote: > >>> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c > >>> index 396701e8c62d..a8fc402b3f3a 100644 > >>>

[PATCH v2 02/13] y2038: alpha: remove unneeded ipc uapi header files

The alpha ipcbuf/msgbuf/sembuf/shmbuf header files are all identical to the version from asm-generic. This patch removes the files and replaces them with 'generic-y' statements as part of the y2038 series. Since there is no 32-bit syscall support for alpha, we don't need the other changes, but

[PATCH v2 13/13] y2038: ipc: report long times to user space

The shmid64_ds/semid64_ds/msqid64_ds data structures have been extended to contain extra fields for storing the upper bits of the time stamps, this patch does the other half of the job and and fills the new fields on 32-bit architectures as well as 32-bit tasks running on a 64-bit kernel in compat

[PATCH v2 09/13] y2038: sparc: extend sysvipc data structures

sparc, uses a nonstandard variation of the generic sysvipc data structures, intended to have the padding moved around so it can deal with big-endian 32-bit user space that has 64-bit time_t. Unlike most architectures, sparc actually succeeded in defining this right for big-endian CPUs, but as

[PATCH v2 03/13] y2038: ia64: remove unneeded ipc uapi header files

The ia64 ipcbuf/msgbuf/sembuf/shmbuf header files are all identical to the version from asm-generic. This patch removes the files and replaces them with 'generic-y' statements as part of the y2038 changes. While ia64 no longer has a compat mode and doesn't need the file any more, it seem nicer to

[PATCH v2 05/13] y2038: arm64: extend sysvipc compat data structures

Both 32-bit amd 64-bit ARM use the asm-generic header files for their sysvipc data structures, so no special care is needed to make those work beyond y2038, with the one exception of compat mode: Since there is no asm-generic definition of the compat mode IPC structures, ARM64 provides its own

[PATCH] net: ethernet: ti: cpsw: fix tx vlan priority mapping

The CPDMA_TX_PRIORITY_MAP in real is vlan pcp field priority mapping register and basically replaces vlan pcp field for tagged packets. So, set it to be 1:1 mapping. Signed-off-by: Ivan Khoronzhuk --- Based on net/master drivers/net/ethernet/ti/cpsw.c | 2 +- 1 file

Re: [PATCH v2 2/2] slab: __GFP_ZERO is incompatible with a constructor

On Thu, Apr 12, 2018 at 09:10:23AM -0500, Christopher Lameter wrote: > On Wed, 11 Apr 2018, Matthew Wilcox wrote: > > I don't see how that works ... can you explain a little more? > > c->freelist is NULL and thus ___slab_alloc (slowpath) is called. > ___slab_alloc populates c->freelist and gets

Re: [PATCH 3/4] lan78xx: Read LED modes from Device Tree

On Thu, Apr 12, 2018 at 02:55:35PM +0100, Phil Elwell wrote: > Add support for DT property "microchip,led-modes", a vector of two > cells (u32s) in the range 0-15, each of which sets the mode for one > of the two LEDs. Some possible values are: > > 0=link/activity 1=link1000/activity

Re: [PATCH 12/14] OMAP: CLK: CLKSRC: Add suspend resume hooks

* Keerthy [180412 03:56]: > Add the save and restore for clksrc as part of suspend and resume > so that it saves the counter value and restores. This is needed in > modes like rtc+ddr in self-refresh not doing this stalls the time. I suspect this too should really happen with

[PATCH] staging: ks7010_sdio: fix NULL pointer dereference and memory leak

priv is being dereferenced when it is still null, hence there is an explicit null pointer dereference at line 935: free_netdev(priv->net_dev) Also, memory allocated for netdev at line 854: netdev = alloc_etherdev(sizeof(*priv)); is not being free'd, hence there is a memory leak. Fix this by null

Re: [PATCH 4/4] dt-bindings: Document the DT bindings for lan78xx

On Thu, Apr 12, 2018 at 02:55:36PM +0100, Phil Elwell wrote: > The Microchip LAN78XX family of devices are Ethernet controllers with > a USB interface. Despite being discoverable devices it can be useful to > be able to configure them from Device Tree, particularly in low-cost > applications

Re: [PATCH 2/2] iio: afe: unit-converter: add support for adi,lt6106

On 2018-04-11 18:13, Andrew F. Davis wrote: > On 04/11/2018 10:51 AM, Lars-Peter Clausen wrote: >> On 04/11/2018 05:43 PM, Andrew F. Davis wrote: >>> On 04/11/2018 09:15 AM, Peter Rosin wrote: This is a current sense amplifier from Analog Devices. Signed-off-by: Peter Rosin

Re: [PATCH 03/14] ARM: OMAP2+: omap_hwmod: Introduce HWMOD_NEEDS_REIDLE

* Keerthy [180412 03:56]: > From: Dave Gerlach > --- a/arch/arm/mach-omap2/omap_device.c > +++ b/arch/arm/mach-omap2/omap_device.c > @@ -208,6 +208,27 @@ static int omap_device_build_from_dt(struct > platform_device *pdev) > return ret; > } > > +/**

Re: [PATCH 4/4] dt-bindings: Document the DT bindings for lan78xx

Hi Andrew, On 12/04/2018 15:30, Andrew Lunn wrote: > On Thu, Apr 12, 2018 at 02:55:36PM +0100, Phil Elwell wrote: >> The Microchip LAN78XX family of devices are Ethernet controllers with >> a USB interface. Despite being discoverable devices it can be useful to >> be able to configure them from

Re: [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap

On 21/02/2018 18:47, KarimAllah Ahmed wrote: > ... since using kvm_vcpu_gpa_to_page() and kmap() will only work for guest > memory that has a "struct page". > > The life-cycle of the mapping also changes to avoid doing map and unmap on > every single exit (which becomes very expesive once we use

Re: [PATCHv2, RESEND] x86/mm: Do not lose cpuinfo_x86::x86_phys_bits adjustment

On Tue, Apr 10, 2018 at 12:27:04PM +0300, Kirill A. Shutemov wrote: > Some features (Intel MKTME, AMD SME) reduce number of effectively > available physical address bits. We adjust x86_phys_bits accordingly. > > If get_cpu_cap() got called more than one time we lose this adjustement. > > That's

[PATCH] display: panel: Add KOE tx14d24vm1bpa display support (320x240)

This commit adds support for KOE's 5.7" display. Signed-off-by: Lukasz Majewski --- .../bindings/display/panel/koe,tx14d24vm1bpa.txt | 42 ++ drivers/gpu/drm/panel/panel-simple.c | 26 ++ 2 files changed, 68 insertions(+) create

Re: [PATCH 05/14] ARM: OMAP2: Add functions to save and restore powerdomain context

* Keerthy [180412 03:56]: > From: Russ Dill > --- a/arch/arm/mach-omap2/powerdomain.c > +++ b/arch/arm/mach-omap2/powerdomain.c > @@ -1199,3 +1199,63 @@ bool pwrdm_can_ever_lose_context(struct powerdomain > *pwrdm) > > return 0; > } > + > +/** > + *

Re: [PATCH 07/10] KVM/nVMX: Use kvm_vcpu_map when mapping the posted interrupt descriptor table

On 21/02/2018 18:47, KarimAllah Ahmed wrote: > ... since using kvm_vcpu_gpa_to_page() and kmap() will only work for guest > memory that has a "struct page". > > The life-cycle of the mapping also changes to avoid doing map and unmap on > every single exit (which becomes very expesive once we use

Re: [PATCH 1/3] mm: introduce NR_INDIRECTLY_RECLAIMABLE_BYTES

On Thu, Apr 12, 2018 at 01:52:17PM +0200, Michal Hocko wrote: > On Thu 12-04-18 08:52:52, Vlastimil Babka wrote: > > On 04/11/2018 03:56 PM, Roman Gushchin wrote: > > > On Wed, Apr 11, 2018 at 03:16:08PM +0200, Vlastimil Babka wrote: > [...] > > >> With that in mind, can we at least for now put

Re: [PATCH 11/14] gpio: omap: Restore power_mode configuration at resume time

* Keerthy [180412 03:56]: > From: Dave Gerlach > > Commit 2dc983c565e0 ("gpio/omap: cleanup prepare_for_idle and > resume_after_idle") introduces omap2_gpio_prepare_for_idle and > omap2_gpio_resume_after_idle to properly configure gpios that are used > as

Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system

On Thu, Apr 12, 2018 at 10:34:37AM -0400, Sinan Kaya wrote: > On 4/12/2018 10:06 AM, Bjorn Helgaas wrote: > > > > I think the scenario you are describing is two systems that are > > identical except that in the first, the endpoint is below a hotplug > > bridge, while in the second, it's below a

[PATCH] tda998x: Check ref count before invoking drm_connector_cleanup in unbind

In a situation when the reference count of the drm connector is greater than 1, the unbind function should not invoke drm_connector_cleanup as this will lead to an inconsistent state where the drm_crtc_state->connector_mask still has a bitmask referring to the stale connector. Later, when drm

Re: [PATCH 2/2] input: touchscreen mc13xxx: Add mc34708 support

On Wed, 11 Apr 2018 09:01:01 -0700 Joe Perches wrote: > On Wed, 2018-04-11 at 16:13 +0200, Lukasz Majewski wrote: > > From: Sascha Hauer > > > > The mc34708 has a different bit to enable pen detection. This > > adds the driver data and devtype

Re: [PATCH] regmap: debugfs: check pointer before access

On Thu, Mar 29, 2018 at 08:21:54PM +0800, Peng Fan wrote: > So add check here. When the driver pointer is NULL, return -EIO. We should be providing a name if the file is there so rather than returning an error we should provide something in the file so we should either suppress creation of the

Re: [PATCH] mfd: mc13xxx: Add mc34708 adc support

Hi Joe, > On Wed, 2018-04-11 at 16:09 +0200, Lukasz Majewski wrote: > > From: Sascha Hauer > > > > The mc34708 has an improved adc. The older variants will always > > convert a fixed order of channels. The mc34708 can do up to eight > > conversions in arbitrary channel

Re: [PATCH 1/3] mm: introduce NR_INDIRECTLY_RECLAIMABLE_BYTES

On Thu 12-04-18 15:38:33, Roman Gushchin wrote: > On Thu, Apr 12, 2018 at 01:52:17PM +0200, Michal Hocko wrote: > > On Thu 12-04-18 08:52:52, Vlastimil Babka wrote: > > > On 04/11/2018 03:56 PM, Roman Gushchin wrote: > > > > On Wed, Apr 11, 2018 at 03:16:08PM +0200, Vlastimil Babka wrote: > >

Applied "ASoC: rsnd: mark PM functions __maybe_unused" to the asoc tree

The patch ASoC: rsnd: mark PM functions __maybe_unused 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 1/3] mm: introduce NR_INDIRECTLY_RECLAIMABLE_BYTES

On Thu, Apr 12, 2018 at 08:52:52AM +0200, Vlastimil Babka wrote: > On 04/11/2018 03:56 PM, Roman Gushchin wrote: > > On Wed, Apr 11, 2018 at 03:16:08PM +0200, Vlastimil Babka wrote: > >> [+CC linux-api] > >> > >> On 03/05/2018 02:37 PM, Roman Gushchin wrote: > >>> This patch introduces a concept

Re: [PATCH 5/5] arm64: allwinner: a64: add SRAM controller device tree node

Hi, On Wed, Apr 11, 2018 at 10:16:41PM +0800, Icenowy Zheng wrote: > Allwinner A64 has a SRAM controller, and in the device tree currently > we have a syscon node to enable EMAC driver to access the EMAC clock > register. As SRAM controller driver can now export regmap for this > register,

[PATCH][next] staging: ks7010: fix null pointer dereference on priv on error exit

From: Colin Ian King In the case where the call to dev_alloc_name fails the current exit path is via err_free_netdev and this calls free_netdev on a null priv pointer, hence causing a null pointer dereference. Fix this by instead exiting via err_release_irq. Detected

Re: [PATCH 3.18 000/121] 3.18.105-stable review

On Thu, Apr 12, 2018 at 10:41:48AM +0530, Harsh Shandilya wrote: > On 12 April 2018 12:05:03 AM IST, Greg Kroah-Hartman > wrote: > >This is the start of the stable review cycle for the 3.18.105 release. > >There are 121 patches in this series, all will be posted as a

Linux 4.16.2

I'm announcing the release of the 4.16.2 kernel. All users of the 4.16 kernel series must upgrade. The updated 4.16.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.16.y and can be browsed at the normal kernel.org git web browser:

Linux 4.15.17

I'm announcing the release of the 4.15.17 kernel. All users of the 4.15 kernel series must upgrade. The updated 4.15.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.15.y and can be browsed at the normal kernel.org git web

Re: Linux 4.16.2

diff --git a/Makefile b/Makefile index 1773c718074e..f0040b05df30 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 VERSION = 4 PATCHLEVEL = 16 -SUBLEVEL = 1 +SUBLEVEL = 2 EXTRAVERSION = NAME = Fearless Coyote diff --git

Re: [PATCH v3 2/2] vfio: platform: Add generic DT reset support

On 4/12/2018 7:49 AM, Auger Eric wrote: > Hi Geert, > On 12/04/18 13:32, Geert Uytterhoeven wrote: >> Hi Eric, >> >> On Thu, Apr 12, 2018 at 12:31 PM, Auger Eric wrote: >>> On 11/04/18 11:15, Geert Uytterhoeven wrote: Vfio-platform requires reset support, provided

Re: [PATCH] memory-model: fix cheat sheet typo

On Wed, Apr 11, 2018 at 07:06:36PM +0200, Paolo Bonzini wrote: > On 11/04/2018 18:31, Peter Zijlstra wrote: > >>>Prior Operation Subsequent Operation > >>>--- - > >>>

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Thu, Apr 12, 2018 at 01:19:49PM +0100, Russell King - ARM Linux wrote: > On Thu, Apr 12, 2018 at 02:03:14PM +0300, Dmitry V. Levin wrote: > > On Thu, Apr 12, 2018 at 10:58:11AM +0100, Russell King - ARM Linux wrote: > > > On Thu, Apr 12, 2018 at 04:34:35AM +0300, Dmitry V. Levin wrote: > > > >

Re: [PATCH 4.9 000/310] 4.9.94-stable review

On 12 April 2018 at 00:02, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.94 release. > There are 310 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

[PATCH v4 1/7] interconnect: Add generic on-chip interconnect API

Hi Matthias, On 04/06/2018 08:38 PM, Matthias Kaehlcke wrote: > On Fri, Mar 09, 2018 at 11:09:52PM +0200, Georgi Djakov wrote: >> This patch introduce a new API to get requirements and configure the >> interconnect buses across the entire chipset to fit with the current >> demand. >> >> The API

Re: [PATCH] perf record: Remove unnecessary warning for missing sysfs entry

Em Thu, Apr 12, 2018 at 01:47:23PM +0200, Thomas Richter escreveu: > Using perf on 4.16.0 kernel on s390 shows warning >failed: can't open node sysfs data > each time I run command perf record ... for example: > > [root@s35lp76 perf]# ./perf record -e rB -- sleep 1 > [ perf record: Woken

Re: [PATCH] perf test: Adapt test case record+probe_libc_inet_pton.sh for s390

Em Thu, Apr 12, 2018 at 10:19:59AM +0200, Thomas Richter escreveu: > perf test case 58 (record+probe_libc_inet_pton.sh) > executed on s390x using kernel 4.16.0rc3 > displays this result: > # ./perf trace --no-syscalls >-e probe_libc:inet_pton/call-graph=dwarf/ ping -6 -c 1 ::1 >

[PATCH v4 5/7] interconnect: qcom: Add msm8916 interconnect provider driver

Hi Matthias, On 04/06/2018 01:58 AM, Matthias Kaehlcke wrote: > On Fri, Mar 09, 2018 at 11:09:56PM +0200, Georgi Djakov wrote: >> Add driver for the Qualcomm interconnect buses found in msm8916 based >> platforms. >> >> Signed-off-by: Georgi Djakov >> --- >>

Re: [PATCH 01/24] Add the ability to lock down access to the running kernel image

On Wed, Apr 11, 2018, 5:38 PM Linus Torvalds wrote: > > On Wed, Apr 11, 2018 at 2:05 PM, Jordan Glover > wrote: > >> > >> If that /dev/mem access prevention was just instead done as an even > >> stricter mode of the existing

Re: [RFC PATCH 1/1] vmscan: Support multiple kswapd threads per node

On Tue 03-04-18 12:41:56, Buddy Lumpkin wrote: > > > On Apr 3, 2018, at 6:31 AM, Michal Hocko wrote: > > > > On Mon 02-04-18 09:24:22, Buddy Lumpkin wrote: > >> Page replacement is handled in the Linux Kernel in one of two ways: > >> > >> 1) Asynchronously via kswapd > >> 2)

[PATCH 3/6] Replace memory function for kasan

From: Andrey Ryabinin Functions like memset/memmove/memcpy do a lot of memory accesses. If bad pointer passed to one of these function it is important to catch this. Compiler's instrumentation cannot do this since these functions are written in assembly. KASan replaces

[PATCH 1/6] Add TTBR operator for kasan_init

The purpose of this patch is to provide set_ttbr0/get_ttbr0 to kasan_init function. The definitions of cp15 registers should be in arch/arm/include/asm/cp15.h rather than arch/arm/include/asm/kvm_hyp.h, so move them. Cc: Andrey Ryabinin Reported-by: Marc Zyngier

Re: [PATCH 4.4 000/190] 4.4.128-stable review

On 04/11/2018 11:34 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.128 release. There are 190 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. Responses should be

Re: [PATCH v4 2/7] dt-bindings: Introduce interconnect provider bindings

On 09/03/2018 22:09, Georgi Djakov wrote: > This binding is intended to represent the interconnect hardware present > in some of the modern SoCs. Currently it consists only of a binding for > the interconnect hardware devices (provider). > > Signed-off-by: Georgi Djakov

[PATCH] mm: allow to decrease swap.max below actual swap usage

Currently an attempt to set swap.max into a value lower than the actual swap usage fails. And a user can't do much with it, except turning off swap globally (using swapoff). This is an actual problem we met in the production. The default value for swap.max is "max", so turning swap on globally

Re: [PATCH v9 21/24] perf tools: Add support for the SPF perf event

On 10/04/2018 08:47, David Rientjes wrote: > On Mon, 26 Mar 2018, Andi Kleen wrote: > >>> Aside: should there be a new spec_flt field for struct task_struct that >>> complements maj_flt and min_flt and be exported through /proc/pid/stat? >> >> No. task_struct is already too bloated. If you need

XDP performance regression due to CONFIG_RETPOLINE Spectre V2

Heads-up XDP performance nerds! I got an unpleasant surprise when I updated my GCC compiler (to support the option -mindirect-branch=thunk-extern). My XDP redirect performance numbers when cut in half; from approx 13Mpps to 6Mpps (single CPU core). I've identified the issue, which is caused by

Re: [PATCH V2] drm/amdgpu: limit DMA size to PAGE_SIZE for scatter-gather buffers

On 12/04/18 10:42, Christian König wrote: Am 12.04.2018 um 08:26 schrieb Christoph Hellwig: On Wed, Apr 11, 2018 at 01:03:59PM +0100, Robin Murphy wrote: On 10/04/18 21:59, Sinan Kaya wrote: Code is expecing to observe the same number of buffers returned from dma_map_sg() function compared to

Re: [PATCH 4.9 000/102] 4.9.93-stable review

On 12/04/2018 14:23, Greg Kroah-Hartman wrote: On Thu, Apr 12, 2018 at 02:17:50PM +0200, Thierry Escande wrote: Hi Greg, On 07/04/2018 08:11, Greg Kroah-Hartman wrote: On Fri, Apr 06, 2018 at 05:25:24PM -0500, Dan Rue wrote: On Fri, Apr 06, 2018 at 03:22:41PM +0200, Greg Kroah-Hartman wrote:

Re: [PATCH 4.4 000/190] 4.4.128-stable review

On Wed, Apr 11, 2018 at 01:52:40PM -0700, Nathan Chancellor wrote: > On Wed, Apr 11, 2018 at 08:34:06PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.128 release. > > There are 190 patches in this series, all will be posted as a response > > to this

Re: [PATCH 4.16 00/18] 4.16.2-stable review

On Wed, Apr 11, 2018 at 02:26:15PM -0500, Dan Rue wrote: > On Wed, Apr 11, 2018 at 12:23:35AM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.16.2 release. > > There are 18 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 4.16 00/18] 4.16.2-stable review

On Wed, Apr 11, 2018 at 10:27:24AM -0700, Guenter Roeck wrote: > On Wed, Apr 11, 2018 at 12:23:35AM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.16.2 release. > > There are 18 patches in this series, all will be posted as a response > > to this one.

Linux 4.14.34

I'm announcing the release of the 4.14.34 kernel. All users of the 4.14 kernel series must upgrade. The updated 4.14.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y and can be browsed at the normal kernel.org git web

Re: [PATCH 4.4 000/190] 4.4.128-stable review

On 12 April 2018 at 00:04, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.128 release. > There are 190 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

Re: [PATCH] HID: i2c-hid: Fix resume issue on Raydium touchscreen device

On Mon, 9 Apr 2018, Aaron Ma wrote: > When Rayd touchscreen resumed from S3, it issues too many errors like: > i2c_hid i2c-RAYD0001:00: i2c_hid_get_input: incomplete report (58/5442) > > And all the report data are corrupted, touchscreen is unresponsive. > > Fix this by re-sending report

Re: [PATCH] nvmx: Check exit qualification RD/WR permission for MMIO accesses

On 04/03/2018 11:16, KarimAllah Ahmed wrote: > Validate that a write MMIO access that follows a read MMIO access would > have the correct access captured in the exit qualification. > > Cc: Paolo Bonzini > Cc: Radim Krčmář > Cc: k...@vger.kernel.org > Cc:

Re: [PATCH v3 2/2] vfio: platform: Add generic DT reset support

Hi Sinan, On Thu, Apr 12, 2018 at 2:36 PM, Sinan Kaya wrote: > On 4/12/2018 7:49 AM, Auger Eric wrote: >> On 12/04/18 13:32, Geert Uytterhoeven wrote: >>> On Thu, Apr 12, 2018 at 12:31 PM, Auger Eric wrote: On 11/04/18 11:15, Geert Uytterhoeven

[PATCH 5/6] Initialize the mapping of KASan shadow memory

From: Andrey Ryabinin This patch initializes KASan shadow region's page table and memory. There are two stage for KASan initializing: 1. At early boot stage the whole shadow region is mapped to just one physical page (kasan_zero_page). It's finished by the function

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