[patch v2 5/6] staging: speakup: migrate apollo, ltlk, audptr, decext, dectlk and spkout

This patch simply uses the changes introduced in previous patches and migrates apollo, ltlk, audptr, decext, spkout and dectlk. Migrations are straightforward function pointer updates. Signed-off by: Okash Khawaja Reviewed-by: Samuel Thibault

[patch v2 3/6] staging: speakup: migrate acntsa, bns, dummy and txprt to ttyio

This changes the above five synths to TTY-based comms. They were chosen as a first pass because their serial comms are straightforward, i.e. they don't use serial input and don't do internal port knocking. Signed-off-by: Okash Khawaja Reviewed-by: Samuel Thibault

[patch v2 5/6] staging: speakup: migrate apollo, ltlk, audptr, decext, dectlk and spkout

This patch simply uses the changes introduced in previous patches and migrates apollo, ltlk, audptr, decext, spkout and dectlk. Migrations are straightforward function pointer updates. Signed-off by: Okash Khawaja Reviewed-by: Samuel Thibault Index:

[patch v2 3/6] staging: speakup: migrate acntsa, bns, dummy and txprt to ttyio

This changes the above five synths to TTY-based comms. They were chosen as a first pass because their serial comms are straightforward, i.e. they don't use serial input and don't do internal port knocking. Signed-off-by: Okash Khawaja Reviewed-by: Samuel Thibault Index:

[patch v2 2/6] staging: speakup: add tty-based comms functions

This adds spk_ttyio.c file. It contains a set of functions which implement those methods in spk_synth struct which relate to sending bytes out using serial comms. Implementations in this file perform the same function but using TTY subsystem instead. Currently synths access serial ports, directly

[patch v2 0/6] staging: speakup: migrate synths to use TTY-based comms

This patchset migrates all external synths from using raw serial i/o to using tty-based comms. The synths not migrated are internal ones - plugged directly into motherboard, communicating over ISA etc. It's important to note that these patches access TTY from inside kernel. Here is the summary of

[patch v2 2/6] staging: speakup: add tty-based comms functions

This adds spk_ttyio.c file. It contains a set of functions which implement those methods in spk_synth struct which relate to sending bytes out using serial comms. Implementations in this file perform the same function but using TTY subsystem instead. Currently synths access serial ports, directly

[patch v2 0/6] staging: speakup: migrate synths to use TTY-based comms

This patchset migrates all external synths from using raw serial i/o to using tty-based comms. The synths not migrated are internal ones - plugged directly into motherboard, communicating over ISA etc. It's important to note that these patches access TTY from inside kernel. Here is the summary of

Re: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

On Mon, 15 May 2017 08:19:28 + "Cheng, Collins" wrote: > Hi Williamson, > > We cannot assume BIOS supports SR-IOV, actually only newer server motherboard > BIOS supports SR-IOV. Normal desktop motherboard BIOS or older server > motherboard BIOS doesn't support

Re: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

On Mon, 15 May 2017 08:19:28 + "Cheng, Collins" wrote: > Hi Williamson, > > We cannot assume BIOS supports SR-IOV, actually only newer server motherboard > BIOS supports SR-IOV. Normal desktop motherboard BIOS or older server > motherboard BIOS doesn't support SR-IOV. This issue would

Re: [PATCH v5 0/3] Handle memmap and mem kernel options in boot stage kaslr

On Fri, May 12, 2017 at 10:46 PM, Baoquan He wrote: > People reported kernel panic occurs during system boots up with mem boot > option. > After checking code, several problems are found about memmap= and mem= in > boot stage > kaslr. > > *) In commit f28442497b5c ("x86/boot:

Re: [PATCH v5 0/3] Handle memmap and mem kernel options in boot stage kaslr

On Fri, May 12, 2017 at 10:46 PM, Baoquan He wrote: > People reported kernel panic occurs during system boots up with mem boot > option. > After checking code, several problems are found about memmap= and mem= in > boot stage > kaslr. > > *) In commit f28442497b5c ("x86/boot: Fix KASLR and

Re: [PATCH 2/2] kvm: arm/arm64: Fix use after free of stage2 page table

On 15/05/17 18:43, Christoffer Dall wrote: On Mon, May 15, 2017 at 02:36:58PM +0100, Suzuki K Poulose wrote: On 15/05/17 11:00, Christoffer Dall wrote: Hi Suzuki, So I don't think this change is wrong, but I wonder if it's sufficient. For example, I can see that this function is called from

Re: [PATCH 2/2] kvm: arm/arm64: Fix use after free of stage2 page table

On 15/05/17 18:43, Christoffer Dall wrote: On Mon, May 15, 2017 at 02:36:58PM +0100, Suzuki K Poulose wrote: On 15/05/17 11:00, Christoffer Dall wrote: Hi Suzuki, So I don't think this change is wrong, but I wonder if it's sufficient. For example, I can see that this function is called from

Re: [PATCH 08/17] uuid: hoist uuid_is_null() helper from libnvdimm

On Mon, May 15, 2017 at 8:42 AM, Christoph Hellwig wrote: > Hoist the libnvdimm helper as an inline helper to linux/uuid.h > using an auxiliary const variable uuid_null in lib/uuid.c. > > [hch: also add the guid variant. Both do the same but I'd like > to keep casts to a minimum] >

Re: [PATCH 08/17] uuid: hoist uuid_is_null() helper from libnvdimm

On Mon, May 15, 2017 at 8:42 AM, Christoph Hellwig wrote: > Hoist the libnvdimm helper as an inline helper to linux/uuid.h > using an auxiliary const variable uuid_null in lib/uuid.c. > > [hch: also add the guid variant. Both do the same but I'd like > to keep casts to a minimum] > > The common

Re: [PATCH] clk: bcm2835: Correct the prediv logic

Hi Eric, > Eric Anholt hat am 15. Mai 2017 um 19:35 geschrieben: > > > From: Phil Elwell > > If a clock has the prediv flag set, both the integer and fractional > parts must be scaled when calculating the resulting frequency. > > Signed-off-by: Phil

Re: [PATCH] clk: bcm2835: Correct the prediv logic

Hi Eric, > Eric Anholt hat am 15. Mai 2017 um 19:35 geschrieben: > > > From: Phil Elwell > > If a clock has the prediv flag set, both the integer and fractional > parts must be scaled when calculating the resulting frequency. > > Signed-off-by: Phil Elwell > Signed-off-by: Eric Anholt >

Re: [PATCH 3/3] coresight: etb10: Improve a size determination in etb_alloc_buffer()

On 12 May 2017 at 12:53, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 12 May 2017 20:36:03 +0200 > > Replace the specification of a data structure by a pointer dereference > as the parameter for the operator "sizeof"

Re: [PATCH 3/3] coresight: etb10: Improve a size determination in etb_alloc_buffer()

On 12 May 2017 at 12:53, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 12 May 2017 20:36:03 +0200 > > Replace the specification of a data structure by a pointer dereference > as the parameter for the operator "sizeof" to make the corresponding size > determination a bit safer

Re: [PATCH v3] Add "shutdown" to "struct class".

On Mon, May 15, 2017 at 10:39:08AM -0700, Josh Zimmerman wrote: > (Continuing thread from patch v1) > > > On Sat, May 13, 2017 at 12:43:11PM +, Winkler, Tomas wrote: > > > > > The TPM class has some common shutdown code that must be executed > > > > > for all drivers. This adds some needed

Re: [PATCH v3] Add "shutdown" to "struct class".

On Mon, May 15, 2017 at 10:39:08AM -0700, Josh Zimmerman wrote: > (Continuing thread from patch v1) > > > On Sat, May 13, 2017 at 12:43:11PM +, Winkler, Tomas wrote: > > > > > The TPM class has some common shutdown code that must be executed > > > > > for all drivers. This adds some needed

Re: [xfstests PATCH v2 2/3] ext4: allow ext4 to use $SCRATCH_LOGDEV

On Tue, May 09, 2017 at 12:12:44PM -0400, Jeff Layton wrote: > The writeback error handling test requires that you put the journal on a > separate device. This allows us to use dmerror to simulate data > writeback failure, without affecting the journal. > > xfs already has infrastructure for this

Re: [xfstests PATCH v2 2/3] ext4: allow ext4 to use $SCRATCH_LOGDEV

On Tue, May 09, 2017 at 12:12:44PM -0400, Jeff Layton wrote: > The writeback error handling test requires that you put the journal on a > separate device. This allows us to use dmerror to simulate data > writeback failure, without affecting the journal. > > xfs already has infrastructure for this

Re: [PATCH 2/3] coresight: etb10: Fix a typo in a comment line

On 12 May 2017 at 12:52, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 12 May 2017 20:30:42 +0200 > > Delete a character in this description for a condition check. > > Signed-off-by: Markus Elfring

Re: [PATCH 2/3] coresight: etb10: Fix a typo in a comment line

On 12 May 2017 at 12:52, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 12 May 2017 20:30:42 +0200 > > Delete a character in this description for a condition check. > > Signed-off-by: Markus Elfring > --- > drivers/hwtracing/coresight/coresight-etb10.c | 2 +- > 1 file changed, 1

Re: [PATCH 1/3] coresight: etb10: Delete an error message for a failed memory allocation in etb_probe()

On 12 May 2017 at 12:51, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 12 May 2017 20:23:43 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the

Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf

On Mon, 15 May 2017 03:36:50 + "Chen, Xiaoguang" wrote: > Hi Alex and Gerd, > > >-Original Message- > >From: Alex Williamson [mailto:alex.william...@redhat.com] > >Sent: Saturday, May 13, 2017 12:38 AM > >To: Gerd Hoffmann > >Cc: Chen,

Re: [PATCH 1/3] coresight: etb10: Delete an error message for a failed memory allocation in etb_probe()

On 12 May 2017 at 12:51, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 12 May 2017 20:23:43 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Link: >

Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf

On Mon, 15 May 2017 03:36:50 + "Chen, Xiaoguang" wrote: > Hi Alex and Gerd, > > >-Original Message- > >From: Alex Williamson [mailto:alex.william...@redhat.com] > >Sent: Saturday, May 13, 2017 12:38 AM > >To: Gerd Hoffmann > >Cc: Chen, Xiaoguang ; Tian, Kevin > >;

Re: [PATCH 2/2] kvm: arm/arm64: Fix use after free of stage2 page table

On Mon, May 15, 2017 at 02:36:58PM +0100, Suzuki K Poulose wrote: > On 15/05/17 11:00, Christoffer Dall wrote: > >Hi Suzuki, > > > >On Wed, May 03, 2017 at 03:17:52PM +0100, Suzuki K Poulose wrote: > >>We yield the kvm->mmu_lock occassionaly while performing an operation > >>(e.g, unmap or

Re: [PATCH 2/2] kvm: arm/arm64: Fix use after free of stage2 page table

On Mon, May 15, 2017 at 02:36:58PM +0100, Suzuki K Poulose wrote: > On 15/05/17 11:00, Christoffer Dall wrote: > >Hi Suzuki, > > > >On Wed, May 03, 2017 at 03:17:52PM +0100, Suzuki K Poulose wrote: > >>We yield the kvm->mmu_lock occassionaly while performing an operation > >>(e.g, unmap or

Re: [PATCH] ipc/sem: Avoid indexing past end of sem_array

On Sun, May 14, 2017 at 6:54 AM, Manfred Spraul wrote: > Hi Kees, > > On 05/09/2017 12:23 AM, Kees Cook wrote: >> >> This changes the struct + trailing data pattern to using a void * so that >> the end of sem_array is found without possibly indexing past the end which >>

Re: [PATCH] ipc/sem: Avoid indexing past end of sem_array

On Sun, May 14, 2017 at 6:54 AM, Manfred Spraul wrote: > Hi Kees, > > On 05/09/2017 12:23 AM, Kees Cook wrote: >> >> This changes the struct + trailing data pattern to using a void * so that >> the end of sem_array is found without possibly indexing past the end which >> can upset some static

Re: [PATCH v3] Add "shutdown" to "struct class".

(Continuing thread from patch v1) > > On Sat, May 13, 2017 at 12:43:11PM +, Winkler, Tomas wrote: > > > > The TPM class has some common shutdown code that must be executed > > > > for all drivers. This adds some needed functionality for that > > > > > > The issue with this is, that on some

Re: [PATCH v3] Add "shutdown" to "struct class".

(Continuing thread from patch v1) > > On Sat, May 13, 2017 at 12:43:11PM +, Winkler, Tomas wrote: > > > > The TPM class has some common shutdown code that must be executed > > > > for all drivers. This adds some needed functionality for that > > > > > > The issue with this is, that on some

Re: [PATCH] mdio: mux: fix device_node_continue.cocci warnings

On Fri, May 12, 2017 at 6:52 PM, Florian Fainelli wrote: > On 05/12/2017 09:22 AM, David Miller wrote: >> From: Julia Lawall >> Date: Fri, 12 May 2017 22:54:23 +0800 (SGT) >> >>> Device node iterators put the previous value of the index variable, so an

Re: [PATCH] mdio: mux: fix device_node_continue.cocci warnings

On Fri, May 12, 2017 at 6:52 PM, Florian Fainelli wrote: > On 05/12/2017 09:22 AM, David Miller wrote: >> From: Julia Lawall >> Date: Fri, 12 May 2017 22:54:23 +0800 (SGT) >> >>> Device node iterators put the previous value of the index variable, so an >>> explicit put causes a double put. >>

[PATCH v3] Add "shutdown" to "struct class".

The TPM class has some common shutdown code that must be executed for all drivers. This adds some needed functionality for that. Usage example: 'tpm: Issue a TPM2_Shutdown for TPM2 devices.' (see https://patchwork.kernel.org/patch/9724919/ for v2). Signed-off-by: Josh Zimmerman

[PATCH] clk: bcm2835: Correct the prediv logic

From: Phil Elwell If a clock has the prediv flag set, both the integer and fractional parts must be scaled when calculating the resulting frequency. Signed-off-by: Phil Elwell Signed-off-by: Eric Anholt --- While this is a bugfix,

[PATCH v3] Add "shutdown" to "struct class".

The TPM class has some common shutdown code that must be executed for all drivers. This adds some needed functionality for that. Usage example: 'tpm: Issue a TPM2_Shutdown for TPM2 devices.' (see https://patchwork.kernel.org/patch/9724919/ for v2). Signed-off-by: Josh Zimmerman - v2: Add

[PATCH] clk: bcm2835: Correct the prediv logic

From: Phil Elwell If a clock has the prediv flag set, both the integer and fractional parts must be scaled when calculating the resulting frequency. Signed-off-by: Phil Elwell Signed-off-by: Eric Anholt --- While this is a bugfix, I haven't put a "Fixes:" line in here to get it automatically

Re: [PATCH 00/17] convert/reorganize Documentation/security/

On Mon, May 15, 2017 at 10:26 AM, Jonathan Corbet wrote: > On Sat, 13 May 2017 04:51:36 -0700 > Kees Cook wrote: > >> This ReSTifies everything under Documentation/security/, and reorganizes >> some of it (mainly the LSMs) under /admin-guide/ per Jon's

Re: [PATCH 00/17] convert/reorganize Documentation/security/

On Mon, May 15, 2017 at 10:26 AM, Jonathan Corbet wrote: > On Sat, 13 May 2017 04:51:36 -0700 > Kees Cook wrote: > >> This ReSTifies everything under Documentation/security/, and reorganizes >> some of it (mainly the LSMs) under /admin-guide/ per Jon's request. Since >> /security/ is already

Re: [v6 PATCH 07/21] x86/insn-eval: Add utility function to get segment descriptor

On Thu, May 11, 2017 at 07:13:57PM -0700, Ricardo Neri wrote: > Sure I can. Would this trigger a v8 of my series? I was hoping v7 series > could be merged and then start doing incremental work on top of it. Does > it make sense? I guess that's tip guys' call. -- Regards/Gruss, Boris. SUSE

Re: [v6 PATCH 07/21] x86/insn-eval: Add utility function to get segment descriptor

On Thu, May 11, 2017 at 07:13:57PM -0700, Ricardo Neri wrote: > Sure I can. Would this trigger a v8 of my series? I was hoping v7 series > could be merged and then start doing incremental work on top of it. Does > it make sense? I guess that's tip guys' call. -- Regards/Gruss, Boris. SUSE

[PATCH v4 2/4] remoteproc: qcom: refactor mss fw image loading sequence

This patch refactor code to first load all firmware blobs and then update modem proc to authenticate and boot fw. Also make a trivial change in a error log. Signed-off-by: Avaneesh Kumar Dwivedi --- drivers/remoteproc/qcom_q6v5_pil.c | 25 - 1

[PATCH v4 2/4] remoteproc: qcom: refactor mss fw image loading sequence

This patch refactor code to first load all firmware blobs and then update modem proc to authenticate and boot fw. Also make a trivial change in a error log. Signed-off-by: Avaneesh Kumar Dwivedi --- drivers/remoteproc/qcom_q6v5_pil.c | 25 - 1 file changed, 12

Re: [PATCH 00/17] convert/reorganize Documentation/security/

On Sat, 13 May 2017 04:51:36 -0700 Kees Cook wrote: > This ReSTifies everything under Documentation/security/, and reorganizes > some of it (mainly the LSMs) under /admin-guide/ per Jon's request. Since > /security/ is already being indexed under the kernel development

Re: [PATCH 00/17] convert/reorganize Documentation/security/

On Sat, 13 May 2017 04:51:36 -0700 Kees Cook wrote: > This ReSTifies everything under Documentation/security/, and reorganizes > some of it (mainly the LSMs) under /admin-guide/ per Jon's request. Since > /security/ is already being indexed under the kernel development portion > of the sphinx

[PATCH v4 4/4] remoteproc: qcom: Add support for mss boot on msm8996

This patch add support for mss boot on msm8996. Major changes include making appropriate change for executing mss reset sequence, adding private data initialization etc. Signed-off-by: Avaneesh Kumar Dwivedi --- .../devicetree/bindings/remoteproc/qcom,q6v5.txt | 4

[PATCH v4 4/4] remoteproc: qcom: Add support for mss boot on msm8996

This patch add support for mss boot on msm8996. Major changes include making appropriate change for executing mss reset sequence, adding private data initialization etc. Signed-off-by: Avaneesh Kumar Dwivedi --- .../devicetree/bindings/remoteproc/qcom,q6v5.txt | 4 +-

[PATCH v4 0/4] Add new SCM call for stage two mem translation and enable mss rproc on msm8996

This patch does following 1- Adds new scm call which helps in stage two translation of a memory region so that multi proc mem access sharing can be achieved on armv8 and later. 2- Enable mss remoteproc on msm8996 This patchset is based on tip of linux-next. Avaneesh

[PATCH v4 3/4] remoteproc: qcom: Add new secure monitor call for access

MSS proc on msm8996 can not access fw loaded region without stage second translation of memory pages where mpss image are loaded. This patch to enable mss boot on msm8996 add these secure monitor calls to switch ownership between apps and modem. Signed-off-by: Avaneesh Kumar Dwivedi

[PATCH v4 0/4] Add new SCM call for stage two mem translation and enable mss rproc on msm8996

This patch does following 1- Adds new scm call which helps in stage two translation of a memory region so that multi proc mem access sharing can be achieved on armv8 and later. 2- Enable mss remoteproc on msm8996 This patchset is based on tip of linux-next. Avaneesh

[PATCH v4 3/4] remoteproc: qcom: Add new secure monitor call for access

MSS proc on msm8996 can not access fw loaded region without stage second translation of memory pages where mpss image are loaded. This patch to enable mss boot on msm8996 add these secure monitor calls to switch ownership between apps and modem. Signed-off-by: Avaneesh Kumar Dwivedi ---

[PATCH v4 1/4] firmware: scm: Add support for shared access of a memory

Two different processors on a SOC need to share memory during loading. So memory access between them need to be synchronized, which is done via level two memory mapping by secure layer. This patch provide interface for making secure monitor call for access sharing or access right transfer between

[PATCH v4 1/4] firmware: scm: Add support for shared access of a memory

Two different processors on a SOC need to share memory during loading. So memory access between them need to be synchronized, which is done via level two memory mapping by secure layer. This patch provide interface for making secure monitor call for access sharing or access right transfer between

Re: [PATCH] soc: imx: Select PM_GENERIC_DOMAINS only if PM is enabled

Hi Guenter, On Mon, May 15, 2017 at 1:33 PM, Guenter Roeck wrote: > Selecting PM_GENERIC_DOMAINS without PM results in the following build > errors, seen when building sparc32:allmodconfig. > > drivers/base/power/domain.c: In function 'genpd_queue_power_off_work': >

Re: [PATCH] soc: imx: Select PM_GENERIC_DOMAINS only if PM is enabled

Hi Guenter, On Mon, May 15, 2017 at 1:33 PM, Guenter Roeck wrote: > Selecting PM_GENERIC_DOMAINS without PM results in the following build > errors, seen when building sparc32:allmodconfig. > > drivers/base/power/domain.c: In function 'genpd_queue_power_off_work': >

[PATCH v5 1/3] drm: mali-dp: Add support for writeback on DP550/DP650

Mali-DP display processors are able to write the composition result to a memory buffer via the SE. Add entry points in the HAL for enabling/disabling this feature, and implement support for it on DP650 and DP550. DP500 acts differently and so is omitted from this change. Changes since v3: - Fix

[PATCH v5 1/3] drm: mali-dp: Add support for writeback on DP550/DP650

Mali-DP display processors are able to write the composition result to a memory buffer via the SE. Add entry points in the HAL for enabling/disabling this feature, and implement support for it on DP650 and DP550. DP500 acts differently and so is omitted from this change. Changes since v3: - Fix

[PATCH v5 0/3] drm/mali-dp: Add support for memory writeback engine

Hi, This series introduces support for Mali DP's memory writeback engine using the generic writeback connector support introduced in the "[PATCH v5 0/2] drm: Introduce writeback connectors" series [1] This version updates the Mali DP code to remove the bespoke encoder used with the

[PATCH v5 0/3] drm/mali-dp: Add support for memory writeback engine

Hi, This series introduces support for Mali DP's memory writeback engine using the generic writeback connector support introduced in the "[PATCH v5 0/2] drm: Introduce writeback connectors" series [1] This version updates the Mali DP code to remove the bespoke encoder used with the

[PATCH v5 3/3] drm: mali-dp: Add writeback connector

From: Brian Starkey Mali-DP has a memory writeback engine which can be used to write the composition result to a memory buffer. Expose this functionality as a DRM writeback connector on supported hardware. Changes since v1: Daniel Vetter: - Don't require a modeset when

[PATCH v5 3/3] drm: mali-dp: Add writeback connector

From: Brian Starkey Mali-DP has a memory writeback engine which can be used to write the composition result to a memory buffer. Expose this functionality as a DRM writeback connector on supported hardware. Changes since v1: Daniel Vetter: - Don't require a modeset when writeback routing

[PATCH v5 2/3] drm: mali-dp: Add RGB writeback formats for DP550/DP650

From: Brian Starkey Add a layer bit for the SE memory-write, and add it to the pixel format matrix for DP550/DP650. Signed-off-by: Brian Starkey [rebased and fixed conflicts] Signed-off-by: Mihail Atanassov Signed-off-by:

[PATCH v5 2/3] drm: mali-dp: Add RGB writeback formats for DP550/DP650

From: Brian Starkey Add a layer bit for the SE memory-write, and add it to the pixel format matrix for DP550/DP650. Signed-off-by: Brian Starkey [rebased and fixed conflicts] Signed-off-by: Mihail Atanassov Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/malidp_hw.c | 28

Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST

Em Mon, 15 May 2017 13:49:19 +0200 Peter Zijlstra escreveu: > On Mon, May 15, 2017 at 01:29:58PM +0300, Jani Nikula wrote: > > On Mon, 15 May 2017, Peter Zijlstra wrote: > > > The intention is to aid readability. Making comments worse so that some >

Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST

Em Mon, 15 May 2017 13:49:19 +0200 Peter Zijlstra escreveu: > On Mon, May 15, 2017 at 01:29:58PM +0300, Jani Nikula wrote: > > On Mon, 15 May 2017, Peter Zijlstra wrote: > > > The intention is to aid readability. Making comments worse so that some > > > retarded script can generate better

Re: [PATCH 1/4] ftrace: Simplify glob handling in unregister_ftrace_function_probe_func()

On Sun, 14 May 2017 01:01:01 +0530 "Naveen N. Rao" wrote: > Handle a NULL glob properly. > > Signed-off-by: Naveen N. Rao > --- > kernel/trace/ftrace.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git

Re: [PATCH 1/4] ftrace: Simplify glob handling in unregister_ftrace_function_probe_func()

On Sun, 14 May 2017 01:01:01 +0530 "Naveen N. Rao" wrote: > Handle a NULL glob properly. > > Signed-off-by: Naveen N. Rao > --- > kernel/trace/ftrace.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c > index

[PATCH v5 0/2] drm: Introduce writeback connectors

Hi, This is v5 of the writeback connector series. Boris Brezillon thought that having to explicitly instantiate an encoder when using drm_writeback_connector is a bit too cumbersome, so I'm pushing out this version where we embed a virtual encoder inside drm_writeback_connector in order to

Re: [PATCH 06/17] doc: security: minor cleanups to build kernel-doc

On Mon, 15 May 2017 09:17:25 +1000 (AEST) James Morris wrote: > On Sat, 13 May 2017, Kees Cook wrote: > > > These fixes were needed to parse lsm_hooks.h kernel-doc. More work is > > needed, but this is the first step. > > > > Cc: Casey Schaufler > >

[PATCH v5 0/2] drm: Introduce writeback connectors

Hi, This is v5 of the writeback connector series. Boris Brezillon thought that having to explicitly instantiate an encoder when using drm_writeback_connector is a bit too cumbersome, so I'm pushing out this version where we embed a virtual encoder inside drm_writeback_connector in order to

Re: [PATCH 06/17] doc: security: minor cleanups to build kernel-doc

On Mon, 15 May 2017 09:17:25 +1000 (AEST) James Morris wrote: > On Sat, 13 May 2017, Kees Cook wrote: > > > These fixes were needed to parse lsm_hooks.h kernel-doc. More work is > > needed, but this is the first step. > > > > Cc: Casey Schaufler > > Signed-off-by: Kees Cook > > Should

[PATCH v5 1/2] drm: Add writeback connector type

From: Brian Starkey Writeback connectors represent writeback engines which can write the CRTC output to a memory framebuffer. Add a writeback connector type and related support functions. Drivers should initialize a writeback connector with drm_writeback_connector_init()

[PATCH v5 1/2] drm: Add writeback connector type

From: Brian Starkey Writeback connectors represent writeback engines which can write the CRTC output to a memory framebuffer. Add a writeback connector type and related support functions. Drivers should initialize a writeback connector with drm_writeback_connector_init() which takes care of

[PATCH v5 2/2] drm: writeback: Add out-fences for writeback connectors

From: Brian Starkey Add the WRITEBACK_OUT_FENCE_PTR property to writeback connectors, to enable userspace to get a fence which will signal once the writeback is complete. It is not allowed to request an out-fence without a framebuffer attached to the connector. A timeline

[PATCH v5 2/2] drm: writeback: Add out-fences for writeback connectors

From: Brian Starkey Add the WRITEBACK_OUT_FENCE_PTR property to writeback connectors, to enable userspace to get a fence which will signal once the writeback is complete. It is not allowed to request an out-fence without a framebuffer attached to the connector. A timeline is added to

[PATCH 2/3] ipc: merge ipc_rcu and kern_ipc_perm

ipc has two management structures that exist for every id: - struct kern_ipc_perm, it contains e.g. the permissions. - struct ipc_rcu, it contains the rcu head for rcu handling and the refcount. The patch merges both structures. As a bonus, we may save one cacheline, because both structures are

[PATCH 2/3] ipc: merge ipc_rcu and kern_ipc_perm

ipc has two management structures that exist for every id: - struct kern_ipc_perm, it contains e.g. the permissions. - struct ipc_rcu, it contains the rcu head for rcu handling and the refcount. The patch merges both structures. As a bonus, we may save one cacheline, because both structures are

[PATCH 3/3] include/linux/sem.h: Correctly document sem_ctime

sem_ctime is initialized to the semget() time and then updated at every semctl() that changes the array. Thus it does not represent the time of the last change. Especially, semop() calls are only stored in sem_otime, not in sem_ctime. This is already described in ipc/sem.c, I just overlooked

[PATCH 3/3] include/linux/sem.h: Correctly document sem_ctime

sem_ctime is initialized to the semget() time and then updated at every semctl() that changes the array. Thus it does not represent the time of the last change. Especially, semop() calls are only stored in sem_otime, not in sem_ctime. This is already described in ipc/sem.c, I just overlooked

[PATCH 1/3] ipc/sem.c: remove sem_base, embed struct sem

sma->sem_base is initialized with sma->sem_base = (struct sem *) [1]; The current code has four problems: - There is an unnecessary pointer dereference - sem_base is not needed. - Alignment for struct sem only works by chance. - The current code causes false positive for static code

[PATCH 1/3] ipc/sem.c: remove sem_base, embed struct sem

sma->sem_base is initialized with sma->sem_base = (struct sem *) [1]; The current code has four problems: - There is an unnecessary pointer dereference - sem_base is not needed. - Alignment for struct sem only works by chance. - The current code causes false positive for static code

[PATCH 0/2] Misc cleanups for ipc

Hi all, could you check the following three patches? As explained, I try to combine the changes for static analyzers and for the randstruct gcc plugin with cleanups. 0001-ipc-sem.c-remove-sem_base-embed-struct-sem.patch: sem_base is not needed. Instead of improving the casts,

[PATCH 0/2] Misc cleanups for ipc

Hi all, could you check the following three patches? As explained, I try to combine the changes for static analyzers and for the randstruct gcc plugin with cleanups. 0001-ipc-sem.c-remove-sem_base-embed-struct-sem.patch: sem_base is not needed. Instead of improving the casts,

Re: [PATCH 0/3] HID-Wacom: Fine-tuning for seven function implementations

Came across these and noticed that it doesn't appear anything has happened with them. The set looks good to me: Reviewed-by: Jason Gerecke Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two,

Re: [PATCH 0/3] HID-Wacom: Fine-tuning for seven function implementations

Came across these and noticed that it doesn't appear anything has happened with them. The set looks good to me: Reviewed-by: Jason Gerecke Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two, / But you can’t take

[PATCH] drivers/perf/arm_pmu: Delete an error message for a failed memory allocation in armpmu_alloc()

From: Markus Elfring Date: Mon, 15 May 2017 19:09:03 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link:

[PATCH] drivers/perf/arm_pmu: Delete an error message for a failed memory allocation in armpmu_alloc()

From: Markus Elfring Date: Mon, 15 May 2017 19:09:03 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf

[PATCH] MAINTAINERS: greybus-dev list is members-only

From: Randy Dunlap <rdun...@infradead.org> The greybus-dev mailing list is a members-only list and is moderated for non-subscribers. Signed-off-by: Randy Dunlap <rdun...@infradead.org> --- MAINTAINERS |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-next-2

[PATCH] MAINTAINERS: greybus-dev list is members-only

From: Randy Dunlap The greybus-dev mailing list is a members-only list and is moderated for non-subscribers. Signed-off-by: Randy Dunlap --- MAINTAINERS |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-next-20170515.orig/MAINTAINERS +++ linux-next-20170515/MAINTAINERS

[PATCH] drm/vc4: Mark the device as active when enabling runtime PM.

Failing to do so meant that we got a resume() callback on first use of the device, so we would leak the bin BO that we allocated during probe. Signed-off-by: Eric Anholt Fixes: 553c942f8b2c ("drm/vc4: Allow using more than 256MB of CMA memory.") ---

[PATCH] drm/vc4: Mark the device as active when enabling runtime PM.

Failing to do so meant that we got a resume() callback on first use of the device, so we would leak the bin BO that we allocated during probe. Signed-off-by: Eric Anholt Fixes: 553c942f8b2c ("drm/vc4: Allow using more than 256MB of CMA memory.") --- drivers/gpu/drm/vc4/vc4_v3d.c | 1 + 1 file

Re: [PATCH 0/5] Convert more books to ReST

On Mon, 15 May 2017 14:09:12 +0200 Boris Brezillon wrote: > > mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings > > Not sure how you plan to merge these changes, but if it goes through > a single tree I'll probably need an immutable topic branch,

Re: [PATCH v2] cros_ec_i2c: prevent i2c timeout for EC_CMD_FLASH_ERASE

Hi, On Mon, May 15, 2017 at 9:22 AM, Wei-Ning Huang wrote: > From: Wei-Ning Huang > > Some EC chip has larger flash sector size which requires longer erase > time. During erase the CPU is usually stalled and can't even respond to > interrupts. We

Re: [PATCH 0/5] Convert more books to ReST

On Mon, 15 May 2017 14:09:12 +0200 Boris Brezillon wrote: > > mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings > > Not sure how you plan to merge these changes, but if it goes through > a single tree I'll probably need an immutable topic branch, because I > plan to change a few

Re: [PATCH v2] cros_ec_i2c: prevent i2c timeout for EC_CMD_FLASH_ERASE

Hi, On Mon, May 15, 2017 at 9:22 AM, Wei-Ning Huang wrote: > From: Wei-Ning Huang > > Some EC chip has larger flash sector size which requires longer erase > time. During erase the CPU is usually stalled and can't even respond to > interrupts. We sleep a while to block any EC command from

<    2   3   4   5   6   7   8   9   10   11   >