Re: [PATCH] perf/x86/intel/uncore: Fix CHA registers configuration procedure for Knights Landing platform

* hchrzani wrote: > CHA events in Knights Landing platform require programming filter registers > properly. > Remote node, local node and NonNearMemCachable bits should be set to 1 at all > times. > > Fixes: 77af003 ('perf/x86/intel/uncore: Add Knights Landing

Re: [PATCH] perf/x86/intel/uncore: Fix CHA registers configuration procedure for Knights Landing platform

* hchrzani wrote: > CHA events in Knights Landing platform require programming filter registers > properly. > Remote node, local node and NonNearMemCachable bits should be set to 1 at all > times. > > Fixes: 77af003 ('perf/x86/intel/uncore: Add Knights Landing uncore PMU > support') >

Re: [PATCH 0/3] x86/KASLR: Build identity mappings on demand

* Kees Cook wrote: > I'm going back to small steps. :) > > This series lets the x86_64 compressed boot environment build > page table identity mappings on demand. This will be used once > we begin randomizing the physical memory position beyond the > existing identity

Re: [PATCH 0/3] x86/KASLR: Build identity mappings on demand

* Kees Cook wrote: > I'm going back to small steps. :) > > This series lets the x86_64 compressed boot environment build > page table identity mappings on demand. This will be used once > we begin randomizing the physical memory position beyond the > existing identity maps. This series was

Re: [PATCH RFC 1/5] net: phy: sun8i-h3-ephy: Add bindings for Allwinner H3 Ethernet PHY

Hi, On Tue, Apr 12, 2016 at 9:38 AM, Chen-Yu Tsai wrote: > On Tue, Apr 12, 2016 at 3:23 AM, Florian Fainelli > wrote: >> On 04/04/16 09:22, Chen-Yu Tsai wrote: >>> The Allwinner H3 SoC incorporates an Ethernet PHY. This is enabled and >>> configured through

Re: [PATCH RFC 1/5] net: phy: sun8i-h3-ephy: Add bindings for Allwinner H3 Ethernet PHY

Hi, On Tue, Apr 12, 2016 at 9:38 AM, Chen-Yu Tsai wrote: > On Tue, Apr 12, 2016 at 3:23 AM, Florian Fainelli > wrote: >> On 04/04/16 09:22, Chen-Yu Tsai wrote: >>> The Allwinner H3 SoC incorporates an Ethernet PHY. This is enabled and >>> configured through a memory mapped hardware register.

Re: [v4.6-rc1 Regression] x86/topology: Create logical package id

* Thomas Gleixner wrote: > > I was hoping to get your feedback, since you are the patch author. Do > > you think gathering any additional data will help diagnose this issue, > > or would it be best to submit a revert request? > > Yuck. That dies with a divide error. And

Re: [v4.6-rc1 Regression] x86/topology: Create logical package id

* Thomas Gleixner wrote: > > I was hoping to get your feedback, since you are the patch author. Do > > you think gathering any additional data will help diagnose this issue, > > or would it be best to submit a revert request? > > Yuck. That dies with a divide error. And that looks like XEN is

[PATCH 3/3] [media] s5p-mfc: fix a typo in s5p_mfc_dec

It is a cosmetic commit. Signed-off-by: ayaka --- drivers/media/platform/s5p-mfc/s5p_mfc_dec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c b/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c index

[PATCH 2/3] [media] s5p-mfc: remove unnecessary check in try_fmt

We don't need to request the sizeimage or num_planes in try_fmt. Signed-off-by: ayaka --- drivers/media/platform/s5p-mfc/s5p_mfc_enc.c | 9 - 1 file changed, 9 deletions(-) diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc_enc.c

[PATCH 3/3] [media] s5p-mfc: fix a typo in s5p_mfc_dec

It is a cosmetic commit. Signed-off-by: ayaka --- drivers/media/platform/s5p-mfc/s5p_mfc_dec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c b/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c index f2d6376..391ed9c 100644 ---

[PATCH 2/3] [media] s5p-mfc: remove unnecessary check in try_fmt

We don't need to request the sizeimage or num_planes in try_fmt. Signed-off-by: ayaka --- drivers/media/platform/s5p-mfc/s5p_mfc_enc.c | 9 - 1 file changed, 9 deletions(-) diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc_enc.c b/drivers/media/platform/s5p-mfc/s5p_mfc_enc.c index

Re: [RESEND PATCH] [media] s5p-mfc: don't close instance after free OUTPUT buffers

Please also notice those patches (A few patches make s5p-mfc work with Gstreamer) I resent to mail recently. Without them, the encoder won't work with Gstreamer either. I hope it will be merged as soon as possible. 在 2016年05月07日 06:11, Javier Martinez Canillas 写道: From: ayaka

Re: [RESEND PATCH] [media] s5p-mfc: don't close instance after free OUTPUT buffers

Please also notice those patches (A few patches make s5p-mfc work with Gstreamer) I resent to mail recently. Without them, the encoder won't work with Gstreamer either. I hope it will be merged as soon as possible. 在 2016年05月07日 06:11, Javier Martinez Canillas 写道: From: ayaka User-space

[PATCH 1/3] [media] s5p-mfc: Add handling of buffer freeing reqbufs request

The encoder forget the work to call hardware to release its buffers. This patch came from chromium project. I just change its code style and make the API match with new kernel. Signed-off-by: ayaka --- drivers/media/platform/s5p-mfc/s5p_mfc_enc.c | 3 +++ 1 file changed, 3

[RESEND PATCH] [PATCH 0/3] A few patches make s5p-mfc work with Gstreamer

A user-space application will follow the V4l2 document, but I meet a problem when I test it with Gstreamer. I look at the V4l2 document, the driver check the external setting which the document not cover, so that is what the second patch do. The first patch comes from chromium project, but I

[PATCH 1/3] [media] s5p-mfc: Add handling of buffer freeing reqbufs request

The encoder forget the work to call hardware to release its buffers. This patch came from chromium project. I just change its code style and make the API match with new kernel. Signed-off-by: ayaka --- drivers/media/platform/s5p-mfc/s5p_mfc_enc.c | 3 +++ 1 file changed, 3 insertions(+) diff

[RESEND PATCH] [PATCH 0/3] A few patches make s5p-mfc work with Gstreamer

A user-space application will follow the V4l2 document, but I meet a problem when I test it with Gstreamer. I look at the V4l2 document, the driver check the external setting which the document not cover, so that is what the second patch do. The first patch comes from chromium project, but I

[tip:perf/core] perf trace: Move futex_op beautifier to tools/perf/trace/beauty/

Commit-ID: d5d71e86d226abe7e08df5763127ed2bd07649a1 Gitweb: http://git.kernel.org/tip/d5d71e86d226abe7e08df5763127ed2bd07649a1 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 6 May 2016 12:45:25 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf trace: Move futex_op beautifier to tools/perf/trace/beauty/

Commit-ID: d5d71e86d226abe7e08df5763127ed2bd07649a1 Gitweb: http://git.kernel.org/tip/d5d71e86d226abe7e08df5763127ed2bd07649a1 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 6 May 2016 12:45:25 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:59 -0300

[tip:perf/core] perf trace: Move open_flags beautifier to tools/perf/trace/beauty/

Commit-ID: 8f48df69b4add63527cae646f2e40cf83c6ec0a0 Gitweb: http://git.kernel.org/tip/8f48df69b4add63527cae646f2e40cf83c6ec0a0 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 6 May 2016 10:02:32 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf trace: Move signum beautifier to tools/perf/trace/beauty/

Commit-ID: 12199d8e20bb4a2ad164d2600bf199557d55c35c Gitweb: http://git.kernel.org/tip/12199d8e20bb4a2ad164d2600bf199557d55c35c Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 6 May 2016 09:58:02 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf trace: Move open_flags beautifier to tools/perf/trace/beauty/

Commit-ID: 8f48df69b4add63527cae646f2e40cf83c6ec0a0 Gitweb: http://git.kernel.org/tip/8f48df69b4add63527cae646f2e40cf83c6ec0a0 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 6 May 2016 10:02:32 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:58 -0300

[tip:perf/core] perf trace: Move signum beautifier to tools/perf/trace/beauty/

Commit-ID: 12199d8e20bb4a2ad164d2600bf199557d55c35c Gitweb: http://git.kernel.org/tip/12199d8e20bb4a2ad164d2600bf199557d55c35c Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 6 May 2016 09:58:02 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:57 -0300

[tip:perf/core] perf stat: Add extra output of counter values with -vv

Commit-ID: 0b1abbf4a7d273a13065534d718661fc904703b9 Gitweb: http://git.kernel.org/tip/0b1abbf4a7d273a13065534d718661fc904703b9 Author: Andi Kleen AuthorDate: Wed, 27 Apr 2016 13:00:51 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6

[tip:perf/core] perf script: Update export-to-postgresql to support callchain export

Commit-ID: 3521f3bc9dae4a79cfb9cc9ffcf6d961bbb7cbac Gitweb: http://git.kernel.org/tip/3521f3bc9dae4a79cfb9cc9ffcf6d961bbb7cbac Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:11 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6

[tip:perf/core] perf stat: Add extra output of counter values with -vv

Commit-ID: 0b1abbf4a7d273a13065534d718661fc904703b9 Gitweb: http://git.kernel.org/tip/0b1abbf4a7d273a13065534d718661fc904703b9 Author: Andi Kleen AuthorDate: Wed, 27 Apr 2016 13:00:51 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:56 -0300 perf stat: Add

[tip:perf/core] perf script: Update export-to-postgresql to support callchain export

Commit-ID: 3521f3bc9dae4a79cfb9cc9ffcf6d961bbb7cbac Gitweb: http://git.kernel.org/tip/3521f3bc9dae4a79cfb9cc9ffcf6d961bbb7cbac Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:11 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:55 -0300 perf script:

[tip:perf/core] perf script: Expose usage of the callchain db export via the python api

Commit-ID: 2c15f5eb04e9e7e19a2c8be6b50c63a4c6062a44 Gitweb: http://git.kernel.org/tip/2c15f5eb04e9e7e19a2c8be6b50c63a4c6062a44 Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:10 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6

[tip:perf/core] perf script: Add call path id to exported sample in db export

Commit-ID: 568850eaad8cdd3783c3347623dfcad4f043cf1c Gitweb: http://git.kernel.org/tip/568850eaad8cdd3783c3347623dfcad4f043cf1c Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:09 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6

[tip:perf/core] perf script: Expose usage of the callchain db export via the python api

Commit-ID: 2c15f5eb04e9e7e19a2c8be6b50c63a4c6062a44 Gitweb: http://git.kernel.org/tip/2c15f5eb04e9e7e19a2c8be6b50c63a4c6062a44 Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:10 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:54 -0300 perf script:

[tip:perf/core] perf script: Add call path id to exported sample in db export

Commit-ID: 568850eaad8cdd3783c3347623dfcad4f043cf1c Gitweb: http://git.kernel.org/tip/568850eaad8cdd3783c3347623dfcad4f043cf1c Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:09 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:53 -0300 perf script:

Re: [PATCH v2] locking/rwsem: Add reader-owned state to the owner field

* Waiman Long wrote: > On a 4-socket Haswell machine running on a 4.6-rc1 based kernel, the > fio test with multithreaded randrw and randwrite tests on the same > file on a XFS partition on top of a NVDIMM were run, the aggregated > bandwidths before and after the patch

[tip:perf/core] perf script: Enable db export to output sampled callchains

Commit-ID: 0a3eba3ad613fa9d5af754f7ae8c4b46047cb2a7 Gitweb: http://git.kernel.org/tip/0a3eba3ad613fa9d5af754f7ae8c4b46047cb2a7 Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:08 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6

Re: [PATCH v2] locking/rwsem: Add reader-owned state to the owner field

* Waiman Long wrote: > On a 4-socket Haswell machine running on a 4.6-rc1 based kernel, the > fio test with multithreaded randrw and randwrite tests on the same > file on a XFS partition on top of a NVDIMM were run, the aggregated > bandwidths before and after the patch were as follows: > >

[tip:perf/core] perf script: Enable db export to output sampled callchains

Commit-ID: 0a3eba3ad613fa9d5af754f7ae8c4b46047cb2a7 Gitweb: http://git.kernel.org/tip/0a3eba3ad613fa9d5af754f7ae8c4b46047cb2a7 Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:08 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:52 -0300 perf script:

[tip:perf/core] perf tools: Refactor code to move call path handling out of thread-stack

Commit-ID: 451db12617bc6ff1bb8ed456ed4f257594134255 Gitweb: http://git.kernel.org/tip/451db12617bc6ff1bb8ed456ed4f257594134255 Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:07 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6

[tip:perf/core] perf tools: Refactor code to move call path handling out of thread-stack

Commit-ID: 451db12617bc6ff1bb8ed456ed4f257594134255 Gitweb: http://git.kernel.org/tip/451db12617bc6ff1bb8ed456ed4f257594134255 Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:07 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 13:00:43 -0300 perf tools:

[tip:perf/core] perf trace: Do not print raw args list for syscalls with no args

Commit-ID: 4c4d6e519091a3551a0ad2e2e8423d77f3000400 Gitweb: http://git.kernel.org/tip/4c4d6e519091a3551a0ad2e2e8423d77f3000400 Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 5 May 2016 23:38:05 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf callchain: Fix incorrect ordering of entries

Commit-ID: 9919a65ec532799544dfdfd6df6f994b74c12b42 Gitweb: http://git.kernel.org/tip/9919a65ec532799544dfdfd6df6f994b74c12b42 Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:06 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6

[tip:perf/core] perf trace: Do not print raw args list for syscalls with no args

Commit-ID: 4c4d6e519091a3551a0ad2e2e8423d77f3000400 Gitweb: http://git.kernel.org/tip/4c4d6e519091a3551a0ad2e2e8423d77f3000400 Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 5 May 2016 23:38:05 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 08:44:30 -0300

[tip:perf/core] perf callchain: Fix incorrect ordering of entries

Commit-ID: 9919a65ec532799544dfdfd6df6f994b74c12b42 Gitweb: http://git.kernel.org/tip/9919a65ec532799544dfdfd6df6f994b74c12b42 Author: Chris Phlipot AuthorDate: Thu, 28 Apr 2016 01:19:06 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 6 May 2016 08:59:47 -0300 perf

Re: [RFC PATCH 05/12] ARM: dts: exynos: Configure Exynos5410 pinctrl for eMMC and SD card

Hi Krzysztof, On Tue, May 3, 2016 at 11:22 PM, Krzysztof Kozlowski wrote: > Configure the pinctrl for MMC0 (eMMC) and MMC2 (microSD card). > > Signed-off-by: Krzysztof Kozlowski > > --- > > I am not sure about sd0_rclk. Also I wonder whether this should go to >

Re: [RFC PATCH 05/12] ARM: dts: exynos: Configure Exynos5410 pinctrl for eMMC and SD card

Hi Krzysztof, On Tue, May 3, 2016 at 11:22 PM, Krzysztof Kozlowski wrote: > Configure the pinctrl for MMC0 (eMMC) and MMC2 (microSD card). > > Signed-off-by: Krzysztof Kozlowski > > --- > > I am not sure about sd0_rclk. Also I wonder whether this should go to > board DTS... > --- >

Re: [GIT PULL 00/11] perf/core improvements and fixes

.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core > (2016-05-06 08:35:14 +0200) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-core-for-mingo-20160506 > > for you to fetch changes

Re: [GIT PULL 00/11] perf/core improvements and fixes

cm/linux/kernel/git/acme/linux into perf/core > (2016-05-06 08:35:14 +0200) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-core-for-mingo-20160506 > > for you to fetch changes up to d5d71e86d226abe7e08d

[PATCH v2 1/3] input: rmi4: Move IRQ handling to rmi_driver

The attn IRQ is related to the chip, rather than the transport, so move all handling of interrupts to the core driver. This also makes sure that there are no races between interrupts and availability of the resources used by the core driver. Signed-off-by: Bjorn Andersson

[PATCH v2 1/3] input: rmi4: Move IRQ handling to rmi_driver

The attn IRQ is related to the chip, rather than the transport, so move all handling of interrupts to the core driver. This also makes sure that there are no races between interrupts and availability of the resources used by the core driver. Signed-off-by: Bjorn Andersson ---

[PATCH v2 0/3] input: rmi4: Regulator supply support

The first version of the regulator support patch suffered from being implemented in the transport driver, as a work around for resource availability racing (EPROBE_DEFER of the core driver) with the interrupt handler. After reconsidering the solutions discussed following that I concluded that the

[PATCH v2 2/3] input: rmi4: Acquire and enable VDD and VIO supplies

For systems where the rmi4 device is not powered by always-on regulators we need to acquire handles to VDD and VIO and enable these. Signed-off-by: Bjorn Andersson --- Changes since v1: - Added patch 1 and 3 - Moved regulator handling to the core driver

[PATCH v2 3/3] input: rmi4: Remove set_page() call before core is initialized

In the case of the chip not already being powered we can't call set_page() before we're letting the core driver enable power to the chip. Signed-off-by: Bjorn Andersson --- drivers/input/rmi4/rmi_i2c.c | 11 ++- drivers/input/rmi4/rmi_spi.c | 11 ++-

[PATCH v2 2/3] input: rmi4: Acquire and enable VDD and VIO supplies

For systems where the rmi4 device is not powered by always-on regulators we need to acquire handles to VDD and VIO and enable these. Signed-off-by: Bjorn Andersson --- Changes since v1: - Added patch 1 and 3 - Moved regulator handling to the core driver

[PATCH v2 3/3] input: rmi4: Remove set_page() call before core is initialized

In the case of the chip not already being powered we can't call set_page() before we're letting the core driver enable power to the chip. Signed-off-by: Bjorn Andersson --- drivers/input/rmi4/rmi_i2c.c | 11 ++- drivers/input/rmi4/rmi_spi.c | 11 ++- 2 files changed, 4

[PATCH v2 0/3] input: rmi4: Regulator supply support

The first version of the regulator support patch suffered from being implemented in the transport driver, as a work around for resource availability racing (EPROBE_DEFER of the core driver) with the interrupt handler. After reconsidering the solutions discussed following that I concluded that the

Re: perf tools: add support for generating bpf prologue on powerpc

On Thu, 2016-05-05 at 15:23:19 UTC, "Naveen N. Rao" wrote: > Generalize existing macros to serve the purpose. > > Cc: Wang Nan > Cc: Arnaldo Carvalho de Melo > Cc: Masami Hiramatsu > Cc: Ian Munsie > Cc: Michael

Re: perf tools: add support for generating bpf prologue on powerpc

On Thu, 2016-05-05 at 15:23:19 UTC, "Naveen N. Rao" wrote: > Generalize existing macros to serve the purpose. > > Cc: Wang Nan > Cc: Arnaldo Carvalho de Melo > Cc: Masami Hiramatsu > Cc: Ian Munsie > Cc: Michael Ellerman > Signed-off-by: Naveen N. Rao > --- > With this patch: > # ./perf

Re: [PATCH] ksm: fix conflict between mmput and scan_get_next_rmap_item

On Fri, 6 May 2016, zhouchengming wrote: > On 2016/5/6 5:07, Andrew Morton wrote: > > On Thu, 5 May 2016 20:42:56 +0800 Zhou Chengming > > wrote: > > > > > A concurrency issue about KSM in the function scan_get_next_rmap_item. > > > > > > task A (ksmd):

Re: [PATCH] ksm: fix conflict between mmput and scan_get_next_rmap_item

On Fri, 6 May 2016, zhouchengming wrote: > On 2016/5/6 5:07, Andrew Morton wrote: > > On Thu, 5 May 2016 20:42:56 +0800 Zhou Chengming > > wrote: > > > > > A concurrency issue about KSM in the function scan_get_next_rmap_item. > > > > > > task A (ksmd):|task B (the

Re: [PATCH] staging: gdm724x: fixing coding style problems listed by checkpatch

On Fri, May 06, 2016 at 06:46:32PM -0400, Bruno Carvalho wrote: > This patch is to fix some coding style issues pointed > by scripts/checkpatch.pl Which ones specifically? Please be descriptive, as other commits are for this driver, take a look at them for examples. And remember, only do one

Re: [PATCH] staging: gdm724x: fixing coding style problems listed by checkpatch

On Fri, May 06, 2016 at 06:46:32PM -0400, Bruno Carvalho wrote: > This patch is to fix some coding style issues pointed > by scripts/checkpatch.pl Which ones specifically? Please be descriptive, as other commits are for this driver, take a look at them for examples. And remember, only do one

Re: [PATCH] ext4 crypto: migrate into vfs's crypto engine

Hi Jaegeuk, On Mon, Apr 25, 2016 at 05:15:36PM -0700, Jaegeuk Kim wrote: > This patch removes the most parts of internal crypto codes. > And then, it modifies and adds some ext4-specific crypt codes to use the > generic > facility. Except for the key name prefix issue that Ted pointed out, this

Re: [PATCH] ext4 crypto: migrate into vfs's crypto engine

Hi Jaegeuk, On Mon, Apr 25, 2016 at 05:15:36PM -0700, Jaegeuk Kim wrote: > This patch removes the most parts of internal crypto codes. > And then, it modifies and adds some ext4-specific crypt codes to use the > generic > facility. Except for the key name prefix issue that Ted pointed out, this

Re: [PATCH] libnvdimm, pfn: fix ARCH=alpha allmodconfig build failure

On 05/06/2016 10:26 AM, Dan Williams wrote: I had relied on the kbuild robot for cross build coverage, however it only builds alpha_defconfig. Switch from HPAGE_SIZE to PMD_SIZE, which is more widely defined. Fixes: 658922e57b84 ("libnvdimm, pfn: fix memmap reservation sizing") Cc:

Re: [PATCH] libnvdimm, pfn: fix ARCH=alpha allmodconfig build failure

On 05/06/2016 10:26 AM, Dan Williams wrote: I had relied on the kbuild robot for cross build coverage, however it only builds alpha_defconfig. Switch from HPAGE_SIZE to PMD_SIZE, which is more widely defined. Fixes: 658922e57b84 ("libnvdimm, pfn: fix memmap reservation sizing") Cc:

[PATCH 08/10] staging: lustre: o2iblnd: remove last of kiblnd_tunables_fini

From: Amir Shehata The function kibnd_tunables_fini() no longer exist. Remove it from o2iblnd.h Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7101 Reviewed-on:

[PATCH 01/10] staging: lustre: lnet: use struct lnet_ioctl_config_data for NI bring up

From: Amir Shehata The LNet layer passes around the individual fields of struct lnet_ioctl_config_data for the case of NI bring up. To simplify the code lets just pass struct lnet_ioctl_config directly. Signed-off-by: Amir Shehata Signed-off-by:

[PATCH 07/10] staging: lustre: o2iblnd: per NI map-on-demand value

From: Amir Shehata Enables support of different map-on-demand values per NI. This is required to support OPA coexistence with MLX5 cards. MLX5 does not support FMR, which is enabled via map-on-demand. However OPA's performance is greatly enahanced when FMR is enabled.

[PATCH 08/10] staging: lustre: o2iblnd: remove last of kiblnd_tunables_fini

From: Amir Shehata The function kibnd_tunables_fini() no longer exist. Remove it from o2iblnd.h Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7101 Reviewed-on: http://review.whamcloud.com/16367 Reviewed-by: Doug Oucharek

[PATCH 01/10] staging: lustre: lnet: use struct lnet_ioctl_config_data for NI bring up

From: Amir Shehata The LNet layer passes around the individual fields of struct lnet_ioctl_config_data for the case of NI bring up. To simplify the code lets just pass struct lnet_ioctl_config directly. Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id:

[PATCH 07/10] staging: lustre: o2iblnd: per NI map-on-demand value

From: Amir Shehata Enables support of different map-on-demand values per NI. This is required to support OPA coexistence with MLX5 cards. MLX5 does not support FMR, which is enabled via map-on-demand. However OPA's performance is greatly enahanced when FMR is enabled. In order to enable

[PATCH 10/10] staging: lustre: lnet: enable configuration per NI interface

From: Amir Shehata Add the ability to configure each NI interface at bring up. Also give the ability for user land utilities to query the configuration of each NI interface. Signed-off-by: Amir Shehata Signed-off-by: James Simmons

[PATCH 04/10] staging: lustre: o2iblnd: convert macros to inline functions

From: Amir Shehata Convert a few macros in o2iblnd.h to inline functions. Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7101 Reviewed-on:

[PATCH 10/10] staging: lustre: lnet: enable configuration per NI interface

From: Amir Shehata Add the ability to configure each NI interface at bring up. Also give the ability for user land utilities to query the configuration of each NI interface. Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7101

[PATCH 04/10] staging: lustre: o2iblnd: convert macros to inline functions

From: Amir Shehata Convert a few macros in o2iblnd.h to inline functions. Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7101 Reviewed-on: http://review.whamcloud.com/16367 Reviewed-by: Doug Oucharek Reviewed-by: Olaf Weber

[PATCH 05/10] staging: lustre: o2iblnd: create default o2iblnd tunable settings

From: Amir Shehata Create and set the default o2iblnd tunables when the ko2iblnd module loads. Move kiblnd_tunables_setup() to when the NI iterface is initialized. Signed-off-by: Amir Shehata Signed-off-by: James Simmons

[PATCH 09/10] staging: lustre: o2iblnd: properly set ibr_why

From: Amir Shehata For the case of when the connections supported fragment count is smaller than what is supported locally only set ibr_why to IBLND_REJECT_RDMA_FRAGS if the ko2iblnd protocol verison is IBLND_MSG_VERSION. Signed-off-by: Amir Shehata

[PATCH 03/10] staging: lustre: lnet: add per NI configuration structures

From: Amir Shehata Currently for LNet all hardware configuration is done with the modprobe configuration file. These settings are applied to all hardware instances for a node. That makes it impossible to configure two different pieces of infiniband hardware that require

[PATCH 05/10] staging: lustre: o2iblnd: create default o2iblnd tunable settings

From: Amir Shehata Create and set the default o2iblnd tunables when the ko2iblnd module loads. Move kiblnd_tunables_setup() to when the NI iterface is initialized. Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7101 Reviewed-on:

[PATCH 09/10] staging: lustre: o2iblnd: properly set ibr_why

From: Amir Shehata For the case of when the connections supported fragment count is smaller than what is supported locally only set ibr_why to IBLND_REJECT_RDMA_FRAGS if the ko2iblnd protocol verison is IBLND_MSG_VERSION. Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id:

[PATCH 03/10] staging: lustre: lnet: add per NI configuration structures

From: Amir Shehata Currently for LNet all hardware configuration is done with the modprobe configuration file. These settings are applied to all hardware instances for a node. That makes it impossible to configure two different pieces of infiniband hardware that require very different settings

[PATCH 02/10] staging: lustre: lnet: use struct lnet_ioctl_config_data for NI query

From: Amir Shehata The functions used to query the NI state passes around the individual fields of struct lnet_ioctl_config_data. To simplify the code lets just pass struct lnet_ioctl_config directly. Signed-off-by: Amir Shehata Signed-off-by:

[PATCH 06/10] staging: lustre: o2iblnd: use data in lnet_ni_t instead of kiblnd_tunables

From: Amir Shehata Currently the ko2iblnd creates a kib_tunable_t stucture to allow the ko2iblnd driver to access the module parameters throught the code. Some of those data fields also exist in lnet_ni_t. Migrate to using the lnet_ni_t data fields instead of

[PATCH 02/10] staging: lustre: lnet: use struct lnet_ioctl_config_data for NI query

From: Amir Shehata The functions used to query the NI state passes around the individual fields of struct lnet_ioctl_config_data. To simplify the code lets just pass struct lnet_ioctl_config directly. Signed-off-by: Amir Shehata Signed-off-by: James Simmons Intel-bug-id:

[PATCH 06/10] staging: lustre: o2iblnd: use data in lnet_ni_t instead of kiblnd_tunables

From: Amir Shehata Currently the ko2iblnd creates a kib_tunable_t stucture to allow the ko2iblnd driver to access the module parameters throught the code. Some of those data fields also exist in lnet_ni_t. Migrate to using the lnet_ni_t data fields instead of kib_tunable_t. Signed-off-by: Amir

[PATCH 00/10] staging: lustre: lnet: per NI map-on-demand value

Enables support of different map-on-demand values per NI. This is required to support OPA coexistence with MLX5 cards. MLX5 does not support FMR, which is enabled via map-on-demand. However OPA's performance is greatly enahanced when FMR is enabled. In order to enable coexistence of both of

[PATCH 00/10] staging: lustre: lnet: per NI map-on-demand value

Enables support of different map-on-demand values per NI. This is required to support OPA coexistence with MLX5 cards. MLX5 does not support FMR, which is enabled via map-on-demand. However OPA's performance is greatly enahanced when FMR is enabled. In order to enable coexistence of both of

Re: [RESEND PATCH] [media] s5p-mfc: don't close instance after free OUTPUT buffers

Thanks for re-submitting. See inline two typos to fix in teh comment. cheers, Nicolas Le vendredi 06 mai 2016 à 18:11 -0400, Javier Martinez Canillas a écrit : > From: ayaka > > User-space applications can use the VIDIOC_REQBUFS ioctl to determine if a > memory mapped, user

Re: [RESEND PATCH] [media] s5p-mfc: don't close instance after free OUTPUT buffers

Thanks for re-submitting. See inline two typos to fix in teh comment. cheers, Nicolas Le vendredi 06 mai 2016 à 18:11 -0400, Javier Martinez Canillas a écrit : > From: ayaka > > User-space applications can use the VIDIOC_REQBUFS ioctl to determine if a > memory mapped, user pointer or DMABUF

Re: [PATCH v3 3/4] mfd: arizona: Switch to using clock driver for 32k clock

On 01/08, Charles Keepax wrote: > Now we have a clock driver that can control the 32k clock use this > rather than directly controlling the 32k clock from the MFD device. > > Signed-off-by: Charles Keepax > --- Applied to clk-next -- Qualcomm Innovation

Re: [PATCH v3 2/4] clk: arizona: Add clock driver for the Arizona devices

I've applied this to clk-next but still have a question, see below. On 01/08, Charles Keepax wrote: > diff --git a/drivers/clk/clk-arizona.c b/drivers/clk/clk-arizona.c > new file mode 100644 > index 000..eaf2877 > --- /dev/null > +++ b/drivers/clk/clk-arizona.c > + > +static int

Re: [PATCH v3 3/4] mfd: arizona: Switch to using clock driver for 32k clock

On 01/08, Charles Keepax wrote: > Now we have a clock driver that can control the 32k clock use this > rather than directly controlling the 32k clock from the MFD device. > > Signed-off-by: Charles Keepax > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora

Re: [PATCH v3 2/4] clk: arizona: Add clock driver for the Arizona devices

I've applied this to clk-next but still have a question, see below. On 01/08, Charles Keepax wrote: > diff --git a/drivers/clk/clk-arizona.c b/drivers/clk/clk-arizona.c > new file mode 100644 > index 000..eaf2877 > --- /dev/null > +++ b/drivers/clk/clk-arizona.c > + > +static int

Re: [PATCH v3 1/4] extcon: arizona: Remove enable/disable of 32k clock

On 01/08, Charles Keepax wrote: > The 32k clock is unconditionally enabled by the MFD core so there is no > need to control it from the extcon device, so this patch removes the > control of the 32k clock. > > Signed-off-by: Charles Keepax > --- Applied to

Re: [PATCH v3 1/4] extcon: arizona: Remove enable/disable of 32k clock

On 01/08, Charles Keepax wrote: > The 32k clock is unconditionally enabled by the MFD core so there is no > need to control it from the extcon device, so this patch removes the > control of the 32k clock. > > Signed-off-by: Charles Keepax > --- Applied to clk-next -- Qualcomm Innovation

Re: [PATCH v3 4/4] mfd: arizona: Add device tree binding documentation for new clock driver

On 05/06/2016 05:47 PM, Stephen Boyd wrote: > On 01/08/2016 03:29 AM, Charles Keepax wrote: >> Specify the device tree binding for the input clocks to Arizona devices. >> >> Signed-off-by: Charles Keepax >> Acked-by: Rob Herring >> --- >> >>

Re: [PATCH v3 4/4] mfd: arizona: Add device tree binding documentation for new clock driver

On 05/06/2016 05:47 PM, Stephen Boyd wrote: > On 01/08/2016 03:29 AM, Charles Keepax wrote: >> Specify the device tree binding for the input clocks to Arizona devices. >> >> Signed-off-by: Charles Keepax >> Acked-by: Rob Herring >> --- >> >> No changes since v2. >> >> Thanks, >> Charles >> >>

Re: [PATCH v3 4/4] mfd: arizona: Add device tree binding documentation for new clock driver

On 01/08/2016 03:29 AM, Charles Keepax wrote: > Specify the device tree binding for the input clocks to Arizona devices. > > Signed-off-by: Charles Keepax > Acked-by: Rob Herring > --- > > No changes since v2. > > Thanks, > Charles > >

Re: [PATCH v3 4/4] mfd: arizona: Add device tree binding documentation for new clock driver

On 01/08/2016 03:29 AM, Charles Keepax wrote: > Specify the device tree binding for the input clocks to Arizona devices. > > Signed-off-by: Charles Keepax > Acked-by: Rob Herring > --- > > No changes since v2. > > Thanks, > Charles > > Documentation/devicetree/bindings/mfd/arizona.txt | 7

[PATCH] intel_pstate: Clean up intel_pstate_get()

From: Rafael J. Wysocki intel_pstate_get() contains a local variable that's initialized but never used and it can be written in fewer lines of code, so clean it up. Signed-off-by: Rafael J. Wysocki --- drivers/cpufreq/intel_pstate.c |

[PATCH] intel_pstate: Clean up intel_pstate_get()

From: Rafael J. Wysocki intel_pstate_get() contains a local variable that's initialized but never used and it can be written in fewer lines of code, so clean it up. Signed-off-by: Rafael J. Wysocki --- drivers/cpufreq/intel_pstate.c |9 ++--- 1 file changed, 2 insertions(+), 7

  1   2   3   4   5   6   7   8   9   10   >