Re: [PATCH v5 3/7] phy: Add set_mode callback

Hi, On Tuesday 10 May 2016 05:09 AM, David Lechner wrote: > The initial use for this is for PHYs that have a mode related to USB OTG. > There are several SoCs (e.g. TI OMAP and DA8xx) that have a mode setting > in the USB PHY to override OTG VBUS and ID signals. > > Of course, the enum can be

Re: [PATCH v5 3/7] phy: Add set_mode callback

Hi, On Tuesday 10 May 2016 05:09 AM, David Lechner wrote: > The initial use for this is for PHYs that have a mode related to USB OTG. > There are several SoCs (e.g. TI OMAP and DA8xx) that have a mode setting > in the USB PHY to override OTG VBUS and ID signals. > > Of course, the enum can be

Re: [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

On Wed, 22 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 11:12:54PM +0200, Julia Lawall wrote: > > On Tue, 21 Jun 2016, Nicolas Palix (LIG) wrote: > > > > > Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : > > > > Help Coccinelle when used against Linux with a set of sensible

Re: [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

On Wed, 22 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 11:12:54PM +0200, Julia Lawall wrote: > > On Tue, 21 Jun 2016, Nicolas Palix (LIG) wrote: > > > > > Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : > > > > Help Coccinelle when used against Linux with a set of sensible

Re: [PATCH 4/5] mfd: qcom-rpm: Add support for pm8018 RPM Regulator

On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: [..] > diff --git a/drivers/mfd/qcom_rpm.c b/drivers/mfd/qcom_rpm.c [..] > + > +static const struct qcom_rpm_data mdm9615_template = { > + .version = 3, > + .resource_table = mdm9615_rpm_resource_table, > + .n_resources =

Re: [PATCH 4/5] mfd: qcom-rpm: Add support for pm8018 RPM Regulator

On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: [..] > diff --git a/drivers/mfd/qcom_rpm.c b/drivers/mfd/qcom_rpm.c [..] > + > +static const struct qcom_rpm_data mdm9615_template = { > + .version = 3, > + .resource_table = mdm9615_rpm_resource_table, > + .n_resources =

Re: [PATCH v8 2/3] CMDQ: Mediatek CMDQ driver

On Tue, 2016-06-21 at 15:41 +0200, Matthias Brugger wrote: > > On 21/06/16 07:52, Horng-Shyang Liao wrote: > > On Fri, 2016-06-17 at 17:57 +0200, Matthias Brugger wrote: > >> > >> On 17/06/16 10:28, Horng-Shyang Liao wrote: > >>> Hi Matthias, > >>> > >>> On Tue, 2016-06-14 at 20:07 +0800,

linux-next: Tree for Jun 22

Hi all, Changes since 20160621: The drm-intel tree gained a conflict against the drm-intel-fixes tree. The drm-misc tree gained a conflict against the arm tree. The akpm-current tree gained conflicts against the arm64 and kspp trees. Non-merge commits (relative to Linus' tree): 4878 4742

Re: [PATCH v8 2/3] CMDQ: Mediatek CMDQ driver

On Tue, 2016-06-21 at 15:41 +0200, Matthias Brugger wrote: > > On 21/06/16 07:52, Horng-Shyang Liao wrote: > > On Fri, 2016-06-17 at 17:57 +0200, Matthias Brugger wrote: > >> > >> On 17/06/16 10:28, Horng-Shyang Liao wrote: > >>> Hi Matthias, > >>> > >>> On Tue, 2016-06-14 at 20:07 +0800,

linux-next: Tree for Jun 22

Hi all, Changes since 20160621: The drm-intel tree gained a conflict against the drm-intel-fixes tree. The drm-misc tree gained a conflict against the arm tree. The akpm-current tree gained conflicts against the arm64 and kspp trees. Non-merge commits (relative to Linus' tree): 4878 4742

Re: [PATCH kernfs/for-4.7-fixes] kernfs: don't depend on d_find_any_alias() when generating notifications

On Tue, Jun 21, 2016 at 11:24:47AM -0400, Tejun Heo wrote: > On Fri, Jun 17, 2016 at 05:51:17PM -0400, Tejun Heo wrote: > > kernfs_notify_workfn() sends out file modified events for the > > scheduled kernfs_nodes. Because the modifications aren't from > > userland, it doesn't have the matching

Re: [PATCH kernfs/for-4.7-fixes] kernfs: don't depend on d_find_any_alias() when generating notifications

On Tue, Jun 21, 2016 at 11:24:47AM -0400, Tejun Heo wrote: > On Fri, Jun 17, 2016 at 05:51:17PM -0400, Tejun Heo wrote: > > kernfs_notify_workfn() sends out file modified events for the > > scheduled kernfs_nodes. Because the modifications aren't from > > userland, it doesn't have the matching

Re: [PATCH v4 5/5] ARM: dts: mt2701: add iommu/smi dtsi node for mt2701

On Tue, 2016-06-21 at 17:57 +0800, Joerg Roedel wrote: > On Wed, Jun 08, 2016 at 05:51:01PM +0800, honghui.zh...@mediatek.com wrote: > > From: Honghui Zhang > > > > Add the dtsi node of iommu and smi for mt2701. > > > > Signed-off-by: Honghui Zhang

Re: [PATCH v4 5/5] ARM: dts: mt2701: add iommu/smi dtsi node for mt2701

On Tue, 2016-06-21 at 17:57 +0800, Joerg Roedel wrote: > On Wed, Jun 08, 2016 at 05:51:01PM +0800, honghui.zh...@mediatek.com wrote: > > From: Honghui Zhang > > > > Add the dtsi node of iommu and smi for mt2701. > > > > Signed-off-by: Honghui Zhang > > --- > > arch/arm/boot/dts/mt2701.dtsi |

[PATCH] ocfs2: disable BUG assertions in reading blocks

According to some high-load testing, these two BUG assertions were encountered, this led system panic. Actually, there were some discussions about removing these two BUG() assertions, it would not bring any side effect. Then, I did the the following changes, 1) use the existing macro

[PATCH] ocfs2: disable BUG assertions in reading blocks

According to some high-load testing, these two BUG assertions were encountered, this led system panic. Actually, there were some discussions about removing these two BUG() assertions, it would not bring any side effect. Then, I did the the following changes, 1) use the existing macro

Re: [PATCH 2/5] input: pmic8xxx-pwrkey: Add support for pm8018 pwrkey

On Tue, Jun 21, 2016 at 10:25 PM, Bjorn Andersson wrote: > On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: > >> In order to support pwrkey for Qualcomm MDM9615 SoC, add support >> for the pm8018 pwrkey in pmic8xxx-pwrkey. >> >> Signed-off-by: Neil Armstrong

Re: [PATCH 2/5] input: pmic8xxx-pwrkey: Add support for pm8018 pwrkey

On Tue, Jun 21, 2016 at 10:25 PM, Bjorn Andersson wrote: > On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: > >> In order to support pwrkey for Qualcomm MDM9615 SoC, add support >> for the pm8018 pwrkey in pmic8xxx-pwrkey. >> >> Signed-off-by: Neil Armstrong > > Reviewed-by: Bjorn Andersson

[PATCH] hfs: Change structure initialisation to C99 style

To allow for structure randomisation, replace the in order struct initialisation style with explicit field style. Also, remove an unnecessary initialisation since NULL values do not need to be explicitly initialised. The Coccinelle semantic patch used to make this change is as follows: @decl@

[PATCH] hfs: Change structure initialisation to C99 style

To allow for structure randomisation, replace the in order struct initialisation style with explicit field style. Also, remove an unnecessary initialisation since NULL values do not need to be explicitly initialised. The Coccinelle semantic patch used to make this change is as follows: @decl@

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Tue, 2016-06-21 at 14:28 +0530, Naveen N. Rao wrote: > On 2016/06/20 03:56PM, Thadeu Lima de Souza Cascardo wrote: > > On Sun, Jun 19, 2016 at 11:19:14PM +0530, Naveen N. Rao wrote: > > > On 2016/06/17 10:00AM, Thadeu Lima de Souza Cascardo wrote: > > > > > > > > Hi, Michael and Naveen. > > >

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Tue, 2016-06-21 at 14:28 +0530, Naveen N. Rao wrote: > On 2016/06/20 03:56PM, Thadeu Lima de Souza Cascardo wrote: > > On Sun, Jun 19, 2016 at 11:19:14PM +0530, Naveen N. Rao wrote: > > > On 2016/06/17 10:00AM, Thadeu Lima de Souza Cascardo wrote: > > > > > > > > Hi, Michael and Naveen. > > >

Re: [PATCH] ARM: AM33xx: PRM: Remove wrongly defined RSTST offset for PER Domain

On Wednesday 22 June 2016 03:55 AM, Suman Anna wrote: Hi Keerthy, On 06/21/2016 05:08 AM, Keerthy wrote: As per the TRM: http://www.ti.com/lit/ug/spruh73m/spruh73m.pdf offset 0x4 is reserved for PRM_PER. Hence removing the wrongly defined address offset. Thanks for the patch. These macros

Re: [PATCH] ARM: AM33xx: PRM: Remove wrongly defined RSTST offset for PER Domain

On Wednesday 22 June 2016 03:55 AM, Suman Anna wrote: Hi Keerthy, On 06/21/2016 05:08 AM, Keerthy wrote: As per the TRM: http://www.ti.com/lit/ug/spruh73m/spruh73m.pdf offset 0x4 is reserved for PRM_PER. Hence removing the wrongly defined address offset. Thanks for the patch. These macros

linux-next: build warnings after merge of the kspp tree

Hi Kees, After merging the kspp tree, today's linux-next build (i386 defconfig) produced these warning: x86_64-linux-gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead (over 2000 of these) Introduced (maybe) by commit e2135c84d5d2 ("kbuild: no gcc-plugins during

linux-next: build warnings after merge of the kspp tree

Hi Kees, After merging the kspp tree, today's linux-next build (i386 defconfig) produced these warning: x86_64-linux-gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead (over 2000 of these) Introduced (maybe) by commit e2135c84d5d2 ("kbuild: no gcc-plugins during

Re: [PATCH 2/5] input: pmic8xxx-pwrkey: Add support for pm8018 pwrkey

On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: > In order to support pwrkey for Qualcomm MDM9615 SoC, add support > for the pm8018 pwrkey in pmic8xxx-pwrkey. > > Signed-off-by: Neil Armstrong Reviewed-by: Bjorn Andersson Regards,

linux-next: manual merge of the akpm-current tree with the kspp tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: mm/page_alloc.c between commit: 0df42965deb7 ("latent_entropy: Add the extra_latent_entropy kernel parameter") from the kspp tree and commit: 6f4f5445297d ("mm: charge/uncharge kmemcg from generic page

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Wed, 22 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 11:44:09PM +0200, Julia Lawall wrote: > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > On Tue, Jun 21, 2016 at 11:32:11PM +0200, Julia Lawall wrote: > > > > > > > > > > > > On Tue, 21 Jun 2016, Luis

Re: [PATCH 2/5] input: pmic8xxx-pwrkey: Add support for pm8018 pwrkey

On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: > In order to support pwrkey for Qualcomm MDM9615 SoC, add support > for the pm8018 pwrkey in pmic8xxx-pwrkey. > > Signed-off-by: Neil Armstrong Reviewed-by: Bjorn Andersson Regards, Bjorn

linux-next: manual merge of the akpm-current tree with the kspp tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: mm/page_alloc.c between commit: 0df42965deb7 ("latent_entropy: Add the extra_latent_entropy kernel parameter") from the kspp tree and commit: 6f4f5445297d ("mm: charge/uncharge kmemcg from generic page

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Wed, 22 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 11:44:09PM +0200, Julia Lawall wrote: > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > On Tue, Jun 21, 2016 at 11:32:11PM +0200, Julia Lawall wrote: > > > > > > > > > > > > On Tue, 21 Jun 2016, Luis

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Fri, 2016-06-17 at 10:00 -0300, Thadeu Lima de Souza Cascardo wrote: > From a984dc02b6317a1d3a3c2302385adba5227be5bd Mon Sep 17 00:00:00 2001 > From: Thadeu Lima de Souza Cascardo > Date: Wed, 15 Jun 2016 13:22:12 -0300 > Subject: [PATCH] ppc: Fix BPF JIT for ABIv2 > >

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Fri, 2016-06-17 at 10:00 -0300, Thadeu Lima de Souza Cascardo wrote: > From a984dc02b6317a1d3a3c2302385adba5227be5bd Mon Sep 17 00:00:00 2001 > From: Thadeu Lima de Souza Cascardo > Date: Wed, 15 Jun 2016 13:22:12 -0300 > Subject: [PATCH] ppc: Fix BPF JIT for ABIv2 > > ABIv2 used for ppc64le

Re: [PATCH 3/5] rtc: rtc-pm8xxx: Add support for pm8018 rtc

On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: > In order to support RTC on Qualcomm MDM9615 SoC, add support for > the pm8018 rtc in rtc-pm8xxx driver. > > Signed-off-by: Neil Armstrong > --- > Documentation/devicetree/bindings/mfd/qcom-pm8xxx.txt | 1 + >

Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE

On Tue, Jun 21, 2016 at 09:47:19PM +0200, Peter Zijlstra wrote: > On Tue, Jun 21, 2016 at 03:43:56PM -0400, Tejun Heo wrote: > > On Tue, Jun 21, 2016 at 09:37:09PM +0200, Peter Zijlstra wrote: > > > Hurm.. So I've applied it, just to get this issue sorted, but I'm not > > > entirely sure I like

Re: [PATCH v4 0/5] /dev/random - a new approach

Am Dienstag, 21. Juni 2016, 15:31:07 schrieb Austin S. Hemmelgarn: Hi Austin, > > Little data, interesting statement for results on 200+ systems including > > all major CPU arches all showing information leading in the same > > directions. > Let me try rephrasing this to make it a bit clearer: >

Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE

On Tue, Jun 21, 2016 at 09:47:19PM +0200, Peter Zijlstra wrote: > On Tue, Jun 21, 2016 at 03:43:56PM -0400, Tejun Heo wrote: > > On Tue, Jun 21, 2016 at 09:37:09PM +0200, Peter Zijlstra wrote: > > > Hurm.. So I've applied it, just to get this issue sorted, but I'm not > > > entirely sure I like

Re: [PATCH v4 0/5] /dev/random - a new approach

Am Dienstag, 21. Juni 2016, 15:31:07 schrieb Austin S. Hemmelgarn: Hi Austin, > > Little data, interesting statement for results on 200+ systems including > > all major CPU arches all showing information leading in the same > > directions. > Let me try rephrasing this to make it a bit clearer: >

Re: [PATCH 3/5] rtc: rtc-pm8xxx: Add support for pm8018 rtc

On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: > In order to support RTC on Qualcomm MDM9615 SoC, add support for > the pm8018 rtc in rtc-pm8xxx driver. > > Signed-off-by: Neil Armstrong > --- > Documentation/devicetree/bindings/mfd/qcom-pm8xxx.txt | 1 + > drivers/rtc/rtc-pm8xxx.c

[PATCHv2 1/1] thermal: core: call thermal_zone_device_update() after mode update

Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal core, after setting the new mode. Also, this patch also remove deadlocks on drivers that

[PATCHv2 1/1] thermal: core: call thermal_zone_device_update() after mode update

Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal core, after setting the new mode. Also, this patch also remove deadlocks on drivers that

Re: [PATCH] torture: use ktime_t consistently

On Wed, Jun 22, 2016 at 10:00:24AM +0800, Boqun Feng wrote: > Hi Paul, > > On Tue, Jun 21, 2016 at 11:39:46AM -0700, Paul E. McKenney wrote: > > On Mon, Jun 20, 2016 at 09:29:56PM +0200, Arnd Bergmann wrote: > > > On Monday, June 20, 2016 11:37:57 AM CEST Paul E. McKenney wrote: > > > > On Mon,

Re: [PATCH] torture: use ktime_t consistently

On Wed, Jun 22, 2016 at 10:00:24AM +0800, Boqun Feng wrote: > Hi Paul, > > On Tue, Jun 21, 2016 at 11:39:46AM -0700, Paul E. McKenney wrote: > > On Mon, Jun 20, 2016 at 09:29:56PM +0200, Arnd Bergmann wrote: > > > On Monday, June 20, 2016 11:37:57 AM CEST Paul E. McKenney wrote: > > > > On Mon,

Re: [PATCH v6 07/11] powerpc/powernv: set power_save func after the idle states are initialized

On Wed, 2016-06-22 at 11:54 +1000, Benjamin Herrenschmidt wrote: > On Wed, 2016-06-08 at 11:54 -0500, Shreyas B. Prabhu wrote: > > > > pnv_init_idle_states discovers supported idle states from the > > device tree and does the required initialization. Set power_save > > function pointer only after

Re: [PATCH v6 07/11] powerpc/powernv: set power_save func after the idle states are initialized

On Wed, 2016-06-22 at 11:54 +1000, Benjamin Herrenschmidt wrote: > On Wed, 2016-06-08 at 11:54 -0500, Shreyas B. Prabhu wrote: > > > > pnv_init_idle_states discovers supported idle states from the > > device tree and does the required initialization. Set power_save > > function pointer only after

[PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal core, after setting the new mode. Also, this patch also remove deadlocks on drivers that

[PATCH 1/1] thermal: core: call thermal_zone_device_update() after mode update

Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal core, after setting the new mode. Also, this patch also remove deadlocks on drivers that

Re: [PATCH 1/5] mfd: pm8921: Add support for pm8018

On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: > In order to support the Qualcomm MDM9615 PMIC, add support for the > pm8018 in pm8921 mfd driver. > > Signed-off-by: Neil Armstrong Reviewed-by: Bjorn Andersson Regards, Bjorn

Re: [PATCH 1/5] mfd: pm8921: Add support for pm8018

On Fri 17 Jun 03:22 PDT 2016, Neil Armstrong wrote: > In order to support the Qualcomm MDM9615 PMIC, add support for the > pm8018 in pm8921 mfd driver. > > Signed-off-by: Neil Armstrong Reviewed-by: Bjorn Andersson Regards, Bjorn

Re: [PATCH v2 0/2] Correct iTCO Watchdog for Apollo Lake

On 06/17/2016 08:36, Yong, Jonathan wrote: These patches fix the iTCO watchdog for Apollo Lake. I changed the watchdog memory io to only use 4 bytes rather the whole region, I'm not sure if that is the correct way. The previous 0x30h offset in intel_pmc_ipc.c was for based on the earlier BXT-M

Re: [PATCH v2 0/2] Correct iTCO Watchdog for Apollo Lake

On 06/17/2016 08:36, Yong, Jonathan wrote: These patches fix the iTCO watchdog for Apollo Lake. I changed the watchdog memory io to only use 4 bytes rather the whole region, I'm not sure if that is the correct way. The previous 0x30h offset in intel_pmc_ipc.c was for based on the earlier BXT-M

Re: [PATCH v10 06/22] IB/hns: Add initial cmd operation

On Tue, Jun 21, 2016 at 09:01:57PM +0800, Wei Hu (Xavier) wrote: > > > On 2016/6/21 19:28, Leon Romanovsky wrote: > >On Tue, Jun 21, 2016 at 06:50:51PM +0800, Wei Hu (Xavier) wrote: > >> > >>On 2016/6/20 21:33, Leon Romanovsky wrote: > >>>On Thu, Jun 16, 2016 at 10:35:14PM +0800, Lijun Ou wrote:

Re: [PATCH v10 06/22] IB/hns: Add initial cmd operation

On Tue, Jun 21, 2016 at 09:01:57PM +0800, Wei Hu (Xavier) wrote: > > > On 2016/6/21 19:28, Leon Romanovsky wrote: > >On Tue, Jun 21, 2016 at 06:50:51PM +0800, Wei Hu (Xavier) wrote: > >> > >>On 2016/6/20 21:33, Leon Romanovsky wrote: > >>>On Thu, Jun 16, 2016 at 10:35:14PM +0800, Lijun Ou wrote:

linux-next: manual merge of the akpm-current tree with the arm64 tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: arch/arm64/mm/dma-mapping.c between commit: b67a8b29df7e ("arm64: mm: only initialize swiotlb when necessary") from the arm64 tree and commit: 29af59a63ef1 ("arm64: dma-mapping: constify attrs passed to

linux-next: manual merge of the akpm-current tree with the arm64 tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: arch/arm64/mm/dma-mapping.c between commit: b67a8b29df7e ("arm64: mm: only initialize swiotlb when necessary") from the arm64 tree and commit: 29af59a63ef1 ("arm64: dma-mapping: constify attrs passed to

Re: [PATCH v2 1/8] arm64: dts: db820c: add basic board support

On Tue 21 Jun 10:22 PDT 2016, Srinivas Kandagatla wrote: [..] > diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dts > b/arch/arm64/boot/dts/qcom/apq8096-db820c.dts [..] > + > +/ { > + model = "Qualcomm Technologies, Inc. DB820c"; > + compatible = "qcom,apq8096-sbc"; I'm still not

Re: [PATCH v2 1/8] arm64: dts: db820c: add basic board support

On Tue 21 Jun 10:22 PDT 2016, Srinivas Kandagatla wrote: [..] > diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dts > b/arch/arm64/boot/dts/qcom/apq8096-db820c.dts [..] > + > +/ { > + model = "Qualcomm Technologies, Inc. DB820c"; > + compatible = "qcom,apq8096-sbc"; I'm still not

Re: [PATCH 3/3] staging: lowmemorykiller: select the task with maximum rss to kill

Hi, David: On Tue, Jun 21, 2016 at 01:14:36PM -0700, David Rientjes wrote: > On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > > > Current task selecting logic in LMK does not fully aware of the memory > > pressure. It may select the task with maximum score adj, but with > > least tasksize. > > >

Re: [PATCH 3/3] staging: lowmemorykiller: select the task with maximum rss to kill

Hi, David: On Tue, Jun 21, 2016 at 01:14:36PM -0700, David Rientjes wrote: > On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > > > Current task selecting logic in LMK does not fully aware of the memory > > pressure. It may select the task with maximum score adj, but with > > least tasksize. > > >

Re: [PATCH v13 01/16] PCI: Let pci_mmap_page_range() take resource address

On Sat, Jun 18, 2016 at 5:17 AM, Bjorn Helgaas wrote: > On Fri, Jun 17, 2016 at 07:24:46PM -0700, Yinghai Lu wrote: >> In 8c05cd08a7 ("PCI: fix offset check for sysfs mmapped files"), try >> to check exposed value with resource start/end in proc mmap path. >> >> |start

Re: [PATCH v13 01/16] PCI: Let pci_mmap_page_range() take resource address

On Sat, Jun 18, 2016 at 5:17 AM, Bjorn Helgaas wrote: > On Fri, Jun 17, 2016 at 07:24:46PM -0700, Yinghai Lu wrote: >> In 8c05cd08a7 ("PCI: fix offset check for sysfs mmapped files"), try >> to check exposed value with resource start/end in proc mmap path. >> >> |start = vma->vm_pgoff; >>

Re: [RFC PATCH v2 1/9] mailbox: Add Amlogic Meson Message-Handling-Unit

On Tue, Jun 21, 2016 at 3:32 PM, Neil Armstrong wrote: > Add Amlogic Meson SoCs Message-Handling-Unit as mailbox controller > with 2 independent channels/links to communicate with a remote processor. > > Signed-off-by: Neil Armstrong . >

Re: [RFC PATCH v2 1/9] mailbox: Add Amlogic Meson Message-Handling-Unit

On Tue, Jun 21, 2016 at 3:32 PM, Neil Armstrong wrote: > Add Amlogic Meson SoCs Message-Handling-Unit as mailbox controller > with 2 independent channels/links to communicate with a remote processor. > > Signed-off-by: Neil Armstrong . > +++ b/drivers/mailbox/meson_mhu.c > @@ -0,0 +1,199

Re: [PATCH v2 6/6] x86: Fix thread_saved_pc()

On Mon, Jun 20, 2016 at 12:01 PM, Josh Poimboeuf wrote: > On Sat, Jun 18, 2016 at 04:56:18PM -0400, Brian Gerst wrote: >> thread_saved_pc() was using a completely bogus method to get the return >> address. Since switch_to() was previously inlined, there was no sane way >> to

Re: [PATCH v2 6/6] x86: Fix thread_saved_pc()

On Mon, Jun 20, 2016 at 12:01 PM, Josh Poimboeuf wrote: > On Sat, Jun 18, 2016 at 04:56:18PM -0400, Brian Gerst wrote: >> thread_saved_pc() was using a completely bogus method to get the return >> address. Since switch_to() was previously inlined, there was no sane way >> to know where on the

Re: [PATCH v3 2/8] mfd: ac100: Add device tree bindings for X-Powers AC100 codec/RTC combo IC

On Tue, Jun 21, 2016 at 9:14 PM, Rob Herring wrote: > On Mon, Jun 20, 2016 at 10:52:12AM +0800, Chen-Yu Tsai wrote: >> Signed-off-by: Chen-Yu Tsai >> --- >> Changes since v2: >> >> - Fix interrupt line for ac100_codec in provided example. >> >> --- >>

Re: [PATCH v3 2/8] mfd: ac100: Add device tree bindings for X-Powers AC100 codec/RTC combo IC

On Tue, Jun 21, 2016 at 9:14 PM, Rob Herring wrote: > On Mon, Jun 20, 2016 at 10:52:12AM +0800, Chen-Yu Tsai wrote: >> Signed-off-by: Chen-Yu Tsai >> --- >> Changes since v2: >> >> - Fix interrupt line for ac100_codec in provided example. >> >> --- >>

Re: [PATCH 2/3] staging: lowmemorykiller: count anon pages only when we have swap devices

Hi, David: On Tue, Jun 21, 2016 at 01:22:00PM -0700, David Rientjes wrote: > On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > > > lowmem_count() should only count anon pages when we have swap device. > > > > Why? I make a mistake. I thought lowmem_count will return the shrinkalbe page of a

Re: [PATCH 2/3] staging: lowmemorykiller: count anon pages only when we have swap devices

Hi, David: On Tue, Jun 21, 2016 at 01:22:00PM -0700, David Rientjes wrote: > On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > > > lowmem_count() should only count anon pages when we have swap device. > > > > Why? I make a mistake. I thought lowmem_count will return the shrinkalbe page of a

Re: [PATCH v8 3/8] perf tests: Add testcase for auxiliary evlist

On 2016/6/22 5:05, Arnaldo Carvalho de Melo wrote: Em Mon, Jun 20, 2016 at 10:47:20AM +, Wang Nan escreveu: Improve test backward [SNIP] diff --git a/tools/perf/tests/backward-ring-buffer.c b/tools/perf/tests/backward-ring-buffer.c index d9ba991..76e34c0 100644 ---

Re: [PATCH] xen/pciback: Fix conf_space read/write overlap check.

On 21/06/16 17:52, Boris Ostrovsky wrote: > On 06/21/2016 10:37 AM, Andrey Grodzovsky wrote: >> Current overlap check is evaluating to false a case where a filter field >> is fully contained (proper subset) of a r/w request. >> This change applies classical overlap check instead to include >> all

Re: [PATCH v8 3/8] perf tests: Add testcase for auxiliary evlist

On 2016/6/22 5:05, Arnaldo Carvalho de Melo wrote: Em Mon, Jun 20, 2016 at 10:47:20AM +, Wang Nan escreveu: Improve test backward [SNIP] diff --git a/tools/perf/tests/backward-ring-buffer.c b/tools/perf/tests/backward-ring-buffer.c index d9ba991..76e34c0 100644 ---

Re: [PATCH] xen/pciback: Fix conf_space read/write overlap check.

On 21/06/16 17:52, Boris Ostrovsky wrote: > On 06/21/2016 10:37 AM, Andrey Grodzovsky wrote: >> Current overlap check is evaluating to false a case where a filter field >> is fully contained (proper subset) of a r/w request. >> This change applies classical overlap check instead to include >> all

Re: [PATCH 1/3] staging: lowmemorykiller: change lowmem_adj to lowmem_score_adj

Hi, David: On Tue, Jun 21, 2016 at 01:27:40PM -0700, David Rientjes wrote: > On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > > > om_adj is deprecated, and in lowmemorykiller module, we use score adj > > to do the comparing. > > --- > > oom_score_adj = p->signal->oom_score_adj; > >

Re: [PATCH 1/3] staging: lowmemorykiller: change lowmem_adj to lowmem_score_adj

Hi, David: On Tue, Jun 21, 2016 at 01:27:40PM -0700, David Rientjes wrote: > On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > > > om_adj is deprecated, and in lowmemorykiller module, we use score adj > > to do the comparing. > > --- > > oom_score_adj = p->signal->oom_score_adj; > >

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Tue, 2016-06-21 at 08:45 -0700, Alexei Starovoitov wrote: > On 6/21/16 7:47 AM, Thadeu Lima de Souza Cascardo wrote: > > > > > > > > The calling convention is different with ABIv2 and so we'll need changes > > > > in bpf_slow_path_common() and sk_negative_common(). > > > > > > How big would

Re: [PATCH] ppc: Fix BPF JIT for ABIv2

On Tue, 2016-06-21 at 08:45 -0700, Alexei Starovoitov wrote: > On 6/21/16 7:47 AM, Thadeu Lima de Souza Cascardo wrote: > > > > > > > > The calling convention is different with ABIv2 and so we'll need changes > > > > in bpf_slow_path_common() and sk_negative_common(). > > > > > > How big would

Re: Reported regressions for 4.7 as of Sunday, 2016-06-19

Investigating. Regards, Quinn Tran -Original Message- From: "Martin K. Petersen" Organization: Oracle Corporation Date: Tuesday, June 21, 2016 at 6:25 PM To: Linus Torvalds Cc: Josh Boyer ,

Re: Reported regressions for 4.7 as of Sunday, 2016-06-19

Investigating. Regards, Quinn Tran -Original Message- From: "Martin K. Petersen" Organization: Oracle Corporation Date: Tuesday, June 21, 2016 at 6:25 PM To: Linus Torvalds Cc: Josh Boyer , "Martin K. Petersen" , Johannes Thumshirn , Thorsten Leemhuis , linux-kernel , Quinn

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

On 6/22/2016 8:14 AM, Nicolas Boichat wrote: Hi Archit, Thanks for your reply. On Tue, Jun 21, 2016 at 11:39 PM, Archit Taneja wrote: Hi, On 6/20/2016 12:44 PM, Nicolas Boichat wrote: ANX7688 is a HDMI to DP converter (as well as USB-C port controller), that has

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

On 6/22/2016 8:14 AM, Nicolas Boichat wrote: Hi Archit, Thanks for your reply. On Tue, Jun 21, 2016 at 11:39 PM, Archit Taneja wrote: Hi, On 6/20/2016 12:44 PM, Nicolas Boichat wrote: ANX7688 is a HDMI to DP converter (as well as USB-C port controller), that has an internal

Re: [PATCH v10 08/22] IB/hns: Add icm support

On 2016/6/21 19:55, Leon Romanovsky wrote: On Tue, Jun 21, 2016 at 12:37:39PM +0800, Wei Hu (Xavier) wrote: On 2016/6/20 21:04, Leon Romanovsky wrote: On Mon, Jun 20, 2016 at 05:48:15PM +0800, Wei Hu (Xavier) wrote: On 2016/6/20 17:27, Leon Romanovsky wrote: On Mon, Jun 20, 2016 at

Re: [PATCH v10 08/22] IB/hns: Add icm support

On 2016/6/21 19:55, Leon Romanovsky wrote: On Tue, Jun 21, 2016 at 12:37:39PM +0800, Wei Hu (Xavier) wrote: On 2016/6/20 21:04, Leon Romanovsky wrote: On Mon, Jun 20, 2016 at 05:48:15PM +0800, Wei Hu (Xavier) wrote: On 2016/6/20 17:27, Leon Romanovsky wrote: On Mon, Jun 20, 2016 at

Re: [PATCH v3] tools/perf: Fix the mask in regs_dump__printf and print_sample_iregs

On Tuesday 21 June 2016 09:05 PM, Yury Norov wrote: > On Tue, Jun 21, 2016 at 08:26:40PM +0530, Madhavan Srinivasan wrote: >> When decoding the perf_regs mask in regs_dump__printf(), >> we loop through the mask using find_first_bit and find_next_bit functions. >> "mask" is of type "u64", but

Re: [PATCH v3] tools/perf: Fix the mask in regs_dump__printf and print_sample_iregs

On Tuesday 21 June 2016 09:05 PM, Yury Norov wrote: > On Tue, Jun 21, 2016 at 08:26:40PM +0530, Madhavan Srinivasan wrote: >> When decoding the perf_regs mask in regs_dump__printf(), >> we loop through the mask using find_first_bit and find_next_bit functions. >> "mask" is of type "u64", but

[PATCH V2 4/4] stm: Mark the functions of writing buffer with notrace

If CONFIG_STM_FTRACE is selected, Function trace data would be writen to STM buffer, all functions that related to writing data packets to STM buffer should be marked 'notrace' to avoid being traced by Ftrace, otherwise the program would stall into an endless loop. Signed-off-by: Chunyan Zhang

[PATCH V2 4/4] stm: Mark the functions of writing buffer with notrace

If CONFIG_STM_FTRACE is selected, Function trace data would be writen to STM buffer, all functions that related to writing data packets to STM buffer should be marked 'notrace' to avoid being traced by Ftrace, otherwise the program would stall into an endless loop. Signed-off-by: Chunyan Zhang

Re: [PATCH v11 08/14] usb: otg: add OTG/dual-role core

On Tue, Jun 21, 2016 at 05:47:47PM +0300, Felipe Balbi wrote: > > Hi, > > Peter Chen writes: > >> >> >> >> >>> + * @otg_dev: OTG controller device, if needs to be used with > >> >> >> >> >>> OTG core. > >> >> >> >> >> > >> >> >> >> >> do you really know of any platform

Re: [PATCH v11 08/14] usb: otg: add OTG/dual-role core

On Tue, Jun 21, 2016 at 05:47:47PM +0300, Felipe Balbi wrote: > > Hi, > > Peter Chen writes: > >> >> >> >> >>> + * @otg_dev: OTG controller device, if needs to be used with > >> >> >> >> >>> OTG core. > >> >> >> >> >> > >> >> >> >> >> do you really know of any platform which has a separate

[PATCH] dm: Check kthread_run's return value

kthread function is used to process kthread_work. And there is no return value checking during create this thread. Add this checking to fix this issue. Signed-off-by: Minfei Huang Signed-off-by: Minfei Huang --- drivers/md/dm.c | 11 +-- 1

[PATCH] dm: Check kthread_run's return value

kthread function is used to process kthread_work. And there is no return value checking during create this thread. Add this checking to fix this issue. Signed-off-by: Minfei Huang Signed-off-by: Minfei Huang --- drivers/md/dm.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-)

[PATCH v2] PCI/MSI: Simplify the return value of arch_setup_msi_irqs

No any callers do care whether arch_setup_msi_irqs returns -ENOSPC or other error numbers. That means they treat the negative numbers in the same way. So there shouldn't make any difference to directly return -ENOSPC if finding it's non-zero. Signed-off-by: Shawn Lin

[PATCH v2] PCI/MSI: Simplify the return value of arch_setup_msi_irqs

No any callers do care whether arch_setup_msi_irqs returns -ENOSPC or other error numbers. That means they treat the negative numbers in the same way. So there shouldn't make any difference to directly return -ENOSPC if finding it's non-zero. Signed-off-by: Shawn Lin --- Changes in v2: - fix

[RESEND PATCH v2 3/4] ARM: dts: rockchip: add GMAC nodes for RK322x SoCs

This patch add the GMAC dt nodes for rk322x SoCs. Signed-off-by: Xing Zheng --- Changes in v2: None arch/arm/boot/dts/rk322x.dtsi | 64 + 1 file changed, 64 insertions(+) diff --git a/arch/arm/boot/dts/rk322x.dtsi

[RESEND PATCH v2 3/4] ARM: dts: rockchip: add GMAC nodes for RK322x SoCs

This patch add the GMAC dt nodes for rk322x SoCs. Signed-off-by: Xing Zheng --- Changes in v2: None arch/arm/boot/dts/rk322x.dtsi | 64 + 1 file changed, 64 insertions(+) diff --git a/arch/arm/boot/dts/rk322x.dtsi b/arch/arm/boot/dts/rk322x.dtsi

[RESEND PATCH v2 4/4] ARM: dts: rockchip: add support rk3229 evb board

Initial release for rk3229 evb board, and turn the GMAC on. Signed-off-by: Xing Zheng --- Changes in v2: - rename rk3228.dtsi to rk322x.dtsi arch/arm/boot/dts/Makefile |1 + arch/arm/boot/dts/rk3229-evb.dts | 90 ++

[RESEND PATCH v2 0/4] Add support i2s/spdif/gmac features for RK322x SoCs

Hi, We have the brother chipset product that RK3228 and RK3229, They have many common configuration, but there are a number of different features. In order to develop the future when they are easy to distinguish, we need them to be independent. And, these patchset add i2s/gmac dts nodes for

[RESEND PATCH v2 1/4] ARM: dts: rockchip: rename rk3228.dtsi to rk322x.dtsi

We have the brother chipset that RK3228 and RK3229, they share most of dts configuration, but there are a number of different features. In order to develop the future when they are easy to distinguish, we need them to be independent. Signed-off-by: Xing Zheng ---

[RESEND PATCH v2 1/4] ARM: dts: rockchip: rename rk3228.dtsi to rk322x.dtsi

We have the brother chipset that RK3228 and RK3229, they share most of dts configuration, but there are a number of different features. In order to develop the future when they are easy to distinguish, we need them to be independent. Signed-off-by: Xing Zheng --- Changes in v2: None

  1   2   3   4   5   6   7   8   9   10   >