[PATCH] KVM: nVMX: expose INS/OUTS information support

Expose the feature to L1 hypervisor if host CPU supports it, since certain hypervisors requires it for own purposes. According to Intel SDM A.1, if CPU supports the feature, VMX_INSTRUCTION_INFO field of VMCS will contain detailed information about INS/OUTS instructions handling. This field is

[PATCH] KVM: nVMX: expose INS/OUTS information support

Expose the feature to L1 hypervisor if host CPU supports it, since certain hypervisors requires it for own purposes. According to Intel SDM A.1, if CPU supports the feature, VMX_INSTRUCTION_INFO field of VMCS will contain detailed information about INS/OUTS instructions handling. This field is

Re: [PATCH] RDS: Simplify code

On Sun, Sep 04, 2016 at 05:57:20PM +0200, Christophe JAILLET wrote: > Le 04/09/2016 à 14:20, Leon Romanovsky a écrit : > >On Sat, Sep 03, 2016 at 07:33:29AM +0200, Christophe JAILLET wrote: > >>Calling 'list_splice' followed by 'INIT_LIST_HEAD' is equivalent to > >>'list_splice_init'. > >It is not

Re: [PATCH] RDS: Simplify code

On Sun, Sep 04, 2016 at 05:57:20PM +0200, Christophe JAILLET wrote: > Le 04/09/2016 à 14:20, Leon Romanovsky a écrit : > >On Sat, Sep 03, 2016 at 07:33:29AM +0200, Christophe JAILLET wrote: > >>Calling 'list_splice' followed by 'INIT_LIST_HEAD' is equivalent to > >>'list_splice_init'. > >It is not

make[2]: *** No rule to make target 'arch/sh/boot/dts/.dtb.o', needed by 'arch/sh/boot/dts/built-in.o'.

Hi Rich, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9ca581b50dab6103183396852cc08e440fcda18e commit: 190fe191cfbead9fe089453dd092869c9469c6d4 sh: add support for linking a builtin device tree blob in the

make[2]: *** No rule to make target 'arch/sh/boot/dts/.dtb.o', needed by 'arch/sh/boot/dts/built-in.o'.

Hi Rich, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9ca581b50dab6103183396852cc08e440fcda18e commit: 190fe191cfbead9fe089453dd092869c9469c6d4 sh: add support for linking a builtin device tree blob in the

[PATCH 2/2] staging: sm750fb: fix block comment style and spelling issues in ddk750_chip.c

Fix the following warning types: - line length - block comment line * prefix - trailing */ on a separate line found by the checkpatch.pl tool in multiple block comments. Fix a single spelling error in a comment. Signed-off-by: Moshe Green ---

[PATCH 2/2] staging: sm750fb: fix block comment style and spelling issues in ddk750_chip.c

Fix the following warning types: - line length - block comment line * prefix - trailing */ on a separate line found by the checkpatch.pl tool in multiple block comments. Fix a single spelling error in a comment. Signed-off-by: Moshe Green --- drivers/staging/sm750fb/ddk750_chip.c | 49

[PATCH 1/2] staging: sm750fb: fix line length coding style issues in ddk750_chip.c

Fix multiple line length warnings found by the checkpatch.pl tool in ddk750_chip.c. Signed-off-by: Moshe Green --- drivers/staging/sm750fb/ddk750_chip.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git

[PATCH 1/2] staging: sm750fb: fix line length coding style issues in ddk750_chip.c

Fix multiple line length warnings found by the checkpatch.pl tool in ddk750_chip.c. Signed-off-by: Moshe Green --- drivers/staging/sm750fb/ddk750_chip.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/staging/sm750fb/ddk750_chip.c

[PATCH 4/4] perf/x86/cqm: Rename jump labels in intel_cqm_init()

From: Markus Elfring Date: Sun, 4 Sep 2016 19:23:57 +0200 Adjust jump labels according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- arch/x86/events/intel/cqm.c | 13 ++--- 1 file changed,

[PATCH 4/4] perf/x86/cqm: Rename jump labels in intel_cqm_init()

From: Markus Elfring Date: Sun, 4 Sep 2016 19:23:57 +0200 Adjust jump labels according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- arch/x86/events/intel/cqm.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git

[PATCH 3/4] perf/x86/cqm: One check and another variable less in intel_mbm_init()

From: Markus Elfring Date: Sun, 4 Sep 2016 19:06:33 +0200 1. Adjust a jump target to eliminate an extra check at the end. 2. Move a jump label according to the current Linux coding style convention. 3. Return only constant values for the success or failure

[PATCH 3/4] perf/x86/cqm: One check and another variable less in intel_mbm_init()

From: Markus Elfring Date: Sun, 4 Sep 2016 19:06:33 +0200 1. Adjust a jump target to eliminate an extra check at the end. 2. Move a jump label according to the current Linux coding style convention. 3. Return only constant values for the success or failure indication. 4. Delete the local

[PATCH 2/4] perf/x86/cqm: Replace two kmalloc() calls by kmalloc_array() in intel_mbm_init()

From: Markus Elfring Date: Sun, 4 Sep 2016 18:25:09 +0200 1. A multiplication for the size determination of memory allocations indicated that array data structures should be processed. Thus use the corresponding function "kmalloc_array". 2. Replace the

[PATCH 2/4] perf/x86/cqm: Replace two kmalloc() calls by kmalloc_array() in intel_mbm_init()

From: Markus Elfring Date: Sun, 4 Sep 2016 18:25:09 +0200 1. A multiplication for the size determination of memory allocations indicated that array data structures should be processed. Thus use the corresponding function "kmalloc_array". 2. Replace the specification of a data structure by

[PATCH 1/4] perf/x86/cqm: Use kmalloc_array() in intel_mbm_init()

From: Markus Elfring Date: Sun, 4 Sep 2016 17:28:13 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was

[PATCH 1/4] perf/x86/cqm: Use kmalloc_array() in intel_mbm_init()

From: Markus Elfring Date: Sun, 4 Sep 2016 17:28:13 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle

[PATCH 5/5] Staging: wlan-ng: changed definition of DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro

This patch changes definition of DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable instead of using directly (P80211DID_MKSECTION(1) | P80211DID_MKGROUP(4)). Signed-off-by: Claudiu Beznea ---

[PATCH 4/5] Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey3

This patch removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey3 macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 4

[PATCH 5/5] Staging: wlan-ng: changed definition of DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro

This patch changes definition of DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable instead of using directly (P80211DID_MKSECTION(1) | P80211DID_MKGROUP(4)). Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 3 +-- 1

[PATCH 4/5] Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey3

This patch removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey3 macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 4 drivers/staging/wlan-ng/p80211req.c | 2 +-

[PATCH 1/5] Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey0

This patch removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey0 macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 4

[PATCH 2/5] Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey1

This patch removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey1 macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 4

[PATCH 1/5] Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey0

This patch removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey0 macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 4 drivers/staging/wlan-ng/p80211req.c | 2 +-

[PATCH 2/5] Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey1

This patch removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey1 macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 4 drivers/staging/wlan-ng/p80211req.c | 2 +-

[PATCH 3/5] Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey2

This patch removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey2 macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 4

[PATCH 0/5] Keep one macro instead of 4 for wep keys

This patchset removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey<#> and uses the new macro DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Claudiu Beznea (5): Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of

[PATCH 0/5] Keep one macro instead of 4 for wep keys

This patchset removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey<#> and uses the new macro DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Claudiu Beznea (5): Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of

[PATCH 3/5] Staging: wlan-ng: uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() macro instead of DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey2

This patch removes DIDmib_dot11smt_dot11WEPDefaultKeysTable_dot11WEPDefaultKey2 macro and uses DIDmib_dot11smt_dot11WEPDefaultKeysTable_key() instead. Signed-off-by: Claudiu Beznea --- drivers/staging/wlan-ng/p80211metadef.h | 4 drivers/staging/wlan-ng/p80211req.c | 2 +-

[PATCH 0/4] perf/x86/cqm: Fine-tuning for two function implementations

From: Markus Elfring Date: Sun, 4 Sep 2016 19:40:40 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Use kmalloc_array() in intel_mbm_init() Replace two kmalloc() calls by kmalloc_array() in

[PATCH 0/4] perf/x86/cqm: Fine-tuning for two function implementations

From: Markus Elfring Date: Sun, 4 Sep 2016 19:40:40 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Use kmalloc_array() in intel_mbm_init() Replace two kmalloc() calls by kmalloc_array() in intel_mbm_init() One check and another

[PATCH] Staging: rtl8188eu: ioctl_linux: Clean up if function returned NULL on failure.

Clean some all functions to return NULL on failure. Used !x instead of x==NULL. Signed-off-by: Amit Ghadge --- drivers/staging/rtl8188eu/os_dep/ioctl_linux.c | 34 +- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git

[PATCH] Staging: rtl8188eu: ioctl_linux: Clean up if function returned NULL on failure.

Clean some all functions to return NULL on failure. Used !x instead of x==NULL. Signed-off-by: Amit Ghadge --- drivers/staging/rtl8188eu/os_dep/ioctl_linux.c | 34 +- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git

Re: Clarification for source code formatting around jump labels

On 09/04/2016 03:50 PM, SF Markus Elfring wrote: I am just curious on how much further software development "fun" the recent update by a topic like "CodingStyle: Clarify and complete chapter 7" will trigger. I don't want to drag this thread onwards for (way) too long, but clearly "it is

Re: Clarification for source code formatting around jump labels

On 09/04/2016 03:50 PM, SF Markus Elfring wrote: I am just curious on how much further software development "fun" the recent update by a topic like "CodingStyle: Clarify and complete chapter 7" will trigger. I don't want to drag this thread onwards for (way) too long, but clearly "it is

[PATCH v2] net: smsc: remove build warning of duplicate definition

The build of m32r was giving warning: In file included from drivers/net/ethernet/smsc/smc91x.c:92:0: drivers/net/ethernet/smsc/smc91x.h:448:0: warning: "SMC_inb" redefined #define SMC_inb(ioaddr, reg) ({ BUG(); 0; }) drivers/net/ethernet/smsc/smc91x.h:106:0: note: this is the location

[PATCH v2] net: smsc: remove build warning of duplicate definition

The build of m32r was giving warning: In file included from drivers/net/ethernet/smsc/smc91x.c:92:0: drivers/net/ethernet/smsc/smc91x.h:448:0: warning: "SMC_inb" redefined #define SMC_inb(ioaddr, reg) ({ BUG(); 0; }) drivers/net/ethernet/smsc/smc91x.h:106:0: note: this is the location

[PATCH] kvm/x86: Fix unused variable warning in kvm_timer_init()

From: Borislav Petkov When CONFIG_CPU_FREQ is not set, int cpu is unused and gcc rightfully warns about it: arch/x86/kvm/x86.c: In function ‘kvm_timer_init’: arch/x86/kvm/x86.c:5697:6: warning: unused variable ‘cpu’ [-Wunused-variable] int cpu; ^~~ But since it is

[PATCH] kvm/x86: Fix unused variable warning in kvm_timer_init()

From: Borislav Petkov When CONFIG_CPU_FREQ is not set, int cpu is unused and gcc rightfully warns about it: arch/x86/kvm/x86.c: In function ‘kvm_timer_init’: arch/x86/kvm/x86.c:5697:6: warning: unused variable ‘cpu’ [-Wunused-variable] int cpu; ^~~ But since it is used only in

ERROR: "__ucmpdi2" [drivers/scsi/sd_mod.ko] undefined!

Hi Mike, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9ca581b50dab6103183396852cc08e440fcda18e commit: 4e1b2d52a80d79296a5d899d73249748dea71a53 block, fs, drivers: remove REQ_OP compat defs and related code

ERROR: "__ucmpdi2" [drivers/scsi/sd_mod.ko] undefined!

Hi Mike, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9ca581b50dab6103183396852cc08e440fcda18e commit: 4e1b2d52a80d79296a5d899d73249748dea71a53 block, fs, drivers: remove REQ_OP compat defs and related code

[PATCH v2 1/1] x86, relocs: add function attributes to die()

When building the kernel with clang and some warning flags, the compiler reports the following warning: arch/x86/tools/relocs.c:979:6: warning: variable 'do_reloc' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized] if (!use_real_mode)

[PATCH v2 1/1] x86, relocs: add function attributes to die()

When building the kernel with clang and some warning flags, the compiler reports the following warning: arch/x86/tools/relocs.c:979:6: warning: variable 'do_reloc' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized] if (!use_real_mode)

[PATCH v2] MAINTAINERS: modify maintainers email of intelfb

Maik is no longer using the plusserver.de email, update with his current email. Signed-off-by: Sudip Mukherjee --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index cccbb1c..17c9bd3 100644 ---

[PATCH v2] MAINTAINERS: modify maintainers email of intelfb

Maik is no longer using the plusserver.de email, update with his current email. Signed-off-by: Sudip Mukherjee --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index cccbb1c..17c9bd3 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

Re: [PATCH v4 2/2] ASoC: Intel: Remove deprecated create_singlethread_workqueue

nce) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Bhaktipriya-Shridhar/ASoC-tlv320dac33-Remove-deprecated-create_singlethread_workqueue/20160904-235837 b

Re: [PATCH v4 2/2] ASoC: Intel: Remove deprecated create_singlethread_workqueue

nce) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Bhaktipriya-Shridhar/ASoC-tlv320dac33-Remove-deprecated-create_singlethread_workqueue/20160904-235837 b

[PATCH] Staging: comedi: das08_cs: Fix block comments use * on subsequent lines.

Fixes checkpatch warning in das08_cs.c file: WARNING: Block comments use * on subsequent lines Signed-off-by: Amit Ghadge --- drivers/staging/comedi/drivers/das08_cs.c | 70 +++ 1 file changed, 35 insertions(+), 35 deletions(-) diff --git

[PATCH] Staging: comedi: das08_cs: Fix block comments use * on subsequent lines.

Fixes checkpatch warning in das08_cs.c file: WARNING: Block comments use * on subsequent lines Signed-off-by: Amit Ghadge --- drivers/staging/comedi/drivers/das08_cs.c | 70 +++ 1 file changed, 35 insertions(+), 35 deletions(-) diff --git

Re: [PATCH v4 3/3] iio: adc: add support for Allwinner SoCs ADC

> The Allwinner SoCs all have an ADC that can also act as a touchscreen > controller and a thermal sensor. This patch adds the ADC driver which is > based on the MFD for the same SoCs ADC. nitpicking ahead > This also registers the thermal adc channel in the iio map array so > iio_hwmon could

Re: [PATCH v4 3/3] iio: adc: add support for Allwinner SoCs ADC

> The Allwinner SoCs all have an ADC that can also act as a touchscreen > controller and a thermal sensor. This patch adds the ADC driver which is > based on the MFD for the same SoCs ADC. nitpicking ahead > This also registers the thermal adc channel in the iio map array so > iio_hwmon could

Re: [PATCH] RDS: Simplify code

Le 04/09/2016 à 14:20, Leon Romanovsky a écrit : On Sat, Sep 03, 2016 at 07:33:29AM +0200, Christophe JAILLET wrote: Calling 'list_splice' followed by 'INIT_LIST_HEAD' is equivalent to 'list_splice_init'. It is not 100% accurate list_splice(y, z) INIT_LIST_HEAD(y) ==> if (!list_empty(y))

Re: [PATCH] RDS: Simplify code

Le 04/09/2016 à 14:20, Leon Romanovsky a écrit : On Sat, Sep 03, 2016 at 07:33:29AM +0200, Christophe JAILLET wrote: Calling 'list_splice' followed by 'INIT_LIST_HEAD' is equivalent to 'list_splice_init'. It is not 100% accurate list_splice(y, z) INIT_LIST_HEAD(y) ==> if (!list_empty(y))

[PATCH v4 2/2] ASoC: Intel: Remove deprecated create_singlethread_workqueue

The workqueue "post_msg_wq" queues a single work item >ipc_post_msg_wq and hence doesn't require ordering. Also, it is not being used on a memory reclaim path. Hence, it has been converted to use system_wq. System workqueues have been able to handle high level of concurrency for a long time now

[PATCH v4 2/2] ASoC: Intel: Remove deprecated create_singlethread_workqueue

The workqueue "post_msg_wq" queues a single work item >ipc_post_msg_wq and hence doesn't require ordering. Also, it is not being used on a memory reclaim path. Hence, it has been converted to use system_wq. System workqueues have been able to handle high level of concurrency for a long time now

[PATCH v4 1/2] ASoC: tlv320dac33: Remove deprecated create_singlethread_workqueue

The workqueue "dac33_wq" queues a single work item >work and hence doesn't require ordering. Also, it is not being used on a memory reclaim path. Hence, it has been converted to use system_wq. System workqueues have been able to handle high level of concurrency for a long time now and hence it's

RE: [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil

Hi Rafael, On 2016.09.02 17:57 Rafael J. Wysocki wrote: > This is a new version of the "iowait boost" series I posted a few weeks > ago. Since the first two patches from that series have been reworked and > are in linux-next now, I've rebased this series on top of my linux-next > branch. > > In

[PATCH v4 1/2] ASoC: tlv320dac33: Remove deprecated create_singlethread_workqueue

The workqueue "dac33_wq" queues a single work item >work and hence doesn't require ordering. Also, it is not being used on a memory reclaim path. Hence, it has been converted to use system_wq. System workqueues have been able to handle high level of concurrency for a long time now and hence it's

RE: [RFC/RFT][PATCH 0/4] cpufreq / sched: iowait boost in intel_pstate and schedutil

Hi Rafael, On 2016.09.02 17:57 Rafael J. Wysocki wrote: > This is a new version of the "iowait boost" series I posted a few weeks > ago. Since the first two patches from that series have been reworked and > are in linux-next now, I've rebased this series on top of my linux-next > branch. > > In

[PATCH v4 0/2] ASoc Remove deprecated create_singlethread_workqueue

This patch set removes deprecated create_singlethread_workqueue instances in sound/soc/. Bhaktipriya Shridhar (2): ASoC: tlv320dac33: Remove deprecated create_singlethread_workqueue ASoC: Intel: Remove deprecated create_singlethread_workqueue sound/soc/codecs/tlv320dac33.c | 17

[PATCH v4 0/2] ASoc Remove deprecated create_singlethread_workqueue

This patch set removes deprecated create_singlethread_workqueue instances in sound/soc/. Bhaktipriya Shridhar (2): ASoC: tlv320dac33: Remove deprecated create_singlethread_workqueue ASoC: Intel: Remove deprecated create_singlethread_workqueue sound/soc/codecs/tlv320dac33.c | 17

[PATCH][RFC] mfd: intel-lpss: Avoid resuming runtime-suspended lpss unnecessarily

We have report that the intel_lpss_prepare() takes too much time during suspend, and this is because we first resume the devices from runtime suspend by resume_lpss_device(), to make sure they are in proper state before system suspend, which takes 100ms for each LPSS devices(PCI power state from

[PATCH][RFC] mfd: intel-lpss: Avoid resuming runtime-suspended lpss unnecessarily

We have report that the intel_lpss_prepare() takes too much time during suspend, and this is because we first resume the devices from runtime suspend by resume_lpss_device(), to make sure they are in proper state before system suspend, which takes 100ms for each LPSS devices(PCI power state from

Re: [PATCH] staging/android: mark sync_timeline_create() static

On Sat, Sep 03, 2016 at 02:34:13PM +0800, Baoyou Xie wrote: > We get 1 warning when building kernel with W=1: > drivers/staging/android/sw_sync.c:56:23: warning: no previous prototype for > 'sync_timeline_create' [-Wmissing-prototypes] > > In fact, this function is only used in the file in which

Re: [PATCH] staging/android: mark sync_timeline_create() static

On Sat, Sep 03, 2016 at 02:34:13PM +0800, Baoyou Xie wrote: > We get 1 warning when building kernel with W=1: > drivers/staging/android/sw_sync.c:56:23: warning: no previous prototype for > 'sync_timeline_create' [-Wmissing-prototypes] > > In fact, this function is only used in the file in which

Re: [PATCH] staging: rtl8712: fixed comment style and space indent

On Fri, Sep 02, 2016 at 09:14:15PM +0800, Louie Lu wrote: > fixed comment style and space indent report from checkpatch > in rtl8712/rtl871x_ioctl_linux.c: > > * WARNING: Statements should start on a tabstop > * WARNING: Block comments use * on subsequent lines > * WARNING: suspect code indent

Re: [PATCH] staging: rtl8712: fixed comment style and space indent

On Fri, Sep 02, 2016 at 09:14:15PM +0800, Louie Lu wrote: > fixed comment style and space indent report from checkpatch > in rtl8712/rtl871x_ioctl_linux.c: > > * WARNING: Statements should start on a tabstop > * WARNING: Block comments use * on subsequent lines > * WARNING: suspect code indent

Re: [PATCH][RFC v5] timekeeping: Ignore the bogus sleep time if pm_trace is enabled

Hi Thomas, Rafael, On Fri, Sep 02, 2016 at 09:26:51PM +0200, Thomas Gleixner wrote: > On Wed, 31 Aug 2016, Rafael J. Wysocki wrote: > > On Monday, August 29, 2016 12:40:39 AM Chen Yu wrote: > > > + > > > + /* > > > + * Make rtc-based persistent clock unusable > > > + * if pm_trace is enabled,

Re: [PATCH][RFC v5] timekeeping: Ignore the bogus sleep time if pm_trace is enabled

Hi Thomas, Rafael, On Fri, Sep 02, 2016 at 09:26:51PM +0200, Thomas Gleixner wrote: > On Wed, 31 Aug 2016, Rafael J. Wysocki wrote: > > On Monday, August 29, 2016 12:40:39 AM Chen Yu wrote: > > > + > > > + /* > > > + * Make rtc-based persistent clock unusable > > > + * if pm_trace is enabled,

[PATCH v3 4/4] fs/afs/flock: Remove deprecated create_singlethread_workqueue

The workqueue "afs_lock_manager" queues work item >lock_work, per vnode. Since there can be multiple vnodes and since their work items can be executed concurrently, alloc_workqueue has been used to replace the deprecated create_singlethread_workqueue instance. The WQ_MEM_RECLAIM flag has been set

[PATCH v3 4/4] fs/afs/flock: Remove deprecated create_singlethread_workqueue

The workqueue "afs_lock_manager" queues work item >lock_work, per vnode. Since there can be multiple vnodes and since their work items can be executed concurrently, alloc_workqueue has been used to replace the deprecated create_singlethread_workqueue instance. The WQ_MEM_RECLAIM flag has been set

[PATCH v3 3/4] fs/afs/callback: Remove deprecated create_singlethread_workqueue

The workqueue "afs_callback_update_worker" queues multiple work items viz >cb_broken_work, >cb_break_work which require strict execution ordering. Hence, an ordered dedicated workqueue has been used. Since the workqueue is being used on a memory reclaim path, WQ_MEM_RECLAIM has been set to

[PATCH v3 3/4] fs/afs/callback: Remove deprecated create_singlethread_workqueue

The workqueue "afs_callback_update_worker" queues multiple work items viz >cb_broken_work, >cb_break_work which require strict execution ordering. Hence, an ordered dedicated workqueue has been used. Since the workqueue is being used on a memory reclaim path, WQ_MEM_RECLAIM has been set to

[PATCH v3 2/4] fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue

The workqueue "afs_async_calls" queues work item >async_work per afs_call. Since there could be multiple calls and since these calls can be run concurrently, alloc_workqueue has been used to replace the deprecated create_singlethread_workqueue instance. The WQ_MEM_RECLAIM flag has been set to

[PATCH v3 2/4] fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue

The workqueue "afs_async_calls" queues work item >async_work per afs_call. Since there could be multiple calls and since these calls can be run concurrently, alloc_workqueue has been used to replace the deprecated create_singlethread_workqueue instance. The WQ_MEM_RECLAIM flag has been set to

[PATCH v3 1/4] fs/afs/vlocation: Remove deprecated create_singlethread_workqueue

The workqueue "afs_vlocation_update_worker" queues a single work item _vlocation_update and hence it doesn't require execution ordering. Hence, alloc_workqueue has been used to replace the deprecated create_singlethread_workqueue instance. Since the workqueue is being used on a memory reclaim

[PATCH v3 1/4] fs/afs/vlocation: Remove deprecated create_singlethread_workqueue

The workqueue "afs_vlocation_update_worker" queues a single work item _vlocation_update and hence it doesn't require execution ordering. Hence, alloc_workqueue has been used to replace the deprecated create_singlethread_workqueue instance. Since the workqueue is being used on a memory reclaim

[PATCH v3 0/4] fs/afs: Remove deprecated create_singlethread_workqueue

This patch set removes deprecated create_singlethread_workqueue usages in fs/afs. Bhaktipriya Shridhar (4): fs/afs/vlocation: Remove deprecated create_singlethread_workqueue fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue fs/afs/callback: Remove deprecated

[PATCH v3 0/4] fs/afs: Remove deprecated create_singlethread_workqueue

This patch set removes deprecated create_singlethread_workqueue usages in fs/afs. Bhaktipriya Shridhar (4): fs/afs/vlocation: Remove deprecated create_singlethread_workqueue fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue fs/afs/callback: Remove deprecated

Re: [PATCH] staging:ks7010:Fix warning about coding style spacing issue around asterisk in ks_wlan_net.c

On Wed, Aug 31, 2016 at 08:20:10PM -0400, Nicholas Krause wrote: > This fixes warning around a asterisk used in ks_wlan_net.c > for the define statement used for this driver's transmit > queue timeout value as defined by the marco, TX_TIMEOUT. > Signed-off-by: Nicholas Krause

Re: [PATCH] staging:ks7010:Fix warning about coding style spacing issue around asterisk in ks_wlan_net.c

On Wed, Aug 31, 2016 at 08:20:10PM -0400, Nicholas Krause wrote: > This fixes warning around a asterisk used in ks_wlan_net.c > for the define statement used for this driver's transmit > queue timeout value as defined by the marco, TX_TIMEOUT. > Signed-off-by: Nicholas Krause > --- Please keep a

Re: [PATCH v2 1/1] drivers: staging: rtl8723au: hal: Remove pointless test

On Sun, Sep 04, 2016 at 01:01:20PM +0200, Matthias Beyer wrote: > This patch removes the pointless `else if` test. > > Signed-off-by: Matthias Beyer > Reported-by: David Binderman > --- looks like Greg has already applied your first patch.

Re: [PATCH v2 1/1] drivers: staging: rtl8723au: hal: Remove pointless test

On Sun, Sep 04, 2016 at 01:01:20PM +0200, Matthias Beyer wrote: > This patch removes the pointless `else if` test. > > Signed-off-by: Matthias Beyer > Reported-by: David Binderman > --- looks like Greg has already applied your first patch. db0c12744f8d ("drivers: staging: rtl8723au: hal:

Re: fs: GPF in bd_mount

On Sun, Sep 04, 2016 at 12:43:28PM +0200, Dmitry Vyukov wrote: AFAICS, it's been introduced in commit 3684aa7099e0ab1038a1a1bf717ae60ffc3018d1 Author: Shaohua Li Date: Mon Feb 22 15:27:40 2016 -0700 block-dev: enable writeback cgroup support See if you can reproduce it after

Re: fs: GPF in bd_mount

On Sun, Sep 04, 2016 at 12:43:28PM +0200, Dmitry Vyukov wrote: AFAICS, it's been introduced in commit 3684aa7099e0ab1038a1a1bf717ae60ffc3018d1 Author: Shaohua Li Date: Mon Feb 22 15:27:40 2016 -0700 block-dev: enable writeback cgroup support See if you can reproduce it after the

Re: Possible code defects: macros and precedence

On Sun, 2016-09-04 at 18:10 +0800, Julia Lawall wrote: > On Sat, 3 Sep 2016, Joe Perches wrote: > > There are many nominally incorrect macro definitions > > in linux-kernel source where parentheses are not used > > for various macros arguments with calculations. > > > > Does coccinelle or smatch

Re: Possible code defects: macros and precedence

On Sun, 2016-09-04 at 18:10 +0800, Julia Lawall wrote: > On Sat, 3 Sep 2016, Joe Perches wrote: > > There are many nominally incorrect macro definitions > > in linux-kernel source where parentheses are not used > > for various macros arguments with calculations. > > > > Does coccinelle or smatch

[PATCH 2/2 RESEND] staging: ks7010: fix memory leak

If the firmware request failed we were just returning but we missed freeing the memory and releasing the MMC Host. Signed-off-by: Sudip Mukherjee --- drivers/staging/ks7010/ks7010_sdio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/2 RESEND] staging: ks7010: return on failure

On failure we were jumping to error_out0 where we were trying sdio_release_host() but at this point of execution we still have not done sdio_claim_host() and as a result host->claimed can still be 0. And if host->claimed is 0 then WARN_ON(!host->claimed) will give a warning. Moreover, if it is

[PATCH 2/2 RESEND] staging: ks7010: fix memory leak

If the firmware request failed we were just returning but we missed freeing the memory and releasing the MMC Host. Signed-off-by: Sudip Mukherjee --- drivers/staging/ks7010/ks7010_sdio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/ks7010/ks7010_sdio.c

[PATCH 1/2 RESEND] staging: ks7010: return on failure

On failure we were jumping to error_out0 where we were trying sdio_release_host() but at this point of execution we still have not done sdio_claim_host() and as a result host->claimed can still be 0. And if host->claimed is 0 then WARN_ON(!host->claimed) will give a warning. Moreover, if it is

[PATCH 1/3] virtio: Basic implementation of virtio pstore driver

The virtio pstore driver provides interface to the pstore subsystem so that the guest kernel's log/dump message can be saved on the host machine. Users can access the log file directly on the host, or on the guest at the next boot using pstore filesystem. It currently deals with kernel log

[PATCH 1/3] virtio: Basic implementation of virtio pstore driver

The virtio pstore driver provides interface to the pstore subsystem so that the guest kernel's log/dump message can be saved on the host machine. Users can access the log file directly on the host, or on the guest at the next boot using pstore filesystem. It currently deals with kernel log

[RFC/PATCHSET 0/3] virtio: Implement virtio pstore device (v5)

Hello, This is another iteration of the virtio-pstore work. I've addressed comments from Michael S. Tsirkin on the kernel code. * changes in v5) - convert __virtioXX to __leXX (Michael) * changes in v4) - use qio_channel_file_new_path() (Daniel) - rename to delete_old_pstore_file

[PATCH 2/3] qemu: Implement virtio-pstore device

From: Namhyung Kim Add virtio pstore device to allow kernel log files saved on the host. It will save the log files on the directory given by pstore device option. $ qemu-system-x86_64 -device virtio-pstore,directory=dir-xx ... (guest) # echo c > /proc/sysrq-trigger

[RFC/PATCHSET 0/3] virtio: Implement virtio pstore device (v5)

Hello, This is another iteration of the virtio-pstore work. I've addressed comments from Michael S. Tsirkin on the kernel code. * changes in v5) - convert __virtioXX to __leXX (Michael) * changes in v4) - use qio_channel_file_new_path() (Daniel) - rename to delete_old_pstore_file

[PATCH 2/3] qemu: Implement virtio-pstore device

From: Namhyung Kim Add virtio pstore device to allow kernel log files saved on the host. It will save the log files on the directory given by pstore device option. $ qemu-system-x86_64 -device virtio-pstore,directory=dir-xx ... (guest) # echo c > /proc/sysrq-trigger $ ls dir-xx

[PATCH 3/3] kvmtool: Implement virtio-pstore device

From: Namhyung Kim Add virtio pstore device to allow kernel log messages saved on the host. With this patch, it will save the log files under directory given by --pstore option. $ lkvm run --pstore=dir-xx (guest) # echo c > /proc/sysrq-trigger $ ls dir-xx

[PATCH 3/3] kvmtool: Implement virtio-pstore device

From: Namhyung Kim Add virtio pstore device to allow kernel log messages saved on the host. With this patch, it will save the log files under directory given by --pstore option. $ lkvm run --pstore=dir-xx (guest) # echo c > /proc/sysrq-trigger $ ls dir-xx dmesg-1.enc.z dmesg-2.enc.z

<    1   2   3   4   5   6   >