Re: [PATCH v1 2/3] perf version: Print the status of compiled-in libraries

* Jin Yao wrote: > +#ifdef HAVE_DWARF_SUPPORT > +#ifdef HAVE_DWARF_GETLOCATIONS > +#ifdef NO_GLIBC > +#ifdef HAVE_GTK2_SUPPORT > +#ifdef HAVE_LIBAUDIT_SUPPORT > +#ifdef HAVE_LIBBFD_SUPPORT > +#ifdef HAVE_LIBELF_SUPPORT > +#ifdef HAVE_LIBNUMA_SUPPORT > +#ifdef NO_LIBPERL

Re: [PATCH v1 2/3] perf version: Print the status of compiled-in libraries

* Jin Yao wrote: > +#ifdef HAVE_DWARF_SUPPORT > +#ifdef HAVE_DWARF_GETLOCATIONS > +#ifdef NO_GLIBC > +#ifdef HAVE_GTK2_SUPPORT > +#ifdef HAVE_LIBAUDIT_SUPPORT > +#ifdef HAVE_LIBBFD_SUPPORT > +#ifdef HAVE_LIBELF_SUPPORT > +#ifdef HAVE_LIBNUMA_SUPPORT > +#ifdef NO_LIBPERL > +#ifdef NO_LIBPYTHON >

Re: [PATCH v6] kernel.h: Retain constant expression output for max()/min()

* Kees Cook wrote: > In the effort to remove all VLAs from the kernel[1], it is desirable to > build with -Wvla. However, this warning is overly pessimistic, in that > it is only happy with stack array sizes that are declared as constant > expressions, and not constant

Re: [PATCH v6] kernel.h: Retain constant expression output for max()/min()

* Kees Cook wrote: > In the effort to remove all VLAs from the kernel[1], it is desirable to > build with -Wvla. However, this warning is overly pessimistic, in that > it is only happy with stack array sizes that are declared as constant > expressions, and not constant values. One case of this

Re: [PATCH] objtool: fix build with future Make

2018-03-26 7:32 GMT+09:00 Rasmus Villemoes : > I tried building using a freshly built Make (4.2.1-69-g8a731d1), but the > objtool build broke with > > orc_dump.c: In function ‘orc_dump’: > orc_dump.c:106:2: error: ‘elf_getshnum’ is deprecated >

Re: [PATCH] objtool: fix build with future Make

2018-03-26 7:32 GMT+09:00 Rasmus Villemoes : > I tried building using a freshly built Make (4.2.1-69-g8a731d1), but the > objtool build broke with > > orc_dump.c: In function ‘orc_dump’: > orc_dump.c:106:2: error: ‘elf_getshnum’ is deprecated > [-Werror=deprecated-declarations] > if

Re: [PATCH] ALSA: aloop: Mark paused device as inactive

On 03/26/2018 04:43 PM, Takashi Iwai wrote: > On Mon, 26 Mar 2018 07:24:49 +0200, > Robert Rosengren wrote: >> >> Show paused ALSA aloop device as inactive, i.e. the control >> "PCM Slave Active" set as false. Notification sent upon state change. >> >> This makes it possible for client capturing

Re: [PATCH] ALSA: aloop: Mark paused device as inactive

On 03/26/2018 04:43 PM, Takashi Iwai wrote: > On Mon, 26 Mar 2018 07:24:49 +0200, > Robert Rosengren wrote: >> >> Show paused ALSA aloop device as inactive, i.e. the control >> "PCM Slave Active" set as false. Notification sent upon state change. >> >> This makes it possible for client capturing

[PATCH v2 06/21] kconfig: remove string expansion for mainmenu after yyparse()

Now that environments are expanded in the lexer, conf_parse() does not need to explicitly expand $ARCH and $KERNELVERSION in the mainmenu. The hack introduced by commit 0724a7c32a54 ("kconfig: Don't leak main menus during parsing") can go away. Signed-off-by: Masahiro Yamada

[PATCH v2 06/21] kconfig: remove string expansion for mainmenu after yyparse()

Now that environments are expanded in the lexer, conf_parse() does not need to explicitly expand $ARCH and $KERNELVERSION in the mainmenu. The hack introduced by commit 0724a7c32a54 ("kconfig: Don't leak main menus during parsing") can go away. Signed-off-by: Masahiro Yamada --- Changes in v2:

[PATCH v2 08/21] kconfig: replace $UNAME_RELEASE with function call

Now that 'shell' function is supported, this can be self-contained in Kconfig. Signed-off-by: Masahiro Yamada --- Changes in v2: None Makefile | 3 +-- init/Kconfig | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile

[PATCH v2 08/21] kconfig: replace $UNAME_RELEASE with function call

Now that 'shell' function is supported, this can be self-contained in Kconfig. Signed-off-by: Masahiro Yamada --- Changes in v2: None Makefile | 3 +-- init/Kconfig | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index 4ae1486..5c395ed 100644

[PATCH v2 15/21] gcov: remove CONFIG_GCOV_FORMAT_AUTODETECT

CONFIG_GCOV_FORMAT_AUTODETECT compiles either gcc_3_4.c or gcc_4_7.c according to your GCC version. We can achieve the equivalent behavior by setting reasonable dependency with the knowledge of the compiler version. If GCC older than 4.7 is used, GCOV_FORMAT_3_4 is the default, but users are

[PATCH v2 15/21] gcov: remove CONFIG_GCOV_FORMAT_AUTODETECT

CONFIG_GCOV_FORMAT_AUTODETECT compiles either gcc_3_4.c or gcc_4_7.c according to your GCC version. We can achieve the equivalent behavior by setting reasonable dependency with the knowledge of the compiler version. If GCC older than 4.7 is used, GCOV_FORMAT_3_4 is the default, but users are

[PATCH v2 13/21] kconfig: add CC_IS_GCC and GCC_VERSION

This will be useful to specify the required compiler version, like this: config FOO bool "Use Foo" depends on GCC_VERSION >= 408000 help This feature requires GCC 4.8 or newer. Signed-off-by: Masahiro Yamada --- Changes in v2:

[PATCH v2 13/21] kconfig: add CC_IS_GCC and GCC_VERSION

This will be useful to specify the required compiler version, like this: config FOO bool "Use Foo" depends on GCC_VERSION >= 408000 help This feature requires GCC 4.8 or newer. Signed-off-by: Masahiro Yamada --- Changes in v2: None init/Kconfig | 8

[PATCH v2 03/21] kconfig: move and rename sym_expand_string_value()

This helper expands symbols contained in a string. I am about to change it to expand environments instead of symbols. Also, I will add function expansion later. Rename it to expand_string_value(), and move it to util.c, which is a more suitable place. Signed-off-by: Masahiro Yamada

[PATCH v2 03/21] kconfig: move and rename sym_expand_string_value()

This helper expands symbols contained in a string. I am about to change it to expand environments instead of symbols. Also, I will add function expansion later. Rename it to expand_string_value(), and move it to util.c, which is a more suitable place. Signed-off-by: Masahiro Yamada ---

[PATCH v2 01/21] kbuild: remove kbuild cache

The kbuild cache was introduced to remember the result of shell commands, some of which are expensive to compute, such as $(call cc-option,...). However, this turned out not so clever as I had first expected. Actually, it is problematic. For example, "$(CC) -print-file-name" is cached. If the

[PATCH v2 01/21] kbuild: remove kbuild cache

The kbuild cache was introduced to remember the result of shell commands, some of which are expensive to compute, such as $(call cc-option,...). However, this turned out not so clever as I had first expected. Actually, it is problematic. For example, "$(CC) -print-file-name" is cached. If the

[PATCH v2 05/21] kconfig: remove string expansion in file_lookup()

There are two callers of file_lookup(). [1] zconf_initscan() This is used to open the first Kconfig. However, it cannot contain environments in the file path because zconf_fopen() is called before file_lookup(). By swapping the call order, KBUILD_KCONFIG would be able to contain

[PATCH v2 07/21] kconfig: add function support and implement 'shell' function

This commit adds a new concept 'function' to do more text processing in Kconfig. A function call looks like this: $(function arg1, arg2, arg3, ...) (Actually, this syntax was inspired by make.) Real examples will look like this: $(shell echo hello world) $(cc-option -fstackprotector)

[PATCH v2 07/21] kconfig: add function support and implement 'shell' function

This commit adds a new concept 'function' to do more text processing in Kconfig. A function call looks like this: $(function arg1, arg2, arg3, ...) (Actually, this syntax was inspired by make.) Real examples will look like this: $(shell echo hello world) $(cc-option -fstackprotector)

[PATCH v2 05/21] kconfig: remove string expansion in file_lookup()

There are two callers of file_lookup(). [1] zconf_initscan() This is used to open the first Kconfig. However, it cannot contain environments in the file path because zconf_fopen() is called before file_lookup(). By swapping the call order, KBUILD_KCONFIG would be able to contain

[PATCH v2 02/21] kbuild: remove CONFIG_CROSS_COMPILE support

Kbuild provides a couple of ways to specify CROSS_COMPILE: [1] Command line [2] Environment [3] arch/*/Makefile (only some architectures) [4] CONFIG_CROSS_COMPILE [4] is problematic for the compiler capability tests in Kconfig. CONFIG_CROSS_COMPILE allows users to change the compiler prefix from

[PATCH v2 12/21] kconfig: show compiler version text in the top comment

The kernel configuration phase is now tightly coupled with the compiler in use. It will be nice to show the compiler information in Kconfig. The compiler information will be displayed like this: $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- config scripts/kconfig/conf --oldaskconfig

[PATCH v2 02/21] kbuild: remove CONFIG_CROSS_COMPILE support

Kbuild provides a couple of ways to specify CROSS_COMPILE: [1] Command line [2] Environment [3] arch/*/Makefile (only some architectures) [4] CONFIG_CROSS_COMPILE [4] is problematic for the compiler capability tests in Kconfig. CONFIG_CROSS_COMPILE allows users to change the compiler prefix from

[PATCH v2 12/21] kconfig: show compiler version text in the top comment

The kernel configuration phase is now tightly coupled with the compiler in use. It will be nice to show the compiler information in Kconfig. The compiler information will be displayed like this: $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- config scripts/kconfig/conf --oldaskconfig

[PATCH v2 09/21] kconfig: add 'macro' keyword to support user-defined function

Now, we got a basic ability to test compiler capability in Kconfig. config CC_HAS_STACKPROTECTOR def_bool $(shell (($CC -Werror -fstack-protector -c -x c /dev/null -o /dev/null) && echo y) || echo n) This works, but it is ugly to repeat this long boilerplate. We want to describe like

[PATCH v2 09/21] kconfig: add 'macro' keyword to support user-defined function

Now, we got a basic ability to test compiler capability in Kconfig. config CC_HAS_STACKPROTECTOR def_bool $(shell (($CC -Werror -fstack-protector -c -x c /dev/null -o /dev/null) && echo y) || echo n) This works, but it is ugly to repeat this long boilerplate. We want to describe like

[PATCH v2 10/21] kconfig: add 'success' and 'cc-option' macros

'cc-option' will be the most frequently used macro. It evaluates to 'y' if the given argument is supported by the compiler, or 'n' otherwise. Signed-off-by: Masahiro Yamada --- Changes in v2: - Implement 'success' as a macro init/Kconfig | 6 ++ 1 file

[PATCH v2 16/21] kcov: imply GCC_PLUGINS and GCC_PLUGIN_SANCOV instead of select'ing them

As Documentation/kbuild/kconfig-language.txt notes, 'select' should be used with care - it forces a lower limit of another symbol, ignoring the dependency. In this case, KCOV can select GCC_PLUGINS even if 'depends on HAVE_GCC_PLUGINS' is unmet. 'imply' is modest enough to observe the

[PATCH v2 16/21] kcov: imply GCC_PLUGINS and GCC_PLUGIN_SANCOV instead of select'ing them

As Documentation/kbuild/kconfig-language.txt notes, 'select' should be used with care - it forces a lower limit of another symbol, ignoring the dependency. In this case, KCOV can select GCC_PLUGINS even if 'depends on HAVE_GCC_PLUGINS' is unmet. 'imply' is modest enough to observe the

[PATCH v2 10/21] kconfig: add 'success' and 'cc-option' macros

'cc-option' will be the most frequently used macro. It evaluates to 'y' if the given argument is supported by the compiler, or 'n' otherwise. Signed-off-by: Masahiro Yamada --- Changes in v2: - Implement 'success' as a macro init/Kconfig | 6 ++ 1 file changed, 6 insertions(+) diff

[PATCH v2 14/21] kconfig: add CC_IS_CLANG and CLANG_VERSION

This will be useful to describe the clang version dependency. Signed-off-by: Masahiro Yamada --- Changes in v2: None init/Kconfig | 7 +++ scripts/clang-version.sh | 24 +++- 2 files changed, 18 insertions(+), 13 deletions(-)

[PATCH v2 14/21] kconfig: add CC_IS_CLANG and CLANG_VERSION

This will be useful to describe the clang version dependency. Signed-off-by: Masahiro Yamada --- Changes in v2: None init/Kconfig | 7 +++ scripts/clang-version.sh | 24 +++- 2 files changed, 18 insertions(+), 13 deletions(-) diff --git a/init/Kconfig

[PATCH v2 19/21] gcc-plugins: test GCC plugin support in Kconfig

Run scripts/gcc-plugin.sh from Kconfig. Users can enable GCC_PLUGINS only when it is supported. Signed-off-by: Masahiro Yamada --- Changes in v2: None arch/Kconfig | 4 +++ scripts/Makefile.gcc-plugins | 82

[PATCH v2 19/21] gcc-plugins: test GCC plugin support in Kconfig

Run scripts/gcc-plugin.sh from Kconfig. Users can enable GCC_PLUGINS only when it is supported. Signed-off-by: Masahiro Yamada --- Changes in v2: None arch/Kconfig | 4 +++ scripts/Makefile.gcc-plugins | 82 scripts/gcc-plugin.sh

[PATCH v2 04/21] kconfig: reference environments directly and remove 'option env=' syntax

To get an environment value, Kconfig needs to define a symbol using "option env=" syntax. It is tedious to add a config entry for each environment given that we need more environments such as 'CC', 'AS', 'srctree' etc. to evaluate the compiler capability in Kconfig. Adding '$' to symbols is

[PATCH v2 21/21] arm64: move GCC version check for ARCH_SUPPORTS_INT128 to Kconfig

This becomes much neater in Kconfig. Signed-off-by: Masahiro Yamada --- Changes in v2: - Newly added arch/arm64/Kconfig | 1 + arch/arm64/Makefile | 2 -- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig

[PATCH v2 04/21] kconfig: reference environments directly and remove 'option env=' syntax

To get an environment value, Kconfig needs to define a symbol using "option env=" syntax. It is tedious to add a config entry for each environment given that we need more environments such as 'CC', 'AS', 'srctree' etc. to evaluate the compiler capability in Kconfig. Adding '$' to symbols is

[PATCH v2 21/21] arm64: move GCC version check for ARCH_SUPPORTS_INT128 to Kconfig

This becomes much neater in Kconfig. Signed-off-by: Masahiro Yamada --- Changes in v2: - Newly added arch/arm64/Kconfig | 1 + arch/arm64/Makefile | 2 -- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 7381eeb..0c97f40 100644 ---

[PATCH v2 18/21] gcc-plugins: move GCC version check for PowerPC to Kconfig

For PowerPC, GCC 5.2 is the requirement for GCC plugins. Move the version check to Kconfig so that the GCC plugin menus will be hidden if an older compiler is in use. Signed-off-by: Masahiro Yamada Acked-by: Andrew Donnellan ---

[PATCH v2 18/21] gcc-plugins: move GCC version check for PowerPC to Kconfig

For PowerPC, GCC 5.2 is the requirement for GCC plugins. Move the version check to Kconfig so that the GCC plugin menus will be hidden if an older compiler is in use. Signed-off-by: Masahiro Yamada Acked-by: Andrew Donnellan --- Changes in v2: None arch/powerpc/Kconfig | 2 +-

[PATCH v2 17/21] gcc-plugins: always build plugins with C++

If the target compiler is GCC 4.8 or newer, plugins are compiled with HOSTCXX. Otherwise, gcc-plugin.sh will select HOSTCC or HOSTCXX. To simplify things, drop the HOSTCC support for plugins. If you use GCC plugins, the requirement for the target compiler is GCC 4.8 (or older compiler with

[PATCH v2 17/21] gcc-plugins: always build plugins with C++

If the target compiler is GCC 4.8 or newer, plugins are compiled with HOSTCXX. Otherwise, gcc-plugin.sh will select HOSTCC or HOSTCXX. To simplify things, drop the HOSTCC support for plugins. If you use GCC plugins, the requirement for the target compiler is GCC 4.8 (or older compiler with

[PATCH v2 11/21] stack-protector: test compiler capability in Kconfig and drop AUTO mode

Move the test for -fstack-protector(-strong) option to Kconfig. If the compiler does not support the option, the corresponding menu is automatically hidden. If _STRONG is not supported, it will fall back to _REGULAR. If _REGULAR is not supported, it will be disabled. This means, _AUTO is

[PATCH v2 00/21] kconfig: move compiler capability tests to Kconfig

Here is v2 to start to move compiler capability tests to Kconfig. V1: https://lkml.org/lkml/2018/2/16/610 I brushed up the implementation even more. Major changes for v2: [1] Environments and functions are expanded in the lexer (zconf.l) The parser (zconf.y) receives expanded tokens. This

[PATCH v2 11/21] stack-protector: test compiler capability in Kconfig and drop AUTO mode

Move the test for -fstack-protector(-strong) option to Kconfig. If the compiler does not support the option, the corresponding menu is automatically hidden. If _STRONG is not supported, it will fall back to _REGULAR. If _REGULAR is not supported, it will be disabled. This means, _AUTO is

[PATCH v2 00/21] kconfig: move compiler capability tests to Kconfig

Here is v2 to start to move compiler capability tests to Kconfig. V1: https://lkml.org/lkml/2018/2/16/610 I brushed up the implementation even more. Major changes for v2: [1] Environments and functions are expanded in the lexer (zconf.l) The parser (zconf.y) receives expanded tokens. This

[PATCH v2 20/21] gcc-plugins: enable GCC_PLUGINS for COMPILE_TEST

The plugin availability is checked in Kconfig, so all{yes,mod}config will not be bothered. Remove 'depends on !COMPILE_TEST'. Signed-off-by: Masahiro Yamada --- Changes in v2: - Remove more 'depends on' arch/Kconfig | 4 1 file changed, 4 deletions(-)

[PATCH v2 20/21] gcc-plugins: enable GCC_PLUGINS for COMPILE_TEST

The plugin availability is checked in Kconfig, so all{yes,mod}config will not be bothered. Remove 'depends on !COMPILE_TEST'. Signed-off-by: Masahiro Yamada --- Changes in v2: - Remove more 'depends on' arch/Kconfig | 4 1 file changed, 4 deletions(-) diff --git a/arch/Kconfig

[PATCH v5 3/3] arm64: allwinner: a64: bananapi-m64: add usb otg

Add usb otg support for bananapi-m64 board, - USB-ID connected with PH9 - USB-DRVVBUS controlled by N_VBUSEN pin from PMIC Signed-off-by: Jagan Teki Reviewed-by: Chen-Yu Tsai --- Changes for v5: - Kept reg_drivevbus node in alphabetical order. -

[PATCH v5 3/3] arm64: allwinner: a64: bananapi-m64: add usb otg

Add usb otg support for bananapi-m64 board, - USB-ID connected with PH9 - USB-DRVVBUS controlled by N_VBUSEN pin from PMIC Signed-off-by: Jagan Teki Reviewed-by: Chen-Yu Tsai --- Changes for v5: - Kept reg_drivevbus node in alphabetical order. - Collect Chen-Yu reviewed-by tag Changes for v4: -

[PATCH v5 1/3] regulator: axp20x: add drivevbus support for axp803

Like axp221, axp223, axp813 the axp803 is also supporting external regulator to drive the OTG VBus through N_VBUSEN PMIC pin. Add support for it. Signed-off-by: Jagan Teki Reviewed-by: Rob Herring Reviewed-by: Chen-Yu Tsai ---

[PATCH v5 2/3] arm64: allwinner: axp803: Add drivevbus regulator

Add reg_drivevbus regualtor for boards which are using external regulator to drive the OTG VBus through N_VBUSEN PMIC pin. Signed-off-by: Jagan Teki Reviewed-by: Chen-Yu Tsai --- Changes for v5: - Collect Chen-Yu reviewed-by tag Changes for v4: -

[PATCH v5 1/3] regulator: axp20x: add drivevbus support for axp803

Like axp221, axp223, axp813 the axp803 is also supporting external regulator to drive the OTG VBus through N_VBUSEN PMIC pin. Add support for it. Signed-off-by: Jagan Teki Reviewed-by: Rob Herring Reviewed-by: Chen-Yu Tsai --- Changes for v5: - Collect Chen-Yu reviewed-by tag Changes for v4:

[PATCH v5 2/3] arm64: allwinner: axp803: Add drivevbus regulator

Add reg_drivevbus regualtor for boards which are using external regulator to drive the OTG VBus through N_VBUSEN PMIC pin. Signed-off-by: Jagan Teki Reviewed-by: Chen-Yu Tsai --- Changes for v5: - Collect Chen-Yu reviewed-by tag Changes for v4: - rebase on master Changes for v3: - none

Re: [tip:irq/core 12/13] drivers/irqchip/irq-vic.c:295:2: error: implicit declaration of function 'set_handle_irq'; did you mean 'vic_handle_irq'?

On Mon, 26 Mar 2018, Palmer Dabbelt wrote: > On Mon, 26 Mar 2018 01:07:54 PDT (-0700), Arnd Bergmann wrote: > > On Tue, Mar 20, 2018 at 6:52 PM, Palmer Dabbelt wrote: > > > On Tue, 20 Mar 2018 00:53:21 PDT (-0700), t...@linutronix.de wrote: > > > > > > > > On Tue, 20 Mar 2018,

Re: [tip:irq/core 12/13] drivers/irqchip/irq-vic.c:295:2: error: implicit declaration of function 'set_handle_irq'; did you mean 'vic_handle_irq'?

On Mon, 26 Mar 2018, Palmer Dabbelt wrote: > On Mon, 26 Mar 2018 01:07:54 PDT (-0700), Arnd Bergmann wrote: > > On Tue, Mar 20, 2018 at 6:52 PM, Palmer Dabbelt wrote: > > > On Tue, 20 Mar 2018 00:53:21 PDT (-0700), t...@linutronix.de wrote: > > > > > > > > On Tue, 20 Mar 2018, kbuild test robot

Re: [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework

Hi Suman, On Tuesday 27 March 2018 06:12 AM, Suman Anna wrote: > I tried booting your tree [3] on the OMAPL138-LCDK board. I am using > NFS, and I am unable to get to the console. I don't have any issues > booting latest -next branch (next-20180326) which only has the reset and >

Re: [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework

Hi Suman, On Tuesday 27 March 2018 06:12 AM, Suman Anna wrote: > I tried booting your tree [3] on the OMAPL138-LCDK board. I am using > NFS, and I am unable to get to the console. I don't have any issues > booting latest -next branch (next-20180326) which only has the reset and >

Re: [PATCH v3 1/2] staging: media: davinci_vpfe: add error handling on kmalloc failure

On Tue, Mar 27, 2018 at 02:00:45PM +0900, Ji-Hun Kim wrote: > > Are there any opinions? I'd like to know how this patch is going. > Looks good. Thanks! Greg just hasn't gotten to it yet. regards, dan carpenter

Re: [PATCH v3 1/2] staging: media: davinci_vpfe: add error handling on kmalloc failure

On Tue, Mar 27, 2018 at 02:00:45PM +0900, Ji-Hun Kim wrote: > > Are there any opinions? I'd like to know how this patch is going. > Looks good. Thanks! Greg just hasn't gotten to it yet. regards, dan carpenter

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

On Tue, Mar 27, 2018 at 01:03:15PM +0800, Wanpeng Li wrote: > 2018-03-27 12:55 GMT+08:00 Konrad Rzeszutek Wilk : > > On Tue, Mar 27, 2018 at 12:40:20AM -0400, Konrad Rzeszutek Wilk wrote: > >> On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: > >> > From: Wanpeng

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

On Tue, Mar 27, 2018 at 01:03:15PM +0800, Wanpeng Li wrote: > 2018-03-27 12:55 GMT+08:00 Konrad Rzeszutek Wilk : > > On Tue, Mar 27, 2018 at 12:40:20AM -0400, Konrad Rzeszutek Wilk wrote: > >> On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: > >> > From: Wanpeng Li > >> > > >> > This

[PATCH] checkpatch: Test SYMBOLIC_PERMS multiple times per line

There are occasions where symbolic perms are used in a ternary like return (channel == 0) ? S_IRUGO | S_IWUSR : S_IRUGO; The current test will find the first use "S_IRUGO | S_IWUSR" but not the second use "S_IRUGO" on the same line. Improve the test to look for all instances on

[PATCH] checkpatch: Test SYMBOLIC_PERMS multiple times per line

There are occasions where symbolic perms are used in a ternary like return (channel == 0) ? S_IRUGO | S_IWUSR : S_IRUGO; The current test will find the first use "S_IRUGO | S_IWUSR" but not the second use "S_IRUGO" on the same line. Improve the test to look for all instances on

Re: [PATCH] staging: wilc1000: replace kmalloc + memcpy with kmemdup

On Mon, 26 Mar 2018 18:16:29 +0100 Colin King wrote: > From: Colin Ian King > > Replace several allocation and memcpys with kmemdup and add in some > missing memory allocation failure checks. Also fix an incorrect > -EFAULT return with

Re: [PATCH] staging: wilc1000: replace kmalloc + memcpy with kmemdup

On Mon, 26 Mar 2018 18:16:29 +0100 Colin King wrote: > From: Colin Ian King > > Replace several allocation and memcpys with kmemdup and add in some > missing memory allocation failure checks. Also fix an incorrect > -EFAULT return with -ENOMEM. > > Signed-off-by: Colin Ian King > --- >

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

2018-03-27 12:40 GMT+08:00 Konrad Rzeszutek Wilk : > On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: >> From: Wanpeng Li >> >> This patch introduces a Force Emulation Prefix (ud2a; .ascii "kvm") for >> "emulate the next instruction", the

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

2018-03-27 12:40 GMT+08:00 Konrad Rzeszutek Wilk : > On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: >> From: Wanpeng Li >> >> This patch introduces a Force Emulation Prefix (ud2a; .ascii "kvm") for >> "emulate the next instruction", the codes will be executed by emulator >> instead

Re: [PATCH v3 1/6] phy: qcom-qmp: Enable pipe_clk before checking USB3 PHY_STATUS

Hi Doug, On 3/27/2018 9:56 AM, Doug Anderson wrote: > Manu > > On Thu, Mar 22, 2018 at 11:11 PM, Manu Gautam wrote: >> QMP PHY for USB mode requires pipe_clk for calibration and PLL lock >> to take place. This clock is output from PHY to GCC clock_ctl and then >> fed

Re: [PATCH v3 1/6] phy: qcom-qmp: Enable pipe_clk before checking USB3 PHY_STATUS

Hi Doug, On 3/27/2018 9:56 AM, Doug Anderson wrote: > Manu > > On Thu, Mar 22, 2018 at 11:11 PM, Manu Gautam wrote: >> QMP PHY for USB mode requires pipe_clk for calibration and PLL lock >> to take place. This clock is output from PHY to GCC clock_ctl and then >> fed back to QMP PHY and is

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

2018-03-27 12:55 GMT+08:00 Konrad Rzeszutek Wilk : > On Tue, Mar 27, 2018 at 12:40:20AM -0400, Konrad Rzeszutek Wilk wrote: >> On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: >> > From: Wanpeng Li >> > >> > This patch introduces a Force

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

2018-03-27 12:55 GMT+08:00 Konrad Rzeszutek Wilk : > On Tue, Mar 27, 2018 at 12:40:20AM -0400, Konrad Rzeszutek Wilk wrote: >> On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: >> > From: Wanpeng Li >> > >> > This patch introduces a Force Emulation Prefix (ud2a; .ascii "kvm") for >> >

Re: [PATCH v3 1/2] staging: media: davinci_vpfe: add error handling on kmalloc failure

On Wed, Mar 21, 2018 at 01:39:09PM +0900, Ji-Hun Kim wrote: > There is no failure checking on the param value which will be allocated > memory by kmalloc. Add a null pointer checking statement. Then goto error: > and return -ENOMEM error code when kmalloc is failed. > > Signed-off-by: Ji-Hun Kim

Re: [PATCH v3 1/2] staging: media: davinci_vpfe: add error handling on kmalloc failure

On Wed, Mar 21, 2018 at 01:39:09PM +0900, Ji-Hun Kim wrote: > There is no failure checking on the param value which will be allocated > memory by kmalloc. Add a null pointer checking statement. Then goto error: > and return -ENOMEM error code when kmalloc is failed. > > Signed-off-by: Ji-Hun Kim

Re: [RFC] new SYSCALL_DEFINE/COMPAT_SYSCALL_DEFINE wrappers

On 03/27/2018 12:40 PM, Linus Torvalds wrote: > On Mon, Mar 26, 2018 at 4:37 PM, John Paul Adrian Glaubitz > wrote: >> >> What about a tarball with a minimal Debian x32 chroot? Then you can >> install interesting packages you would like to test yourself. > > That

Re: [RFC] new SYSCALL_DEFINE/COMPAT_SYSCALL_DEFINE wrappers

On 03/27/2018 12:40 PM, Linus Torvalds wrote: > On Mon, Mar 26, 2018 at 4:37 PM, John Paul Adrian Glaubitz > wrote: >> >> What about a tarball with a minimal Debian x32 chroot? Then you can >> install interesting packages you would like to test yourself. > > That probably works fine. I just

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

On Tue, Mar 27, 2018 at 12:40:20AM -0400, Konrad Rzeszutek Wilk wrote: > On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: > > From: Wanpeng Li > > > > This patch introduces a Force Emulation Prefix (ud2a; .ascii "kvm") for > > "emulate the next instruction",

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

On Tue, Mar 27, 2018 at 12:40:20AM -0400, Konrad Rzeszutek Wilk wrote: > On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: > > From: Wanpeng Li > > > > This patch introduces a Force Emulation Prefix (ud2a; .ascii "kvm") for > > "emulate the next instruction", the codes will be

Re: linux-next: manual merge of the powerpc tree with the powerpc-fixes tree

Stephen Rothwell writes: > Hi all, > > Today's linux-next merge of the powerpc tree got a conflict in: > > arch/powerpc/include/asm/cputable.h > arch/powerpc/kernel/dt_cpu_ftrs.c > > between commit: > > a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue

Re: linux-next: manual merge of the powerpc tree with the powerpc-fixes tree

Stephen Rothwell writes: > Hi all, > > Today's linux-next merge of the powerpc tree got a conflict in: > > arch/powerpc/include/asm/cputable.h > arch/powerpc/kernel/dt_cpu_ftrs.c > > between commit: > > a5d4b5891c2f ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9") > > from the

Re: [PATCH 1/1] aio: make sure the input "timeout" value is valid

On Mon, Mar 26, 2018 at 2:55 PM, Matthew Wilcox wrote: > On Mon, Mar 26, 2018 at 10:01:30PM +0200, Arnd Bergmann wrote: >> I had suggested a more complete helper function at some point, >> to take care of all combinations of checking/non-checking, 32/64 >> bit,

Re: [PATCH 1/1] aio: make sure the input "timeout" value is valid

On Mon, Mar 26, 2018 at 2:55 PM, Matthew Wilcox wrote: > On Mon, Mar 26, 2018 at 10:01:30PM +0200, Arnd Bergmann wrote: >> I had suggested a more complete helper function at some point, >> to take care of all combinations of checking/non-checking, 32/64 >> bit, microsecond/nanosecond, and

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: > From: Wanpeng Li > > This patch introduces a Force Emulation Prefix (ud2a; .ascii "kvm") for > "emulate the next instruction", the codes will be executed by emulator > instead of processor, for testing

Re: [PATCH 2/2] KVM: VMX: Add Force Emulation Prefix for "emulate the next instruction"

On Mon, Mar 26, 2018 at 07:12:15PM -0700, Wanpeng Li wrote: > From: Wanpeng Li > > This patch introduces a Force Emulation Prefix (ud2a; .ascii "kvm") for > "emulate the next instruction", the codes will be executed by emulator > instead of processor, for testing purposes. Can you expand a

Re: [PATCH 1/2] KVM: VMX: Introduce handle_ud()

On Mon, Mar 26, 2018 at 07:12:14PM -0700, Wanpeng Li wrote: > From: Wanpeng Li > > Introduce handle_ud() to handle invalid opcode, this function will be > used by later patches. > Reviewed-by: Konrad Rzeszutek Wilk Thank you! > Cc: Paolo Bonzini

Re: [PATCH 1/2] KVM: VMX: Introduce handle_ud()

On Mon, Mar 26, 2018 at 07:12:14PM -0700, Wanpeng Li wrote: > From: Wanpeng Li > > Introduce handle_ud() to handle invalid opcode, this function will be > used by later patches. > Reviewed-by: Konrad Rzeszutek Wilk Thank you! > Cc: Paolo Bonzini > Cc: Radim Krčmář > Cc: Andrew Cooper >

[PATCH] nvme-multipath: implement active-active round-robin path selector

Some storage environments (e.g., dual-port NVMe SSD) provide higher performance when using multiple paths simultaneously. Choosing a path from multiple paths in a round-robin fashion is a simple and efficient way to meet these requirements. We implement the active-active round-robin path selector

[PATCH] nvme-multipath: implement active-active round-robin path selector

Some storage environments (e.g., dual-port NVMe SSD) provide higher performance when using multiple paths simultaneously. Choosing a path from multiple paths in a round-robin fashion is a simple and efficient way to meet these requirements. We implement the active-active round-robin path selector

Re: [PATCH v4 2/3] arm64: Implement page table free interfaces

On 3/26/2018 3:25 PM, Mark Rutland wrote: On Tue, Mar 20, 2018 at 05:15:13PM +0530, Chintan Pandya wrote: +static int __pmd_free_pte_page(pmd_t *pmd, unsigned long addr, bool tlb_inv) +{ + pmd_t *table; + + if (pmd_val(*pmd)) { + table = __va(pmd_val(*pmd)); +

Re: [PATCH v4 2/3] arm64: Implement page table free interfaces

On 3/26/2018 3:25 PM, Mark Rutland wrote: On Tue, Mar 20, 2018 at 05:15:13PM +0530, Chintan Pandya wrote: +static int __pmd_free_pte_page(pmd_t *pmd, unsigned long addr, bool tlb_inv) +{ + pmd_t *table; + + if (pmd_val(*pmd)) { + table = __va(pmd_val(*pmd)); +

RE: [PATCH] Input: ALPS - fix DualPoint flag for 74 03 28 devices

Hi, We can get OTP page 0 value by EA EA E9 commands, but we cannot get it by EA EA EA E9. As far as I remember, Device initialization finish at EA command, then sends EA EA E9 commands. In this case we cannot get correct OTP page 0 value. So I changed this order. (We can get OTP page 1 value

RE: [PATCH] Input: ALPS - fix DualPoint flag for 74 03 28 devices

Hi, We can get OTP page 0 value by EA EA E9 commands, but we cannot get it by EA EA EA E9. As far as I remember, Device initialization finish at EA command, then sends EA EA E9 commands. In this case we cannot get correct OTP page 0 value. So I changed this order. (We can get OTP page 1 value

Re: [PATCH v3 1/6] phy: qcom-qmp: Enable pipe_clk before checking USB3 PHY_STATUS

Manu On Thu, Mar 22, 2018 at 11:11 PM, Manu Gautam wrote: > QMP PHY for USB mode requires pipe_clk for calibration and PLL lock > to take place. This clock is output from PHY to GCC clock_ctl and then > fed back to QMP PHY and is available from PHY only after PHY is reset

Re: [PATCH v3 1/6] phy: qcom-qmp: Enable pipe_clk before checking USB3 PHY_STATUS

Manu On Thu, Mar 22, 2018 at 11:11 PM, Manu Gautam wrote: > QMP PHY for USB mode requires pipe_clk for calibration and PLL lock > to take place. This clock is output from PHY to GCC clock_ctl and then > fed back to QMP PHY and is available from PHY only after PHY is reset > and initialized,

Re: [PATCH v4] mm, pkey: treat pkey-0 special

On Tue, Mar 27, 2018 at 2:48 PM, Michael Ellerman wrote: > Ram Pai writes: > >> On Fri, Mar 16, 2018 at 10:02:22PM +1100, Balbir Singh wrote: >>> On Fri, Mar 16, 2018 at 9:33 PM, Ram Pai wrote: >>> > Applications need the ability to

Re: [PATCH v4] mm, pkey: treat pkey-0 special

On Tue, Mar 27, 2018 at 2:48 PM, Michael Ellerman wrote: > Ram Pai writes: > >> On Fri, Mar 16, 2018 at 10:02:22PM +1100, Balbir Singh wrote: >>> On Fri, Mar 16, 2018 at 9:33 PM, Ram Pai wrote: >>> > Applications need the ability to associate an address-range with some >>> > key and latter

  1   2   3   4   5   6   7   8   9   10   >