Re: [PATCH 00/13] Virtually mapped stacks with guard pages (x86, core)

On Fri, Jun 17, 2016 at 10:38:24AM -0700, Andy Lutomirski wrote: > > A disassembly looks like this (r15 is the stackpointer): > > > > 0670 : > > 670: eb 6f f0 48 00 24 stmg%r6,%r15,72(%r15) > > 676: c0 d0 00 00 00 00 larl%r13,676

Re: [PATCH 00/13] Virtually mapped stacks with guard pages (x86, core)

On Fri, Jun 17, 2016 at 10:38:24AM -0700, Andy Lutomirski wrote: > > A disassembly looks like this (r15 is the stackpointer): > > > > 0670 : > > 670: eb 6f f0 48 00 24 stmg%r6,%r15,72(%r15) > > 676: c0 d0 00 00 00 00 larl%r13,676 > > 67c:

Re: [v2 PATCH 2/4] phy: Add USB Type-C PHY driver for rk3399

Hi Guenter On 06/18/2016 11:45 PM, Guenter Roeck wrote: Hi Chris, On Mon, Jun 13, 2016 at 2:39 AM, Chris Zhong wrote: Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has

Re: [v2 PATCH 2/4] phy: Add USB Type-C PHY driver for rk3399

Hi Guenter On 06/18/2016 11:45 PM, Guenter Roeck wrote: Hi Chris, On Mon, Jun 13, 2016 at 2:39 AM, Chris Zhong wrote: Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components:

[PATCH] ddbridge: Replace vmalloc with vzalloc

vzalloc combines vmalloc and memset 0. The Coccinelle semantic patch used to make this change is as follows: @@ type T; T *d; expression e; statement S; @@ d = -vmalloc +vzalloc (...); if (!d) S - memset(d, 0, sizeof(T)); Signed-off-by:

[PATCH] ddbridge: Replace vmalloc with vzalloc

vzalloc combines vmalloc and memset 0. The Coccinelle semantic patch used to make this change is as follows: @@ type T; T *d; expression e; statement S; @@ d = -vmalloc +vzalloc (...); if (!d) S - memset(d, 0, sizeof(T)); Signed-off-by:

[PATCH v2 1/2] drm/dsi: Implement dcs set/get display brightness

Provide a small convenience wrapper that set/get the display brightness value Cc: John Stultz Cc: Sumit Semwal Cc: Archit Taneja Cc: Rob Clark Cc: Jani Nikula Cc:

[PATCH v7 2/2] drm/panel: Add JDI LT070ME05000 WUXGA DSI Panel

Add support for the JDI LT070ME05000 WUXGA DSI panel used in Nexus 7 2013 devices. Programming sequence for the panel is was originally found in the android-msm-flo-3.4-lollipop-release branch from: https://android.googlesource.com/kernel/msm.git And video mode setting is from

[PATCH v2 1/2] drm/dsi: Implement dcs set/get display brightness

Provide a small convenience wrapper that set/get the display brightness value Cc: John Stultz Cc: Sumit Semwal Cc: Archit Taneja Cc: Rob Clark Cc: Jani Nikula Cc: Thierry Reding Signed-off-by: Vinay Simha BN --- v1: *tested in nexus7 2nd gen. v2: * implemented jani review comments

[PATCH v7 2/2] drm/panel: Add JDI LT070ME05000 WUXGA DSI Panel

Add support for the JDI LT070ME05000 WUXGA DSI panel used in Nexus 7 2013 devices. Programming sequence for the panel is was originally found in the android-msm-flo-3.4-lollipop-release branch from: https://android.googlesource.com/kernel/msm.git And video mode setting is from

[PATCH] ACPICA: Use acpi_os_allocate_zeroed

acpi_os_allocate_zeroed combines acpi_os_allocate and memset 0. The Coccinelle semantic patch used to make this change is as follows: @@ type T; T *d; expression e; statement S; @@ d = -acpi_os_allocate +acpi_os_allocate_zeroed (...); if (!d)

[PATCH] ACPICA: Use acpi_os_allocate_zeroed

acpi_os_allocate_zeroed combines acpi_os_allocate and memset 0. The Coccinelle semantic patch used to make this change is as follows: @@ type T; T *d; expression e; statement S; @@ d = -acpi_os_allocate +acpi_os_allocate_zeroed (...); if (!d)

Re: [PATCH v5 0/7] /dev/random - a new approach

Am Sonntag, 19. Juni 2016, 21:36:14 schrieb Pavel Machek: Hi Pavel, > On Sun 2016-06-19 17:58:41, Stephan Mueller wrote: > > Hi Herbert, Ted, > > > > The following patch set provides a different approach to /dev/random which > > I call Linux Random Number Generator (LRNG) to collect entropy

Re: [PATCH v5 0/7] /dev/random - a new approach

Am Sonntag, 19. Juni 2016, 21:36:14 schrieb Pavel Machek: Hi Pavel, > On Sun 2016-06-19 17:58:41, Stephan Mueller wrote: > > Hi Herbert, Ted, > > > > The following patch set provides a different approach to /dev/random which > > I call Linux Random Number Generator (LRNG) to collect entropy

Re: [PATCH] clk: samsung: exynos5433: use clock_ignore_unused flag for SPI3 related clocks

Hi Tomasz, > >> > The SPI 3 bus uses two clocks, a bus clock and an input clock. > >> > Do not disable the clocks when unused in order to allow access to > >> > the SPI 3 device. > >> > >> If unused, why would access to SPI 3 device needed? > > > > because next I will submit a small driver which

Re: [PATCH] clk: samsung: exynos5433: use clock_ignore_unused flag for SPI3 related clocks

Hi Tomasz, > >> > The SPI 3 bus uses two clocks, a bus clock and an input clock. > >> > Do not disable the clocks when unused in order to allow access to > >> > the SPI 3 device. > >> > >> If unused, why would access to SPI 3 device needed? > > > > because next I will submit a small driver which

Re: [RFC PATCH] net: macb: Add gmii2rgmii converter support

On June 19, 2016 10:27:17 PM MST, Kedareswara rao Appana wrote: >This patch adds support for gmii2rgmii converter >in the macb driver. > >The GMII to RGMII IP core provides the >Reduced Gigabit Media Independent Interface >(RGMII) between Ethernet physical media

Re: [RFC PATCH] net: macb: Add gmii2rgmii converter support

On June 19, 2016 10:27:17 PM MST, Kedareswara rao Appana wrote: >This patch adds support for gmii2rgmii converter >in the macb driver. > >The GMII to RGMII IP core provides the >Reduced Gigabit Media Independent Interface >(RGMII) between Ethernet physical media devices >And the Gigabit Ethernet

Re: Add mt6755 basic chip support

On Tue, 2016-06-14 at 10:20 +0800, Mars Cheng wrote: > This patch adds basic support for Mediatek's new 8-core chip, mt6755. > It is also named as Helio P10. It is based on 4.7-rc1 > > Mars Cheng (2): > Document: DT: Add bindings for mediatek MT6755 SoC Platform > arm64: dts: mediatek: add

Re: Add mt6755 basic chip support

On Tue, 2016-06-14 at 10:20 +0800, Mars Cheng wrote: > This patch adds basic support for Mediatek's new 8-core chip, mt6755. > It is also named as Helio P10. It is based on 4.7-rc1 > > Mars Cheng (2): > Document: DT: Add bindings for mediatek MT6755 SoC Platform > arm64: dts: mediatek: add

RE: [PATCH net-next] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

Hi all, A very limited review below. + + /* get capabilities of particular feature */ + ENA_ADMIN_GET_FEATURE = 8, Instead /* get capabilities SHOULD BE: /* set capabilities . + + /* get capabilities of particular feature */ + ENA_ADMIN_SET_FEATURE = 9, + ..

RE: [PATCH net-next] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

Hi all, A very limited review below. + + /* get capabilities of particular feature */ + ENA_ADMIN_GET_FEATURE = 8, Instead /* get capabilities SHOULD BE: /* set capabilities . + + /* get capabilities of particular feature */ + ENA_ADMIN_SET_FEATURE = 9, + ..

[PATCH 5/6] staging: rtl8188eu: remove EFUSE_GetEfuseDefinition function

This function does not used. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c| 63 --- drivers/staging/rtl8188eu/include/rtw_efuse.h | 2 - 2 files changed, 65 deletions(-) diff --git

[PATCH 5/6] staging: rtl8188eu: remove EFUSE_GetEfuseDefinition function

This function does not used. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c| 63 --- drivers/staging/rtl8188eu/include/rtw_efuse.h | 2 - 2 files changed, 65 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c

[PATCH 6/6] staging: rtl8188eu: remove _EFUSE_DEF_TYPE enum

This enumeration does not used. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/include/rtw_efuse.h | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/staging/rtl8188eu/include/rtw_efuse.h b/drivers/staging/rtl8188eu/include/rtw_efuse.h index

[PATCH 2/6] staging: rtl8188eu: remove efuse_max variable in hal_EfusePartialWriteCheck

This variable does not used after assigning value. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c

[PATCH 1/6] staging: rtl8188eu: replace EFUSE_GetEfuseDefinition(..., TYPE_EFUSE_MAP_LEN, ...) call with it's result (EFUSE_MAP_LEN_88E)

This makes the code easier to read. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c | 18 +++--- 1 file changed, 3 insertions(+), 15 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c

[PATCH 3/6] staging: rtl8188eu: replace EFUSE_GetEfuseDefinition(..., TYPE_EFUSE_MAX_SECTION, ) with a = EFUSE_MAX_SECTION_88E

This makes the code easier to read. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c b/drivers/staging/rtl8188eu/core/rtw_efuse.c

[PATCH 2/6] staging: rtl8188eu: remove efuse_max variable in hal_EfusePartialWriteCheck

This variable does not used after assigning value. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c b/drivers/staging/rtl8188eu/core/rtw_efuse.c index

[PATCH 1/6] staging: rtl8188eu: replace EFUSE_GetEfuseDefinition(..., TYPE_EFUSE_MAP_LEN, ...) call with it's result (EFUSE_MAP_LEN_88E)

This makes the code easier to read. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c | 18 +++--- 1 file changed, 3 insertions(+), 15 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c b/drivers/staging/rtl8188eu/core/rtw_efuse.c index

[PATCH 3/6] staging: rtl8188eu: replace EFUSE_GetEfuseDefinition(..., TYPE_EFUSE_MAX_SECTION, ) with a = EFUSE_MAX_SECTION_88E

This makes the code easier to read. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c b/drivers/staging/rtl8188eu/core/rtw_efuse.c index 9d5bd43..1e96a81

[PATCH 6/6] staging: rtl8188eu: remove _EFUSE_DEF_TYPE enum

This enumeration does not used. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/include/rtw_efuse.h | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/staging/rtl8188eu/include/rtw_efuse.h b/drivers/staging/rtl8188eu/include/rtw_efuse.h index 9e7d135..168c12d

[RFC PATCH] net: macb: Add gmii2rgmii converter support

This patch adds support for gmii2rgmii converter in the macb driver. The GMII to RGMII IP core provides the Reduced Gigabit Media Independent Interface (RGMII) between Ethernet physical media devices And the Gigabit Ethernet controller. This core can switch dynamically between the Three different

[PATCH 4/6] staging: rtl8188eu: replace EFUSE_GetEfuseDefinition(..., TYPE_AVAILABLE_EFUSE_BYTES_BANK, ) call with a = (EFUSE_REAL_CONTENT_LEN_88E - EFUSE_OOB_PROTECT_BYTES_88E)

This makes the code easier to read. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c

[RFC PATCH] net: macb: Add gmii2rgmii converter support

This patch adds support for gmii2rgmii converter in the macb driver. The GMII to RGMII IP core provides the Reduced Gigabit Media Independent Interface (RGMII) between Ethernet physical media devices And the Gigabit Ethernet controller. This core can switch dynamically between the Three different

[PATCH 4/6] staging: rtl8188eu: replace EFUSE_GetEfuseDefinition(..., TYPE_AVAILABLE_EFUSE_BYTES_BANK, ) call with a = (EFUSE_REAL_CONTENT_LEN_88E - EFUSE_OOB_PROTECT_BYTES_88E)

This makes the code easier to read. Signed-off-by: Ivan Safonov --- drivers/staging/rtl8188eu/core/rtw_efuse.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c b/drivers/staging/rtl8188eu/core/rtw_efuse.c index

Re: [PATCH v6 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Frank, On Sun, Jun 19, 2016 at 8:32 PM, Frank Wang wrote: > Hi Heiko & Guenter, > > > On 2016/6/20 11:00, Guenter Roeck wrote: >> >> On Sun, Jun 19, 2016 at 6:27 PM, Frank Wang >> wrote: >>> >>> Hi Guenter, >>> >>> >>> On 2016/6/17 21:20,

Re: [PATCH v6 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Hi Frank, On Sun, Jun 19, 2016 at 8:32 PM, Frank Wang wrote: > Hi Heiko & Guenter, > > > On 2016/6/20 11:00, Guenter Roeck wrote: >> >> On Sun, Jun 19, 2016 at 6:27 PM, Frank Wang >> wrote: >>> >>> Hi Guenter, >>> >>> >>> On 2016/6/17 21:20, Guenter Roeck wrote: Hi Frank, On

[PATCH 4/5] fs/buffer.c: Remove trailing white space

Trailing white space is not accepted in kernel coding style. Remove them. Signed-off-by: Byungchul Park --- fs/buffer.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/fs/buffer.c b/fs/buffer.c index e1632ab..a75ca74 100644

[PATCH 4/5] fs/buffer.c: Remove trailing white space

Trailing white space is not accepted in kernel coding style. Remove them. Signed-off-by: Byungchul Park --- fs/buffer.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/fs/buffer.c b/fs/buffer.c index e1632ab..a75ca74 100644 --- a/fs/buffer.c +++

[PATCH 3/5] lockdep: Apply bit_spin_lock lockdep to zram

In order to use lockdep-enabled bit_spin_lock, we have to call bit_spin_init() when a instance including the bit used as lock creates, and bit_spin_free() when the instance including the bit destroys. The zram is one of bit_spin_lock users. And this patch adds bit_spin_init() and bit_spin_free()

[PATCH] staging: unisys: visorbus: Replace semaphore with mutex

The semaphore 'visordriver_callback_lock' is a simple mutex, so it should be written as one. Semaphores are going away in the future. Signed-off-by: Binoy Jayan --- drivers/staging/unisys/include/visorbus.h | 3 ++- drivers/staging/unisys/visorbus/visorbus_main.c

[RFC 06/12] lockdep: Apply crossrelease to completion

wait_for_complete() and its family can cause deadlock. Nevertheless, it cannot use the lock correntness validator because complete() will be called in different context from the context calling wait_for_complete(), which violates original lockdep's assumption. However, thanks to

[PATCH] staging: unisys: visorbus: Replace semaphore with mutex

The semaphore 'visordriver_callback_lock' is a simple mutex, so it should be written as one. Semaphores are going away in the future. Signed-off-by: Binoy Jayan --- drivers/staging/unisys/include/visorbus.h | 3 ++- drivers/staging/unisys/visorbus/visorbus_main.c | 14 +++--- 2

[RFC 06/12] lockdep: Apply crossrelease to completion

wait_for_complete() and its family can cause deadlock. Nevertheless, it cannot use the lock correntness validator because complete() will be called in different context from the context calling wait_for_complete(), which violates original lockdep's assumption. However, thanks to

[PATCH 3/5] lockdep: Apply bit_spin_lock lockdep to zram

In order to use lockdep-enabled bit_spin_lock, we have to call bit_spin_init() when a instance including the bit used as lock creates, and bit_spin_free() when the instance including the bit destroys. The zram is one of bit_spin_lock users. And this patch adds bit_spin_init() and bit_spin_free()

[RFC 10/12] mm/swap_state.c: Remove trailing white space

Trailing white space is not accepted in kernel coding style. Remove them. Signed-off-by: Byungchul Park --- mm/swap_state.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/mm/swap_state.c b/mm/swap_state.c index 69cb246..3fb7013 100644 ---

[RFC 01/12] lockdep: Refactor lookup_chain_cache()

Currently, lookup_chain_cache() provides both "lookup" and "add" functionalities in a function. However each one is useful indivisually. Some features, e.g. crossrelease, can use each one indivisually. Thus, splited these functionalities into 2 functions. Signed-off-by: Byungchul Park

[RFC 10/12] mm/swap_state.c: Remove trailing white space

Trailing white space is not accepted in kernel coding style. Remove them. Signed-off-by: Byungchul Park --- mm/swap_state.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/mm/swap_state.c b/mm/swap_state.c index 69cb246..3fb7013 100644 --- a/mm/swap_state.c +++

[RFC 01/12] lockdep: Refactor lookup_chain_cache()

Currently, lookup_chain_cache() provides both "lookup" and "add" functionalities in a function. However each one is useful indivisually. Some features, e.g. crossrelease, can use each one indivisually. Thus, splited these functionalities into 2 functions. Signed-off-by: Byungchul Park ---

[RFC 11/12] lockdep: Call lock_acquire(release) when accessing PG_locked manually

The PG_locked bit can be updated through SetPageLocked() or ClearPageLocked(), not by lock_page() and unlock_page(). SetPageLockded() and ClearPageLocked() also have to be considered to get balanced between acquring and releasing the PG_locked lock. Signed-off-by: Byungchul Park

[RFC 05/12] lockdep: Implement crossrelease feature

Crossrelease feature calls a lock which is releasable by a different context from the context having acquired the lock, crosslock. For crosslock, all locks having been held in the context unlocking the crosslock, until eventually the crosslock will be unlocked, have dependency with the crosslock.

[RFC 04/12] lockdep: Make save_trace can copy from other stack_trace

Currently, save_trace() can only save current context's stack trace. However, it would be useful if it can save(copy from) another context's stack trace. Especially, it can be used by crossrelease feature. Signed-off-by: Byungchul Park --- kernel/locking/lockdep.c | 22

[RFC 11/12] lockdep: Call lock_acquire(release) when accessing PG_locked manually

The PG_locked bit can be updated through SetPageLocked() or ClearPageLocked(), not by lock_page() and unlock_page(). SetPageLockded() and ClearPageLocked() also have to be considered to get balanced between acquring and releasing the PG_locked lock. Signed-off-by: Byungchul Park ---

[RFC 05/12] lockdep: Implement crossrelease feature

Crossrelease feature calls a lock which is releasable by a different context from the context having acquired the lock, crosslock. For crosslock, all locks having been held in the context unlocking the crosslock, until eventually the crosslock will be unlocked, have dependency with the crosslock.

[RFC 04/12] lockdep: Make save_trace can copy from other stack_trace

Currently, save_trace() can only save current context's stack trace. However, it would be useful if it can save(copy from) another context's stack trace. Especially, it can be used by crossrelease feature. Signed-off-by: Byungchul Park --- kernel/locking/lockdep.c | 22 ++ 1

[RFC 00/12] lockdep: Implement crossrelease feature

Crossrelease feature calls a lock which is releasable by a different context from the context having acquired the lock, crosslock. For crosslock, all locks having been held in the context unlocking the crosslock, until eventually the crosslock will be unlocked, have dependency with the crosslock.

[RFC 08/12] lockdep: Apply crossrelease to PG_locked lock

lock_page() and its family can cause deadlock. Nevertheless, it cannot use the lock correctness validator becasue unlock_page() can be called in different context from the context calling lock_page(), which violates original lockdep's assumption. However, thanks to CONFIG_LOCKDEP_CROSSRELEASE, we

[RFC 03/12] lockdep: Make check_prev_add can use a stack_trace of other context

Currently, check_prev_add() can only save its current context's stack trace. But it would be useful if a seperated stack_trace can be taken and used in check_prev_add(). Crossrelease feature can use check_prev_add() with another context's stack_trace. Signed-off-by: Byungchul Park

[RFC 09/12] cifs/file.c: Remove trailing white space

Trailing white space is not accepted in kernel coding style. Remove them. Signed-off-by: Byungchul Park --- fs/cifs/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/cifs/file.c b/fs/cifs/file.c index ff882ae..bcf9ead 100644 ---

[PATCH 5/5] lockdep: Apply bit_spin_lock lockdep to BH_Uptodate_Lock

In order to use lockdep-enabled bit_spin_lock, we have to call bit_spin_init() when a instance including the bit used as lock creates, and bit_spin_free() when the instance including the bit destroys. BH_Uptodate_Lock bit of buffer head's b_state is one of bit_spin_lock users. And this patch adds

[RFC 07/12] pagemap.h: Remove trailing white space

Trailing white space is not accepted in kernel coding style. Remove them. Signed-off-by: Byungchul Park --- include/linux/pagemap.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h index

[RFC 09/12] cifs/file.c: Remove trailing white space

Trailing white space is not accepted in kernel coding style. Remove them. Signed-off-by: Byungchul Park --- fs/cifs/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/cifs/file.c b/fs/cifs/file.c index ff882ae..bcf9ead 100644 --- a/fs/cifs/file.c +++ b/fs/cifs/file.c

[PATCH 5/5] lockdep: Apply bit_spin_lock lockdep to BH_Uptodate_Lock

In order to use lockdep-enabled bit_spin_lock, we have to call bit_spin_init() when a instance including the bit used as lock creates, and bit_spin_free() when the instance including the bit destroys. BH_Uptodate_Lock bit of buffer head's b_state is one of bit_spin_lock users. And this patch adds

[RFC 07/12] pagemap.h: Remove trailing white space

Trailing white space is not accepted in kernel coding style. Remove them. Signed-off-by: Byungchul Park --- include/linux/pagemap.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h index 92395a0..c0049d9 100644 ---

[RFC 00/12] lockdep: Implement crossrelease feature

Crossrelease feature calls a lock which is releasable by a different context from the context having acquired the lock, crosslock. For crosslock, all locks having been held in the context unlocking the crosslock, until eventually the crosslock will be unlocked, have dependency with the crosslock.

[RFC 08/12] lockdep: Apply crossrelease to PG_locked lock

lock_page() and its family can cause deadlock. Nevertheless, it cannot use the lock correctness validator becasue unlock_page() can be called in different context from the context calling lock_page(), which violates original lockdep's assumption. However, thanks to CONFIG_LOCKDEP_CROSSRELEASE, we

[RFC 03/12] lockdep: Make check_prev_add can use a stack_trace of other context

Currently, check_prev_add() can only save its current context's stack trace. But it would be useful if a seperated stack_trace can be taken and used in check_prev_add(). Crossrelease feature can use check_prev_add() with another context's stack_trace. Signed-off-by: Byungchul Park ---

[RFC 12/12] x86/dumpstack: Optimize save_stack_trace

Currently, x86 implementation of save_stack_trace() is walking all stack region word by word regardless of what the trace->max_entries is. However, it's unnecessary to walk after already fulfilling caller's requirement, say, if trace->nr_entries >= trace->max_entries is true. For example,

[RFC 02/12] lockdep: Add a function building a chain between two hlocks

add_chain_cache() can only be used by current context since it depends on a task's held_locks which is not protected by lock. However, it would be useful if a dependency chain can be built in any context. This patch makes the chain building not depend on its context. Especially, crossrelease

[RFC 12/12] x86/dumpstack: Optimize save_stack_trace

Currently, x86 implementation of save_stack_trace() is walking all stack region word by word regardless of what the trace->max_entries is. However, it's unnecessary to walk after already fulfilling caller's requirement, say, if trace->nr_entries >= trace->max_entries is true. For example,

[RFC 02/12] lockdep: Add a function building a chain between two hlocks

add_chain_cache() can only be used by current context since it depends on a task's held_locks which is not protected by lock. However, it would be useful if a dependency chain can be built in any context. This patch makes the chain building not depend on its context. Especially, crossrelease

[PATCH 2/5] lockdep: Apply bitlock to bit_spin_lock

Currently, bit_spin_lock does not use lockdep_map at all. Of course, the lock correctness validator is not supported for bit_spin_lock. This patch makes bit_spin_lock possible to use the validator using CONFIG_BITLOCK_ALLOC. Signed-off-by: Byungchul Park ---

[PATCH 0/5] Implement bitlock map allocator

Currently, bit-based lock e.g. bit_spin_lock cannot use the lock correctness validator using lockdep. However, it would be useful if the validator supports for even bit-based lock as well. Therefore, this patch provides interface for allocation and freeing lockdep_map for bit-based lock so that

[PATCH 1/5] lockdep: Implement bitlock map allocator

Currently, bit-based lock e.g. bit_spin_lock cannot use the lock correctness validator using lockdep. However, it would be useful if the validator supports for even bit-based lock as well. Therefore, this patch provides interface for allocation and freeing lockdep_map for bit-based lock so that

[PATCH 2/5] lockdep: Apply bitlock to bit_spin_lock

Currently, bit_spin_lock does not use lockdep_map at all. Of course, the lock correctness validator is not supported for bit_spin_lock. This patch makes bit_spin_lock possible to use the validator using CONFIG_BITLOCK_ALLOC. Signed-off-by: Byungchul Park --- include/linux/bit_spinlock.h | 57

[PATCH 0/5] Implement bitlock map allocator

Currently, bit-based lock e.g. bit_spin_lock cannot use the lock correctness validator using lockdep. However, it would be useful if the validator supports for even bit-based lock as well. Therefore, this patch provides interface for allocation and freeing lockdep_map for bit-based lock so that

[PATCH 1/5] lockdep: Implement bitlock map allocator

Currently, bit-based lock e.g. bit_spin_lock cannot use the lock correctness validator using lockdep. However, it would be useful if the validator supports for even bit-based lock as well. Therefore, this patch provides interface for allocation and freeing lockdep_map for bit-based lock so that

Re: [PATCH 5/7] random: replace non-blocking pool with a Chacha20-based CRNG

On Mon, Jun 20, 2016 at 09:25:28AM +0800, Herbert Xu wrote: > > Yes, I understand the argument that the networking stack is now > > requiring the crypto layer --- but not all IOT devices may necessarily > > require the IP stack (they might be using some alternate wireless > > communications stack)

Re: [PATCH 5/7] random: replace non-blocking pool with a Chacha20-based CRNG

On Mon, Jun 20, 2016 at 09:25:28AM +0800, Herbert Xu wrote: > > Yes, I understand the argument that the networking stack is now > > requiring the crypto layer --- but not all IOT devices may necessarily > > require the IP stack (they might be using some alternate wireless > > communications stack)

Linux 4.7-rc4

It's been a fairly normal week, and rc4 is out. Go test. The statistics look very normal: about two thirds drivers, with the rest being half architecture updates and half "misc" (small ffilesystem updates,. some documentation, and a smattering of patches elsewhere). The bulk of the driver

Linux 4.7-rc4

It's been a fairly normal week, and rc4 is out. Go test. The statistics look very normal: about two thirds drivers, with the rest being half architecture updates and half "misc" (small ffilesystem updates,. some documentation, and a smattering of patches elsewhere). The bulk of the driver

linux-next: manual merge of the staging tree with the drm tree

Hi Greg, Today's linux-next merge of the staging tree got a conflict in: drivers/staging/android/sync.h between commit: 76bf0db55439 ("dma-buf/fence: make fence context 64 bit v2") from the drm tree and commits: 342952d3a5c4 ("staging/android: remove 'destroyed' member from struct

linux-next: manual merge of the staging tree with the drm tree

Hi Greg, Today's linux-next merge of the staging tree got a conflict in: drivers/staging/android/sync.h between commit: 76bf0db55439 ("dma-buf/fence: make fence context 64 bit v2") from the drm tree and commits: 342952d3a5c4 ("staging/android: remove 'destroyed' member from struct

Re: [PATCH v7 7/8] perf tools: Check write_backward during evlist config

On 2016/6/17 5:47, Arnaldo Carvalho de Melo wrote: Em Wed, Jun 15, 2016 at 02:23:34AM +, Wang Nan escreveu: Before this patch, when using overwritable ring buffer on an old kernel, error message is misleading: # ~/perf record -m 1 -e raw_syscalls:*/overwrite/ -a Error: The

Re: [PATCH v7 7/8] perf tools: Check write_backward during evlist config

On 2016/6/17 5:47, Arnaldo Carvalho de Melo wrote: Em Wed, Jun 15, 2016 at 02:23:34AM +, Wang Nan escreveu: Before this patch, when using overwritable ring buffer on an old kernel, error message is misleading: # ~/perf record -m 1 -e raw_syscalls:*/overwrite/ -a Error: The

[PATCH v3] mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus()

This patch removes following UBSAN warnings in dw_mci_setup_bus(). UBSAN: Undefined behaviour in drivers/mmc/host/dw_mmc.c:1102:14 shift exponent 250 is too large for 32-bit type 'unsigned int' Call trace: [] dump_backtrace+0x0/0x380 [] show_stack+0x14/0x20 [] dump_stack+0xe0/0x120

[PATCH v3] mmc: dw_mmc: remove UBSAN warning in dw_mci_setup_bus()

This patch removes following UBSAN warnings in dw_mci_setup_bus(). UBSAN: Undefined behaviour in drivers/mmc/host/dw_mmc.c:1102:14 shift exponent 250 is too large for 32-bit type 'unsigned int' Call trace: [] dump_backtrace+0x0/0x380 [] show_stack+0x14/0x20 [] dump_stack+0xe0/0x120

Re: [PATCH v2] mfd: intel_soc_pmic_bxtwc: Add Intel BXT WhiskeyCove PMIC ADC thermal channel-zone mapping

On Fri, Jun 17, 2016 at 09:01:59AM +0100, Lee Jones wrote: > > +static struct trip_config_map str0_trip_config[] = { > > + { > > + .irq_reg = BXTWC_THRM0IRQ, > > + .irq_mask = 0x01, > > + .irq_en = BXTWC_MTHRM0IRQ, > > + .irq_en_mask = 0x01, > > +

Re: [PATCH v2] mfd: intel_soc_pmic_bxtwc: Add Intel BXT WhiskeyCove PMIC ADC thermal channel-zone mapping

On Fri, Jun 17, 2016 at 09:01:59AM +0100, Lee Jones wrote: > > +static struct trip_config_map str0_trip_config[] = { > > + { > > + .irq_reg = BXTWC_THRM0IRQ, > > + .irq_mask = 0x01, > > + .irq_en = BXTWC_MTHRM0IRQ, > > + .irq_en_mask = 0x01, > > +

[PATCH] ARM: AM43XX: hwmod: Fix RSTST register offset for pruss

pruss hwmod RSTST register wrongly points to PWRSTCTRL register in case of am43xx. Fix the RSTST register offset value. This can lead to setting of wrong power state values for PER domain. Fixes: 1c7e224d ("ARM: OMAP2+: hwmod: AM335x: runtime register update") Signed-off-by: Keerthy

[PATCH] ARM: AM43XX: hwmod: Fix RSTST register offset for pruss

pruss hwmod RSTST register wrongly points to PWRSTCTRL register in case of am43xx. Fix the RSTST register offset value. This can lead to setting of wrong power state values for PER domain. Fixes: 1c7e224d ("ARM: OMAP2+: hwmod: AM335x: runtime register update") Signed-off-by: Keerthy ---

[PATCH v3 2/4] arm64: dts: hi6220: Add media subsystem reset dts

Add media subsystem reset dts support. Signed-off-by: Chen Feng Signed-off-by: Xinliang Liu --- arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 2 ++ include/dt-bindings/reset/hisi,hi6220-resets.h | 8 2 files changed, 10

[PATCH v3 1/4] reset: hisilicon: Add media reset controller binding

Add compatible for media reset controller. Actually, there are two reset controllers in hi6220 SoC: The peripheral reset controller bits are part of sysctrl registers. The media reset controller bits are part of mediactrl registers. So for the compatible part, it should contain "syscon" for both

[PATCH v3 2/4] arm64: dts: hi6220: Add media subsystem reset dts

Add media subsystem reset dts support. Signed-off-by: Chen Feng Signed-off-by: Xinliang Liu --- arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 2 ++ include/dt-bindings/reset/hisi,hi6220-resets.h | 8 2 files changed, 10 insertions(+) diff --git

[PATCH v3 1/4] reset: hisilicon: Add media reset controller binding

Add compatible for media reset controller. Actually, there are two reset controllers in hi6220 SoC: The peripheral reset controller bits are part of sysctrl registers. The media reset controller bits are part of mediactrl registers. So for the compatible part, it should contain "syscon" for both

Re: [PATCH v2] gpio: add Intel WhiskeyCove GPIO driver

> > Looks good. I have couple of minor comments, see below. Thanks for review again. > > > + * Copyright (C) 2015 Intel Corporation. All rights reserved. > > It is 2016 now isn't it? :-) Will fix this in v3. > > +#define DRV_NAME "bxt_wcove_gpio" > > Drop this. We have _TWO_ places using

[PATCH v3 3/4] reset: hisilicon: Change to syscon register access

From: Chen Feng There are two reset controllers in hi6220 SoC: The peripheral reset controller bits are part of sysctrl registers. The media reset controller bits are part of mediactrl registers. So change register access to syscon way. And rename current reset

[PATCH v3 0/4] Add hi6220 media subsystem reset controller driver

This patch set adds support for HiSilicon hi6220 SoC media subsystem reset controller. Change history: v3: - Split regmap register access change and mediactrl support. v2: - Update binding document for media reset controller. - Separate peripheral and media reset controller ops. Chen Feng (1):

[PATCH v3 4/4] reset: hisilicon: Add hi6220 media subsystem reset support

Add hi6220 media subsystem reset controller. Signed-off-by: Chen Feng Signed-off-by: Xia Qing Signed-off-by: Xinliang Liu --- drivers/reset/hisilicon/hi6220_reset.c | 49 -- 1 file

  1   2   3   4   5   6   >