Re: [PATCH v2 2/2] lib/uuid.c: eliminate uuid_[bl]e_index arrays

Hi, [auto build test WARNING on v4.7-rc1] [cannot apply to next-20160603] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/George-Spelvin/Clean-up-and-shrink-uuid-input-output/20160604-131729

Re: [PATCH v2 2/2] lib/uuid.c: eliminate uuid_[bl]e_index arrays

Hi, [auto build test WARNING on v4.7-rc1] [cannot apply to next-20160603] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/George-Spelvin/Clean-up-and-shrink-uuid-input-output/20160604-131729

[PATCH] usb: gadget: bdc: fix spelling mistake: "allocted" -> "allocated"

From: Colin Ian King trivial fix to spelling mistake Signed-off-by: Colin Ian King --- drivers/usb/gadget/udc/bdc/bdc_ep.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/gadget/udc/bdc/bdc_ep.c

[PATCH] usb: gadget: bdc: fix spelling mistake: "allocted" -> "allocated"

From: Colin Ian King trivial fix to spelling mistake Signed-off-by: Colin Ian King --- drivers/usb/gadget/udc/bdc/bdc_ep.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/gadget/udc/bdc/bdc_ep.c b/drivers/usb/gadget/udc/bdc/bdc_ep.c index d619950..b48b259

Re: [PATCH v9 00/14] Add support for remote unwind

在 2016/6/4 5:09, Arnaldo Carvalho de Melo 写道: Em Fri, Jun 03, 2016 at 06:06:02PM -0300, Arnaldo Carvalho de Melo escreveu: Em Fri, Jun 03, 2016 at 04:42:05PM -0300, Arnaldo Carvalho de Melo escreveu: Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu: On Fri, Jun 03, 2016 at

Re: [PATCH v9 00/14] Add support for remote unwind

在 2016/6/4 5:09, Arnaldo Carvalho de Melo 写道: Em Fri, Jun 03, 2016 at 06:06:02PM -0300, Arnaldo Carvalho de Melo escreveu: Em Fri, Jun 03, 2016 at 04:42:05PM -0300, Arnaldo Carvalho de Melo escreveu: Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu: On Fri, Jun 03, 2016 at

[PATCH v2 1/2] locking/rwsem: Convert sem->count to atomic_long_t

Convert the rwsem count variable to an atomic_long_t since we use it as an atomic variable. This also allows us to remove the rwsem_atomic_{add,update} "abstraction" which would now be an unnecesary level of indirection. In follow up patches, we also remove the rwsem_atomic_{add,update}

[PATCH v2 2/2] Remove rwsem_atomic_add() and rwsem_atomic_update()

The rwsem-xadd count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the arch implementations of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low ---

[PATCH v2 1/2] locking/rwsem: Convert sem->count to atomic_long_t

Convert the rwsem count variable to an atomic_long_t since we use it as an atomic variable. This also allows us to remove the rwsem_atomic_{add,update} "abstraction" which would now be an unnecesary level of indirection. In follow up patches, we also remove the rwsem_atomic_{add,update}

[PATCH v2 2/2] Remove rwsem_atomic_add() and rwsem_atomic_update()

The rwsem-xadd count has been converted to an atomic variable and the rwsem code now directly uses atomic_long_add() and atomic_long_add_return(), so we can remove the arch implementations of rwsem_atomic_add() and rwsem_atomic_update(). Signed-off-by: Jason Low ---

[PATCH v2 0/2] locking/rwsem: Convert rwsem count to atomic_long_t

v1->v2: - Also convert sem->count usages in arch/{alph,ia64}/include/asm/rwsem.h to be used as atomic_long_t. - Merge the patches to remove rwsem_atomic_add() and rwsem_atomic_update() across the various architectures into one patch. This series converts the rwsem count variable to an

[PATCH v2 0/2] locking/rwsem: Convert rwsem count to atomic_long_t

v1->v2: - Also convert sem->count usages in arch/{alph,ia64}/include/asm/rwsem.h to be used as atomic_long_t. - Merge the patches to remove rwsem_atomic_add() and rwsem_atomic_update() across the various architectures into one patch. This series converts the rwsem count variable to an

[PATCH v9 10/14 UPDATE] perf tools: Check the target platform before assigning unwind methods

Currently, perf script uses host unwind methods to parse perf.data callchain info regardless of the target architecture. So we get wrong result without any warnings when unwinding callchains of x86(32-bit) on x86(64-bit) machine. This patch adds extra step that check the target platform before

[PATCH v9 10/14 UPDATE] perf tools: Check the target platform before assigning unwind methods

Currently, perf script uses host unwind methods to parse perf.data callchain info regardless of the target architecture. So we get wrong result without any warnings when unwinding callchains of x86(32-bit) on x86(64-bit) machine. This patch adds extra step that check the target platform before

[PATCH] staging: comedi: adl_pci9118: fix spelling mistake "acqusition" -> "acquisition"

From: Colin Ian King trivial fix to spelling mistake Signed-off-by: Colin Ian King --- drivers/staging/comedi/drivers/adl_pci9118.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH] staging: comedi: adl_pci9118: fix spelling mistake "acqusition" -> "acquisition"

From: Colin Ian King trivial fix to spelling mistake Signed-off-by: Colin Ian King --- drivers/staging/comedi/drivers/adl_pci9118.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/comedi/drivers/adl_pci9118.c

[PATCH] regulator: lp8755: fix spelling mistake "acceess" -> "access"

From: Colin Ian King trivial fix to spelling mistake Signed-off-by: Colin Ian King --- drivers/regulator/lp8755.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/regulator/lp8755.c

[PATCH] regulator: lp8755: fix spelling mistake "acceess" -> "access"

From: Colin Ian King trivial fix to spelling mistake Signed-off-by: Colin Ian King --- drivers/regulator/lp8755.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/regulator/lp8755.c b/drivers/regulator/lp8755.c index d6773da..6e810e9 100644 ---

Re: [PATCH] ASoC: sgtl5000: only check VDDD-supply, not revision

Hi Fabio and Clemens, On 06/03/2016 06:23 PM, Eric Nelson wrote: > Hi Fabio, > > On 06/02/2016 05:48 PM, Fabio Estevam wrote: >> Hi Clemens, >> >> On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber >> wrote: >>> Instead of checking the SGTL5000 chip revision, we should

Re: [PATCH] ASoC: sgtl5000: only check VDDD-supply, not revision

Hi Fabio and Clemens, On 06/03/2016 06:23 PM, Eric Nelson wrote: > Hi Fabio, > > On 06/02/2016 05:48 PM, Fabio Estevam wrote: >> Hi Clemens, >> >> On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber >> wrote: >>> Instead of checking the SGTL5000 chip revision, we should only check if >>> the VDDD

SIGSYS annoyance

https://bugzilla.mozilla.org/show_bug.cgi?id=1176099 Should SIGSYS be delivered to the handler even if blocked? What, if anything, does POSIX say? All I can find is in pthread_sigmask(3p): If any of the SIGFPE, SIGILL, SIGSEGV, or SIGBUS signals are generated while they are blocked, the result

SIGSYS annoyance

https://bugzilla.mozilla.org/show_bug.cgi?id=1176099 Should SIGSYS be delivered to the handler even if blocked? What, if anything, does POSIX say? All I can find is in pthread_sigmask(3p): If any of the SIGFPE, SIGILL, SIGSEGV, or SIGBUS signals are generated while they are blocked, the result

[PATCH v2 2/2] lib/uuid.c: eliminate uuid_[bl]e_index arrays

Both input and output code is simplified if we use a mapping from binary UUID index to ASCII UUID position. This lets us combine hyphen-skipping and endian-swapping into one table. This significantly simplifies __uuid_to_bin(), which was using *two* lookup tables. uuid_[bl]e_index were

[PATCH v2 2/2] lib/uuid.c: eliminate uuid_[bl]e_index arrays

Both input and output code is simplified if we use a mapping from binary UUID index to ASCII UUID position. This lets us combine hyphen-skipping and endian-swapping into one table. This significantly simplifies __uuid_to_bin(), which was using *two* lookup tables. uuid_[bl]e_index were

[PATCH v2 1/2] lib/vsprintf.c: Simplify uuid_string()

Rather than have a second pass to upcase the buffer, just make the hex lookup table a variable. Removing the conditional branch from the inner loop is also a speedup, but since this is not hot code, the important factor it shrinks both source and compiled forms: Before After Delta

[PATCH v2 1/2] lib/vsprintf.c: Simplify uuid_string()

Rather than have a second pass to upcase the buffer, just make the hex lookup table a variable. Removing the conditional branch from the inner loop is also a speedup, but since this is not hot code, the important factor it shrinks both source and compiled forms: Before After Delta

[PATCH v2 0/2] Clean up and shrink uuid input & output

Okay, here's a more formal submission. Net code size changes for both patches: uuid_string() __uuid_to_bin() Before After Delta Percent Before After Delta Percent x86-32 245 196 -49-20.0% 122 90 -32 -26.2% x86-64 246

[PATCH v2 0/2] Clean up and shrink uuid input & output

Okay, here's a more formal submission. Net code size changes for both patches: uuid_string() __uuid_to_bin() Before After Delta Percent Before After Delta Percent x86-32 245 196 -49-20.0% 122 90 -32 -26.2% x86-64 246

[PATCH v3 2/2] checkpatch: testing more config for Kconfig help text

Current help text check only check a config option if it is followed by another config. Adding check for help text if the next entry is menuconfig, choice/ endchoice, comment, menu/endmenu, if/endif, source or end of file. Signed-off-by: Yingjoe Chen ---

[PATCH v3 1/2] checkpatch: add Kconfig 'default n' test

If a Kconfig config option doesn't specify 'default', the default will be n. Adding 'default n' is unnecessary. Add a test to warn about this. Signed-off-by: Yingjoe Chen --- For this series, rebase to v4.7-rc1 and dropped 'relax Kconfig help text line number

[PATCH v3 2/2] checkpatch: testing more config for Kconfig help text

Current help text check only check a config option if it is followed by another config. Adding check for help text if the next entry is menuconfig, choice/ endchoice, comment, menu/endmenu, if/endif, source or end of file. Signed-off-by: Yingjoe Chen --- scripts/checkpatch.pl | 8 +++- 1

[PATCH v3 1/2] checkpatch: add Kconfig 'default n' test

If a Kconfig config option doesn't specify 'default', the default will be n. Adding 'default n' is unnecessary. Add a test to warn about this. Signed-off-by: Yingjoe Chen --- For this series, rebase to v4.7-rc1 and dropped 'relax Kconfig help text line number threshold' patch. Let me know what

Re: [PATCH 6/6] x86/signal: add SA_{X32,IA32}_ABI sa_flags

On Jun 1, 2016 6:13 AM, "Dmitry Safonov" wrote: > > Introduce new flags that defines which ABI to use on creating sigframe. > Those flags kernel will set according to sigaction syscall ABI, > which set handler for the signal being delivered. > > So that will drop the

Re: [PATCH 2/2] x86/entry: Inline enter_from_user_mode

On May 30, 2016 5:30 AM, "Paolo Bonzini" wrote: > > This matches what is already done for prepare_exit_to_usermode, > and saves about 60 clock cycles (4% speedup) with the benchmark > in the previous commit message. > > Cc: Andy Lutomirski > Cc: Peter

Re: [PATCH 6/6] x86/signal: add SA_{X32,IA32}_ABI sa_flags

On Jun 1, 2016 6:13 AM, "Dmitry Safonov" wrote: > > Introduce new flags that defines which ABI to use on creating sigframe. > Those flags kernel will set according to sigaction syscall ABI, > which set handler for the signal being delivered. > > So that will drop the dependency on

Re: [PATCH 2/2] x86/entry: Inline enter_from_user_mode

On May 30, 2016 5:30 AM, "Paolo Bonzini" wrote: > > This matches what is already done for prepare_exit_to_usermode, > and saves about 60 clock cycles (4% speedup) with the benchmark > in the previous commit message. > > Cc: Andy Lutomirski > Cc: Peter Zijlstra > Cc: Rik van Riel > Cc: H. Peter

Re: [PATCH 1/2] x86/entry: Avoid interrupt flag save and restore

On May 30, 2016 5:30 AM, "Paolo Bonzini" wrote: > > Thanks to all the work that was done by Andy Lutomirski and others, > enter_from_user_mode and prepare_exit_to_usermode are now called only with > interrupts disabled. Let's provide them a version of user_enter/user_exit >

Re: [PATCH 1/2] x86/entry: Avoid interrupt flag save and restore

On May 30, 2016 5:30 AM, "Paolo Bonzini" wrote: > > Thanks to all the work that was done by Andy Lutomirski and others, > enter_from_user_mode and prepare_exit_to_usermode are now called only with > interrupts disabled. Let's provide them a version of user_enter/user_exit > that skips saving and

Re: [PATCH] LSM: Fix for security_inode_getsecurity and -EOPNOTSUPP

On Tue, May 31, 2016 at 05:24:15PM -0700, Casey Schaufler wrote: > Subject: [PATCH] LSM: Fix for security_inode_getsecurity and -EOPNOTSUPP > > Serge Hallyn pointed out that the current implementation of > security_inode_getsecurity() works if there is only one hook > provided for it, but will

Re: [PATCH] LSM: Fix for security_inode_getsecurity and -EOPNOTSUPP

On Tue, May 31, 2016 at 05:24:15PM -0700, Casey Schaufler wrote: > Subject: [PATCH] LSM: Fix for security_inode_getsecurity and -EOPNOTSUPP > > Serge Hallyn pointed out that the current implementation of > security_inode_getsecurity() works if there is only one hook > provided for it, but will

[power_supply] 7f8d22d52d: WARNING: CPU: 0 PID: 1 at drivers/power/power_supply_core.c:569 power_supply_read_temp+0x87/0x90

FYI, we noticed the following commit: https://github.com/0day-ci/linux Rhyland-Klein/power_supply-power_supply_read_temp-only-if-use_cnt-0/20160604-043353 commit 7f8d22d52dade417e135fd1c08ab9977882ff0b6 ("power_supply: power_supply_read_temp only if use_cnt > 0") on test machine:

[power_supply] 7f8d22d52d: WARNING: CPU: 0 PID: 1 at drivers/power/power_supply_core.c:569 power_supply_read_temp+0x87/0x90

FYI, we noticed the following commit: https://github.com/0day-ci/linux Rhyland-Klein/power_supply-power_supply_read_temp-only-if-use_cnt-0/20160604-043353 commit 7f8d22d52dade417e135fd1c08ab9977882ff0b6 ("power_supply: power_supply_read_temp only if use_cnt > 0") on test machine:

Re: [PATCH] hwmon: (tmp401) Add support for TI TMP461

On 05/31/2016 09:27 AM, Andrew F. Davis wrote: Signed-off-by: Andrew F. Davis --- Documentation/hwmon/tmp401 | 18 +-- drivers/hwmon/Kconfig | 2 +- drivers/hwmon/tmp401.c | 81 ++ 3 files changed, 92 insertions(+),

Re: [PATCH] hwmon: (tmp401) Add support for TI TMP461

On 05/31/2016 09:27 AM, Andrew F. Davis wrote: Signed-off-by: Andrew F. Davis --- Documentation/hwmon/tmp401 | 18 +-- drivers/hwmon/Kconfig | 2 +- drivers/hwmon/tmp401.c | 81 ++ 3 files changed, 92 insertions(+), 9

Re: [PATCH 1/1 v6] hwmon: add support for Sensirion SHT3x sensors

On 06/02/2016 12:59 AM, Pascal Sachs wrote: From: David Frey This driver implements support for the Sensirion SHT3x-DIS chip, a humidity and temperature sensor. Temperature is measured in degrees celsius, relative humidity is expressed as a percentage. In the sysfs

Re: [PATCH 1/1 v6] hwmon: add support for Sensirion SHT3x sensors

On 06/02/2016 12:59 AM, Pascal Sachs wrote: From: David Frey This driver implements support for the Sensirion SHT3x-DIS chip, a humidity and temperature sensor. Temperature is measured in degrees celsius, relative humidity is expressed as a percentage. In the sysfs interface, all values are

Re: [PATCH] hwmon: ina2xx: Document compatible for INA231

On 06/01/2016 02:43 AM, Krzysztof Kozlowski wrote: Document the compatible for INA231 sensor. Signed-off-by: Krzysztof Kozlowski Applied. Thanks, Guenter --- Documentation/devicetree/bindings/hwmon/ina2xx.txt | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH] hwmon: ina2xx: Document compatible for INA231

On 06/01/2016 02:43 AM, Krzysztof Kozlowski wrote: Document the compatible for INA231 sensor. Signed-off-by: Krzysztof Kozlowski Applied. Thanks, Guenter --- Documentation/devicetree/bindings/hwmon/ina2xx.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 1/2] b43: Remove unused phy_a code

gcc-6 reports the following error with -Werror=unused-const-variable. drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error: 'b43_phyops_a' defined but not used Per Michael Büsch: "All a-phy code is usused", so remove phy_a.c completely. Move the remaining Type-G initialization code

[PATCH v2 2/2] b43: Completely remove support for phy_a

Per Michael Büsch: "All a-phy code is usused", so remove it all. Signed-off-by: Guenter Roeck --- v2: Added patch drivers/net/wireless/broadcom/b43/main.c | 31 +--- drivers/net/wireless/broadcom/b43/wa.c | 283 +++

[PATCH v2 1/2] b43: Remove unused phy_a code

gcc-6 reports the following error with -Werror=unused-const-variable. drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error: 'b43_phyops_a' defined but not used Per Michael Büsch: "All a-phy code is usused", so remove phy_a.c completely. Move the remaining Type-G initialization code

[PATCH v2 2/2] b43: Completely remove support for phy_a

Per Michael Büsch: "All a-phy code is usused", so remove it all. Signed-off-by: Guenter Roeck --- v2: Added patch drivers/net/wireless/broadcom/b43/main.c | 31 +--- drivers/net/wireless/broadcom/b43/wa.c | 283 +++ drivers/net/wireless/broadcom/b43/xmit.c | 17

Re: [PATCH v13 03/10] arm64: add conditional instruction simulation support

On Thu, 2 Jun 2016 23:26:17 -0400 David Long wrote: > From: "David A. Long" > > Cease using the arm32 arm_check_condition() function and replace it with > a local version for use in deprecated instruction support on arm64. Also > make the function

Re: [PATCH v13 03/10] arm64: add conditional instruction simulation support

On Thu, 2 Jun 2016 23:26:17 -0400 David Long wrote: > From: "David A. Long" > > Cease using the arm32 arm_check_condition() function and replace it with > a local version for use in deprecated instruction support on arm64. Also > make the function table used by this available for future use

Re: [PATCH 2/2] aer: add support aer interrupt with none MSI/MSI-X/INTx mode

On Fri, Jun 03, 2016 at 01:31:11PM -0400, Murali Karicheri wrote: > Po, > > Sorry to hijack your discussion, but the problem seems to be same for > Keystone PCI controller which is also designware (old version) based. > > On 06/03/2016 12:09 AM, Bjorn Helgaas wrote: > > On Thu, Jun 02, 2016 at

Re: [PATCH 2/2] aer: add support aer interrupt with none MSI/MSI-X/INTx mode

On Fri, Jun 03, 2016 at 01:31:11PM -0400, Murali Karicheri wrote: > Po, > > Sorry to hijack your discussion, but the problem seems to be same for > Keystone PCI controller which is also designware (old version) based. > > On 06/03/2016 12:09 AM, Bjorn Helgaas wrote: > > On Thu, Jun 02, 2016 at

Re: [PATCH v13 04/10] arm64: Blacklist non-kprobe-able symbol

Hi David, On Thu, 2 Jun 2016 23:26:18 -0400 David Long wrote: > From: Pratyush Anand > > Add all function symbols which are called from do_debug_exception under > NOKPROBE_SYMBOL, as they can not kprobed. I see, but this patch should be applied after

Re: [PATCH v13 04/10] arm64: Blacklist non-kprobe-able symbol

Hi David, On Thu, 2 Jun 2016 23:26:18 -0400 David Long wrote: > From: Pratyush Anand > > Add all function symbols which are called from do_debug_exception under > NOKPROBE_SYMBOL, as they can not kprobed. I see, but this patch should be applied after kprobes are implemented on arm64. And

[PATCH v3 5/7] zram: delete custom lzo/lz4

Remove lzo/lz4 backends, we use crypto API now. Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim Cc: Joonsoo Kim Acked-by: Minchan Kim --- drivers/block/zram/Kconfig | 9 ---

[PATCH v3 2/7] zram: switch to crypto compress API

We don't have an idle zstreams list anymore and our write path now works absolutely differently, preventing preemption during compression. This removes possibilities of read paths preempting writes at wrong places (which could badly affect the performance of both paths) and at the same time opens

[PATCH v3 6/7] zram: add more compression algorithms

Add "deflate", "lz4hc", "842" algorithms to the list of known compression backends. The real availability of those algorithms, however, depends on the corresponding CONFIG_CRYPTO_FOO config options. Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim

[PATCH v3 5/7] zram: delete custom lzo/lz4

Remove lzo/lz4 backends, we use crypto API now. Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim Cc: Joonsoo Kim Acked-by: Minchan Kim --- drivers/block/zram/Kconfig | 9 --- drivers/block/zram/Makefile| 4 +-- drivers/block/zram/zcomp.c | 2 +- drivers/block/zram/zcomp.h

[PATCH v3 2/7] zram: switch to crypto compress API

We don't have an idle zstreams list anymore and our write path now works absolutely differently, preventing preemption during compression. This removes possibilities of read paths preempting writes at wrong places (which could badly affect the performance of both paths) and at the same time opens

[PATCH v3 6/7] zram: add more compression algorithms

Add "deflate", "lz4hc", "842" algorithms to the list of known compression backends. The real availability of those algorithms, however, depends on the corresponding CONFIG_CRYPTO_FOO config options. Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim Cc: Joonsoo Kim ---

[PATCH v3 3/7] zram: use crypto api to check alg availability

There is no way to get a string with all the crypto comp algorithms supported by the crypto comp engine, so we need to maintain our own backends list. At the same time we additionally need to use crypto_has_comp() to make sure that the user has requested a compression algorithm that is recognized

[PATCH v3 3/7] zram: use crypto api to check alg availability

There is no way to get a string with all the crypto comp algorithms supported by the crypto comp engine, so we need to maintain our own backends list. At the same time we additionally need to use crypto_has_comp() to make sure that the user has requested a compression algorithm that is recognized

[PATCH v3 1/7] zram: rename zstrm find-release functions

We don't perform any zstream idle list lookup anymore, so zcomp_strm_find()/zcomp_strm_release() names are not representative. Rename to zcomp_stream_get()/zcomp_stream_put(). Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim Cc: Joonsoo Kim

[PATCH v3 0/7] zram: switch to crypto api

Hello, This has started as a 'add zlib support' work, but after some thinking I saw no blockers for a bigger change -- a switch to crypto API. We don't have an idle zstreams list anymore and our write path now works absolutely differently, preventing preemption during compression. This

[PATCH v3 7/7] zram: drop gfp_t from zcomp_strm_alloc()

We now allocate streams from CPU_UP hot-plug path, there are no context-dependent stream allocations anymore and we can schedule from zcomp_strm_alloc(). Use GFP_KERNEL directly and drop a gfp_t parameter. Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim

[PATCH v3 4/7] zram: cosmetic: cleanup documentation

zram documentation is a mix of different styles: spaces, tabs, tabs + spaces, etc. clean it up. Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim Cc: Joonsoo Kim Cc: Jonathan Corbet Acked-by: Minchan

[PATCH v3 1/7] zram: rename zstrm find-release functions

We don't perform any zstream idle list lookup anymore, so zcomp_strm_find()/zcomp_strm_release() names are not representative. Rename to zcomp_stream_get()/zcomp_stream_put(). Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim Cc: Joonsoo Kim Acked-by: Minchan Kim ---

[PATCH v3 0/7] zram: switch to crypto api

Hello, This has started as a 'add zlib support' work, but after some thinking I saw no blockers for a bigger change -- a switch to crypto API. We don't have an idle zstreams list anymore and our write path now works absolutely differently, preventing preemption during compression. This

[PATCH v3 7/7] zram: drop gfp_t from zcomp_strm_alloc()

We now allocate streams from CPU_UP hot-plug path, there are no context-dependent stream allocations anymore and we can schedule from zcomp_strm_alloc(). Use GFP_KERNEL directly and drop a gfp_t parameter. Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim Cc: Joonsoo Kim Acked-by: Minchan Kim

[PATCH v3 4/7] zram: cosmetic: cleanup documentation

zram documentation is a mix of different styles: spaces, tabs, tabs + spaces, etc. clean it up. Signed-off-by: Sergey Senozhatsky Cc: Minchan Kim Cc: Joonsoo Kim Cc: Jonathan Corbet Acked-by: Minchan Kim --- Documentation/blockdev/zram.txt | 91 - 1

Re: [PATCH v10 2/7] usb: mux: add generic code for dual role port mux

On Sat, Jun 04, 2016 at 12:06:06AM +0800, Lu Baolu wrote: > Hi Peter, > > On 06/03/2016 03:41 PM, Peter Chen wrote: > > On Thu, Jun 02, 2016 at 09:37:24AM +0800, Lu Baolu wrote: > >> > Several Intel platforms implement USB dual role by having completely > >> > separate xHCI and dwc3 IPs in PCH or

Re: [PATCH v10 2/7] usb: mux: add generic code for dual role port mux

On Sat, Jun 04, 2016 at 12:06:06AM +0800, Lu Baolu wrote: > Hi Peter, > > On 06/03/2016 03:41 PM, Peter Chen wrote: > > On Thu, Jun 02, 2016 at 09:37:24AM +0800, Lu Baolu wrote: > >> > Several Intel platforms implement USB dual role by having completely > >> > separate xHCI and dwc3 IPs in PCH or

[PATCH] dmaengine: bcm2835: Fix polling for completion of DMA with interrupts masked.

The tx_status hook is supposed to be safe to call from interrupt context, but it wouldn't ever return completion for the last transfer, meaning you couldn't poll for DMA completion with interrupts masked. This fixes IRQ handling for bcm2835's DSI1, which requires using the DMA engine to write its

[PATCH] dmaengine: bcm2835: Fix polling for completion of DMA with interrupts masked.

The tx_status hook is supposed to be safe to call from interrupt context, but it wouldn't ever return completion for the last transfer, meaning you couldn't poll for DMA completion with interrupts masked. This fixes IRQ handling for bcm2835's DSI1, which requires using the DMA engine to write its

[PATCH] dma: bcm2835: Fix compiler warning on arm64.

The min() macro was complaining about mismatched types. The max len is at most SZ_1G, so we can just put it in an unsigned int. Signed-off-by: Eric Anholt --- Vinod, if you ack it, this one would be nice to be able to merge through the -soc tree, so that when we enable of

[PATCH] dma: bcm2835: Fix compiler warning on arm64.

The min() macro was complaining about mismatched types. The max len is at most SZ_1G, so we can just put it in an unsigned int. Signed-off-by: Eric Anholt --- Vinod, if you ack it, this one would be nice to be able to merge through the -soc tree, so that when we enable of arm64 builds of this

[PATCH] sd: remove redundant check for BLK_DEF_MAX_SECTORS

q->limits.max_sectors is already checked against BLK_DEF_MAX_SECTORS in __scsi_alloc_queue(), when it calls blk_queue_max_hw_sectors(). There is no need to check it again in sd. This change also allows a SCSI driver set an maximum sector size bigger than BLK_DEF_MAX_SECTORS, without returning

[PATCH] sd: remove redundant check for BLK_DEF_MAX_SECTORS

q->limits.max_sectors is already checked against BLK_DEF_MAX_SECTORS in __scsi_alloc_queue(), when it calls blk_queue_max_hw_sectors(). There is no need to check it again in sd. This change also allows a SCSI driver set an maximum sector size bigger than BLK_DEF_MAX_SECTORS, without returning

[PATCH v12 08/15] powerpc/PCI: Keep resource idx order with bridge register number

Same as sparc version. Make resource with consistent sequence like other arch or directly from pci_read_bridge_bases(), even when non-pref mmio is missing, or out of ordering in firmware reporting. Just hold i = 1 for non pref mmio, and i = 2 for pref mmio. Signed-off-by: Yinghai Lu

[PATCH v12 08/15] powerpc/PCI: Keep resource idx order with bridge register number

Same as sparc version. Make resource with consistent sequence like other arch or directly from pci_read_bridge_bases(), even when non-pref mmio is missing, or out of ordering in firmware reporting. Just hold i = 1 for non pref mmio, and i = 2 for pref mmio. Signed-off-by: Yinghai Lu Cc:

Re: Dcache oops

On Fri, Jun 03, 2016 at 07:58:37PM -0400, Oleg Drokin wrote: > > EOPENSTALE, that is... Oleg, could you check if the following works? > > Yes, this one lasted for an hour with no crashing, so it must be good. > Thanks. > (note, I am not equipped to verify correctness of NFS operations, though).

Re: Dcache oops

On Fri, Jun 03, 2016 at 07:58:37PM -0400, Oleg Drokin wrote: > > EOPENSTALE, that is... Oleg, could you check if the following works? > > Yes, this one lasted for an hour with no crashing, so it must be good. > Thanks. > (note, I am not equipped to verify correctness of NFS operations, though).

Re: [PATCH] b43: Remove unused phy_a code

On 06/03/2016 02:35 PM, Michael Büsch wrote: On Fri, 3 Jun 2016 14:32:46 -0700 Guenter Roeck wrote: gcc-6 reports the following error with -Werror=unused-const-variable. drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error: 'b43_phyops_a' defined but not used

Re: [PATCH] b43: Remove unused phy_a code

On 06/03/2016 02:35 PM, Michael Büsch wrote: On Fri, 3 Jun 2016 14:32:46 -0700 Guenter Roeck wrote: gcc-6 reports the following error with -Werror=unused-const-variable. drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error: 'b43_phyops_a' defined but not used Turns out a lot of

[PATCH] Drivers: ssb: Fix bare unsigned and changed to trailing comments

I changed drivers/ssb/driver_gpio.c to better fit the coding style. I changed unsigned to unsigned int Two comments were changed to not end on a line with the text. Signed-off-by: Hugh Sipiere --- drivers/ssb/driver_gpio.c | 26 ++ 1 file changed, 14

[PATCH] Drivers: ssb: Fix bare unsigned and changed to trailing comments

I changed drivers/ssb/driver_gpio.c to better fit the coding style. I changed unsigned to unsigned int Two comments were changed to not end on a line with the text. Signed-off-by: Hugh Sipiere --- drivers/ssb/driver_gpio.c | 26 ++ 1 file changed, 14 insertions(+), 12

Re: Builtin microcode does nothing..

On 03.06.2016 10:02, Borislav Petkov wrote: On Thu, May 26, 2016 at 02:46:06PM +0200, Borislav Petkov wrote: In the meantime, I've simplified the code even more and testing here with your .config looks good. I'll prepare another patchset next week and post it here in case you guys feel bored

Re: Builtin microcode does nothing..

On 03.06.2016 10:02, Borislav Petkov wrote: On Thu, May 26, 2016 at 02:46:06PM +0200, Borislav Petkov wrote: In the meantime, I've simplified the code even more and testing here with your .config looks good. I'll prepare another patchset next week and post it here in case you guys feel bored

[PATCH v12 07/15] sparc/PCI: Keep resource idx order with bridge register number

On one system found strange "no compatible bridge window" warning even we already had pref_compat support that add extra pref bit for device resource. PCI: Claiming :00:01.0: Resource 14: 00020001..000200010fff [10220c] PCI: Claiming :01:00.0: Resource 1:

[PATCH v12 07/15] sparc/PCI: Keep resource idx order with bridge register number

On one system found strange "no compatible bridge window" warning even we already had pref_compat support that add extra pref bit for device resource. PCI: Claiming :00:01.0: Resource 14: 00020001..000200010fff [10220c] PCI: Claiming :01:00.0: Resource 1:

[PATCH v12 12/15] PCI: Only treat non-pref mmio64 as pref if all bridges have MEM_64

If any bridge up to root only have 32bit pref mmio, We don't need to treat device non-pref mmio64 as as pref mmio64. We need to move pci_bridge_check_ranges calling early. For parent bridges pref mmio BAR may not allocated by BIOS, res flags is still 0, we need to have it correct set before we

[PATCH v12 05/15] sparc/PCI: Reserve legacy mmio after PCI mmio

On one system found bunch of claim resource fail from pci device. pci_sun4v f02b894c: PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus address [0x-0xfff]) pci_bus :00: root bus resource [mem 0x2-0x27eff]

[PATCH v12 12/15] PCI: Only treat non-pref mmio64 as pref if all bridges have MEM_64

If any bridge up to root only have 32bit pref mmio, We don't need to treat device non-pref mmio64 as as pref mmio64. We need to move pci_bridge_check_ranges calling early. For parent bridges pref mmio BAR may not allocated by BIOS, res flags is still 0, we need to have it correct set before we

[PATCH v12 05/15] sparc/PCI: Reserve legacy mmio after PCI mmio

On one system found bunch of claim resource fail from pci device. pci_sun4v f02b894c: PCI host bridge to bus :00 pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus address [0x-0xfff]) pci_bus :00: root bus resource [mem 0x2-0x27eff]

[PATCH v12 02/15] PCI: Let pci_mmap_page_range() take resource address

In 8c05cd08a7 ("PCI: fix offset check for sysfs mmapped files"), try to check exposed value with resource start/end in proc mmap path. |start = vma->vm_pgoff; |size = ((pci_resource_len(pdev, resno) - 1) >> PAGE_SHIFT) + 1; |pci_start = (mmap_api == PCI_MMAP_PROCFS) ? |

[PATCH v12 02/15] PCI: Let pci_mmap_page_range() take resource address

In 8c05cd08a7 ("PCI: fix offset check for sysfs mmapped files"), try to check exposed value with resource start/end in proc mmap path. |start = vma->vm_pgoff; |size = ((pci_resource_len(pdev, resno) - 1) >> PAGE_SHIFT) + 1; |pci_start = (mmap_api == PCI_MMAP_PROCFS) ? |

  1   2   3   4   5   6   7   8   9   10   >