[v9] clk: qcom: clk-rpmh: Add QCOM RPMh clock driver

[v9] * clean up recalc function to use integer division. * Add back type casting the desc data passed to "getter" function and added comment for the same. [v8] * cleanup code to remove of rpmh_client handle. * pass the hw_clks array to the devm_of_clk_add_hw_provider getter

[v9] clk: qcom: clk-rpmh: Add QCOM RPMh clock driver

[v9] * clean up recalc function to use integer division. * Add back type casting the desc data passed to "getter" function and added comment for the same. [v8] * cleanup code to remove of rpmh_client handle. * pass the hw_clks array to the devm_of_clk_add_hw_provider getter

[v9] clk: qcom: clk-rpmh: Add QCOM RPMh clock driver

Add the RPMh clock driver to control the RPMh managed clock resources on some of the Qualcomm Technologies, Inc. SoCs. Signed-off-by: Taniya Das --- drivers/clk/qcom/Kconfig| 9 ++ drivers/clk/qcom/Makefile | 1 + drivers/clk/qcom/clk-rpmh.c | 333

[v9] clk: qcom: clk-rpmh: Add QCOM RPMh clock driver

Add the RPMh clock driver to control the RPMh managed clock resources on some of the Qualcomm Technologies, Inc. SoCs. Signed-off-by: Taniya Das --- drivers/clk/qcom/Kconfig| 9 ++ drivers/clk/qcom/Makefile | 1 + drivers/clk/qcom/clk-rpmh.c | 333

My name is BOVID EGAVI, a bank's manager in republic of TOGO. I have an abandoned unclaimed sum of thirty-six million euros only. can I trust you with this? if yes then contact me for full details thr

My name is BOVID EGAVI, a bank's manager in republic of TOGO. I have an abandoned unclaimed sum of thirty-six million euros only. can I trust you with this? if yes then contact me for full details thr

Re: BUG: please report to d...@vger.kernel.org => prev = 0, last = 0 at net/dccp/ccids/lib/packet_history.c:LINE/tfrc_rx_his

On Wed, May 09, 2018 at 07:23:41AM +0200, 'Dmitry Vyukov' via syzkaller-bugs wrote: > On Wed, May 9, 2018 at 7:05 AM, Eric Biggers wrote: > > On Sat, May 05, 2018 at 05:57:02PM -0700, syzbot wrote: > >> Hello, > >> > >> syzbot found the following crash on: > >> > >> HEAD

Re: BUG: please report to d...@vger.kernel.org => prev = 0, last = 0 at net/dccp/ccids/lib/packet_history.c:LINE/tfrc_rx_his

On Wed, May 09, 2018 at 07:23:41AM +0200, 'Dmitry Vyukov' via syzkaller-bugs wrote: > On Wed, May 9, 2018 at 7:05 AM, Eric Biggers wrote: > > On Sat, May 05, 2018 at 05:57:02PM -0700, syzbot wrote: > >> Hello, > >> > >> syzbot found the following crash on: > >> > >> HEAD commit:c1c07416cdd4

[PATCH v4 7/7] ocxl: Document new OCXL IOCTLs

From: Alastair D'Silva Signed-off-by: Alastair D'Silva --- Documentation/accelerators/ocxl.rst | 11 +++ 1 file changed, 11 insertions(+) diff --git a/Documentation/accelerators/ocxl.rst b/Documentation/accelerators/ocxl.rst index

[PATCH v4 7/7] ocxl: Document new OCXL IOCTLs

From: Alastair D'Silva Signed-off-by: Alastair D'Silva --- Documentation/accelerators/ocxl.rst | 11 +++ 1 file changed, 11 insertions(+) diff --git a/Documentation/accelerators/ocxl.rst b/Documentation/accelerators/ocxl.rst index ddcc58d01cfb..14cefc020e2d 100644 ---

[PATCH v4 5/7] ocxl: Expose the thread_id needed for wait on POWER9

From: Alastair D'Silva In order to successfully issue as_notify, an AFU needs to know the TID to notify, which in turn means that this information should be available in userspace so it can be communicated to the AFU. Signed-off-by: Alastair D'Silva

[PATCH v4 1/7] powerpc: Add TIDR CPU feature for POWER9

From: Alastair D'Silva This patch adds a CPU feature bit to show whether the CPU has the TIDR register available, enabling as_notify/wait in userspace. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/cputable.h | 3 ++-

[PATCH v4 5/7] ocxl: Expose the thread_id needed for wait on POWER9

From: Alastair D'Silva In order to successfully issue as_notify, an AFU needs to know the TID to notify, which in turn means that this information should be available in userspace so it can be communicated to the AFU. Signed-off-by: Alastair D'Silva --- drivers/misc/ocxl/context.c | 5

[PATCH v4 1/7] powerpc: Add TIDR CPU feature for POWER9

From: Alastair D'Silva This patch adds a CPU feature bit to show whether the CPU has the TIDR register available, enabling as_notify/wait in userspace. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/cputable.h | 3 ++- arch/powerpc/kernel/dt_cpu_ftrs.c | 1 + 2 files changed,

[PATCH v4 4/7] ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

From: Alastair D'Silva The function removes the process element from NPU cache. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/pnv-ocxl.h | 2 +- arch/powerpc/platforms/powernv/ocxl.c | 4 ++-- drivers/misc/ocxl/link.c |

[PATCH v4 0/7] ocxl: Implement Power9 as_notify/wait for OpenCAPI

From: Alastair D'Silva The Power 9 as_notify/wait feature provides a lower latency way to signal a thread that work is complete. This series enables the use of this feature from OpenCAPI adapters, as well as addressing a potential starvation issue when allocating thread

[PATCH v4 4/7] ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

From: Alastair D'Silva The function removes the process element from NPU cache. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/pnv-ocxl.h | 2 +- arch/powerpc/platforms/powernv/ocxl.c | 4 ++-- drivers/misc/ocxl/link.c | 2 +- 3 files changed, 4 insertions(+), 4

[PATCH v4 0/7] ocxl: Implement Power9 as_notify/wait for OpenCAPI

From: Alastair D'Silva The Power 9 as_notify/wait feature provides a lower latency way to signal a thread that work is complete. This series enables the use of this feature from OpenCAPI adapters, as well as addressing a potential starvation issue when allocating thread IDs. Changelog: v4:

[PATCH v4 3/7] powerpc: use task_pid_nr() for TID allocation

From: Alastair D'Silva The current implementation of TID allocation, using a global IDR, may result in an errant process starving the system of available TIDs. Instead, use task_pid_nr(), as mentioned by the original author. The scenario described which prevented it's use

[PATCH v4 3/7] powerpc: use task_pid_nr() for TID allocation

From: Alastair D'Silva The current implementation of TID allocation, using a global IDR, may result in an errant process starving the system of available TIDs. Instead, use task_pid_nr(), as mentioned by the original author. The scenario described which prevented it's use is not applicable, as

[PATCH v4 6/7] ocxl: Add an IOCTL so userspace knows what OCXL features are available

From: Alastair D'Silva In order for a userspace AFU driver to call the POWER9 specific OCXL_IOCTL_ENABLE_P9_WAIT, it needs to verify that it can actually make that call. Signed-off-by: Alastair D'Silva --- drivers/misc/ocxl/file.c | 25

[PATCH v4 6/7] ocxl: Add an IOCTL so userspace knows what OCXL features are available

From: Alastair D'Silva In order for a userspace AFU driver to call the POWER9 specific OCXL_IOCTL_ENABLE_P9_WAIT, it needs to verify that it can actually make that call. Signed-off-by: Alastair D'Silva --- drivers/misc/ocxl/file.c | 25 + include/uapi/misc/ocxl.h | 4

[PATCH v4 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

From: Alastair D'Silva Switch the use of TIDR on it's CPU feature, rather than assuming it is available based on architecture. Signed-off-by: Alastair D'Silva --- arch/powerpc/kernel/process.c | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH v4 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

From: Alastair D'Silva Switch the use of TIDR on it's CPU feature, rather than assuming it is available based on architecture. Signed-off-by: Alastair D'Silva --- arch/powerpc/kernel/process.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [PATCH] isdn: eicon: fix a missing-check bug

Hello Could you please review this patch? We need a confirmation because we are working on an approaching deadline. Thanks! Wenwen On Sat, May 5, 2018 at 2:32 PM, Wenwen Wang wrote: > In divasmain.c, the function divas_write() firstly invokes the function >

Re: [PATCH] isdn: eicon: fix a missing-check bug

Hello Could you please review this patch? We need a confirmation because we are working on an approaching deadline. Thanks! Wenwen On Sat, May 5, 2018 at 2:32 PM, Wenwen Wang wrote: > In divasmain.c, the function divas_write() firstly invokes the function > diva_xdi_open_adapter() to open the

Re: [PATCH V2 3/5] backlight: qcom-wled: Add support for short circuit handling

On 2018-05-08 16:05, Daniel Thompson wrote: On Thu, May 03, 2018 at 03:42:30PM +0530, Kiran Gunda wrote: Handle the short circuit interrupt and check if the short circuit interrupt is valid. Re-enable the module to check if it goes away. Disable the module altogether if the short circuit event

Re: [PATCH V2 3/5] backlight: qcom-wled: Add support for short circuit handling

On 2018-05-08 16:05, Daniel Thompson wrote: On Thu, May 03, 2018 at 03:42:30PM +0530, Kiran Gunda wrote: Handle the short circuit interrupt and check if the short circuit interrupt is valid. Re-enable the module to check if it goes away. Disable the module altogether if the short circuit event

Re: [PATCH] scsi: mpt3sas: fix a missing-check bug

Hello Could you please review this patch? We need a confirmation because we are working on an approaching deadline. Thanks! Wenwen On Sat, May 5, 2018 at 1:31 AM, Wenwen Wang wrote: > In _ctl_ioctl_main(), 'ioctl_header' is first copied from the userspace > pointer 'arg'.

Re: [PATCH] scsi: mpt3sas: fix a missing-check bug

Hello Could you please review this patch? We need a confirmation because we are working on an approaching deadline. Thanks! Wenwen On Sat, May 5, 2018 at 1:31 AM, Wenwen Wang wrote: > In _ctl_ioctl_main(), 'ioctl_header' is first copied from the userspace > pointer 'arg'.

Re: BUG: please report to d...@vger.kernel.org => prev = 0, last = 0 at net/dccp/ccids/lib/packet_history.c:LINE/tfrc_rx_his

On Wed, May 9, 2018 at 7:05 AM, Eric Biggers wrote: > On Sat, May 05, 2018 at 05:57:02PM -0700, syzbot wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:c1c07416cdd4 Merge tag 'kbuild-fixes-v4.17' of git://git.k.. >> git tree: upstream >>

Re: BUG: please report to d...@vger.kernel.org => prev = 0, last = 0 at net/dccp/ccids/lib/packet_history.c:LINE/tfrc_rx_his

On Wed, May 9, 2018 at 7:05 AM, Eric Biggers wrote: > On Sat, May 05, 2018 at 05:57:02PM -0700, syzbot wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:c1c07416cdd4 Merge tag 'kbuild-fixes-v4.17' of git://git.k.. >> git tree: upstream >> console output:

Re: [PATCH] h8300: switch to NO_BOOTMEM

On Sat, 17 Mar 2018 06:33:06 +0900, Rob Herring wrote: > > Commit 0fa1c579349f ("of/fdt: use memblock_virt_alloc for early alloc") > inadvertently switched the DT unflattening allocations from memblock to > bootmem which doesn't work because the unflattening happens before > bootmem is

Re: [PATCH] h8300: switch to NO_BOOTMEM

On Sat, 17 Mar 2018 06:33:06 +0900, Rob Herring wrote: > > Commit 0fa1c579349f ("of/fdt: use memblock_virt_alloc for early alloc") > inadvertently switched the DT unflattening allocations from memblock to > bootmem which doesn't work because the unflattening happens before > bootmem is

Re: linux-next: build failure after merge of the drm-intel tree

Hi Christoph, On Wed, 9 May 2018 07:08:55 +0200 Christoph Hellwig wrote: > > FYI, because the dma_configure change touch so much code and the author > wants to base more work on it it actually is in a guranteed stable > branch with just those patches: > >

Re: linux-next: build failure after merge of the drm-intel tree

Hi Christoph, On Wed, 9 May 2018 07:08:55 +0200 Christoph Hellwig wrote: > > FYI, because the dma_configure change touch so much code and the author > wants to base more work on it it actually is in a guranteed stable > branch with just those patches: > >

Re: [RESEND PATCH] pinctrl: rockchip: Disable interrupt when changing it's capability

Hi, On Tue, May 8, 2018 at 7:21 PM, JeffyChen wrote: > Hi Doug, > > On 05/09/2018 03:46 AM, Doug Anderson wrote: >> >> One note is that in the case Brian points at (where we need to >> simulate EDGE_BOTH by swapping edges) we purposely ignored the TRM and >> we needed

Re: [RESEND PATCH] pinctrl: rockchip: Disable interrupt when changing it's capability

Hi, On Tue, May 8, 2018 at 7:21 PM, JeffyChen wrote: > Hi Doug, > > On 05/09/2018 03:46 AM, Doug Anderson wrote: >> >> One note is that in the case Brian points at (where we need to >> simulate EDGE_BOTH by swapping edges) we purposely ignored the TRM and >> we needed to do that to avoid losing

Re: [PATCH V2 4/5] backlight: qcom-wled: Add support for OVP interrupt handling

On 2018-05-08 16:09, Daniel Thompson wrote: On Thu, May 03, 2018 at 03:42:31PM +0530, Kiran Gunda wrote: WLED peripheral has over voltage protection(OVP) circuitry and the OVP fault is notified through an interrupt. Though this fault condition rising is due to an incorrect hardware

Re: [PATCH V2 4/5] backlight: qcom-wled: Add support for OVP interrupt handling

On 2018-05-08 16:09, Daniel Thompson wrote: On Thu, May 03, 2018 at 03:42:31PM +0530, Kiran Gunda wrote: WLED peripheral has over voltage protection(OVP) circuitry and the OVP fault is notified through an interrupt. Though this fault condition rising is due to an incorrect hardware

Re: [PATCH V1 2/5] backlight: qcom-wled: Add support for WLED4 peripheral

On 2018-05-08 22:47, Bjorn Andersson wrote: On Tue 08 May 03:25 PDT 2018, kgu...@codeaurora.org wrote: On 2018-05-07 21:50, Bjorn Andersson wrote: > On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote: [..] > > +- qcom,ovp > > + Usage:optional > > + Value type: > > +

Re: [PATCH V1 2/5] backlight: qcom-wled: Add support for WLED4 peripheral

On 2018-05-08 22:47, Bjorn Andersson wrote: On Tue 08 May 03:25 PDT 2018, kgu...@codeaurora.org wrote: On 2018-05-07 21:50, Bjorn Andersson wrote: > On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote: [..] > > +- qcom,ovp > > + Usage:optional > > + Value type: > > +

Re: [PATCH] nvme-rdma: clear NVME_RDMA_Q_LIVE before free the queue

Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH] nvme-rdma: clear NVME_RDMA_Q_LIVE before free the queue

Looks fine, Reviewed-by: Christoph Hellwig

Re: bug in tag handling in blk-mq?

On Tue, 2018-05-08 at 14:37 -0600, Jens Axboe wrote: > > - sdd has nothing pending, yet has 6 active waitqueues. sdd is where ccache storage lives, which that should have been the only activity on that drive, as I built source in sdb, and was doing nothing else that utilizes sdd. -Mike

Re: bug in tag handling in blk-mq?

On Tue, 2018-05-08 at 14:37 -0600, Jens Axboe wrote: > > - sdd has nothing pending, yet has 6 active waitqueues. sdd is where ccache storage lives, which that should have been the only activity on that drive, as I built source in sdb, and was doing nothing else that utilizes sdd. -Mike

Re: [PATCH v6 2/6] ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set

On Tue, May 08, 2018 at 01:40:33PM +0100, Russell King - ARM Linux wrote: > On Mon, Mar 05, 2018 at 11:25:19AM +0100, Oleksij Rempel wrote: > > One of the Freescale recommended sequences for power off with external > > PMIC is the following: > > ... > > 3. SoC is programming PMIC for power off

Re: [PATCH v6 2/6] ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set

On Tue, May 08, 2018 at 01:40:33PM +0100, Russell King - ARM Linux wrote: > On Mon, Mar 05, 2018 at 11:25:19AM +0100, Oleksij Rempel wrote: > > One of the Freescale recommended sequences for power off with external > > PMIC is the following: > > ... > > 3. SoC is programming PMIC for power off

Re: bug in tag handling in blk-mq?

> Il giorno 09 mag 2018, alle ore 06:11, Mike Galbraith ha > scritto: > > On Tue, 2018-05-08 at 19:09 -0600, Jens Axboe wrote: >> >> Alright, I managed to reproduce it. What I think is happening is that >> BFQ is limiting the inflight case to something less than the wake >>

Re: bug in tag handling in blk-mq?

> Il giorno 09 mag 2018, alle ore 06:11, Mike Galbraith ha > scritto: > > On Tue, 2018-05-08 at 19:09 -0600, Jens Axboe wrote: >> >> Alright, I managed to reproduce it. What I think is happening is that >> BFQ is limiting the inflight case to something less than the wake >> batch for

Re: [PATCH V1 4/5] backlight: qcom-wled: Add support for OVP interrupt handling

On 2018-05-08 22:49, Bjorn Andersson wrote: On Tue 08 May 05:26 PDT 2018, kgu...@codeaurora.org wrote: On 2018-05-07 22:51, Bjorn Andersson wrote: > On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote: [..] > > @@ -220,7 +255,12 @@ static int wled_module_enable(struct wled > > *wled, int val) >

Re: [PATCH V1 4/5] backlight: qcom-wled: Add support for OVP interrupt handling

On 2018-05-08 22:49, Bjorn Andersson wrote: On Tue 08 May 05:26 PDT 2018, kgu...@codeaurora.org wrote: On 2018-05-07 22:51, Bjorn Andersson wrote: > On Thu 03 May 02:57 PDT 2018, Kiran Gunda wrote: [..] > > @@ -220,7 +255,12 @@ static int wled_module_enable(struct wled > > *wled, int val) >

Re: linux-next: build failure after merge of the drm-intel tree

On Wed, May 09, 2018 at 03:02:55PM +1000, Stephen Rothwell wrote: > > - ret = of_dma_configure(dev, NULL); > > + ret = of_dma_configure(dev, NULL, true); > > if (ret < 0) { > > DRM_ERROR("Cannot setup DMA ops, ret %d", ret); > > return ret; > > -- > > 2.17.0 > >

Re: linux-next: build failure after merge of the drm-intel tree

On Wed, May 09, 2018 at 03:02:55PM +1000, Stephen Rothwell wrote: > > - ret = of_dma_configure(dev, NULL); > > + ret = of_dma_configure(dev, NULL, true); > > if (ret < 0) { > > DRM_ERROR("Cannot setup DMA ops, ret %d", ret); > > return ret; > > -- > > 2.17.0 > >

Re: linux-next: build failure after merge of the drm-intel tree

Hi all, On Tue, 8 May 2018 11:07:16 +1000 Stephen Rothwell wrote: > > After merging the drm-intel tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/gpu/drm/xen/xen_drm_front.c: In function 'xen_drv_probe': >

Re: linux-next: build failure after merge of the drm-intel tree

Hi all, On Tue, 8 May 2018 11:07:16 +1000 Stephen Rothwell wrote: > > After merging the drm-intel tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/gpu/drm/xen/xen_drm_front.c: In function 'xen_drv_probe': > drivers/gpu/drm/xen/xen_drm_front.c:740:10: error:

Re: BUG: please report to d...@vger.kernel.org => prev = 0, last = 0 at net/dccp/ccids/lib/packet_history.c:LINE/tfrc_rx_his

On Sat, May 05, 2018 at 05:57:02PM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:c1c07416cdd4 Merge tag 'kbuild-fixes-v4.17' of git://git.k.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=13d5de4780 >

Re: BUG: please report to d...@vger.kernel.org => prev = 0, last = 0 at net/dccp/ccids/lib/packet_history.c:LINE/tfrc_rx_his

On Sat, May 05, 2018 at 05:57:02PM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:c1c07416cdd4 Merge tag 'kbuild-fixes-v4.17' of git://git.k.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=13d5de4780 >

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Kim Phillips writes: > This patch is in the context of allowing the Coresight h/w > trace driver suite to be loaded as modules. Coresight uses > find_task_by_vpid when running in direct capture mode (via sysfs) > when getting/setting the context ID comparator to trigger on

Re: [PATCH 2/4] pid: Export find_task_by_vpid for use in external modules

Kim Phillips writes: > This patch is in the context of allowing the Coresight h/w > trace driver suite to be loaded as modules. Coresight uses > find_task_by_vpid when running in direct capture mode (via sysfs) > when getting/setting the context ID comparator to trigger on >

linux-next: build warning after merge of the mac80211-next tree

Hi Johannes, After merging the mac80211-next tree, today's linux-next build (arm_multi v7_defconfig) produced this warning: drivers/net/wireless/marvell/mwifiex/uap_event.c: In function 'mwifiex_process_uap_event': drivers/net/wireless/marvell/mwifiex/uap_event.c:333:1: warning: the frame size

linux-next: build warning after merge of the mac80211-next tree

Hi Johannes, After merging the mac80211-next tree, today's linux-next build (arm_multi v7_defconfig) produced this warning: drivers/net/wireless/marvell/mwifiex/uap_event.c: In function 'mwifiex_process_uap_event': drivers/net/wireless/marvell/mwifiex/uap_event.c:333:1: warning: the frame size

Re: [PATCH] Revert "cpufreq: schedutil: Don't restrict kthread to related_cpus unnecessarily"

On 08-05-18, 08:33, Dietmar Eggemann wrote: > This reverts commit e2cabe48c20efb174ce0c01190f8b9c5f3ea1d13. > > Lifting the restriction that the sugov kthread is bound to the > policy->related_cpus for a system with a slow switching cpufreq driver, > which is able to perform DVFS from any cpu

Re: [PATCH] Revert "cpufreq: schedutil: Don't restrict kthread to related_cpus unnecessarily"

On 08-05-18, 08:33, Dietmar Eggemann wrote: > This reverts commit e2cabe48c20efb174ce0c01190f8b9c5f3ea1d13. > > Lifting the restriction that the sugov kthread is bound to the > policy->related_cpus for a system with a slow switching cpufreq driver, > which is able to perform DVFS from any cpu

Re: [RFC PATCH] sched/cpufreq/schedutil: handling urgent frequency requests

On Tue, May 08, 2018 at 12:24:35PM +0530, Viresh Kumar wrote: > On 07-05-18, 16:43, Claudio Scordino wrote: > > At OSPM, it was mentioned the issue about urgent CPU frequency requests > > arriving when a frequency switch is already in progress. > > > > Besides the various issues (physical time

Re: [RFC PATCH] sched/cpufreq/schedutil: handling urgent frequency requests

On Tue, May 08, 2018 at 12:24:35PM +0530, Viresh Kumar wrote: > On 07-05-18, 16:43, Claudio Scordino wrote: > > At OSPM, it was mentioned the issue about urgent CPU frequency requests > > arriving when a frequency switch is already in progress. > > > > Besides the various issues (physical time

Re: [PATCH] Revert "cpufreq: schedutil: Don't restrict kthread to related_cpus unnecessarily"

On 08-05-18, 22:36, Rafael J. Wysocki wrote: > Because that makes things more complex and harder to debug in general. > > What's the exact reason why non-policy CPUs should ever run the sugov > kthread for the given policy? The only benefit was to let the scheduler run the kthread on the best

Re: [PATCH] Revert "cpufreq: schedutil: Don't restrict kthread to related_cpus unnecessarily"

On 08-05-18, 22:36, Rafael J. Wysocki wrote: > Because that makes things more complex and harder to debug in general. > > What's the exact reason why non-policy CPUs should ever run the sugov > kthread for the given policy? The only benefit was to let the scheduler run the kthread on the best

Re: [PATCH] Kirin-PCIe: Add kirin pcie msi feature.

Hi Bjorn, On Tue, May 08, 2018 at 07:56:58AM -0500, Bjorn Helgaas wrote: ... > > + return ret; > > + } > > + } > > + > > + pci->pp.root_bus_nr = -1; > > Setting root_bus_nr looks like an unrelated change that should be in a > separate patch. > > But I'm not sure

Re: [PATCH] Kirin-PCIe: Add kirin pcie msi feature.

Hi Bjorn, On Tue, May 08, 2018 at 07:56:58AM -0500, Bjorn Helgaas wrote: ... > > + return ret; > > + } > > + } > > + > > + pci->pp.root_bus_nr = -1; > > Setting root_bus_nr looks like an unrelated change that should be in a > separate patch. > > But I'm not sure

linux-next: build warning after merge of the bpf-next tree

Hi all, After merging the bpf-next tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/dma-mapping.h:5:0, from include/linux/skbuff.h:34, from include/linux/if_ether.h:23, from

linux-next: build warning after merge of the bpf-next tree

Hi all, After merging the bpf-next tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/dma-mapping.h:5:0, from include/linux/skbuff.h:34, from include/linux/if_ether.h:23, from

RE: [External] Re: [RFC PATCH v1 0/6] use mm to manage NVDIMM (pmem) zone

> > On Tue, May 08, 2018 at 02:59:40AM +, Huaisheng HS1 Ye wrote: > > Currently in our mind, an ideal use scenario is that, we put all page > > caches to > > zone_nvm, without any doubt, page cache is an efficient and common cache > > implement, but it has a disadvantage that all dirty data

RE: [External] Re: [RFC PATCH v1 0/6] use mm to manage NVDIMM (pmem) zone

> > On Tue, May 08, 2018 at 02:59:40AM +, Huaisheng HS1 Ye wrote: > > Currently in our mind, an ideal use scenario is that, we put all page > > caches to > > zone_nvm, without any doubt, page cache is an efficient and common cache > > implement, but it has a disadvantage that all dirty data

Re: [PATCH v4 1/2] clk: x86: Add ST oscout platform clock

On 5/8/2018 9:08 PM, Deucher, Alexander wrote: >> -Original Message- >> From: Agrawal, Akshu >> Sent: Tuesday, May 8, 2018 12:04 AM >> To: Deucher, Alexander >> Cc: djku...@chromium.org; mturque...@baylibre.com; sb...@kernel.org; >> Koenig, Christian

Re: [Ksummit-discuss] bug-introducing patches

On Tue, May 08, 2018 at 08:29:14PM +, Sasha Levin wrote: > What if, instead, Linus doesn't actually ever release a point release? > We can make the merge window open more often, and since there's no > actual release, people won't rush to push fixes in later -rc cycles. And then what's the

Re: [PATCH v4 1/2] clk: x86: Add ST oscout platform clock

On 5/8/2018 9:08 PM, Deucher, Alexander wrote: >> -Original Message- >> From: Agrawal, Akshu >> Sent: Tuesday, May 8, 2018 12:04 AM >> To: Deucher, Alexander >> Cc: djku...@chromium.org; mturque...@baylibre.com; sb...@kernel.org; >> Koenig, Christian ; airl...@redhat.com; Liu, >>

Re: [Ksummit-discuss] bug-introducing patches

On Tue, May 08, 2018 at 08:29:14PM +, Sasha Levin wrote: > What if, instead, Linus doesn't actually ever release a point release? > We can make the merge window open more often, and since there's no > actual release, people won't rush to push fixes in later -rc cycles. And then what's the

Re: KASAN: out-of-bounds Read in ip6_xmit

On Sun, Jan 28, 2018 at 11:24:01AM -0800, syzbot wrote: > Hello, > > syzbot hit the following crash on net-next commit > 6bb46bc57c8e9ce947cc605e555b7204b44d2b10 (Fri Jan 26 16:00:23 2018 +) > Merge branch 'cxgb4-fix-dump-collection-when-firmware-crashed' > > Unfortunately, I don't have any

Re: KASAN: out-of-bounds Read in ip6_xmit

On Sun, Jan 28, 2018 at 11:24:01AM -0800, syzbot wrote: > Hello, > > syzbot hit the following crash on net-next commit > 6bb46bc57c8e9ce947cc605e555b7204b44d2b10 (Fri Jan 26 16:00:23 2018 +) > Merge branch 'cxgb4-fix-dump-collection-when-firmware-crashed' > > Unfortunately, I don't have any

Re: KASAN: use-after-free Read in ip6_xmit

On Thu, Jan 04, 2018 at 02:58:01AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 0e08c463db387a2adcb0243b15ab868a73f87807 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: KASAN: use-after-free Read in ip6_xmit

On Thu, Jan 04, 2018 at 02:58:01AM -0800, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 0e08c463db387a2adcb0243b15ab868a73f87807 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console

Re: [PATCH V4] clk: at91: PLL recalc_rate() now using cached MUL and DIV values

On Mon, Apr 30, 2018 at 07:58:47AM +0200, Boris Brezillon wrote: > On Sun, 29 Apr 2018 15:01:11 -0400 > Marcin Ziemianowicz wrote: > > > When a USB device is connected to the USB host port on the SAM9N12 then > > you get "-62" error which seems to indicate USB replies

Re: [PATCH V4] clk: at91: PLL recalc_rate() now using cached MUL and DIV values

On Mon, Apr 30, 2018 at 07:58:47AM +0200, Boris Brezillon wrote: > On Sun, 29 Apr 2018 15:01:11 -0400 > Marcin Ziemianowicz wrote: > > > When a USB device is connected to the USB host port on the SAM9N12 then > > you get "-62" error which seems to indicate USB replies from the device > > are

Re: [PATCH v7 12/24] ASoC: qdsp6: q6afe: Add support to MI2S sysclks

On 5/1/2018 5:08 AM, Srinivas Kandagatla wrote: This patch adds support to LPASS Bit clock, LPASS Digital core clock and OSR clock. These clocks are required for both MI2S and PCM setup. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar

Re: [PATCH v7 12/24] ASoC: qdsp6: q6afe: Add support to MI2S sysclks

On 5/1/2018 5:08 AM, Srinivas Kandagatla wrote: This patch adds support to LPASS Bit clock, LPASS Digital core clock and OSR clock. These clocks are required for both MI2S and PCM setup. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar --- sound/soc/qcom/qdsp6/q6afe.c

[PATCH] ASoC: AMD: Change codec to channel link as per hardware redesign

This is a correction to match acutal hardware configuration. The hardware configuration looks like: I2S_BT -> SPK(Max) + DMIC(Adau) I2S_SP -> DA7219 Headset No actual products have been shipped with previous configuration. Signed-off-by: Akshu Agrawal --- This patch is

[PATCH] ASoC: AMD: Change codec to channel link as per hardware redesign

This is a correction to match acutal hardware configuration. The hardware configuration looks like: I2S_BT -> SPK(Max) + DMIC(Adau) I2S_SP -> DA7219 Headset No actual products have been shipped with previous configuration. Signed-off-by: Akshu Agrawal --- This patch is dependent on [V4,10/10]

RE: [External] [RFC PATCH v1 3/6] mm, zone_type: create ZONE_NVM and fill into GFP_ZONE_TABLE

> On 05/07/2018 07:33 PM, Huaisheng HS1 Ye wrote: > > diff --git a/mm/Kconfig b/mm/Kconfig > > index c782e8f..5fe1f63 100644 > > --- a/mm/Kconfig > > +++ b/mm/Kconfig > > @@ -687,6 +687,22 @@ config ZONE_DEVICE > > > > +config ZONE_NVM > > + bool "Manage NVDIMM (pmem) by memory management

RE: [External] [RFC PATCH v1 3/6] mm, zone_type: create ZONE_NVM and fill into GFP_ZONE_TABLE

> On 05/07/2018 07:33 PM, Huaisheng HS1 Ye wrote: > > diff --git a/mm/Kconfig b/mm/Kconfig > > index c782e8f..5fe1f63 100644 > > --- a/mm/Kconfig > > +++ b/mm/Kconfig > > @@ -687,6 +687,22 @@ config ZONE_DEVICE > > > > +config ZONE_NVM > > + bool "Manage NVDIMM (pmem) by memory management

Re: linux-next: manual merge of the bpf-next tree with the s390 tree

Hi all, On Tue, 8 May 2018 10:26:38 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the bpf-next tree got a conflict in: > > arch/s390/net/bpf_jit.S > > between commit: > > de5cb6eb514e ("s390: use expoline thunks in the BPF JIT") > > from the s390

Re: linux-next: manual merge of the bpf-next tree with the s390 tree

Hi all, On Tue, 8 May 2018 10:26:38 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the bpf-next tree got a conflict in: > > arch/s390/net/bpf_jit.S > > between commit: > > de5cb6eb514e ("s390: use expoline thunks in the BPF JIT") > > from the s390 tree and commit: > >

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: tools/testing/selftests/net/Makefile between commit: 1751eb42ddb5 ("selftests: net: use TEST_PROGS_EXTENDED") from the net tree and commits: a7b15ab887e5 ("Merge

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: tools/testing/selftests/net/Makefile between commit: 1751eb42ddb5 ("selftests: net: use TEST_PROGS_EXTENDED") from the net tree and commits: a7b15ab887e5 ("Merge

[PATCH v2 2/2] perf cs-etm: Remove redundant space

There have two spaces ahead function name cs_etm__set_pid_tid_cpu(), so remove one space and correct indentation. Signed-off-by: Leo Yan Acked-by: Mathieu Poirier --- tools/perf/util/cs-etm.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH v2 2/2] perf cs-etm: Remove redundant space

There have two spaces ahead function name cs_etm__set_pid_tid_cpu(), so remove one space and correct indentation. Signed-off-by: Leo Yan Acked-by: Mathieu Poirier --- tools/perf/util/cs-etm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/perf/util/cs-etm.c

[PATCH v2 1/2] perf cs-etm: Support unknown_thread in cs_etm_auxtrace

CoreSight doesn't allocate thread structure for unknown_thread in etm auxtrace, so unknown_thread is NULL pointer. If the perf data doesn't contain valid tid and then cs_etm__mem_access() uses unknown_thread instead as thread handler, this results in segmentation fault when

[PATCH v2 1/2] perf cs-etm: Support unknown_thread in cs_etm_auxtrace

CoreSight doesn't allocate thread structure for unknown_thread in etm auxtrace, so unknown_thread is NULL pointer. If the perf data doesn't contain valid tid and then cs_etm__mem_access() uses unknown_thread instead as thread handler, this results in segmentation fault when

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/tls/tls_main.c between commit: 98f0a39529e5 ("tls: fix use after free in tls_sk_proto_close") from the net tree and commit: f66de3ee2c16 ("net/tls: Split conf to rx + tx") from the net-next tree. I fixed it

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/tls/tls_main.c between commit: 98f0a39529e5 ("tls: fix use after free in tls_sk_proto_close") from the net tree and commit: f66de3ee2c16 ("net/tls: Split conf to rx + tx") from the net-next tree. I fixed it

  1   2   3   4   5   6   7   8   9   10   >