[PATCH for-next 6/6] IB/hns: Fix the IB device name

From: Lijun Ou This patch mainly fix the name for IB device in order to match with libhns. Signed-off-by: Lijun Ou Signed-off-by: Salil Mehta --- drivers/infiniband/hw/hns/hns_roce_main.c |2 +- 1 file changed, 1

[PATCH for-next 1/6] IB/hns: Fix the bug when destroy qp

From: "Wei Hu (Xavier)" If send queue is still working when qp is in reset state by modify qp in destroy qp function, hardware will hold on and don't work in hip06 SoC. In current codes, RoCE driver check hardware pointer of sending and hardware pointer of processing to

[PATCH for-next 6/6] IB/hns: Fix the IB device name

From: Lijun Ou This patch mainly fix the name for IB device in order to match with libhns. Signed-off-by: Lijun Ou Signed-off-by: Salil Mehta --- drivers/infiniband/hw/hns/hns_roce_main.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH for-next 1/6] IB/hns: Fix the bug when destroy qp

From: "Wei Hu (Xavier)" If send queue is still working when qp is in reset state by modify qp in destroy qp function, hardware will hold on and don't work in hip06 SoC. In current codes, RoCE driver check hardware pointer of sending and hardware pointer of processing to ensure that hardware has

[PATCH for-next 4/6] IB/hns: Delete the redundant memset operation

From: "Wei Hu (Xavier)" It deleted the redundant memset operation because the memory allocated by ib_alloc_device has been set zero. Signed-off-by: Wei Hu (Xavier) Signed-off-by: Salil Mehta ---

[PATCH for-next 4/6] IB/hns: Delete the redundant memset operation

From: "Wei Hu (Xavier)" It deleted the redundant memset operation because the memory allocated by ib_alloc_device has been set zero. Signed-off-by: Wei Hu (Xavier) Signed-off-by: Salil Mehta --- drivers/infiniband/hw/hns/hns_roce_main.c |3 --- 1 file changed, 3 deletions(-) diff --git

[PATCH for-next 2/6] IB/hns: Fix the bug when free mr

From: Shaobo Xu If the resources of mr are freed while executing the user case, hardware can not been notified in hip06 SoC. Then hardware will hold on when it reads the payload by the PA which has been released. In order to slove this problem, RoCE driver creates 8

[PATCH for-next 2/6] IB/hns: Fix the bug when free mr

From: Shaobo Xu If the resources of mr are freed while executing the user case, hardware can not been notified in hip06 SoC. Then hardware will hold on when it reads the payload by the PA which has been released. In order to slove this problem, RoCE driver creates 8 reserved loopback QPs to

[PATCH for-next 3/6] IB/hns: Fix the bug of setting port mtu

From: "Wei Hu (Xavier)" In hns_roce driver, we need not call iboe_get_mtu to reduce IB headers from effective IBoE MTU because hr_dev->caps.max_mtu has already been reduced. Signed-off-by: Wei Hu (Xavier) Signed-off-by: Salil Mehta

[PATCH for-next 0/6] IB/hns: Bug Fixes for HNS RoCE Driver

This patch-set contains bug fixes for the HNS RoCE driver. Lijun Ou (1): IB/hns: Fix the IB device name Shaobo Xu (2): IB/hns: Fix the bug when free mr IB/hns: Fix the bug when free cq Wei Hu (Xavier) (3): IB/hns: Fix the bug when destroy qp IB/hns: Fix the bug of setting port mtu

[PATCH for-next 0/6] IB/hns: Bug Fixes for HNS RoCE Driver

This patch-set contains bug fixes for the HNS RoCE driver. Lijun Ou (1): IB/hns: Fix the IB device name Shaobo Xu (2): IB/hns: Fix the bug when free mr IB/hns: Fix the bug when free cq Wei Hu (Xavier) (3): IB/hns: Fix the bug when destroy qp IB/hns: Fix the bug of setting port mtu

[PATCH for-next 3/6] IB/hns: Fix the bug of setting port mtu

From: "Wei Hu (Xavier)" In hns_roce driver, we need not call iboe_get_mtu to reduce IB headers from effective IBoE MTU because hr_dev->caps.max_mtu has already been reduced. Signed-off-by: Wei Hu (Xavier) Signed-off-by: Salil Mehta --- drivers/infiniband/hw/hns/hns_roce_main.c | 16

Re: 4.8.8 kernel trigger OOM killer repeatedly when I have lots of RAM that should be free

On Tue, Nov 29, 2016 at 09:40:19AM -0800, Marc MERLIN wrote: > Thanks for the reply and suggestions. > > On Tue, Nov 29, 2016 at 09:07:03AM -0800, Linus Torvalds wrote: > > On Tue, Nov 29, 2016 at 8:34 AM, Marc MERLIN wrote: > > > Now, to be fair, this is not a new problem,

Re: 4.8.8 kernel trigger OOM killer repeatedly when I have lots of RAM that should be free

On Tue, Nov 29, 2016 at 09:40:19AM -0800, Marc MERLIN wrote: > Thanks for the reply and suggestions. > > On Tue, Nov 29, 2016 at 09:07:03AM -0800, Linus Torvalds wrote: > > On Tue, Nov 29, 2016 at 8:34 AM, Marc MERLIN wrote: > > > Now, to be fair, this is not a new problem, it's just varying

Re: 4.9-rc7: (forcedeth?) BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

On Tue, 2016-11-29 at 12:06 -0800, Linus Torvalds wrote: > On Nov 29, 2016 11:58 AM, "Eric Dumazet" > wrote: > > > > nv_do_nic_poll() is simply buggy and needs a fix. > > > > synchronize_irq() can sleep. > > Yes, but why did it start showing up now? None of this has

Re: 4.9-rc7: (forcedeth?) BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

On Tue, 2016-11-29 at 12:06 -0800, Linus Torvalds wrote: > On Nov 29, 2016 11:58 AM, "Eric Dumazet" > wrote: > > > > nv_do_nic_poll() is simply buggy and needs a fix. > > > > synchronize_irq() can sleep. > > Yes, but why did it start showing up now? None of this has changed as > far as I can

[PATCH V8 1/3] ACPI: Add support for ResourceSource/IRQ domain mapping

When an Extended IRQ Resource contains a valid ResourceSource use it to map the IRQ on the domain associated with the ACPI device referenced. With this in place an irqchip driver can create its domain using irq_domain_create_linear and pass the device fwnode to create the domain mapping. When

[PATCH V8 1/3] ACPI: Add support for ResourceSource/IRQ domain mapping

When an Extended IRQ Resource contains a valid ResourceSource use it to map the IRQ on the domain associated with the ACPI device referenced. With this in place an irqchip driver can create its domain using irq_domain_create_linear and pass the device fwnode to create the domain mapping. When

[PATCH V8 3/3] irqchip: qcom: Add IRQ combiner driver

Driver for interrupt combiners in the Top-level Control and Status Registers (TCSR) hardware block in Qualcomm Technologies chips. An interrupt combiner in this block combines a set of interrupts by OR'ing the individual interrupt signals into a summary interrupt signal routed to a parent

[PATCH V8 3/3] irqchip: qcom: Add IRQ combiner driver

Driver for interrupt combiners in the Top-level Control and Status Registers (TCSR) hardware block in Qualcomm Technologies chips. An interrupt combiner in this block combines a set of interrupts by OR'ing the individual interrupt signals into a summary interrupt signal routed to a parent

[PATCH V8 0/3] irqchip: qcom: Add IRQ combiner driver

Add support for IRQ combiners in the Top-level Control and Status Registers (TCSR) hardware block in Qualcomm Technologies chips. The first patch adds support for ResourceSource/IRQ domain mapping when using Extended IRQ Resources with a specific ResourceSource. The patch prevents the ACPI core

[PATCH V8 2/3] ACPI: Retry IRQ conversion if it failed previously

This allows probe deferral to work properly when a dependent device fails to get a valid IRQ because the IRQ domain was not registered at the time the resources were added to the platform_device. Signed-off-by: Agustin Vega-Frias --- drivers/acpi/irq.c | 144

[PATCH V8 0/3] irqchip: qcom: Add IRQ combiner driver

Add support for IRQ combiners in the Top-level Control and Status Registers (TCSR) hardware block in Qualcomm Technologies chips. The first patch adds support for ResourceSource/IRQ domain mapping when using Extended IRQ Resources with a specific ResourceSource. The patch prevents the ACPI core

[PATCH V8 2/3] ACPI: Retry IRQ conversion if it failed previously

This allows probe deferral to work properly when a dependent device fails to get a valid IRQ because the IRQ domain was not registered at the time the resources were added to the platform_device. Signed-off-by: Agustin Vega-Frias --- drivers/acpi/irq.c | 144

Re: [PATCH V4 15/15] blk-throttle: add latency target support

Hello, On Tue, Nov 29, 2016 at 10:14:03AM -0800, Shaohua Li wrote: > What the patches do doesn't conflict what you are talking about. We need a way > to detect if cgroups are idle or active. I think the problem is how to define > 'active' and 'idle'. We must quantify the state. We could use: > 1.

Re: [PATCH V4 15/15] blk-throttle: add latency target support

Hello, On Tue, Nov 29, 2016 at 10:14:03AM -0800, Shaohua Li wrote: > What the patches do doesn't conflict what you are talking about. We need a way > to detect if cgroups are idle or active. I think the problem is how to define > 'active' and 'idle'. We must quantify the state. We could use: > 1.

[PATCH v7] Input: synaptics-rmi4 - add support for F34 V7 bootloader

Port firmware update code from Samsung Galaxy S7 driver into mainline framework. This patch has been tested on Synaptics S7813. Signed-off-by: Nick Dyer Tested-by: Chris Healy --- Hi Dmitry- Here's an updated version of the F34 V7 support. This patch

[PATCH v7] Input: synaptics-rmi4 - add support for F34 V7 bootloader

Port firmware update code from Samsung Galaxy S7 driver into mainline framework. This patch has been tested on Synaptics S7813. Signed-off-by: Nick Dyer Tested-by: Chris Healy --- Hi Dmitry- Here's an updated version of the F34 V7 support. This patch applies on top of dtor/synaptics-rmi4.

[PATCH] arm: add stat support to fiq

This patch allows drivers that uses fiq to have a stat on the execution number of the fiq handler. For that three APIs has been defined: - fiq_kstat_enable: this function enables fiq stat and allocates required memory for it - fiq_kstat_disable: this function disable fiq stat and free its

[PATCH] arm: add stat support to fiq

This patch allows drivers that uses fiq to have a stat on the execution number of the fiq handler. For that three APIs has been defined: - fiq_kstat_enable: this function enables fiq stat and allocates required memory for it - fiq_kstat_disable: this function disable fiq stat and free its

PROBLEM-PERSISTS: dmesg spam: alloc_contig_range: [XX, YY) PFNs busy

I didn't get any responses to this. git bisect shows that the problem did actually exist in 4.5.0-rc6, but has gotten worse by many orders of magnitude (< 1/week to ~20M/hour). Presently with 4.9-rc5, it's now writing ~2.5GB/hour to syslog. The list of addresses in that time is only ~80 unique

PROBLEM-PERSISTS: dmesg spam: alloc_contig_range: [XX, YY) PFNs busy

I didn't get any responses to this. git bisect shows that the problem did actually exist in 4.5.0-rc6, but has gotten worse by many orders of magnitude (< 1/week to ~20M/hour). Presently with 4.9-rc5, it's now writing ~2.5GB/hour to syslog. The list of addresses in that time is only ~80 unique

Re: [PATCHv4 06/10] xen: Switch to using __pa_symbol

On 11/29/2016 02:26 PM, Boris Ostrovsky wrote: > On 11/29/2016 01:55 PM, Laura Abbott wrote: >> __pa_symbol is the correct macro to use on kernel >> symbols. Switch to this from __pa. >> >> Signed-off-by: Laura Abbott >> --- >> Found during a sweep of the kernel. Untested. >>

Re: [PATCHv4 06/10] xen: Switch to using __pa_symbol

On 11/29/2016 02:26 PM, Boris Ostrovsky wrote: > On 11/29/2016 01:55 PM, Laura Abbott wrote: >> __pa_symbol is the correct macro to use on kernel >> symbols. Switch to this from __pa. >> >> Signed-off-by: Laura Abbott >> --- >> Found during a sweep of the kernel. Untested. >> --- >>

[RELEASE] LTTng-UST 2.9.0 (Linux user-space tracer)

This is the official announcement of the release of LTTng-UST 2.9.0. Release name: Joannès. LTTng-UST, the Linux Trace Toolkit Next Generation Userspace Tracer, is a low-overhead application tracer. The library "liblttng-ust" enables tracing of applications and libraries. New and Noteworthy for

[RELEASE] LTTng-UST 2.9.0 (Linux user-space tracer)

This is the official announcement of the release of LTTng-UST 2.9.0. Release name: Joannès. LTTng-UST, the Linux Trace Toolkit Next Generation Userspace Tracer, is a low-overhead application tracer. The library "liblttng-ust" enables tracing of applications and libraries. New and Noteworthy for

[RELEASE] LTTng-modules 2.9.0 (Linux kernel tracer)

This is the official announcement of the release of LTTng-modules 2.9.0. Release name: Joannès. The LTTng modules provide Linux kernel tracing capability to the LTTng 2.9 tracer toolset. New and Noteworthy for LTTng-modules 2.9: * Various performance improvements. Tested on x86-64 and ARM32. *

[RELEASE] LTTng-modules 2.9.0 (Linux kernel tracer)

This is the official announcement of the release of LTTng-modules 2.9.0. Release name: Joannès. The LTTng modules provide Linux kernel tracing capability to the LTTng 2.9 tracer toolset. New and Noteworthy for LTTng-modules 2.9: * Various performance improvements. Tested on x86-64 and ARM32. *

Re: [PATCH V4 13/15] blk-throttle: add a mechanism to estimate IO latency

Hello, On Tue, Nov 29, 2016 at 10:30:44AM -0800, Shaohua Li wrote: > > As discussed separately, it might make more sense to just use the avg > > of the closest bucket instead of trying to line-fit the buckets, but > > it's an implementation detail and whatever which works is fine. > > that is

Re: [PATCH 0/2] z3fold fixes

On Tue, 29 Nov 2016 17:33:19 -0500 Dan Streetman wrote: > On Sat, Nov 26, 2016 at 2:15 PM, Vitaly Wool wrote: > > Here come 2 patches with z3fold fixes for chunks counting and locking. As > > commit 50a50d2 ("z3fold: don't fail kernel build is

Re: [PATCH 0/2] z3fold fixes

On Tue, 29 Nov 2016 17:33:19 -0500 Dan Streetman wrote: > On Sat, Nov 26, 2016 at 2:15 PM, Vitaly Wool wrote: > > Here come 2 patches with z3fold fixes for chunks counting and locking. As > > commit 50a50d2 ("z3fold: don't fail kernel build is z3fold_header is too > > big") was NAK'ed [1], I

Re: [PATCH V4 13/15] blk-throttle: add a mechanism to estimate IO latency

Hello, On Tue, Nov 29, 2016 at 10:30:44AM -0800, Shaohua Li wrote: > > As discussed separately, it might make more sense to just use the avg > > of the closest bucket instead of trying to line-fit the buckets, but > > it's an implementation detail and whatever which works is fine. > > that is

Re: [PATCH 0/2] z3fold fixes

On Sat, Nov 26, 2016 at 2:15 PM, Vitaly Wool wrote: > Here come 2 patches with z3fold fixes for chunks counting and locking. As > commit 50a50d2 ("z3fold: don't fail kernel build is z3fold_header is too > big") was NAK'ed [1], I would suggest that we removed that one and

Re: [PATCH 0/2] z3fold fixes

On Sat, Nov 26, 2016 at 2:15 PM, Vitaly Wool wrote: > Here come 2 patches with z3fold fixes for chunks counting and locking. As > commit 50a50d2 ("z3fold: don't fail kernel build is z3fold_header is too > big") was NAK'ed [1], I would suggest that we removed that one and the next > z3fold

Re: [PATCH 3/3] z3fold: discourage use of pages that weren't compacted

On Mon, Nov 28, 2016 at 9:14 AM, Vitaly Wool wrote: > On Fri, Nov 25, 2016 at 7:25 PM, Dan Streetman wrote: >> On Tue, Nov 15, 2016 at 11:00 AM, Vitaly Wool wrote: >>> If a z3fold page couldn't be compacted, we don't want it to be

Re: [PATCH 3/3] z3fold: discourage use of pages that weren't compacted

On Mon, Nov 28, 2016 at 9:14 AM, Vitaly Wool wrote: > On Fri, Nov 25, 2016 at 7:25 PM, Dan Streetman wrote: >> On Tue, Nov 15, 2016 at 11:00 AM, Vitaly Wool wrote: >>> If a z3fold page couldn't be compacted, we don't want it to be >>> used for next object allocation in the first place. >> >>

[PATCH v3 1/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver

This driver provides an access to EEPROM of IDT PCIe-switches. IDT PCIe- switches expose a simple SMBus interface to perform IO-operations from/to EEPROM, which is located at private (so called Master) SMBus. The driver creates a simple binary sysfs-file to have an access to the EEPROM using the

[PATCH v3 2/2] eeprom: Add IDT 89HPESx driver dts-binding file

IDT 89HPESx PCIe-switches exposes SMBus interface to have an access to the device CSRs and EEPROM. So to properly utilize the interface functionality, developer should declare a valid dts-file node, which would refer to the corresponding 89HPESx device. Signed-off-by: Serge Semin

linux-next: build failure after merge of the cifs tree

napshot timestamp mount parm") CONFIG_CIFS_SMB2 is not set for this build ... I have used the cifs tree from next-20161129 for today. -- Cheers, Stephen Rothwell

[PATCH v3 2/2] eeprom: Add IDT 89HPESx driver dts-binding file

IDT 89HPESx PCIe-switches exposes SMBus interface to have an access to the device CSRs and EEPROM. So to properly utilize the interface functionality, developer should declare a valid dts-file node, which would refer to the corresponding 89HPESx device. Signed-off-by: Serge Semin ---

linux-next: build failure after merge of the cifs tree

napshot timestamp mount parm") CONFIG_CIFS_SMB2 is not set for this build ... I have used the cifs tree from next-20161129 for today. -- Cheers, Stephen Rothwell

[PATCH v3 1/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver

This driver provides an access to EEPROM of IDT PCIe-switches. IDT PCIe- switches expose a simple SMBus interface to perform IO-operations from/to EEPROM, which is located at private (so called Master) SMBus. The driver creates a simple binary sysfs-file to have an access to the EEPROM using the

[PATCH v3 0/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver

Changelog v3: - Get rid of dev_*_idt() macros - Replace to_pdev_kobj() macro with naked dev_get_drvdata() call - Return naked 0 instead of SUCCESS macro - IDT CSR debug file is moved to debugfs - BIN_ATTR_RW is used to declare sysfs binary attribute - Moved bindings file to a separate patch - Need

[PATCH v3 0/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver

Changelog v3: - Get rid of dev_*_idt() macros - Replace to_pdev_kobj() macro with naked dev_get_drvdata() call - Return naked 0 instead of SUCCESS macro - IDT CSR debug file is moved to debugfs - BIN_ATTR_RW is used to declare sysfs binary attribute - Moved bindings file to a separate patch - Need

[PATCH] net: ethernet: ti: cpsw: fix ASSERT_RTNL() warning during resume

netif_set_real_num_tx/rx_queues() are required to be called with rtnl_lock taken, otherwise ASSERT_RTNL() warning will be triggered - which happens now during System resume from suspend: cpsw_resume() |- cpsw_ndo_open() |- netif_set_real_num_tx/rx_queues() |- ASSERT_RTNL(); Hence, fix it

[PATCH] net: ethernet: ti: cpsw: fix ASSERT_RTNL() warning during resume

netif_set_real_num_tx/rx_queues() are required to be called with rtnl_lock taken, otherwise ASSERT_RTNL() warning will be triggered - which happens now during System resume from suspend: cpsw_resume() |- cpsw_ndo_open() |- netif_set_real_num_tx/rx_queues() |- ASSERT_RTNL(); Hence, fix it

Re: [PATCHv4 06/10] xen: Switch to using __pa_symbol

On 11/29/2016 01:55 PM, Laura Abbott wrote: > __pa_symbol is the correct macro to use on kernel > symbols. Switch to this from __pa. > > Signed-off-by: Laura Abbott > --- > Found during a sweep of the kernel. Untested. > --- > drivers/xen/xenbus/xenbus_dev_backend.c | 2 +- >

Re: [PATCHv4 06/10] xen: Switch to using __pa_symbol

On 11/29/2016 01:55 PM, Laura Abbott wrote: > __pa_symbol is the correct macro to use on kernel > symbols. Switch to this from __pa. > > Signed-off-by: Laura Abbott > --- > Found during a sweep of the kernel. Untested. > --- > drivers/xen/xenbus/xenbus_dev_backend.c | 2 +- >

Re: [PATCH v11 0/8] powerpc: Implement kexec_file_load()

Hello Andrew, Am Dienstag, 29. November 2016, 13:45:18 BRST schrieb Andrew Morton: > On Tue, 29 Nov 2016 23:45:46 +1100 Michael Ellerman wrote: > > This is v11 of the kexec_file_load() for powerpc series. > > > > I've stripped this down to the minimum we need, so we can

Re: [PATCH v11 0/8] powerpc: Implement kexec_file_load()

Hello Andrew, Am Dienstag, 29. November 2016, 13:45:18 BRST schrieb Andrew Morton: > On Tue, 29 Nov 2016 23:45:46 +1100 Michael Ellerman wrote: > > This is v11 of the kexec_file_load() for powerpc series. > > > > I've stripped this down to the minimum we need, so we can get this in for > >

[PATCH] soc: ti: qmss: fix the case when !SMP

The irq_set_affinity_hint() will always fail when !SMP and Networking will fail on Keystone 2 devices in this case. Hence, fix by ignoring IRQ affinity settings when !SMP. Cc: Murali Karicheri Signed-off-by: Grygorii Strashko ---

[PATCH] soc: ti: qmss: fix the case when !SMP

The irq_set_affinity_hint() will always fail when !SMP and Networking will fail on Keystone 2 devices in this case. Hence, fix by ignoring IRQ affinity settings when !SMP. Cc: Murali Karicheri Signed-off-by: Grygorii Strashko --- drivers/soc/ti/knav_qmss_queue.c | 2 +- 1 file changed, 1

Re: [PATCH RESEND 2/2] gpio: axp209: add pinctrl support

Hi Linus, On 24/11/2016 15:17, Linus Walleij wrote: > On Wed, Nov 23, 2016 at 3:11 PM, Quentin Schulz > wrote: > >> The GPIOs present in the AXP209 PMIC have multiple functions. They >> typically allow a pin to be used as GPIO input or output and can also be

Re: [PATCH RESEND 2/2] gpio: axp209: add pinctrl support

Hi Linus, On 24/11/2016 15:17, Linus Walleij wrote: > On Wed, Nov 23, 2016 at 3:11 PM, Quentin Schulz > wrote: > >> The GPIOs present in the AXP209 PMIC have multiple functions. They >> typically allow a pin to be used as GPIO input or output and can also be >> used as ADC or regulator for

Re: [PATCH v2] vfs: fix put_compat_statfs64() does not handle errors

> On Nov 15, 2016, at 2:19 AM, Li Wang wrote: > > put_compat_statfs64() does NOT return -1 and setting errno to EOVERFLOW > when some variables(like: f_bsize) overflowed in the returned struct. > > The reason is that the ubuf->f_blocks is __u64 type, it couldn't be > 4bits

Re: [PATCH v2] vfs: fix put_compat_statfs64() does not handle errors

> On Nov 15, 2016, at 2:19 AM, Li Wang wrote: > > put_compat_statfs64() does NOT return -1 and setting errno to EOVERFLOW > when some variables(like: f_bsize) overflowed in the returned struct. > > The reason is that the ubuf->f_blocks is __u64 type, it couldn't be > 4bits as the judgement in

Re: [PATCH v3 0/8] mm/swap: Regular page swap optimizations

On Tue, 2016-11-29 at 13:50 -0800, Andrew Morton wrote: > On Mon, 28 Nov 2016 13:14:01 -0800 Tim Chen > wrote: > > > > > On Tue, 2016-11-15 at 15:47 -0800, Tim Chen wrote: > > > > > > Andrew, > > > > > > It seems like there are no objections to this patch series

Re: [PATCH v3 0/8] mm/swap: Regular page swap optimizations

On Tue, 2016-11-29 at 13:50 -0800, Andrew Morton wrote: > On Mon, 28 Nov 2016 13:14:01 -0800 Tim Chen > wrote: > > > > > On Tue, 2016-11-15 at 15:47 -0800, Tim Chen wrote: > > > > > > Andrew, > > > > > > It seems like there are no objections to this patch series so far. > > > Can you help us

Re: [RFC PATCH] ARM: dts: sun8i: add simplefb node for H3

On Mon, Nov 28, 2016 at 11:42:18AM +0100, Jean-Francois Moine wrote: > On Mon, 28 Nov 2016 17:59:00 +0800 > Icenowy Zheng wrote: > > > As there's currently a fork of U-Boot which provides simplefb support > > for H3, a simplefb node can be added to the device tree. > > > >

Re: [RFC PATCH] ARM: dts: sun8i: add simplefb node for H3

On Mon, Nov 28, 2016 at 11:42:18AM +0100, Jean-Francois Moine wrote: > On Mon, 28 Nov 2016 17:59:00 +0800 > Icenowy Zheng wrote: > > > As there's currently a fork of U-Boot which provides simplefb support > > for H3, a simplefb node can be added to the device tree. > > > > Signed-off-by:

Re: [RFD] Common userspace tool for fscypto

Joe, On 29.11.2016 22:42, Joe Richey wrote: > Hi Richard, > > I'm Joe Richey, and I work on Mike's team. We've been playing around > with a few design > ideas regarding a tool for managing filesystem encryption. After going > though some iterations > with Ted, we have a fairly good idea about

Re: [RFD] Common userspace tool for fscypto

Joe, On 29.11.2016 22:42, Joe Richey wrote: > Hi Richard, > > I'm Joe Richey, and I work on Mike's team. We've been playing around > with a few design > ideas regarding a tool for managing filesystem encryption. After going > though some iterations > with Ted, we have a fairly good idea about

Re: [PATCH v3 3/5] thermal: rockchip: fixes invalid temperature case

Hi Eduardo, I'm not sure I completely understand what you're asking, but I'll see what I can answer. On Mon, Nov 28, 2016 at 05:45:54PM -0800, Eduardo Valentin wrote: > On Mon, Nov 28, 2016 at 07:12:02PM +0800, Caesar Wang wrote: > > The temp_to_code function will return 0 when we set the

Re: [PATCH v3 3/5] thermal: rockchip: fixes invalid temperature case

Hi Eduardo, I'm not sure I completely understand what you're asking, but I'll see what I can answer. On Mon, Nov 28, 2016 at 05:45:54PM -0800, Eduardo Valentin wrote: > On Mon, Nov 28, 2016 at 07:12:02PM +0800, Caesar Wang wrote: > > The temp_to_code function will return 0 when we set the

Re: [POC/RFC PATCH] overlayfs: constant inode numbers

On Tue, Nov 29, 2016 at 1:03 PM, Amir Goldstein wrote: > On Tue, Nov 29, 2016 at 1:34 PM, Amir Goldstein wrote: >> On Tue, Nov 29, 2016 at 12:16 PM, Miklos Szeredi wrote: >>> On Mon, Nov 28, 2016 at 12:56 PM, Amir Goldstein

Re: [POC/RFC PATCH] overlayfs: constant inode numbers

On Tue, Nov 29, 2016 at 1:03 PM, Amir Goldstein wrote: > On Tue, Nov 29, 2016 at 1:34 PM, Amir Goldstein wrote: >> On Tue, Nov 29, 2016 at 12:16 PM, Miklos Szeredi wrote: >>> On Mon, Nov 28, 2016 at 12:56 PM, Amir Goldstein wrote: >> Not sure that I understand what you are suggesting, but I

Re: [PATCH v3 0/8] mm/swap: Regular page swap optimizations

On Mon, 28 Nov 2016 13:14:01 -0800 Tim Chen wrote: > On Tue, 2016-11-15 at 15:47 -0800, Tim Chen wrote: > > Andrew, > > > > It seems like there are no objections to this patch series so far. > > Can you help us get this patch series to be code reviewed in more__ > >

Re: [PATCH v3 0/8] mm/swap: Regular page swap optimizations

On Mon, 28 Nov 2016 13:14:01 -0800 Tim Chen wrote: > On Tue, 2016-11-15 at 15:47 -0800, Tim Chen wrote: > > Andrew, > > > > It seems like there are no objections to this patch series so far. > > Can you help us get this patch series to be code reviewed in more__ > > depth so it can be

Re: [linux-sunxi] Re: [RFC PATCH] ARM: dts: sun8i: add simplefb node for H3

On Mon, Nov 28, 2016 at 06:24:24PM +0800, Chen-Yu Tsai wrote: > On Mon, Nov 28, 2016 at 6:19 PM, Icenowy Zheng wrote: > > > > > > 28.11.2016, 18:07, "Chen-Yu Tsai" : > >> On Mon, Nov 28, 2016 at 5:59 PM, Icenowy Zheng wrote: > >>> As there's

Re: [linux-sunxi] Re: [RFC PATCH] ARM: dts: sun8i: add simplefb node for H3

On Mon, Nov 28, 2016 at 06:24:24PM +0800, Chen-Yu Tsai wrote: > On Mon, Nov 28, 2016 at 6:19 PM, Icenowy Zheng wrote: > > > > > > 28.11.2016, 18:07, "Chen-Yu Tsai" : > >> On Mon, Nov 28, 2016 at 5:59 PM, Icenowy Zheng wrote: > >>> As there's currently a fork of U-Boot which provides simplefb

[PATCH] mpt3sas: Recognize and act on iopriority info

From: Adam Manzanares This patch adds support for request iopriority handling in the mpt3sas layer. This works only when a ATA device is behind the SATL. The ATA device also has to indicate that it supports command priorities in the identify information that is pulled

Re: [v6,1/2] i2c: qup: add ACPI support

On Tue, Oct 11, 2016 at 10:27:56AM -0600, Austin Christ wrote: > From: Naveen Kaje > > Add support to get the device parameters from ACPI. Assume > that the clocks are managed by firmware. > > Signed-off-by: Naveen Kaje > Signed-off-by: Austin Christ

[PATCH] mpt3sas: Recognize and act on iopriority info

From: Adam Manzanares This patch adds support for request iopriority handling in the mpt3sas layer. This works only when a ATA device is behind the SATL. The ATA device also has to indicate that it supports command priorities in the identify information that is pulled from the SATL. This patch

Re: [v6,1/2] i2c: qup: add ACPI support

On Tue, Oct 11, 2016 at 10:27:56AM -0600, Austin Christ wrote: > From: Naveen Kaje > > Add support to get the device parameters from ACPI. Assume > that the clocks are managed by firmware. > > Signed-off-by: Naveen Kaje > Signed-off-by: Austin Christ > Reviewed-by: Sricharan R Applied to

Re: [v6,2/2] i2c: qup: support SMBus block read

On Tue, Oct 11, 2016 at 10:27:57AM -0600, Austin Christ wrote: > From: Naveen Kaje > > I2C QUP driver relies on SMBus emulation support from the framework. > To handle SMBus block reads, the driver should check I2C_M_RECV_LEN > flag and should read the first byte received

Re: [v6,2/2] i2c: qup: support SMBus block read

On Tue, Oct 11, 2016 at 10:27:57AM -0600, Austin Christ wrote: > From: Naveen Kaje > > I2C QUP driver relies on SMBus emulation support from the framework. > To handle SMBus block reads, the driver should check I2C_M_RECV_LEN > flag and should read the first byte received as the message length.

Re: [PATCH v11 0/8] powerpc: Implement kexec_file_load()

On Tue, 29 Nov 2016 23:45:46 +1100 Michael Ellerman wrote: > This is v11 of the kexec_file_load() for powerpc series. > > I've stripped this down to the minimum we need, so we can get this in for > 4.10. > Any additions can come later incrementally. This made a bit of a

Re: [PATCH v11 0/8] powerpc: Implement kexec_file_load()

On Tue, 29 Nov 2016 23:45:46 +1100 Michael Ellerman wrote: > This is v11 of the kexec_file_load() for powerpc series. > > I've stripped this down to the minimum we need, so we can get this in for > 4.10. > Any additions can come later incrementally. This made a bit of a mess of Mimi's series

Re: [PATCH v2 1/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver

On Tue, Nov 29, 2016 at 10:24:12PM +0100, Greg KH wrote: > On Wed, Nov 30, 2016 at 12:16:25AM +0300, Serge Semin wrote: > > On Tue, Nov 29, 2016 at 08:37:50PM +0100, Greg KH > > wrote: > > > On Tue, Nov 29, 2016 at 01:38:20AM +0300, Serge

Re: [PATCH v2 1/2] eeprom: Add IDT 89HPESx EEPROM/CSR driver

On Tue, Nov 29, 2016 at 10:24:12PM +0100, Greg KH wrote: > On Wed, Nov 30, 2016 at 12:16:25AM +0300, Serge Semin wrote: > > On Tue, Nov 29, 2016 at 08:37:50PM +0100, Greg KH > > wrote: > > > On Tue, Nov 29, 2016 at 01:38:20AM +0300, Serge Semin wrote: > > > > +struct idt_89hpesx_dev { > > > >

RE: [char-msic 2/3] mei: me: fix place for kaby point device ids.

> > On Tue, Nov 29, 2016 at 08:24:08PM +, Winkler, Tomas wrote: > > > > > > > > On Tue, Nov 29, 2016 at 02:44:45PM +0200, Tomas Winkler wrote: > > > > > This is fix of the backported patch only, it places KBL DIDs on > > > > > correct place to easy on backporting of further DIDs. > > > > > >

RE: [char-msic 2/3] mei: me: fix place for kaby point device ids.

> > On Tue, Nov 29, 2016 at 08:24:08PM +, Winkler, Tomas wrote: > > > > > > > > On Tue, Nov 29, 2016 at 02:44:45PM +0200, Tomas Winkler wrote: > > > > > This is fix of the backported patch only, it places KBL DIDs on > > > > > correct place to easy on backporting of further DIDs. > > > > > >

[tip:x86/timers 8/13] arch/x86/kernel/tsc_sync.c:34: warning: unused variable 'ref'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/timers head: cc4db26899dcd0e6ff0448c77abd8eb61b1a1333 commit: 8b223bc7abe0e30e8d297a24ee6c6c07ef8d0bb9 [8/13] x86/tsc: Store and check TSC ADJUST MSR config: x86_64-randconfig-a0-11300349 (attached as .config) compiler:

[tip:x86/timers 8/13] arch/x86/kernel/tsc_sync.c:34: warning: unused variable 'ref'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/timers head: cc4db26899dcd0e6ff0448c77abd8eb61b1a1333 commit: 8b223bc7abe0e30e8d297a24ee6c6c07ef8d0bb9 [8/13] x86/tsc: Store and check TSC ADJUST MSR config: x86_64-randconfig-a0-11300349 (attached as .config) compiler:

Re: [RFD] Common userspace tool for fscypto

Hi Richard, I'm Joe Richey, and I work on Mike's team. We've been playing around with a few design ideas regarding a tool for managing filesystem encryption. After going though some iterations with Ted, we have a fairly good idea about where to head design wise, and I'm working on a design

Re: [RFD] Common userspace tool for fscypto

Hi Richard, I'm Joe Richey, and I work on Mike's team. We've been playing around with a few design ideas regarding a tool for managing filesystem encryption. After going though some iterations with Ted, we have a fairly good idea about where to head design wise, and I'm working on a design

RE: [char-msic 1/3] mei: me: disable driver on SPT SPS firmware

> > On Tue, Nov 29, 2016 at 07:21:43PM +, Winkler, Tomas wrote: > > > > > > On Tue, Nov 29, 2016 at 02:44:44PM +0200, Tomas Winkler wrote: > > > > commit 8c57cac1457f3125a5d13dc03635c0708c61bff0 upstream > > > > > > > > Sunrise Point PCH with SPS Firmware doesn't expose working MEI > > > >

RE: [char-msic 1/3] mei: me: disable driver on SPT SPS firmware

> > On Tue, Nov 29, 2016 at 07:21:43PM +, Winkler, Tomas wrote: > > > > > > On Tue, Nov 29, 2016 at 02:44:44PM +0200, Tomas Winkler wrote: > > > > commit 8c57cac1457f3125a5d13dc03635c0708c61bff0 upstream > > > > > > > > Sunrise Point PCH with SPS Firmware doesn't expose working MEI > > > >

[PATCH v2] PCI: Add information about describing PCI in ACPI

Add a writeup about how PCI host bridges should be described in ACPI using PNP0A03/PNP0A08 devices, PNP0C02 devices, and the MCFG table. Signed-off-by: Bjorn Helgaas --- Documentation/PCI/00-INDEX |2 Documentation/PCI/acpi-info.txt | 180

[PATCH v2] PCI: Add information about describing PCI in ACPI

Add a writeup about how PCI host bridges should be described in ACPI using PNP0A03/PNP0A08 devices, PNP0C02 devices, and the MCFG table. Signed-off-by: Bjorn Helgaas --- Documentation/PCI/00-INDEX |2 Documentation/PCI/acpi-info.txt | 180 +++ 2

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