Re: [PATCH] ARM: dts: da850: specify the maximum bandwidth for tilcdc

On Monday 28 November 2016 01:12 PM, Tomi Valkeinen wrote: > On 28/11/16 07:24, Sekhar Nori wrote: >> On Friday 25 November 2016 09:07 PM, Bartosz Golaszewski wrote: >>> It has been determined that the maximum resolution supported correctly >>> by tilcdc rev1 on da850 SoCs is 800x600@60. Due to

Re: [PATCH] ARM: dts: da850: specify the maximum bandwidth for tilcdc

On Monday 28 November 2016 01:12 PM, Tomi Valkeinen wrote: > On 28/11/16 07:24, Sekhar Nori wrote: >> On Friday 25 November 2016 09:07 PM, Bartosz Golaszewski wrote: >>> It has been determined that the maximum resolution supported correctly >>> by tilcdc rev1 on da850 SoCs is 800x600@60. Due to

[PATCH 1/1] net: macb: ensure ordering write to re-enable RX smoothly

When a hardware issue happened as described by inline comments, the register write pattern looks like the following: + wmb(); There might be a memory barrier between these two write operations, so add wmb to ensure an flip from 0 to 1 for NCR. Signed-off-by: Zumeng Chen

[PATCH] bcma: add Dell Inspiron 3148

This is what is in the laptop: 01:00.0 Network controller [0280]: Broadcom Limited BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Dell Device [1028:0018] Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at b040 (64-bit, non-prefetchable) [size=32K]

[PATCH 1/1] net: macb: ensure ordering write to re-enable RX smoothly

When a hardware issue happened as described by inline comments, the register write pattern looks like the following: + wmb(); There might be a memory barrier between these two write operations, so add wmb to ensure an flip from 0 to 1 for NCR. Signed-off-by: Zumeng Chen ---

[PATCH] bcma: add Dell Inspiron 3148

This is what is in the laptop: 01:00.0 Network controller [0280]: Broadcom Limited BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Dell Device [1028:0018] Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at b040 (64-bit, non-prefetchable) [size=32K]

[PATCH] dt-bindings: add MYIR Tech hardware vendor prefix

MYIR Tech Limited offers a range of ARM powered development boards and SoMs, for details reference a list on http://elinux.org/Development_Platforms#ARM or company's website http://myirtech.com Signed-off-by: Vladimir Zapolskiy ---

[PATCH] dt-bindings: add MYIR Tech hardware vendor prefix

MYIR Tech Limited offers a range of ARM powered development boards and SoMs, for details reference a list on http://elinux.org/Development_Platforms#ARM or company's website http://myirtech.com Signed-off-by: Vladimir Zapolskiy --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1

RE: [PATCH v2] fsl/usb: Workarourd for USB erratum-A005697

Thanks a lot, Alan, I will send the v3 with your suggestion. Best Regards Jerry Huang -Original Message- From: Alan Stern [mailto:st...@rowland.harvard.edu] Sent: Friday, November 25, 2016 11:14 PM To: Jerry Huang Cc: gre...@linuxfoundation.org; Ramneek Mehresh

RE: [PATCH v2] fsl/usb: Workarourd for USB erratum-A005697

Thanks a lot, Alan, I will send the v3 with your suggestion. Best Regards Jerry Huang -Original Message- From: Alan Stern [mailto:st...@rowland.harvard.edu] Sent: Friday, November 25, 2016 11:14 PM To: Jerry Huang Cc: gre...@linuxfoundation.org; Ramneek Mehresh ;

[PATCH] x86/traps: get rid of unnecessary preempt_disable/preempt_enable_no_resched

Exception handlers which may run on IST stack calls ist_enter() at the start of execution and ist_exit() in the end. The ist_enter() disables preemption unconditionally and ist_exit() enables it. Besides this, such exception handlers do additional unnecessary calls of preempt_disable() and

[PATCH] x86/traps: get rid of unnecessary preempt_disable/preempt_enable_no_resched

Exception handlers which may run on IST stack calls ist_enter() at the start of execution and ist_exit() in the end. The ist_enter() disables preemption unconditionally and ist_exit() enables it. Besides this, such exception handlers do additional unnecessary calls of preempt_disable() and

Re: virtio gpu sparse warning

On Do, 2016-11-24 at 04:57 +0200, Michael S. Tsirkin wrote: > sparse produces these warnings: > > drivers/gpu/drm/virtio/virtgpu_fb.c:340:27: warning: incorrect type in > assignment (different address spaces) > drivers/gpu/drm/virtio/virtgpu_fb.c:340:27:expected char [noderef] > *screen_base

Re: virtio gpu sparse warning

On Do, 2016-11-24 at 04:57 +0200, Michael S. Tsirkin wrote: > sparse produces these warnings: > > drivers/gpu/drm/virtio/virtgpu_fb.c:340:27: warning: incorrect type in > assignment (different address spaces) > drivers/gpu/drm/virtio/virtgpu_fb.c:340:27:expected char [noderef] > *screen_base

Re: [GIT PULL] stm class/intel_th: Updates for char-misc-next

On Wed, Nov 23, 2016 at 01:45:16PM +0200, Alexander Shishkin wrote: > Hi Greg, > > Let's try again. These are my updates for STM and Intel TH for > v4.10. Please consider pulling. Thanks. > > The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6: > > Linux 4.9-rc5

Re: [GIT PULL] stm class/intel_th: Updates for char-misc-next

On Wed, Nov 23, 2016 at 01:45:16PM +0200, Alexander Shishkin wrote: > Hi Greg, > > Let's try again. These are my updates for STM and Intel TH for > v4.10. Please consider pulling. Thanks. > > The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6: > > Linux 4.9-rc5

Re: [GIT PULL] phy: for 4.10

On Fri, Nov 18, 2016 at 06:58:23PM +0530, Kishon Vijay Abraham I wrote: > Hi Greg, > > Please find the pull request for 4.10 merge window below. Major changes > include adding anew phy driver for meson8b/gxbb SoC, removing a couple > of phy drivers from unsupported SoCs, adding sysfs entry to

Re: [GIT PULL] extcon next for v4.10

On Tue, Nov 22, 2016 at 03:08:03PM +0900, Chanwoo Choi wrote: > Dear Greg, > > This is extcon-next pull request for v4.10. I add detailed description of > this pull request on below. Please pull extcon with following updates. > > Best Regards, > Chanwoo Choi > > The following changes since

Re: [GIT PULL] phy: for 4.10

On Fri, Nov 18, 2016 at 06:58:23PM +0530, Kishon Vijay Abraham I wrote: > Hi Greg, > > Please find the pull request for 4.10 merge window below. Major changes > include adding anew phy driver for meson8b/gxbb SoC, removing a couple > of phy drivers from unsupported SoCs, adding sysfs entry to

Re: [GIT PULL] extcon next for v4.10

On Tue, Nov 22, 2016 at 03:08:03PM +0900, Chanwoo Choi wrote: > Dear Greg, > > This is extcon-next pull request for v4.10. I add detailed description of > this pull request on below. Please pull extcon with following updates. > > Best Regards, > Chanwoo Choi > > The following changes since

Re: [PATCH] ARM: dts: da850: specify the maximum bandwidth for tilcdc

On 28/11/16 07:24, Sekhar Nori wrote: > On Friday 25 November 2016 09:07 PM, Bartosz Golaszewski wrote: >> It has been determined that the maximum resolution supported correctly >> by tilcdc rev1 on da850 SoCs is 800x600@60. Due to memory throughput >> constraints we must filter out higher modes.

Re: [PATCH] ARM: dts: da850: specify the maximum bandwidth for tilcdc

On 28/11/16 07:24, Sekhar Nori wrote: > On Friday 25 November 2016 09:07 PM, Bartosz Golaszewski wrote: >> It has been determined that the maximum resolution supported correctly >> by tilcdc rev1 on da850 SoCs is 800x600@60. Due to memory throughput >> constraints we must filter out higher modes.

Re: [PATCH v3 10/30] perf clang: Add builtin clang support ant test case

On 2016/11/27 1:17, Alexei Starovoitov wrote: On Sat, Nov 26, 2016 at 07:03:34AM +, Wang Nan wrote: Add basic clang support in clang.cpp and test__clang() testcase. The first testcase checks if builtin clang is able to generate LLVM IR. tests/clang.c is a proxy. Real testcase resides in

Re: [PATCH v3 10/30] perf clang: Add builtin clang support ant test case

On 2016/11/27 1:17, Alexei Starovoitov wrote: On Sat, Nov 26, 2016 at 07:03:34AM +, Wang Nan wrote: Add basic clang support in clang.cpp and test__clang() testcase. The first testcase checks if builtin clang is able to generate LLVM IR. tests/clang.c is a proxy. Real testcase resides in

Re: [PATCH v2] usb: xhci: Remove unuseful 'return' and 'break' statement

On 28 November 2016 at 15:21, Greg KH wrote: > On Mon, Nov 28, 2016 at 02:29:25PM +0800, Baolin Wang wrote: >> Hi Mathias, >> >> On 24 November 2016 at 19:16, Baolin Wang wrote: >> > Since these 'return' statements are not generally useful in

Re: [PATCH v2] usb: xhci: Remove unuseful 'return' and 'break' statement

On 28 November 2016 at 15:21, Greg KH wrote: > On Mon, Nov 28, 2016 at 02:29:25PM +0800, Baolin Wang wrote: >> Hi Mathias, >> >> On 24 November 2016 at 19:16, Baolin Wang wrote: >> > Since these 'return' statements are not generally useful in void >> > function, remove them. Also remove one

Re: [PATCH v6 0/6] Introduce ZONE_CMA

On Mon, Nov 07, 2016 at 03:25:01PM +0900, Joonsoo Kim wrote: > On Fri, Oct 14, 2016 at 12:03:10PM +0900, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Hello, > > > > Changes from v5 > > o Add acked/reviewed-by tag from Vlastimil and Aneesh > > o Rebase on

Re: [PATCH v6 0/6] Introduce ZONE_CMA

On Mon, Nov 07, 2016 at 03:25:01PM +0900, Joonsoo Kim wrote: > On Fri, Oct 14, 2016 at 12:03:10PM +0900, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Hello, > > > > Changes from v5 > > o Add acked/reviewed-by tag from Vlastimil and Aneesh > > o Rebase on next-20161013 > > o Cosmetic

Re: [PATCH] cpuset: Remove unused 'struct cpuset*' variable

On Sat 26-11-16 08:42:40, Li Zefan wrote: > On 2016/11/25 17:46, Arnd Bergmann wrote: > > On Friday, November 25, 2016 1:46:04 PM CET Zefan Li wrote: > >> On 2016/11/25 12:55, Kirtika Ruchandani wrote: > >>> 'struct cpuset* cs' that is set but not used, was introduced in commit > >>> 1f7dd3e5a6e4

Re: [PATCH] cpuset: Remove unused 'struct cpuset*' variable

On Sat 26-11-16 08:42:40, Li Zefan wrote: > On 2016/11/25 17:46, Arnd Bergmann wrote: > > On Friday, November 25, 2016 1:46:04 PM CET Zefan Li wrote: > >> On 2016/11/25 12:55, Kirtika Ruchandani wrote: > >>> 'struct cpuset* cs' that is set but not used, was introduced in commit > >>> 1f7dd3e5a6e4

Re: [patch] mm, slab: faster active and free stats

On Fri, Nov 11, 2016 at 02:30:39AM -0800, David Rientjes wrote: > On Fri, 11 Nov 2016, Joonsoo Kim wrote: > > > Hello, David. > > > > Maintaining acitve/free_slab counters looks so complex. And, I think > > that we don't need to maintain these counters for faster slabinfo. > > Key point is to

Re: [patch] mm, slab: faster active and free stats

On Fri, Nov 11, 2016 at 02:30:39AM -0800, David Rientjes wrote: > On Fri, 11 Nov 2016, Joonsoo Kim wrote: > > > Hello, David. > > > > Maintaining acitve/free_slab counters looks so complex. And, I think > > that we don't need to maintain these counters for faster slabinfo. > > Key point is to

Re: Adding a .platform_init callback to sdhci_arasan_ops

+Sai for Xilinx perspective. On 25.11.2016 16:24, Sebastian Frias wrote: > Hi, > > When using the Arasan SDHCI HW IP, there is a set of parameters called > "Hardware initialized registers" > > (Table 7, Section "Pin Signals", page 56 of Arasan "SD3.0/SDIO3.0/eMMC4.4 > AHB Host Controller",

Re: Adding a .platform_init callback to sdhci_arasan_ops

+Sai for Xilinx perspective. On 25.11.2016 16:24, Sebastian Frias wrote: > Hi, > > When using the Arasan SDHCI HW IP, there is a set of parameters called > "Hardware initialized registers" > > (Table 7, Section "Pin Signals", page 56 of Arasan "SD3.0/SDIO3.0/eMMC4.4 > AHB Host Controller",

Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup

On Sun, Nov 27, 2016 at 04:59:14PM -0700, Jonathan Corbet wrote: > On Fri, 25 Nov 2016 22:58:14 +0100 > Peter Zijlstra wrote: > > > Not a fan of this. The atomic_ops.txt file needs a lot of love, and I > > wouldn't want to edit a .rst file. > > > > Then again, I probably

Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup

On Sun, Nov 27, 2016 at 04:59:14PM -0700, Jonathan Corbet wrote: > On Fri, 25 Nov 2016 22:58:14 +0100 > Peter Zijlstra wrote: > > > Not a fan of this. The atomic_ops.txt file needs a lot of love, and I > > wouldn't want to edit a .rst file. > > > > Then again, I probably won't actually get

Re: linux-next: build warning after merge of the wireless-drivers-next tree

Stephen Rothwell writes: > Hi all, > > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) produced this warning: > > In file included from include/linux/usb/ch9.h:35:0, > from include/linux/usb.h:5, >

Re: linux-next: build warning after merge of the wireless-drivers-next tree

Stephen Rothwell writes: > Hi all, > > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) produced this warning: > > In file included from include/linux/usb/ch9.h:35:0, > from include/linux/usb.h:5, > from >

[tip:x86/urgent] x86/build: Annotate die() with noreturn to fix build warning on clang

Commit-ID: adee8705d2517f0e163ffc45e8d7f9e97a58f1f6 Gitweb: http://git.kernel.org/tip/adee8705d2517f0e163ffc45e8d7f9e97a58f1f6 Author: Peter Foley AuthorDate: Sat, 26 Nov 2016 17:22:29 -0500 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016

[tip:x86/build] x86/build: Remove three unneeded genhdr-y entries

Commit-ID: 9190e21780dfeff524a67c6e7b806c8a9d496086 Gitweb: http://git.kernel.org/tip/9190e21780dfeff524a67c6e7b806c8a9d496086 Author: Paul Bolle AuthorDate: Fri, 25 Nov 2016 13:41:47 +0100 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016

[tip:x86/urgent] x86/build: Annotate die() with noreturn to fix build warning on clang

Commit-ID: adee8705d2517f0e163ffc45e8d7f9e97a58f1f6 Gitweb: http://git.kernel.org/tip/adee8705d2517f0e163ffc45e8d7f9e97a58f1f6 Author: Peter Foley AuthorDate: Sat, 26 Nov 2016 17:22:29 -0500 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016 07:47:22 +0100 x86/build: Annotate die()

[tip:x86/build] x86/build: Remove three unneeded genhdr-y entries

Commit-ID: 9190e21780dfeff524a67c6e7b806c8a9d496086 Gitweb: http://git.kernel.org/tip/9190e21780dfeff524a67c6e7b806c8a9d496086 Author: Paul Bolle AuthorDate: Fri, 25 Nov 2016 13:41:47 +0100 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016 07:49:17 +0100 x86/build: Remove three

[tip:x86/urgent] x86/unwind: Fix guess-unwinder regression

Commit-ID: 55f856e640560494518eaf24fe9d2d2089fba71a Gitweb: http://git.kernel.org/tip/55f856e640560494518eaf24fe9d2d2089fba71a Author: Josh Poimboeuf AuthorDate: Sun, 27 Nov 2016 23:13:07 -0600 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016

[tip:x86/urgent] x86/platform/olpc: Fix resume handler build warning

Commit-ID: 20ab6677716c7bbdcfd1cdb9aef296a0b3101f73 Gitweb: http://git.kernel.org/tip/20ab6677716c7bbdcfd1cdb9aef296a0b3101f73 Author: Borislav Petkov AuthorDate: Sat, 26 Nov 2016 15:27:06 +0100 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016

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

Marc, could you try this patch please? I think it should be pretty clear it should help you but running it through your use case would be more than welcome before I ask Greg to take this to the 4.8 stable tree. Thanks! On Wed 23-11-16 07:34:10, Michal Hocko wrote: [...] > commit

[tip:x86/build] x86/build: Don't use $(LINUXINCLUDE) twice

Commit-ID: 06cbbac0f57d947656a12c30a0a69d4cf0ac6dea Gitweb: http://git.kernel.org/tip/06cbbac0f57d947656a12c30a0a69d4cf0ac6dea Author: Paul Bolle AuthorDate: Fri, 25 Nov 2016 13:38:34 +0100 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016

[tip:x86/urgent] x86/unwind: Fix guess-unwinder regression

Commit-ID: 55f856e640560494518eaf24fe9d2d2089fba71a Gitweb: http://git.kernel.org/tip/55f856e640560494518eaf24fe9d2d2089fba71a Author: Josh Poimboeuf AuthorDate: Sun, 27 Nov 2016 23:13:07 -0600 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016 07:47:54 +0100 x86/unwind: Fix

[tip:x86/urgent] x86/platform/olpc: Fix resume handler build warning

Commit-ID: 20ab6677716c7bbdcfd1cdb9aef296a0b3101f73 Gitweb: http://git.kernel.org/tip/20ab6677716c7bbdcfd1cdb9aef296a0b3101f73 Author: Borislav Petkov AuthorDate: Sat, 26 Nov 2016 15:27:06 +0100 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016 07:46:03 +0100 x86/platform/olpc: Fix

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

Marc, could you try this patch please? I think it should be pretty clear it should help you but running it through your use case would be more than welcome before I ask Greg to take this to the 4.8 stable tree. Thanks! On Wed 23-11-16 07:34:10, Michal Hocko wrote: [...] > commit

[tip:x86/build] x86/build: Don't use $(LINUXINCLUDE) twice

Commit-ID: 06cbbac0f57d947656a12c30a0a69d4cf0ac6dea Gitweb: http://git.kernel.org/tip/06cbbac0f57d947656a12c30a0a69d4cf0ac6dea Author: Paul Bolle AuthorDate: Fri, 25 Nov 2016 13:38:34 +0100 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016 07:49:17 +0100 x86/build: Don't use

[tip:x86/boot] x86/boot/64: Optimize fixmap page fixup

Commit-ID: 6248f4567442081994ad61c63bd9870e147983e0 Gitweb: http://git.kernel.org/tip/6248f4567442081994ad61c63bd9870e147983e0 Author: Borislav Petkov AuthorDate: Fri, 25 Nov 2016 12:14:48 +0100 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016

[tip:x86/boot] x86/boot/64: Optimize fixmap page fixup

Commit-ID: 6248f4567442081994ad61c63bd9870e147983e0 Gitweb: http://git.kernel.org/tip/6248f4567442081994ad61c63bd9870e147983e0 Author: Borislav Petkov AuthorDate: Fri, 25 Nov 2016 12:14:48 +0100 Committer: Ingo Molnar CommitDate: Mon, 28 Nov 2016 07:45:17 +0100 x86/boot/64: Optimize

Re: [PATCH v2] usb: xhci: Remove unuseful 'return' and 'break' statement

On Mon, Nov 28, 2016 at 02:29:25PM +0800, Baolin Wang wrote: > Hi Mathias, > > On 24 November 2016 at 19:16, Baolin Wang wrote: > > Since these 'return' statements are not generally useful in void > > function, remove them. Also remove one unuseful 'break' statement > >

Re: [PATCH v2] usb: xhci: Remove unuseful 'return' and 'break' statement

On Mon, Nov 28, 2016 at 02:29:25PM +0800, Baolin Wang wrote: > Hi Mathias, > > On 24 November 2016 at 19:16, Baolin Wang wrote: > > Since these 'return' statements are not generally useful in void > > function, remove them. Also remove one unuseful 'break' statement > > in

Re: [PATCH v18 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

On 25 November 2016 at 21:00, Mark Brown wrote: > On Tue, Nov 22, 2016 at 09:40:07AM +1100, NeilBrown wrote: > >> I agree that the question of where the responsibility for information >> aggregation lies is open for discussion. If fact all details on how >> things should work

Re: [PATCH v18 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

On 25 November 2016 at 21:00, Mark Brown wrote: > On Tue, Nov 22, 2016 at 09:40:07AM +1100, NeilBrown wrote: > >> I agree that the question of where the responsibility for information >> aggregation lies is open for discussion. If fact all details on how >> things should work are always open for

Re: drm: GPF in drm_getcap

On 28/11/16 03:55 PM, Daniel Vetter wrote: > On Sat, Nov 26, 2016 at 7:22 PM, David Herrmann wrote: >> On Sat, Nov 26, 2016 at 7:07 PM, Dmitry Vyukov wrote: >>> grep "card0" dmesg: >>> [5.298617] device: 'card0': device_add >>> [5.298946] PM:

Re: drm: GPF in drm_getcap

On 28/11/16 03:55 PM, Daniel Vetter wrote: > On Sat, Nov 26, 2016 at 7:22 PM, David Herrmann wrote: >> On Sat, Nov 26, 2016 at 7:07 PM, Dmitry Vyukov wrote: >>> grep "card0" dmesg: >>> [5.298617] device: 'card0': device_add >>> [5.298946] PM: Adding info for No Bus:card0 >>> [

Re: [PATCH] net: fec: turn on device when extracting statistics

28.11.2016 04:29, David Miller пишет: > From: Nikita Yushchenko > Date: Fri, 25 Nov 2016 13:02:00 +0300 > >> +int i, ret; >> + >> +ret = pm_runtime_get_sync(>pdev->dev); >> +if (IS_ERR_VALUE(ret)) { >> +memset(data, 0, sizeof(*data) *

Re: [PATCH] net: fec: turn on device when extracting statistics

28.11.2016 04:29, David Miller пишет: > From: Nikita Yushchenko > Date: Fri, 25 Nov 2016 13:02:00 +0300 > >> +int i, ret; >> + >> +ret = pm_runtime_get_sync(>pdev->dev); >> +if (IS_ERR_VALUE(ret)) { >> +memset(data, 0, sizeof(*data) * ARRAY_SIZE(fec_stats)); >> +

[PATCH] vxlan: fix a potential issue when create a new vxlan fdb entry.

vxlan_fdb_append may return error, so add the proper check, otherwise it will cause memory leak. Signed-off-by: Haishuang Yan --- drivers/net/vxlan.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/drivers/net/vxlan.c

[PATCH] vxlan: fix a potential issue when create a new vxlan fdb entry.

vxlan_fdb_append may return error, so add the proper check, otherwise it will cause memory leak. Signed-off-by: Haishuang Yan --- drivers/net/vxlan.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c index 21e92be..3b7b237

RE: BALANCE PAYMENT

Dear Sir/s, Please see attached. Thanks and regards, Accounts Department Al Omraniya Trading Co. LLC P.O. Box: 10757, Al Khabaisi Area, Deira 2, Dubai, U.A.E. Tel: +971 4 268 2730 / Fax: +971 4 268 4117

RE: BALANCE PAYMENT

Dear Sir/s, Please see attached. Thanks and regards, Accounts Department Al Omraniya Trading Co. LLC P.O. Box: 10757, Al Khabaisi Area, Deira 2, Dubai, U.A.E. Tel: +971 4 268 2730 / Fax: +971 4 268 4117

RE: [PATCH 0/7] hv: CPU onlining/offlining fixes and improvements

> From: Stephen Hemminger [mailto:step...@networkplumber.org] > Sent: Sunday, November 27, 2016 01:06 > To: Vitaly Kuznetsov > Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; KY Srinivasan > ; Haiyang Zhang ; Dexuan

[PATCH v2] clkdev: add devm_of_clk_get()

Current Linux has of_clk_get(), but doesn't have devm_of_clk_get(). This patch adds it. This is based on devm_clk_get() Signed-off-by: Kuninori Morimoto --- v1 -> v2 - update git log drivers/clk/clkdev.c | 26 ++ include/linux/clk.h

RE: [PATCH 0/7] hv: CPU onlining/offlining fixes and improvements

> From: Stephen Hemminger [mailto:step...@networkplumber.org] > Sent: Sunday, November 27, 2016 01:06 > To: Vitaly Kuznetsov > Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; KY Srinivasan > ; Haiyang Zhang ; Dexuan Cui > > Subject: Re: [PATCH 0/7] hv: CPU onlining/offlining

[PATCH v2] clkdev: add devm_of_clk_get()

Current Linux has of_clk_get(), but doesn't have devm_of_clk_get(). This patch adds it. This is based on devm_clk_get() Signed-off-by: Kuninori Morimoto --- v1 -> v2 - update git log drivers/clk/clkdev.c | 26 ++ include/linux/clk.h | 7 +++ 2 files changed, 33

Re: drm: GPF in drm_getcap

On Sat, Nov 26, 2016 at 7:22 PM, David Herrmann wrote: > On Sat, Nov 26, 2016 at 7:07 PM, Dmitry Vyukov wrote: >> grep "card0" dmesg: >> [5.298617] device: 'card0': device_add >> [5.298946] PM: Adding info for No Bus:card0 >> [6.436178]

Re: drm: GPF in drm_getcap

On Sat, Nov 26, 2016 at 7:22 PM, David Herrmann wrote: > On Sat, Nov 26, 2016 at 7:07 PM, Dmitry Vyukov wrote: >> grep "card0" dmesg: >> [5.298617] device: 'card0': device_add >> [5.298946] PM: Adding info for No Bus:card0 >> [6.436178] device: 'card0': device_add >> [6.436488]

RE: BALANCE PAYMENT

Dear Sir/s, Please see attached. Thanks and regards, Accounts Department Al Omraniya Trading Co. LLC P.O. Box: 10757, Al Khabaisi Area, Deira 2, Dubai, U.A.E. Tel: +971 4 268 2730 / Fax: +971 4 268 4117

RE: BALANCE PAYMENT

Dear Sir/s, Please see attached. Thanks and regards, Accounts Department Al Omraniya Trading Co. LLC P.O. Box: 10757, Al Khabaisi Area, Deira 2, Dubai, U.A.E. Tel: +971 4 268 2730 / Fax: +971 4 268 4117

Re: [PATCH 2/2] rcu: Force resched_cpu when jiffies >= rcu_state.jiffies_resched

On Sat, Nov 26, 2016 at 04:00:46AM -0800, Paul E. McKenney wrote: > On Fri, Nov 25, 2016 at 12:34:26AM -0800, Paul E. McKenney wrote: > > On Tue, Nov 22, 2016 at 05:12:20PM +0900, Byungchul Park wrote: > > > On Wed, Nov 09, 2016 at 03:32:15PM +0900, Byungchul Park wrote: > > > > Currently rcu code

Re: [PATCH 2/2] rcu: Force resched_cpu when jiffies >= rcu_state.jiffies_resched

On Sat, Nov 26, 2016 at 04:00:46AM -0800, Paul E. McKenney wrote: > On Fri, Nov 25, 2016 at 12:34:26AM -0800, Paul E. McKenney wrote: > > On Tue, Nov 22, 2016 at 05:12:20PM +0900, Byungchul Park wrote: > > > On Wed, Nov 09, 2016 at 03:32:15PM +0900, Byungchul Park wrote: > > > > Currently rcu code

[patch net] net: dsa: fix unbalanced dsa_switch_tree reference counting

_dsa_register_switch() gets a dsa_switch_tree object either via dsa_get_dst() or via dsa_add_dst(). Former path does not increase kref in returned object (resulting into caller not owning a reference), while later path does create a new object (resulting into caller owning a reference). The rest

[patch net] net: dsa: fix unbalanced dsa_switch_tree reference counting

_dsa_register_switch() gets a dsa_switch_tree object either via dsa_get_dst() or via dsa_add_dst(). Former path does not increase kref in returned object (resulting into caller not owning a reference), while later path does create a new object (resulting into caller owning a reference). The rest

[PATCH v4 2/2] usb: dwc3: core: Support the dwc3 host suspend/resume

For some mobile devices with strict power management, we also want to suspend the host when the slave is detached for power saving. Thus we add the host suspend/resume functions to support this requirement. Signed-off-by: Baolin Wang --- Changes since v3: - No updates.

[PATCH v4] Fixes for compiling with clang

Fix reversed conditional checking if HOSTCC is clang. Suppress warnings about unsupported optimization options. Suppress warnings about unused functions, as they are generated for every module and are therefore far too spammy. Disable clang's integrated assembler which is incompatible with kernel

[PATCH v4 2/2] usb: dwc3: core: Support the dwc3 host suspend/resume

For some mobile devices with strict power management, we also want to suspend the host when the slave is detached for power saving. Thus we add the host suspend/resume functions to support this requirement. Signed-off-by: Baolin Wang --- Changes since v3: - No updates. Changes since v2: -

[PATCH v4] Fixes for compiling with clang

Fix reversed conditional checking if HOSTCC is clang. Suppress warnings about unsupported optimization options. Suppress warnings about unused functions, as they are generated for every module and are therefore far too spammy. Disable clang's integrated assembler which is incompatible with kernel

[PATCH v4 1/2] usb: host: plat: Enable xhci plat runtime PM

Enable the xhci plat runtime PM for parent device to suspend/resume xhci. Also call pm_runtime_get_noresume() in probe() function in case the parent device doesn't call suspend/resume callback by runtime PM now. Signed-off-by: Baolin Wang --- Changes since v3: - Fix

[PATCH v4 1/2] usb: host: plat: Enable xhci plat runtime PM

Enable the xhci plat runtime PM for parent device to suspend/resume xhci. Also call pm_runtime_get_noresume() in probe() function in case the parent device doesn't call suspend/resume callback by runtime PM now. Signed-off-by: Baolin Wang --- Changes since v3: - Fix kbuild error. Changes since

Re: [PATCH v3 20/30] perf clang jit: add PerfModule::doJIT to JIT perfhook functions

On 2016/11/27 1:29, Alexei Starovoitov wrote: On Sat, Nov 26, 2016 at 07:03:44AM +, Wang Nan wrote: PerfModule::doJIT JIT compile perfhook functions and saves result into a map. Add a test case for it. At this stage perfhook functions can do no useful things because they can't invoke

Re: [PATCH v3 20/30] perf clang jit: add PerfModule::doJIT to JIT perfhook functions

On 2016/11/27 1:29, Alexei Starovoitov wrote: On Sat, Nov 26, 2016 at 07:03:44AM +, Wang Nan wrote: PerfModule::doJIT JIT compile perfhook functions and saves result into a map. Add a test case for it. At this stage perfhook functions can do no useful things because they can't invoke

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

Hi Boris, Stefan, > On Tue, 22 Nov 2016 13:04:11 -0800 > Stefan Agner wrote: > > > On 2016-11-01 00:10, Lukasz Majewski wrote: > > > From: Sascha Hauer > > > > > > The use of the ipg clock was introduced with commit 7b27c160c681 > > > ("pwm: i.MX: fix

Re: [PATCH v3 02/11] pwm: imx: remove ipg clock

Hi Boris, Stefan, > On Tue, 22 Nov 2016 13:04:11 -0800 > Stefan Agner wrote: > > > On 2016-11-01 00:10, Lukasz Majewski wrote: > > > From: Sascha Hauer > > > > > > The use of the ipg clock was introduced with commit 7b27c160c681 > > > ("pwm: i.MX: fix clock lookup"). > > > In the commit

RE: [PATCH 1/7] hv: acquire vmbus_connection.channel_mutex in vmbus_free_channels()

> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Friday, November 25, 2016 20:49 > To: de...@linuxdriverproject.org > Cc: linux-kernel@vger.kernel.org; KY Srinivasan ; Haiyang > Zhang ; Dexuan Cui ; > Stephen Hemminger

RE: [PATCH 1/7] hv: acquire vmbus_connection.channel_mutex in vmbus_free_channels()

> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Friday, November 25, 2016 20:49 > To: de...@linuxdriverproject.org > Cc: linux-kernel@vger.kernel.org; KY Srinivasan ; Haiyang > Zhang ; Dexuan Cui ; > Stephen Hemminger > Subject: [PATCH 1/7] hv: acquire vmbus_connection.channel_mutex

Re: [PATCH v3 14/30] perf clang: Support compile IR to BPF object and add testcase

On 2016/11/27 1:25, Alexei Starovoitov wrote: On Sat, Nov 26, 2016 at 07:03:38AM +, Wang Nan wrote: getBPFObjectFromModule() is introduced to compile LLVM IR(Module) to BPF object. Add new testcase for it. Test result: $ ./buildperf/perf test -v clang 51: Test builtin clang support

Re: [PATCH v3 14/30] perf clang: Support compile IR to BPF object and add testcase

On 2016/11/27 1:25, Alexei Starovoitov wrote: On Sat, Nov 26, 2016 at 07:03:38AM +, Wang Nan wrote: getBPFObjectFromModule() is introduced to compile LLVM IR(Module) to BPF object. Add new testcase for it. Test result: $ ./buildperf/perf test -v clang 51: Test builtin clang support

Re: [PATCH v2] usb: xhci: Remove unuseful 'return' and 'break' statement

Hi Mathias, On 24 November 2016 at 19:16, Baolin Wang wrote: > Since these 'return' statements are not generally useful in void > function, remove them. Also remove one unuseful 'break' statement > in xhci_setup_addressable_virt_dev() function. > > Signed-off-by: Baolin

Re: [PATCH v2] usb: xhci: Remove unuseful 'return' and 'break' statement

Hi Mathias, On 24 November 2016 at 19:16, Baolin Wang wrote: > Since these 'return' statements are not generally useful in void > function, remove them. Also remove one unuseful 'break' statement > in xhci_setup_addressable_virt_dev() function. > > Signed-off-by: Baolin Wang > --- > Changes

Talent Scout

Dear Concern, I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a Film Corporation Located in the United State, is Soliciting for the Right to use Your Photo/Face and Personality as One of the Semi -Major Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story of

Talent Scout

Dear Concern, I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a Film Corporation Located in the United State, is Soliciting for the Right to use Your Photo/Face and Personality as One of the Semi -Major Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story of

Re: [PATCH v2] ARM: dts: da850: add the mstpri and ddrctl nodes

On Wed, Nov 23, 2016 at 9:03 PM, Sekhar Nori wrote: > On Thursday 24 November 2016 04:18 AM, David Lechner wrote: >> On 11/23/2016 04:32 PM, Kevin Hilman wrote: >>> David Lechner writes: >>> On 11/23/2016 04:27 AM, Bartosz Golaszewski wrote: >

Re: [PATCH v2] ARM: dts: da850: add the mstpri and ddrctl nodes

On Wed, Nov 23, 2016 at 9:03 PM, Sekhar Nori wrote: > On Thursday 24 November 2016 04:18 AM, David Lechner wrote: >> On 11/23/2016 04:32 PM, Kevin Hilman wrote: >>> David Lechner writes: >>> On 11/23/2016 04:27 AM, Bartosz Golaszewski wrote: > 2016-11-22 23:23 GMT+01:00 David Lechner :

Re: [PATCH] md/raid5: limit request size according to implementation limits

On Mon, Nov 28, 2016 at 7:40 AM, Coly Li wrote: > On 2016/11/28 上午12:32, Konstantin Khlebnikov wrote: >> Current implementation employ 16bit counter of active stripes in lower >> bits of bio->bi_phys_segments. If request is big enough to overflow >> this counter bio will be

Re: [PATCH] md/raid5: limit request size according to implementation limits

On Mon, Nov 28, 2016 at 7:40 AM, Coly Li wrote: > On 2016/11/28 上午12:32, Konstantin Khlebnikov wrote: >> Current implementation employ 16bit counter of active stripes in lower >> bits of bio->bi_phys_segments. If request is big enough to overflow >> this counter bio will be completed and freed

linux-next: Tree for Nov 28

Hi all, Changes since 20161125: New tree: modules The mmc tree gained a conflict against the block tree. The edac-amd tree gained a conflict agaainst the edac tree. The kvm tree gained a conflict against the tip tree. The akpm-current tree still had its build failure for which I added a

linux-next: Tree for Nov 28

Hi all, Changes since 20161125: New tree: modules The mmc tree gained a conflict against the block tree. The edac-amd tree gained a conflict agaainst the edac tree. The kvm tree gained a conflict against the tip tree. The akpm-current tree still had its build failure for which I added a

  1   2   3   4   5   6   >