Re: [PATCH v1] mm:memcg: skip memcg of current in mem_cgroup_soft_limit_reclaim

On Fri 03-08-18 14:11:26, Zhaoyang Huang wrote: > On Fri, Aug 3, 2018 at 1:48 PM Zhaoyang Huang wrote: > > > > for the soft_limit reclaim has more directivity than global reclaim, we40960 > > have current memcg be skipped to avoid potential page thrashing. > > > The patch is tested in our android

Re: Linux 4.9.117

diff --git a/Documentation/devicetree/bindings/net/dsa/qca8k.txt b/Documentation/devicetree/bindings/net/dsa/qca8k.txt index 9c67ee4890d7..bbcb255c3150 100644 --- a/Documentation/devicetree/bindings/net/dsa/qca8k.txt +++ b/Documentation/devicetree/bindings/net/dsa/qca8k.txt @@ -2,7 +2,10 @@

Re: [PATCH 4.14 000/246] 4.14.60-stable review

On Fri, Aug 03, 2018 at 11:53:53AM +0530, Naresh Kamboju wrote: > > I've pushed out -rc2 releases for all of these with that patch removed. > > Results from Linaro’s test farm. > No regressions on arm64, arm and x86_64. Great!

Linux 4.9.117

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

Re: [PATCH] media: platform: cros-ec-cec: fix dependency on MFD_CROS_EC

On 08/03/2018 12:58 AM, Mauro Carvalho Chehab wrote: > Em Tue, 24 Jul 2018 11:35:59 +0200 > Arnd Bergmann escreveu: > >> Without the MFD driver, we run into a link error: > > Weird... I'm not seeing this driver at the media tree... was it merged via > some other tree? Yes, it's going via the

Linux 4.17.12

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

Linux 4.14.60

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

Re: [PATCH 4.9 000/144] 4.9.117-stable review

On 2 August 2018 at 12:29, Naresh Kamboju wrote: > On 1 August 2018 at 22:20, Greg Kroah-Hartman > wrote: >> This is the start of the stable review cycle for the 4.9.117 release. >> There are 144 patches in this series, all will be posted as a response >> to this one. If anyone has any issues

linux-next: manual merge of the scsi-mkp tree with Linus' tree

Hi all, Today's linux-next merge of the scsi-mkp tree got conflicts in: drivers/scsi/qla2xxx/qla_gs.c between commit: b5f3bc39a0e8 ("scsi: qla2xxx: Fix inconsistent DMA mem alloc/free") from Linus' tree and commit: 8777e4314d39 ("scsi: qla2xxx: Migrate NVME N2N handling into state

[PATCH] ARM: dmabounce: remove unnecessary NULL check before dma_pool_destroy

dma_pool_destroy will do NULL check,thus the check before the call is not needed. Signed-off-by: YueHaibing --- arch/arm/common/dmabounce.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/arch/arm/common/dmabounce.c b/arch/arm/common/dmabounce.c index 9a92de6..dcdd80c

Re: [PATCH 4.17 000/336] 4.17.12-stable review

On 2 August 2018 at 12:33, Greg Kroah-Hartman wrote: > On Thu, Aug 02, 2018 at 12:27:24PM +0530, Naresh Kamboju wrote: >> On 1 August 2018 at 22:15, Greg Kroah-Hartman >> wrote: >> > This is the start of the stable review cycle for the 4.17.12 release. >> > There are 336 patches in this series,

[RESEND PATCH] resource: Merge resources on a node when hot-adding memory

When hot-removing memory release_mem_region_adjustable() splits iomem resources if they are not the exact size of the memory being hot-deleted. Adding this memory back to the kernel adds a new resource. Eg a node has memory 0x0 - 0xf. Offlining and hot-removing 1GB from 0xf4000

linux-next: manual merge of the scsi-mkp tree with Linus' tree

Hi all, Today's linux-next merge of the scsi-mkp tree got a conflict in: drivers/scsi/qla2xxx/qla_init.c between commit: 36eb8ff672fa ("scsi: qla2xxx: Fix NULL pointer dereference for fcport search") from Linus' tree and commit: 48acad099074 ("scsi: qla2xxx: Fix N2N link re-connect")

Re: [RFC 1/2] slub: Avoid trying to allocate memory on offline nodes

On Thu 02-08-18 22:21:53, Jeremy Linton wrote: > Hi, > > On 08/02/2018 04:15 AM, Michal Hocko wrote: > > On Wed 01-08-18 15:04:17, Jeremy Linton wrote: > > [...] > > > @@ -2519,6 +2519,8 @@ static void *___slab_alloc(struct kmem_cache *s, > > > gfp_t gfpflags, int node, > > >

Re: linux-next: manual merge of the mips tree with the kbuild tree

Hi Christoph, On Fri, 3 Aug 2018 08:41:28 +0200 Christoph Hellwig wrote: > > On Fri, Aug 03, 2018 at 09:21:00AM +1000, Stephen Rothwell wrote: > > I fixed it up (see below) > > I can't find any fixup below.. Sorry about that - see below. -- Cheers, Stephen Rothwell

Re: [RFC 2/2] mm: harden alloc_pages code paths against bogus nodes

On Thu 02-08-18 22:17:49, Jeremy Linton wrote: > Hi, > > On 08/02/2018 02:31 AM, Michal Hocko wrote: > > On Wed 01-08-18 15:04:18, Jeremy Linton wrote: > > > Its possible to crash __alloc_pages_nodemask by passing it > > > bogus node ids. This is caused by NODE_DATA() returning null > > >

Re: [PATCH 4.14 000/246] 4.14.60-stable review

> I've pushed out -rc2 releases for all of these with that patch removed. Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.14.60-rc2 git repo:

[PATCH 2/6] mm/migrate: Use trylock while resetting rate limit

Since this spinlock will only serialize migrate rate limiting, convert the spinlock to a trylock. If another task races ahead of this task then this task can simply move on. While here, add correct two abnormalities. - Avoid time being stretched for every interval. - Use READ/WRITE_ONCE with next

[PATCH 5/6] sched/numa: Reset scan rate whenever task moves across nodes

Currently task scan rate is reset when numa balancer migrates the task to a different node. If numa balancer initiates a swap, reset is only applicable to the task that initiates the swap. Similarly no scan rate reset is done if the task is migrated across nodes by traditional load balancer.

[PATCH 6/6] sched/numa: Limit the conditions where scan period is reset

From: Mel Gorman migrate_task_rq_fair resets the scan rate for NUMA balancing on every cross-node migration. In the event of excessive load balancing due to saturation, this may result in the scan rate being pegged at maximum and further overloading the machine. This patch only resets the scan

Re: [PATCH v1] mm:memcg: skip memcg of current in mem_cgroup_soft_limit_reclaim

On Fri 03-08-18 13:48:05, Zhaoyang Huang wrote: > for the soft_limit reclaim has more directivity than global reclaim, we > have current memcg be skipped to avoid potential page thrashing. a) this changelog doesn't really explain the problem nor does it explain why the proposed solution is

Re: [PATCH] mm,page_alloc: PF_WQ_WORKER threads must sleep at should_reclaim_retry().

On Fri 03-08-18 07:05:54, Tetsuo Handa wrote: > On 2018/07/31 14:09, Michal Hocko wrote: > > On Tue 31-07-18 06:01:48, Tetsuo Handa wrote: > >> On 2018/07/31 4:10, Michal Hocko wrote: > >>> Since should_reclaim_retry() should be a natural reschedule point, > >>> let's do the short sleep for

Re: linux-next: manual merge of the mips tree with the kbuild tree

On Fri, Aug 03, 2018 at 09:21:00AM +1000, Stephen Rothwell wrote: > I fixed it up (see below) I can't find any fixup below..

Re: [PATCH v1] mm:memcg: skip memcg of current in mem_cgroup_soft_limit_reclaim

On Fri, Aug 3, 2018 at 1:48 PM Zhaoyang Huang wrote: > > for the soft_limit reclaim has more directivity than global reclaim, we40960 > have current memcg be skipped to avoid potential page thrashing. > The patch is tested in our android system with 2GB ram. The case mainly focus on the smooth

[PATCH v2] watchdog: Reduce message verbosity

Code is emitting the following error message during boot on systems without PMU hardware support while probing NMI capability. NMI watchdog: Perf event create on CPU 0 failed with -2 This error is coming from this path: lockup_detector_init watchdog_nmi_probe hardlockup_detector_perf_init

[PATCH 1/2] resource: Merge resources on a node when hot-adding memory

When hot-removing memory release_mem_region_adjustable() splits iomem resources if they are not the exact size of the memory being hot-deleted. Adding this memory back to the kernel adds a new resource. Eg a node has memory 0x0 - 0xf. Offlining and hot-removing 1GB from 0xf4000

Re: framebuffer corruption due to overlapping stp instructions on arm64

On Thu, 2 Aug 2018, Matt Sealey wrote: > The easiest explanation for this would be that the memory isn?t mapped > correctly. You can?t use PCIe memory spaces with anything other than > Device-nGnRE or stricter mappings. That?s just differences between the > AMBA and PCIe (posted/unposted)

Re: [PATCH v3 2/4] Refactor FPU codes in signal setup/return procedures

/commits/Alan-Kao/Extract-FPU-context-operations-from-entry-S/20180803-064749 config: riscv-defconfig (attached as .config) compiler: riscv64-linux-gcc (GCC) 8.1.0 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x

Re: [PATCH v10 00/10] drivers: Introduce firmware dnd clock river for ZynqMP core

On 2.8.2018 22:59, Stephen Boyd wrote: > Quoting Michal Simek (2018-07-30 05:50:42) >> On 26.7.2018 18:36, Stephen Boyd wrote: >>> Quoting Michal Simek (2018-07-25 02:51:14) On 24.7.2018 20:14, Jolly Shah wrote: >>> create mode 100644 drivers/firmware/xilinx/zynqmp-debug.h >>>

[PATCH 3/6] sched/numa: Avoid task migration for small numa improvement

If numa improvement from the task migration is going to be very minimal, then avoid task migration. specjbb2005 / bops/JVM / higher bops are better on 2 Socket/2 Node Intel JVMS PrevCurrent %Change 4 200892 210118 4.59252 1 325766 313171 -3.86627 on 2 Socket/4 Node Power8

[PATCH 1/6] sched/numa: Stop multiple tasks from moving to the cpu at the same time

Task migration under numa balancing can happen in parallel. More than one task might choose to migrate to the same cpu at the same time. This can result in - During task swap, choosing a task that was not part of the evaluation. - During task swap, task which just got moved into its preferred

[PATCH 0/6] numa-balancing patches

This patchset based on current tip/sched/core, provides left out patches from the previous series. This version handles the comments given to some of the patches. It drops "sched/numa: Restrict migrating in parallel to the same node." It adds an additional patch from Mel Gorman. It also provides

[PATCH 4/6] sched/numa: Pass destination cpu as a parameter to migrate_task_rq

This additional parameter (new_cpu) is used later for identifying if task migration is across nodes. No functional change. Signed-off-by: Srikar Dronamraju --- kernel/sched/core.c | 2 +- kernel/sched/deadline.c | 2 +- kernel/sched/fair.c | 2 +- kernel/sched/sched.h| 2 +- 4

[PATCH] um: NULL check before kfree is not needed

kfree(NULL) is safe,so this removes NULL check before freeing the mem Signed-off-by: YueHaibing --- arch/um/drivers/vector_kern.c | 15 +-- arch/um/drivers/vector_user.c | 6 ++ arch/um/kernel/irq.c | 3 +-- 3 files changed, 8 insertions(+), 16 deletions(-) diff

Re: framebuffer corruption due to overlapping stp instructions on arm64

On Thu, Aug 2, 2018 at 12:31 PM Mikulas Patocka wrote: > > Hi > > I tried to use a PCIe graphics card on the MacchiatoBIN board and I hit a > strange problem. > > When I use the links browser in graphics mode on the framebuffer, I get > occasional pixel corruption. Links does memcpy, memset and

[PATCH 37/46] dmaengine: imx-sdma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label err_register Signed-off-by: Huang Shijie --- drivers/dma/imx-sdma.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/imx-sdma.c

[PATCH 38/46] dmaengine: imx-dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label err_of_dma_controller Signed-off-by: Huang Shijie --- drivers/dma/imx-dma.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

[PATCH 39/46] dmaengine: img-mdc-dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister remove label unregister Signed-off-by: Huang Shijie --- drivers/dma/img-mdc-dma.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/img-mdc-dma.c

[PATCH 31/46] dmaengine: moxart-dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/moxart-dma.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/dma/moxart-dma.c b/drivers/dma/moxart-dma.c index

[PATCH 18/46] dmaengine: stm32-dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister Signed-off-by: Huang Shijie --- drivers/dma/stm32-dma.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/dma/stm32-dma.c b/drivers/dma/stm32-dma.c index

[PATCH 34/46] dmaengine: mxs-dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/mxs-dma.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/dma/mxs-dma.c b/drivers/dma/mxs-dma.c index

Re: [PATCH v12 0/3] tracing: Centralize preemptirq tracepoints and unify their usage

Hi Joel, Thank you for trying to fix that. On Thu, 2 Aug 2018 19:57:09 -0700 Joel Fernandes wrote: > Hi Masami, > > On Thu, Aug 2, 2018 at 7:55 AM, Masami Hiramatsu wrote: > > Hi Joel, > > > > I found this caused several issues when testing ftrace. > > > > #1) ftrace boottest

Re: simplified RISC-V interrupt and clocksource handling v2

On Thu, 2 Aug 2018, Palmer Dabbelt wrote: > bit of arch/riscv diff here so I don't mind taking it through the RISC-V tree, > but there's also some irqchip and clocksource stuff as well so I'm not sure if > that's OK to do. I have no objections if that goes through the risc-v tree once the DT

Re: [PATCH v5 09/14] sched: Add over-utilization/tipping point indicator

On Thu, 2 Aug 2018 at 18:59, Quentin Perret wrote: > > On Thursday 02 Aug 2018 at 18:38:01 (+0200), Vincent Guittot wrote: > > On Thu, 2 Aug 2018 at 18:10, Quentin Perret wrote: > > > > > > On Thursday 02 Aug 2018 at 18:07:49 (+0200), Vincent Guittot wrote: > > > > On Thu, 2 Aug 2018 at 18:00,

Re: [PATCH 08/46] dmaengine: edma: use dmaenginem_async_device_register to simplify the code

On 2018-08-03 10:19, Huang Shijie wrote: > Use dmaenginem_async_device_register to simplify the code: >remove dma_async_device_unregister > > Signed-off-by: Huang Shijie > --- > drivers/dma/ti/edma.c | 8 ++-- > 1 file changed, 2 insertions(+), 6 deletions(-) > > diff --git

Re: [PATCH v2 1/2] leds: core: Introduce LED pattern trigger

Hi Jacek, On 3 August 2018 at 05:21, Jacek Anaszewski wrote: > Hi Baolin, > > Thank you for addressing review remarks. > > I've played a bit with the interface and I have one conclusion > regarding pattern parsing, please refer below. > > Also one tiny optimization request in

Built in PS2 keyboard in new ASUS/acer laptops can not wake up system after s2idle

Hi guys, We have some new laptops with Intel new Intel WiskyLake CPU come in and they all have the same problem. They all have the so-called "Modern Standby" feature which is s2idle in Linux. The problem is the built-in keyboard no longer wake up the system after it goes to s2idle. Only

[ANNOUNCE] v4.16.18-rt12

Dear RT folks! I'm pleased to announce the v4.16.18-rt12 patch set. Changes since v4.16.18-rt11: - Mark RCU's "rcu_iw" irqwork to be invoked in hardirq context as expected by RCU. Reported by John Ogness. - Drop the "is_special_task_state()" check from rtmutex's custom set_state

hi

Please reply me back I have something to tell you.I am Sgt.Sherri.

[PATCH] xfs: fix a comment in xfs_log_reserve

From: "Huang Chong" Fix the comment in xfs_log_reserve to avoid confusing. Signed-of-by: Huang Chong --- fs/xfs/xfs_log.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c index 5e56f3b..891ffb1 100644 --- a/fs/xfs/xfs_log.c +++

Re: [PATCH 00/46] Use dmaenginem_async_device_register to simplify code

On Fri, Aug 03, 2018 at 11:20:49AM +0300, Peter Ujfalusi wrote: > Hi, > > On 2018-08-03 10:19, Huang Shijie wrote: > > All the patches are using dmaenginem_async_device_register to simplify code > > except the last one: > > dmaengine: add COMPILE_TEST for the drivers > > > > I use the last one

[PATCH] misc: eeprom: assignment outside the if statement

Assignment of any variable should be kept outside the if statement Signed-off-by: Parth Y Shah --- drivers/misc/eeprom/max6875.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/misc/eeprom/max6875.c b/drivers/misc/eeprom/max6875.c index 0e32709..fc0cf9a 100644 ---

Re: framebuffer corruption due to overlapping stp instructions on arm64

On Fri, Aug 03, 2018 at 09:16:39AM +0200, Ard Biesheuvel wrote: > On 3 August 2018 at 08:35, Mikulas Patocka wrote: > > > > > > On Thu, 2 Aug 2018, Matt Sealey wrote: > > > >> The easiest explanation for this would be that the memory isn?t mapped > >> correctly. You can?t use PCIe memory spaces

[PATCH v2 3/4] dt-bindings: phy: add DT bindings for UniPhier USB2 PHY driver

Add DT bindings for PHY interface built into USB2 controller implemented on Socionext UniPhier SoCs. Signed-off-by: Kunihiko Hayashi --- .../devicetree/bindings/phy/uniphier-usb2-phy.txt | 45 ++ 1 file changed, 45 insertions(+) create mode 100644

[PATCH v2 4/4] phy: socionext: add USB2 PHY driver for UniPhier SoC

Add a driver for PHY interface built into USB2 controller implemented on UniPhier SoCs. This driver supports HS-PHY for Pro4 and LD11. Signed-off-by: Kunihiko Hayashi --- drivers/phy/socionext/Kconfig | 13 ++ drivers/phy/socionext/Makefile| 1 +

[PATCH v2 1/4] dt-bindings: phy: add DT bindings for UniPhier USB3 PHY driver

Add DT bindings for PHY interface built into USB3 controller implemented in UniPhier SoCs. Signed-off-by: Kunihiko Hayashi --- .../bindings/phy/uniphier-usb3-hsphy.txt | 69 ++ .../bindings/phy/uniphier-usb3-ssphy.txt | 57 ++ 2 files

[PATCH v2 2/4] phy: socionext: add USB3 PHY driver for UniPhier SoC

Add a driver for PHY interface built into USB3 controller implemented in UniPhier SoCs. This driver supports High-Speed PHY and Super-Speed PHY. Signed-off-by: Kunihiko Hayashi Signed-off-by: Motoya Tanigawa Signed-off-by: Masami Hiramatsu --- drivers/phy/Kconfig | 1

[PATCH v2 0/4] phy: socionext: add new UniPhier USB PHY driver support

This series adds support for PHY interface built into USB controller implemented in Socionext UniPhier SoCs. The USB3 PHY driver supports High-Speed PHY and Super-Speed PHY included in the USB3 glue layer, and the USB2 PHY driver supports High-Speed PHY integrated into system controller.

Re: [PATCH 1/3] perf auxtrace: Support for perf report -D for s390

Arnaldo, On Thu, Aug 02, 2018 at 09:49:09AM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Aug 02, 2018 at 09:46:20AM +0200, Thomas Richter escreveu: > > Add initial support for s390 auxiliary traces using the > > CPU-Measurement Sampling Facility. > > Could you please provide one or two

Re: Finish the GENERIC_IRQ_MULTI_HANDLER conversion

On Thu, 2 Aug 2018, Palmer Dabbelt wrote: > On Sun, 24 Jun 2018 06:15:25 PDT (-0700), t...@linutronix.de wrote: > > On Thu, 21 Jun 2018, Palmer Dabbelt wrote: > > > A while ago I sent a patch set that adds a GENERIC_IRQ_MULTI_HANDLER, > > > which is an exact copy of the existing IRQ_MULTI_HANDLER

Re: [PATCH v11 1/2] mfd: bd71837: mfd driver for ROHM BD71837 PMIC

Hi Matti, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on ljones-mfd/for-mfd-next] [also build test WARNING on v4.18-rc7 next-20180802] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH 21/46] dmaengine: bam_dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label err_unregister_dma Signed-off-by: Huang Shijie --- drivers/dma/qcom/bam_dma.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git

[PATCH 09/46] dmaengine: cppi41: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister Signed-off-by: Huang Shijie --- drivers/dma/ti/cppi41.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/ti/cppi41.c b/drivers/dma/ti/cppi41.c index

[PATCH 35/46] dmaengine: mtk-hsdma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/mediatek/mtk-hsdma.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/dma/mediatek/mtk-hsdma.c

[PATCH 24/46] dmaengine: nbpfaxi: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label e_dma_dev_unreg Signed-off-by: Huang Shijie --- drivers/dma/nbpfaxi.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/nbpfaxi.c

[PATCH 29/46] dmaengine: hidma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/qcom/hidma.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/dma/qcom/hidma.c b/drivers/dma/qcom/hidma.c index

[PATCH 28/46] dmaengine: rcar-dmac: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/sh/rcar-dmac.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/dma/sh/rcar-dmac.c b/drivers/dma/sh/rcar-dmac.c index

[PATCH 26/46] dmaengine: shdmac: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/sh/shdmac.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/dma/sh/shdmac.c b/drivers/dma/sh/shdmac.c index

[PATCH 41/46] dmaengine: at_hdmac: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/at_hdmac.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/dma/at_hdmac.c b/drivers/dma/at_hdmac.c index

[PATCH 46/46] dmaengine: add COMPILE_TEST for the drivers

We can do the compiling test with COMPILE_TEST. Thisi patch adds the COMPILE_TEST for the drivers. Signed-off-by: Huang Shijie --- drivers/dma/Kconfig| 24 drivers/dma/ti/Kconfig | 2 +- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git

[PATCH 44/46] dmaengine: dma-jz4740: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label err_unregister Signed-off-by: Huang Shijie --- drivers/dma/dma-jz4740.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/dma-jz4740.c

[PATCH 43/46] dmaengine: dma-jz4780: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label err_unregister_dev Signed-off-by: Huang Shijie --- drivers/dma/dma-jz4780.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

[PATCH 32/46] dmaengine: pl330: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/pl330.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c index

[PATCH 36/46] dmaengine: k3dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label of_dma_register_fail Signed-off-by: Huang Shijie --- drivers/dma/k3dma.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/k3dma.c

[PATCH 30/46] dmaengine: pxa_dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/pxa_dma.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/dma/pxa_dma.c b/drivers/dma/pxa_dma.c index

[PATCH 40/46] dmaengine: fsl-edma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/fsl-edma.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/dma/fsl-edma.c b/drivers/dma/fsl-edma.c index

[PATCH 42/46] dmaengine: at_xdmac: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label err_dma_unregister Signed-off-by: Huang Shijie --- drivers/dma/at_xdmac.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/at_xdmac.c

[PATCH 45/46] dmaengine: dma-axi-dmac: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label err_unregister_device Signed-off-by: Huang Shijie --- drivers/dma/dma-axi-dmac.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git

[PATCH 20/46] dmaengine: sirf-dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. remove label unreg_dma_dev Signed-off-by: Huang Shijie --- drivers/dma/sirf-dma.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/sirf-dma.c

[PATCH 33/46] dmaengine: pch_dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister. Signed-off-by: Huang Shijie --- drivers/dma/pch_dma.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/dma/pch_dma.c b/drivers/dma/pch_dma.c index

Re: [PATCH v2 15/18] serial: intel: Support more platform

On 8/3/2018 1:57 PM, Greg Kroah-Hartman wrote: On Fri, Aug 03, 2018 at 11:02:34AM +0800, Songjun Wu wrote: Support more platform. Signed-off-by: Songjun Wu --- Your changelog text makes no sense, sorry. Thanks for your comment. I will describe it more clearly.

Re: [PATCH 00/46] Use dmaenginem_async_device_register to simplify code

On 08/03/2018 09:19 AM, Huang Shijie wrote: > All the patches are using dmaenginem_async_device_register to simplify code > except the last one: > dmaengine: add COMPILE_TEST for the drivers > > I use the last one to do the compiler test. > There are still 20 drivers which do not use the >

Re: linux-next: manual merge of the mips tree with the kbuild tree

Hi Christoph, On Fri, 3 Aug 2018 09:12:26 +0200 Christoph Hellwig wrote: > > On Fri, Aug 03, 2018 at 04:42:52PM +1000, Stephen Rothwell wrote: > > > > On Fri, 3 Aug 2018 08:41:28 +0200 Christoph Hellwig wrote: > > > > > > On Fri, Aug 03, 2018 at 09:21:00AM +1000, Stephen Rothwell wrote: >

Re: [PATCH v5 4/4] clk: bd71837: Add driver for BD71837 PMIC clock

On Tue, Jul 31, 2018 at 11:28:58AM +0300, Matti Vaittinen wrote: > On Tue, Jun 26, 2018 at 11:13:19AM +0300, Matti Vaittinen wrote: > > On Mon, Jun 25, 2018 at 04:44:57PM -0700, Stephen Boyd wrote: > > > Quoting Matti Vaittinen (2018-06-12 01:23:54) > > > > On Tue, Jun 12, 2018 at 12:44:11AM

Re: [RFC v6 PATCH 2/2] mm: mmap: zap pages with read mmap_sem in munmap

On Fri 27-07-18 02:10:14, Yang Shi wrote: > When running some mmap/munmap scalability tests with large memory (i.e. > > 300GB), the below hung task issue may happen occasionally. > > INFO: task ps:14018 blocked for more than 120 seconds. >Tainted: GE

Re: framebuffer corruption due to overlapping stp instructions on arm64

On Fri, Aug 3, 2018 at 8:53 AM, Florian Weimer wrote: > On 08/03/2018 09:11 AM, Andrew Pinski wrote: >> >> Yes fix Links not to use memcpy on the framebuffer. >> It is undefined behavior to use device memory with memcpy. > > > Some (de facto) ABIs require that it is supported, though. For

Re: [PATCH 0/2] gpio: mvebu: Add support for multiple PWM lines

Hi Linus and Adita On dim., juil. 29 2018, Linus Walleij wrote: > Hoping for some review from Gergory, Ralph or Richard who all seem > to use this driver! Would it be possible to resend the series adding me in CC? I would like to comment the patches, but unfortunately it seems that I was in

Re: framebuffer corruption due to overlapping stp instructions on arm64

< snip> > I guess the semantics of a framebuffer are not strictly defined, but > the current reality is that it is expected to have memory semantics > (by Linux/glibc) > > Matt is saying fundamental properties of the underlying interconnects > (AMBA) make that impossible on ARM, but I'd like to

[tip:irq/core] arm64: Use the new GENERIC_IRQ_MULTI_HANDLER

Commit-ID: 78ae2e1cd845480caaa2f181fee64e51f679f5aa Gitweb: https://git.kernel.org/tip/78ae2e1cd845480caaa2f181fee64e51f679f5aa Author: Palmer Dabbelt AuthorDate: Fri, 22 Jun 2018 10:01:24 -0700 Committer: Thomas Gleixner CommitDate: Fri, 3 Aug 2018 12:14:09 +0200 arm64: Use the new

[tip:irq/core] openrisc: Use the new GENERIC_IRQ_MULTI_HANDLER

Commit-ID: c5ca4560de0f04a3c872bdd17ae3378762c66bd2 Gitweb: https://git.kernel.org/tip/c5ca4560de0f04a3c872bdd17ae3378762c66bd2 Author: Palmer Dabbelt AuthorDate: Fri, 22 Jun 2018 10:01:25 -0700 Committer: Thomas Gleixner CommitDate: Fri, 3 Aug 2018 12:14:09 +0200 openrisc: Use the

Re: [alsa-devel] [PATCH 0/4] ALSA: Mark expected switch fall-throughs

On Thu, 02 Aug 2018 22:40:08 +0200, Gustavo A. R. Silva wrote: > > Hi all, > > In preparation to enabling -Wimplicit-fallthrough, this patchset aims > to add some annotations in order to mark switch cases where we are > expecting to fall through. > > Thanks > > Gustavo A. R. Silva (4): >

[tip:irq/core] genirq/irqchip: Remove MULTI_IRQ_HANDLER as it's now obselete

Commit-ID: 4f7799d96e6621ce584df60739e1480a6fd89f0a Gitweb: https://git.kernel.org/tip/4f7799d96e6621ce584df60739e1480a6fd89f0a Author: Palmer Dabbelt AuthorDate: Fri, 22 Jun 2018 10:01:26 -0700 Committer: Thomas Gleixner CommitDate: Fri, 3 Aug 2018 12:14:10 +0200 genirq/irqchip:

Re: [PATCH v1] mm:memcg: skip memcg of current in mem_cgroup_soft_limit_reclaim

On Fri, Aug 3, 2018 at 2:18 PM Michal Hocko wrote: > > On Fri 03-08-18 14:11:26, Zhaoyang Huang wrote: > > On Fri, Aug 3, 2018 at 1:48 PM Zhaoyang Huang > > wrote: > > > > > > for the soft_limit reclaim has more directivity than global reclaim, > > > we40960 > > > have current memcg be skipped

Re: [PATCH] mm: Move check for SHRINKER_NUMA_AWARE to do_shrink_slab()

On 02.08.2018 20:26, Yang Shi wrote: > On Thu, Aug 2, 2018 at 9:54 AM, Shakeel Butt wrote: >> On Thu, Aug 2, 2018 at 9:47 AM Yang Shi wrote: >>> >>> On Thu, Aug 2, 2018 at 4:00 AM, Kirill Tkhai wrote: In case of shrink_slab_memcg() we do not zero nid, when shrinker is not numa-aware.

Re: [PATCH] Input: cros_ec_keyb: Remove check before calling pm_wakeup_event.

Hi All, On 2018-06-06 00:44, Ravi Chandra Sadineni wrote: > Remove the unnecessary check before calling pm_wakeup_event. If the > device is not wake enabled, this call is no-op anyway. > > Signed-off-by: Ravi Chandra Sadineni This patch breaks suspend/resume on Samsung Exynos5250 Snow

[PATCH 11/46] dmaengine: tegra20-apb-dma: use helper dmaenginem_async_device_register

Use dmaenginem_async_device_register to simplify the code: remove dma_async_device_unregister remove the label err_unregister_dma_dev Signed-off-by: Huang Shijie --- drivers/dma/tegra20-apb-dma.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

Re: [RFC] perf annotate: option to report global percentage

Hi Jiri, On Tue, Jul 31, 2018 at 2:21 AM Jiri Olsa wrote: > > On Thu, Jul 19, 2018 at 10:25:39AM +0200, Jiri Olsa wrote: > > On Wed, Jul 18, 2018 at 02:55:14PM -0700, Stephane Eranian wrote: > > > Hi Jiri, > > > > > > As far as I know, once you go into annotate mode, via perf report TUI > > >

[PATCH 01/46] dmaengine: zx_dma: use dmaenginem_async_device_register to simplify the code

Use dmaenginem_async_device_register() to simplify the code. Remove the code calling dma_async_device_unregister(). Signed-off-by: Huang Shijie --- drivers/dma/zx_dma.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/dma/zx_dma.c b/drivers/dma/zx_dma.c index

Re: [PATCH 00/46] Use dmaenginem_async_device_register to simplify code

On Fri, Aug 03, 2018 at 09:51:43AM +0200, Lars-Peter Clausen wrote: > On 08/03/2018 09:19 AM, Huang Shijie wrote: > > All the patches are using dmaenginem_async_device_register to simplify code > > except the last one: > > dmaengine: add COMPILE_TEST for the drivers > > > > I use the last one

Re: [PATCH 1/4] genirq: Provide basic NMI management for interrupt lines

On Thu, 2 Aug 2018, Ricardo Neri wrote: > On Thu, Aug 02, 2018 at 11:40:55AM +0200, Thomas Gleixner wrote: > > Yes, focussing on "sane" architectures (by some definition of sane) where > > the NMI mode is just changing the delivery restrictions allows to still > > differentiate from which source

  1   2   3   4   5   6   7   8   9   10   >