[RESEND PATCH 2/7] time: Change posix clocks ops interfaces to use timespec64

struct timespec is not y2038 safe. Replace the posix_clock ops interfaces to use struct timespec64. The patch also changes struct itimerspec interfaces to struct itimerspec64 as itimerspec internally uses timespec and itimerspec64 uses timespec64. PTP clocks is the only module that sets up

[RESEND PATCH 2/7] time: Change posix clocks ops interfaces to use timespec64

struct timespec is not y2038 safe. Replace the posix_clock ops interfaces to use struct timespec64. The patch also changes struct itimerspec interfaces to struct itimerspec64 as itimerspec internally uses timespec and itimerspec64 uses timespec64. PTP clocks is the only module that sets up

[RESEND PATCH 3/7] Change k_clock clock_get() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[RESEND PATCH 4/7] Change k_clock clock_getres() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[RESEND PATCH 3/7] Change k_clock clock_get() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- drivers/char/mmtimer.c | 4

[RESEND PATCH 4/7] Change k_clock clock_getres() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- drivers/char/mmtimer.c | 2 +-

[RESEND PATCH 6/7] Change k_clock timer_set() and timer_get() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[RESEND PATCH 6/7] Change k_clock timer_set() and timer_get() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- drivers/char/mmtimer.c | 20

[RESEND PATCH 5/7] Change k_clock clock_set() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[RESEND PATCH 5/7] Change k_clock clock_set() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- drivers/char/mmtimer.c | 2 +-

[PATCH tip:x86/mm] x86/tls: Forcibly set the accessed bit in TLS segments

For mysterious historical reasons, struct user_desc doesn't indicate whether segments are accessed. set_thread_area() has always programmed segments as non-accessed, so the first write will set the accessed bit. This will fault if the GDT is read-only. Fix it by making TLS segments start out

[PATCH tip:x86/mm] x86/tls: Forcibly set the accessed bit in TLS segments

For mysterious historical reasons, struct user_desc doesn't indicate whether segments are accessed. set_thread_area() has always programmed segments as non-accessed, so the first write will set the accessed bit. This will fault if the GDT is read-only. Fix it by making TLS segments start out

[RESEND PATCH 1/7] time: Delete do_sys_setimeofday()

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces will be changed in a separate series. Call to do_sys_setimeofday() is superfluous as all the necessary checks and functions

[RESEND PATCH 7/7] Change k_clock nsleep() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[RESEND PATCH 1/7] time: Delete do_sys_setimeofday()

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces will be changed in a separate series. Call to do_sys_setimeofday() is superfluous as all the necessary checks and functions

[RESEND PATCH 7/7] Change k_clock nsleep() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- include/linux/hrtimer.h| 2 +-

[RESEND PATCH 0/7] Change k_clock interfaces to use timespec64

Resending to update author id in patch 7/7. The series is aimed at replacing struct timespec which is not y2038 safe with y2038 safe struct timespec64 for k_clock interfaces. The series does not change the syscall interface. This will be done in a follow up series. A few existing

[RESEND PATCH 0/7] Change k_clock interfaces to use timespec64

Resending to update author id in patch 7/7. The series is aimed at replacing struct timespec which is not y2038 safe with y2038 safe struct timespec64 for k_clock interfaces. The series does not change the syscall interface. This will be done in a follow up series. A few existing

[PATCH v2 3/3] staging: speakup: Simplify "NULL" comparisons

Fixed coding style for null comparisons in speakup driver to be more consistant with the rest of the kernel coding style. Replaced 'x != NULL' with 'x' and 'x = NULL' with '!x'. Signed-off-by: Arushi Singhal --- changes in v2 - no change

[PATCH v2 3/3] staging: speakup: Simplify "NULL" comparisons

Fixed coding style for null comparisons in speakup driver to be more consistant with the rest of the kernel coding style. Replaced 'x != NULL' with 'x' and 'x = NULL' with '!x'. Signed-off-by: Arushi Singhal --- changes in v2 - no change drivers/staging/speakup/selection.c | 2 +-

[PATCH v2 2/3] staging: speakup: Remove multiple assignments

This patch fixes the checkpatch.pl warning "multiple assignments should be avoided." Signed-off-by: Arushi Singhal --- changes in v2 - no change. drivers/staging/speakup/main.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff

[PATCH v2 0/3] staging: speakup: Multiple checkpatch issues

Improve readability by fixing multiple checkpatch.pl issues in speakup driver. Arushi Singhal (3): staging: speakup: Moved logical to previous line. staging: speakup: Remove multiple assignments staging: speakup: Simplify "NULL" comparisons drivers/staging/speakup/main.c| 30

[PATCH v2 1/3] staging: speakup: Moved logical to previous line.

Moved logical AND operator to previous line to fix the following checkpatch issue: CHECK: Logical continuations should be on the previous line. Signed-off-by: Arushi Singhal --- changes in v2 - Change the commit message. drivers/staging/speakup/main.c | 12

[PATCH v2 0/3] staging: speakup: Multiple checkpatch issues

Improve readability by fixing multiple checkpatch.pl issues in speakup driver. Arushi Singhal (3): staging: speakup: Moved logical to previous line. staging: speakup: Remove multiple assignments staging: speakup: Simplify "NULL" comparisons drivers/staging/speakup/main.c| 30

[PATCH v2 1/3] staging: speakup: Moved logical to previous line.

Moved logical AND operator to previous line to fix the following checkpatch issue: CHECK: Logical continuations should be on the previous line. Signed-off-by: Arushi Singhal --- changes in v2 - Change the commit message. drivers/staging/speakup/main.c | 12 ++-- 1 file changed, 6

[PATCH v2 2/3] staging: speakup: Remove multiple assignments

This patch fixes the checkpatch.pl warning "multiple assignments should be avoided." Signed-off-by: Arushi Singhal --- changes in v2 - no change. drivers/staging/speakup/main.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git

[PATCH] ARM: dts: sun7i: lamobo-r1: Fix CPU port RGMII settings

The CPU port of the BCM53125 is configured with RGMII (no delays) but this should actually be RGMII with transmit delay (rgmii-txid) because STMMAC takes care of inserting the transmitter delay. This fixes occasional packet loss encountered. Fixes: d7b9eaff5f0c ("ARM: dts: sun7i: Add BCM53125

[PATCH] ARM: dts: sun7i: lamobo-r1: Fix CPU port RGMII settings

The CPU port of the BCM53125 is configured with RGMII (no delays) but this should actually be RGMII with transmit delay (rgmii-txid) because STMMAC takes care of inserting the transmitter delay. This fixes occasional packet loss encountered. Fixes: d7b9eaff5f0c ("ARM: dts: sun7i: Add BCM53125

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Mar 19, 2017, at 12:41 AM, Greg Kroah-Hartman wrote: > On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote: >> Ever since sysfs migration, class_process_proc_param stopped working >> correctly as all the useful params were no longer present as lvars. >> Replace all the nasty fake proc

[PATCH] ARM: dts: sun7i: lamobo-r1: Fix CPU port RGMII settings

The CPU port of the BCM53125 is configured with RGMII (no delays) but this should actually be RGMII with transmit delay (rgmii-txid) because STMMAC takes care of inserting the transmitter delay. This fixes occasional packet loss encountered. Fixes: d7b9eaff5f0c ("ARM: dts: sun7i: Add BCM53125

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Mar 19, 2017, at 12:41 AM, Greg Kroah-Hartman wrote: > On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote: >> Ever since sysfs migration, class_process_proc_param stopped working >> correctly as all the useful params were no longer present as lvars. >> Replace all the nasty fake proc

[PATCH] ARM: dts: sun7i: lamobo-r1: Fix CPU port RGMII settings

The CPU port of the BCM53125 is configured with RGMII (no delays) but this should actually be RGMII with transmit delay (rgmii-txid) because STMMAC takes care of inserting the transmitter delay. This fixes occasional packet loss encountered. Fixes: d7b9eaff5f0c ("ARM: dts: sun7i: Add BCM53125

[PATCH] staging: speakup: fix: braces {} should used on all arms of statement

This patch fixes the checks reported by checkpatch.pl for braces {} should be used on all arms of this statement. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 35 +++-

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Sun, Mar 19, 2017 at 12:41:20AM -0400, Oleg Drokin wrote: > > On Mar 19, 2017, at 12:29 AM, Greg Kroah-Hartman wrote: > > > On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote: > >> > >> On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote: > >> > >>> On Sat, Mar 18, 2017 at

[PATCH] staging: speakup: fix: braces {} should used on all arms of statement

This patch fixes the checks reported by checkpatch.pl for braces {} should be used on all arms of this statement. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 35 +++- drivers/staging/speakup/speakup_decext.c | 6 +++---

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Sun, Mar 19, 2017 at 12:41:20AM -0400, Oleg Drokin wrote: > > On Mar 19, 2017, at 12:29 AM, Greg Kroah-Hartman wrote: > > > On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote: > >> > >> On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote: > >> > >>> On Sat, Mar 18, 2017 at

[PATCH] staging: speakup: Remove multiple assignments

This patch fixes the checkpatch.pl warning "multiple assignments should be avoided." Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/speakup/main.c

[PATCH] staging: speakup: Remove multiple assignments

This patch fixes the checkpatch.pl warning "multiple assignments should be avoided." Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/speakup/main.c b/drivers/staging/speakup/main.c index

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Mar 19, 2017, at 12:29 AM, Greg Kroah-Hartman wrote: > On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote: >> >> On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote: >> >>> On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote: Ever since sysfs migration,

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Mar 19, 2017, at 12:29 AM, Greg Kroah-Hartman wrote: > On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote: >> >> On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote: >> >>> On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote: Ever since sysfs migration,

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote: > Ever since sysfs migration, class_process_proc_param stopped working > correctly as all the useful params were no longer present as lvars. > Replace all the nasty fake proc writes with hopefully less nasty > kobject attribute search

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote: > Ever since sysfs migration, class_process_proc_param stopped working > correctly as all the useful params were no longer present as lvars. > Replace all the nasty fake proc writes with hopefully less nasty > kobject attribute search

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote: > > On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote: > > > On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote: > >> Ever since sysfs migration, class_process_proc_param stopped working > >> correctly as all the useful

Re: [PATCH/RFC] staging/lustre: Rework class_process_proc_param

On Sat, Mar 18, 2017 at 11:17:55AM -0400, Oleg Drokin wrote: > > On Mar 18, 2017, at 6:34 AM, Greg Kroah-Hartman wrote: > > > On Sat, Mar 18, 2017 at 02:24:08AM -0400, Oleg Drokin wrote: > >> Ever since sysfs migration, class_process_proc_param stopped working > >> correctly as all the useful

Re: [GIT PULL] target fixes for v4.11-rc3

On Sat, 2017-03-18 at 19:08 -0700, Nicholas A. Bellinger wrote: > Hello Linus, > > Here are the target-pending fixes for v4.11-rc3 code. Please go ahead > and pull from: > > git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master > > The bulk of the changes are in qla2xxx

Re: [GIT PULL] target fixes for v4.11-rc3

On Sat, 2017-03-18 at 19:08 -0700, Nicholas A. Bellinger wrote: > Hello Linus, > > Here are the target-pending fixes for v4.11-rc3 code. Please go ahead > and pull from: > > git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master > > The bulk of the changes are in qla2xxx

[PATCH 5/7] Change k_clock clock_set() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[PATCH 5/7] Change k_clock clock_set() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- drivers/char/mmtimer.c | 2 +-

[PATCH 2/7] time: Change posix clocks ops interfaces to use timespec64

struct timespec is not y2038 safe. Replace the posix_clock ops interfaces to use struct timespec64. The patch also changes struct itimerspec interfaces to struct itimerspec64 as itimerspec internally uses timespec and itimerspec64 uses timespec64. PTP clocks is the only module that sets up

[PATCH 7/7] Change k_clock nsleep() to use timespec64

From: Deepa Dinamani struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa

[PATCH 2/7] time: Change posix clocks ops interfaces to use timespec64

struct timespec is not y2038 safe. Replace the posix_clock ops interfaces to use struct timespec64. The patch also changes struct itimerspec interfaces to struct itimerspec64 as itimerspec internally uses timespec and itimerspec64 uses timespec64. PTP clocks is the only module that sets up

[PATCH 7/7] Change k_clock nsleep() to use timespec64

From: Deepa Dinamani struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[PATCH 1/7] time: Delete do_sys_setimeofday()

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces will be changed in a separate series. Call to do_sys_setimeofday() is superfluous as all the necessary checks and functions

[PATCH 1/7] time: Delete do_sys_setimeofday()

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces will be changed in a separate series. Call to do_sys_setimeofday() is superfluous as all the necessary checks and functions

[PATCH 4/7] Change k_clock clock_getres() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[PATCH 3/7] Change k_clock clock_get() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[PATCH 6/7] Change k_clock timer_set() and timer_get() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani ---

[PATCH 0/7] Change k_clock interfaces to use timespec64

The series is aimed at replacing struct timespec which is not y2038 safe with y2038 safe struct timespec64 for k_clock interfaces. The series does not change the syscall interface. This will be done in a follow up series. A few existing checkpatch-noted style issues, such as the 80 line

[PATCH 4/7] Change k_clock clock_getres() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- drivers/char/mmtimer.c | 2 +-

[PATCH 3/7] Change k_clock clock_get() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- drivers/char/mmtimer.c | 4

[PATCH 6/7] Change k_clock timer_set() and timer_get() to use timespec64

struct timespec is not y2038 safe. The plan is to get rid of all uses of timespec internally in the kernel. Replace uses of timespec with timespec64. The syscall interfaces themselves will be changed in a separate series. Signed-off-by: Deepa Dinamani --- drivers/char/mmtimer.c | 20

[PATCH 0/7] Change k_clock interfaces to use timespec64

The series is aimed at replacing struct timespec which is not y2038 safe with y2038 safe struct timespec64 for k_clock interfaces. The series does not change the syscall interface. This will be done in a follow up series. A few existing checkpatch-noted style issues, such as the 80 line

Re: [PATCH 4/4] mfd: cpcap: Fix bad use of IRQ sense register

On Thu, Mar 16, 2017 at 05:36:33PM -0700, Tony Lindgren wrote: > The cpcap INTS registers are for getting the value of the line, > not for configuring the type. > > Cc: Lee Jones > Cc: Marcel Partap > Cc: Michael Scott > Cc:

Re: [PATCH 4/4] mfd: cpcap: Fix bad use of IRQ sense register

On Thu, Mar 16, 2017 at 05:36:33PM -0700, Tony Lindgren wrote: > The cpcap INTS registers are for getting the value of the line, > not for configuring the type. > > Cc: Lee Jones > Cc: Marcel Partap > Cc: Michael Scott > Cc: Sebastian Reichel Reviewed-By: Sebastian Reichel > Signed-off-by:

Re: [sched/core] 8a8c69c327: WARNING: CPU: 0 PID: 8 at kernel/locking/lockdep.c:3548 lock_release

2017-03-17 22:13 GMT+08:00 Peter Zijlstra : > On Fri, Mar 17, 2017 at 03:09:09PM +0100, Peter Zijlstra wrote: >> On Fri, Mar 17, 2017 at 09:24:11PM +0800, Wanpeng Li wrote: >> > I have another version of patch which utilizes raw_spin_lock_irqsave() >> > instead of

Re: [sched/core] 8a8c69c327: WARNING: CPU: 0 PID: 8 at kernel/locking/lockdep.c:3548 lock_release

2017-03-17 22:13 GMT+08:00 Peter Zijlstra : > On Fri, Mar 17, 2017 at 03:09:09PM +0100, Peter Zijlstra wrote: >> On Fri, Mar 17, 2017 at 09:24:11PM +0800, Wanpeng Li wrote: >> > I have another version of patch which utilizes raw_spin_lock_irqsave() >> > instead of rq_lock_irqsave() in

[GIT PULL] target fixes for v4.11-rc3

Hello Linus, Here are the target-pending fixes for v4.11-rc3 code. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master The bulk of the changes are in qla2xxx target driver code to address various issues found during Cavium/QLogic's

[GIT PULL] target fixes for v4.11-rc3

Hello Linus, Here are the target-pending fixes for v4.11-rc3 code. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master The bulk of the changes are in qla2xxx target driver code to address various issues found during Cavium/QLogic's

[PATCH] drm/nouveau/mpeg: mthd returns true on success now

Signed-off-by: Ilia Mirkin Fixes: 590801c1a3 ("drm/nouveau/mpeg: remove dependence on namedb/engctx lookup") Cc: sta...@vger.kernel.org # v4.3+ --- This is just a nice-to-have, as it only affects an error print afterwards. drivers/gpu/drm/nouveau/nvkm/engine/mpeg/nv31.c

[PATCH] drm/nouveau/mpeg: mthd returns true on success now

Signed-off-by: Ilia Mirkin Fixes: 590801c1a3 ("drm/nouveau/mpeg: remove dependence on namedb/engctx lookup") Cc: sta...@vger.kernel.org # v4.3+ --- This is just a nice-to-have, as it only affects an error print afterwards. drivers/gpu/drm/nouveau/nvkm/engine/mpeg/nv31.c | 2 +-

Re: [PATCH 07/17] net: convert sock.sk_refcnt from atomic_t to refcount_t

From: Herbert Xu Date: Sun, 19 Mar 2017 00:47:59 +0800 > Eric Dumazet wrote: >> On Fri, 2017-03-17 at 07:42 +, Reshetova, Elena wrote: >> >>> Should we then first measure the actual numbers to understand what we >>> are talking here

Re: [PATCH 07/17] net: convert sock.sk_refcnt from atomic_t to refcount_t

From: Herbert Xu Date: Sun, 19 Mar 2017 00:47:59 +0800 > Eric Dumazet wrote: >> On Fri, 2017-03-17 at 07:42 +, Reshetova, Elena wrote: >> >>> Should we then first measure the actual numbers to understand what we >>> are talking here about? >>> I would be glad to do it if you suggest what

[PATCH V1] mmc: core: fix still flush cache when eMMC cache off

This patch fixes the issue that mmc_blk_issue_rq still flushes cache when eMMC cache has already been off through user space tool, such as mmc-utils. The reason is that card->ext_csd.cache_ctrl isn't reset. Signed-off-by: beanhuo --- drivers/mmc/core/block.c | 9 + 1

[PATCH V1] mmc: core: fix still flush cache when eMMC cache off

This patch fixes the issue that mmc_blk_issue_rq still flushes cache when eMMC cache has already been off through user space tool, such as mmc-utils. The reason is that card->ext_csd.cache_ctrl isn't reset. Signed-off-by: beanhuo --- drivers/mmc/core/block.c | 9 + 1 file changed, 9

[PATCH] Staging: rtl8192e - fixed style of block comments

Fixed style of block comment across whole driver Found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/rtl8192e/rtl8192e/r8190P_def.h | 2 +- drivers/staging/rtl8192e/rtl8192e/r8190P_rtl8256.c | 2 +- drivers/staging/rtl8192e/rtl8192e/r8190P_rtl8256.h

[PATCH] Staging: rtl8192e - fixed style of block comments

Fixed style of block comment across whole driver Found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/rtl8192e/rtl8192e/r8190P_def.h | 2 +- drivers/staging/rtl8192e/rtl8192e/r8190P_rtl8256.c | 2 +- drivers/staging/rtl8192e/rtl8192e/r8190P_rtl8256.h | 2 +-

Re: [PATCH v5 00/39] i.MX Media Driver

On Sat, Mar 18, 2017 at 08:41:14PM -0400, Nicolas Dufresne wrote: > Le samedi 18 mars 2017 à 20:43 +, Russell King - ARM Linux a > écrit : > > On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: > > > Can you share your gstreamer pipeline? For now, until > > >

Re: [PATCH v5 00/39] i.MX Media Driver

On Sat, Mar 18, 2017 at 08:41:14PM -0400, Nicolas Dufresne wrote: > Le samedi 18 mars 2017 à 20:43 +, Russell King - ARM Linux a > écrit : > > On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: > > > Can you share your gstreamer pipeline? For now, until > > >

Re: [PATCH v5 00/39] i.MX Media Driver

Le samedi 18 mars 2017 à 20:43 +, Russell King - ARM Linux a écrit : > On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: > > Can you share your gstreamer pipeline? For now, until > > VIDIOC_ENUM_FRAMESIZES is implemented, try a pipeline that > > does not attempt to specify a

Re: [PATCH v5 00/39] i.MX Media Driver

Le samedi 18 mars 2017 à 20:43 +, Russell King - ARM Linux a écrit : > On Sat, Mar 18, 2017 at 12:58:27PM -0700, Steve Longerbeam wrote: > > Can you share your gstreamer pipeline? For now, until > > VIDIOC_ENUM_FRAMESIZES is implemented, try a pipeline that > > does not attempt to specify a

Re: Passionate Partner

Dear Sir, Did you recieved my mail? I have sent it twice without a response. Castano Giovanni

Re: Passionate Partner

Dear Sir, Did you recieved my mail? I have sent it twice without a response. Castano Giovanni

[PATCH] Staging: ks7010 - fixed style block comments

Fixed style of all block comments across whole driver Found by checkpatch Signed-off-by: Derek Robson --- drivers/staging/ks7010/ks7010_sdio.c | 3 ++- drivers/staging/ks7010/ks_hostif.h | 35 +- drivers/staging/ks7010/ks_wlan.h | 3 ++-

[PATCH] Staging: ks7010 - fixed style block comments

Fixed style of all block comments across whole driver Found by checkpatch Signed-off-by: Derek Robson --- drivers/staging/ks7010/ks7010_sdio.c | 3 ++- drivers/staging/ks7010/ks_hostif.h | 35 +- drivers/staging/ks7010/ks_wlan.h | 3 ++-

[GIT PULL] Openrisc fixes for 4.11

Hi Linus Please consider for pull, OpenRISC fixes for build issues that were exposed by kbuild robots after 4.11 merge. All from allmodconfig builds. This includes: - bug handling 8 byte get_user calls - module build failure due to multile missing symbol exports Also, FYI, there is a build

[GIT PULL] Openrisc fixes for 4.11

Hi Linus Please consider for pull, OpenRISC fixes for build issues that were exposed by kbuild robots after 4.11 merge. All from allmodconfig builds. This includes: - bug handling 8 byte get_user calls - module build failure due to multile missing symbol exports Also, FYI, there is a build

[PATCH] perf report: enable sorting by srcline as key

Often it is interesting to know how costly a given source line is in total. Previously, one had to build these sums manually based on all addresses that pointed to the same source line. This patch introduces srcline as a sort key, which will do the aggregation for us. Paired with the recent

[PATCH] perf report: enable sorting by srcline as key

Often it is interesting to know how costly a given source line is in total. Previously, one had to build these sums manually based on all addresses that pointed to the same source line. This patch introduces srcline as a sort key, which will do the aggregation for us. Paired with the recent

Attention please;

Attention please; Please forgive my intrusion into your privacy, I am Mrs Bazira Zurmati, and I am a banker. It is true that we have not meet each other in person, but I strongly believe that no trust, no friendship in every business. I have the deceased customer’s abandoned fund, which I

Attention please;

Attention please; Please forgive my intrusion into your privacy, I am Mrs Bazira Zurmati, and I am a banker. It is true that we have not meet each other in person, but I strongly believe that no trust, no friendship in every business. I have the deceased customer’s abandoned fund, which I

[PATCH] staging: speakup: fixes braces {} used on all arms of this statement

This patch fixes the checks reported by checkpatch.pl for braces {} should be used on all arms of this statement. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 35 +++-

[PATCH] staging: speakup: fixes braces {} used on all arms of this statement

This patch fixes the checks reported by checkpatch.pl for braces {} should be used on all arms of this statement. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 35 +++- drivers/staging/speakup/speakup_decext.c | 6 +++---

[tip:WIP.x86/boot 35/62] WARNING: vmlinux.o(.text.unlikely+0x2f69): Section mismatch in reference from the function can_free_region() to the function .init.text:e820__mapped_all()

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/boot head: 687d77a5f7b2aae4ea0507888648823f7c24e974 commit: 3bce64f019a801f526cc38523c77ffda4e846155 [35/62] x86/boot/e820: Rename e820_any_mapped()/e820_all_mapped() to e820__mapped_any()/e820__mapped_all() config:

[tip:WIP.x86/boot 35/62] WARNING: vmlinux.o(.text.unlikely+0x2f69): Section mismatch in reference from the function can_free_region() to the function .init.text:e820__mapped_all()

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/boot head: 687d77a5f7b2aae4ea0507888648823f7c24e974 commit: 3bce64f019a801f526cc38523c77ffda4e846155 [35/62] x86/boot/e820: Rename e820_any_mapped()/e820_all_mapped() to e820__mapped_any()/e820__mapped_all() config:

[PATCH 0/6 v3] [GIT PULL] ftrace/x86: Ftrace cleanup and add support for -mfentry on x86_32

[ Ingo, Thomas or Peter, I believe this is all set to go now. I updated those patches that Linus commented on and I don't believe there are any more issues. I ran this through several tests (although some of my tests are failing due to bugs introduced by others in 4.11-rc2). You can take

[PATCH 5/6 v3] ftrace/x86_32: Add -mfentry support to x86_32 with DYNAMIC_FTRACE set

From: "Steven Rostedt (VMware)" x86_64 has had fentry support for some time. I did not add support to x86_32 as I was unsure if it will be used much in the future. It is still very much used, and there's issues with function graph tracing with gcc playing around with the

[PATCH 0/6 v3] [GIT PULL] ftrace/x86: Ftrace cleanup and add support for -mfentry on x86_32

[ Ingo, Thomas or Peter, I believe this is all set to go now. I updated those patches that Linus commented on and I don't believe there are any more issues. I ran this through several tests (although some of my tests are failing due to bugs introduced by others in 4.11-rc2). You can take

[PATCH 5/6 v3] ftrace/x86_32: Add -mfentry support to x86_32 with DYNAMIC_FTRACE set

From: "Steven Rostedt (VMware)" x86_64 has had fentry support for some time. I did not add support to x86_32 as I was unsure if it will be used much in the future. It is still very much used, and there's issues with function graph tracing with gcc playing around with the mcount frames, causing

[PATCH 2/6 v3] ftrace/x86_32: Move the ftrace specific code out of entry_32.S

From: "Steven Rostedt (VMware)" The function tracing hook code for ftrace is not an entry point from userspace and does not belong in the entry_*.S files. It has already been moved out of entry_64.S. This moves it out of entry_32.S into its own ftrace_32.S file.

[PATCH 2/6 v3] ftrace/x86_32: Move the ftrace specific code out of entry_32.S

From: "Steven Rostedt (VMware)" The function tracing hook code for ftrace is not an entry point from userspace and does not belong in the entry_*.S files. It has already been moved out of entry_64.S. This moves it out of entry_32.S into its own ftrace_32.S file. Signed-off-by: Steven Rostedt

  1   2   3   4   >