Re: [PATCH 4/6] clk: rockchip: rk3399: update necessary critical clocks

Am Mittwoch, 20. April 2016, 19:06:52 schrieb Xing Zheng: > We need to declare that we enable all NOCs which are critical > clocks always and clearly and explicitly show that we have enabled > them at clk_summary. > > We need to add some has been verified and required critical clocks > in the

Re: [PATCH 4/6] clk: rockchip: rk3399: update necessary critical clocks

Am Mittwoch, 20. April 2016, 19:06:52 schrieb Xing Zheng: > We need to declare that we enable all NOCs which are critical > clocks always and clearly and explicitly show that we have enabled > them at clk_summary. > > We need to add some has been verified and required critical clocks > in the

Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2

On Monday, April 25, 2016 02:56:08 PM Stephen Boyd wrote: > On 04/25, Rafael J. Wysocki wrote: > > On Mon, Apr 25, 2016 at 11:45 PM, Stephen Boyd wrote: > > > On 04/25, Viresh Kumar wrote: > > >> On 22-04-16, 15:27, Stephen Boyd wrote: > > >> > On 04/21, Viresh Kumar wrote:

Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2

On Monday, April 25, 2016 02:56:08 PM Stephen Boyd wrote: > On 04/25, Rafael J. Wysocki wrote: > > On Mon, Apr 25, 2016 at 11:45 PM, Stephen Boyd wrote: > > > On 04/25, Viresh Kumar wrote: > > >> On 22-04-16, 15:27, Stephen Boyd wrote: > > >> > On 04/21, Viresh Kumar wrote: > > >> > > @@ -167,14

Re: [PATCH/RFC v2] perf core: Allow setting up max frame stack depth via sysctl

On Mon, Apr 25, 2016 at 05:17:50PM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, Apr 25, 2016 at 01:06:48PM -0700, Alexei Starovoitov escreveu: > > On Mon, Apr 25, 2016 at 04:22:29PM -0300, Arnaldo Carvalho de Melo wrote: > > > Em Mon, Apr 25, 2016 at 01:27:06PM -0300, Arnaldo Carvalho de Melo

Re: [PATCH/RFC v2] perf core: Allow setting up max frame stack depth via sysctl

On Mon, Apr 25, 2016 at 05:17:50PM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, Apr 25, 2016 at 01:06:48PM -0700, Alexei Starovoitov escreveu: > > On Mon, Apr 25, 2016 at 04:22:29PM -0300, Arnaldo Carvalho de Melo wrote: > > > Em Mon, Apr 25, 2016 at 01:27:06PM -0300, Arnaldo Carvalho de Melo

[PATCH] megaraid_sas: trivial fix, add missing space in dev_err message

From: Colin Ian King Add a missing space in dev_err message, missed because the string spans a few lines. Signed-off-by: Colin Ian King --- drivers/scsi/megaraid/megaraid_sas_base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH] megaraid_sas: trivial fix, add missing space in dev_err message

From: Colin Ian King Add a missing space in dev_err message, missed because the string spans a few lines. Signed-off-by: Colin Ian King --- drivers/scsi/megaraid/megaraid_sas_base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c

Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2

On 04/25, Rafael J. Wysocki wrote: > On Mon, Apr 25, 2016 at 11:45 PM, Stephen Boyd wrote: > > On 04/25, Viresh Kumar wrote: > >> On 22-04-16, 15:27, Stephen Boyd wrote: > >> > On 04/21, Viresh Kumar wrote: > >> > > @@ -167,14 +167,16 @@ static int cpufreq_init(struct

Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2

On 04/25, Rafael J. Wysocki wrote: > On Mon, Apr 25, 2016 at 11:45 PM, Stephen Boyd wrote: > > On 04/25, Viresh Kumar wrote: > >> On 22-04-16, 15:27, Stephen Boyd wrote: > >> > On 04/21, Viresh Kumar wrote: > >> > > @@ -167,14 +167,16 @@ static int cpufreq_init(struct cpufreq_policy > >> > >

[PATCH v2] ftrace: Match dot symbols when searching functions on ppc64

In the ppc64 big endian ABI, function symbols point to function descriptors. The symbols which point to the function entry points have a dot in front of the function name. Consequently, when the ftrace filter mechanism searches for the symbol corresponding to an entry point address, it gets the

[PATCH v2] ftrace: Match dot symbols when searching functions on ppc64

In the ppc64 big endian ABI, function symbols point to function descriptors. The symbols which point to the function entry points have a dot in front of the function name. Consequently, when the ftrace filter mechanism searches for the symbol corresponding to an entry point address, it gets the

Re: [PATCH net v2 2/3] drivers: net: cpsw: fix error messages when using phy-handle DT property

On Mon, 25 Apr 2016 22:12:20 +0300 Grygorii Strashko wrote: > On 04/22/2016 06:45 PM, David Rivshin (Allworx) wrote: > > On Fri, 22 Apr 2016 16:03:34 +0300 > > Grygorii Strashko wrote: > > > >> On 04/21/2016 09:26 PM, David Rivshin

Re: [PATCH net v2 2/3] drivers: net: cpsw: fix error messages when using phy-handle DT property

On Mon, 25 Apr 2016 22:12:20 +0300 Grygorii Strashko wrote: > On 04/22/2016 06:45 PM, David Rivshin (Allworx) wrote: > > On Fri, 22 Apr 2016 16:03:34 +0300 > > Grygorii Strashko wrote: > > > >> On 04/21/2016 09:26 PM, David Rivshin (Allworx) wrote: > >>> From: David Rivshin > >>> > >>>

Re: [patch v2] mm, hugetlb_cgroup: round limit_in_bytes down to hugepage size

On Mon, 18 Apr 2016 14:23:58 -0700 (PDT) David Rientjes wrote: > On Fri, 15 Apr 2016, Michal Hocko wrote: > > > > > > +static void hugetlb_cgroup_init(struct hugetlb_cgroup *h_cgroup, > > > > > + struct hugetlb_cgroup *parent_h_cgroup) > > > > >

Re: [patch v2] mm, hugetlb_cgroup: round limit_in_bytes down to hugepage size

On Mon, 18 Apr 2016 14:23:58 -0700 (PDT) David Rientjes wrote: > On Fri, 15 Apr 2016, Michal Hocko wrote: > > > > > > +static void hugetlb_cgroup_init(struct hugetlb_cgroup *h_cgroup, > > > > > + struct hugetlb_cgroup *parent_h_cgroup) > > > > > +{ > > > > > +

[PATCH] iscsi-target: graceful disconnect on invalid mapping to iovec

Ensures the first page entry is within bounds. A failed check would terminate the iSCSI connection instead of causing a NULL-dereference. This violation seems to happen with certain iSCSI commands where the computed CDB length is zero but the expected transfer length is non-zero. The real problem

[PATCH] iscsi-target: graceful disconnect on invalid mapping to iovec

Ensures the first page entry is within bounds. A failed check would terminate the iSCSI connection instead of causing a NULL-dereference. This violation seems to happen with certain iSCSI commands where the computed CDB length is zero but the expected transfer length is non-zero. The real problem

Re: [PATCH 3/4] perf/x86/mbm: Fix mbm counting when RMIDs are reused

'per event' rc_count = read_sample(event->rmid) - per event start count; 'per event' rc_count += read_sample(event->rmid) - per event start count;

Re: [PATCH 3/4] perf/x86/mbm: Fix mbm counting when RMIDs are reused

'per event' rc_count = read_sample(event->rmid) - per event start count; 'per event' rc_count += read_sample(event->rmid) - per event start count;

Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2

On Mon, Apr 25, 2016 at 11:45 PM, Stephen Boyd wrote: > On 04/25, Viresh Kumar wrote: >> On 22-04-16, 15:27, Stephen Boyd wrote: >> > On 04/21, Viresh Kumar wrote: >> > > @@ -167,14 +167,16 @@ static int cpufreq_init(struct cpufreq_policy >> > > *policy) >> > > /* Get

Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2

On Mon, Apr 25, 2016 at 11:45 PM, Stephen Boyd wrote: > On 04/25, Viresh Kumar wrote: >> On 22-04-16, 15:27, Stephen Boyd wrote: >> > On 04/21, Viresh Kumar wrote: >> > > @@ -167,14 +167,16 @@ static int cpufreq_init(struct cpufreq_policy >> > > *policy) >> > > /* Get OPP-sharing information

Re: [PATCH v7 06/15] dt-bindings: i2c: Add Octeon cn78xx TWSI

On Mon, Apr 25, 2016 at 04:33:35PM +0200, Jan Glauber wrote: > Add compatible string for Cavium Octeon cn78XX SOCs TWSI. > > Cc: Rob Herring > Cc: Pawel Moll > Cc: Mark Rutland > Cc: Ian Campbell >

Re: [PATCH v7 07/15] i2c: octeon: Add support for cn78xx chips

On Mon, Apr 25, 2016 at 04:33:36PM +0200, Jan Glauber wrote: > From: David Daney > > cn78xx has a different interrupt architecture, so we have to manage > the interrupts differently. > > Signed-off-by: David Daney > Signed-off-by: Jan Glauber

Re: [PATCH v7 06/15] dt-bindings: i2c: Add Octeon cn78xx TWSI

On Mon, Apr 25, 2016 at 04:33:35PM +0200, Jan Glauber wrote: > Add compatible string for Cavium Octeon cn78XX SOCs TWSI. > > Cc: Rob Herring > Cc: Pawel Moll > Cc: Mark Rutland > Cc: Ian Campbell > Cc: Kumar Gala > > Signed-off-by: Jan Glauber > Acked-by: David Daney Applied to for-next,

Re: [PATCH v7 07/15] i2c: octeon: Add support for cn78xx chips

On Mon, Apr 25, 2016 at 04:33:36PM +0200, Jan Glauber wrote: > From: David Daney > > cn78xx has a different interrupt architecture, so we have to manage > the interrupts differently. > > Signed-off-by: David Daney > Signed-off-by: Jan Glauber Applied to for-next, thanks! signature.asc

Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2

On 04/25, Viresh Kumar wrote: > On 22-04-16, 15:27, Stephen Boyd wrote: > > On 04/21, Viresh Kumar wrote: > > > @@ -167,14 +167,16 @@ static int cpufreq_init(struct cpufreq_policy > > > *policy) > > > /* Get OPP-sharing information from "operating-points-v2" bindings */ > > > ret =

Re: [PATCH v6 10/19] i2c: octeon: Add support for cn78xx chips

> Personally, I preferred the old way where each device had interrupt enable > bits that could be controlled independently of the interrupt controller. I > have been told that I should abandon my preference for that type of > antiquated architecture and welcome the brave new world of the unified

Re: [PATCH 07/10] cpufreq: dt: Identify cpu-sharing for platforms without operating-points-v2

On 04/25, Viresh Kumar wrote: > On 22-04-16, 15:27, Stephen Boyd wrote: > > On 04/21, Viresh Kumar wrote: > > > @@ -167,14 +167,16 @@ static int cpufreq_init(struct cpufreq_policy > > > *policy) > > > /* Get OPP-sharing information from "operating-points-v2" bindings */ > > > ret =

Re: [PATCH v6 10/19] i2c: octeon: Add support for cn78xx chips

> Personally, I preferred the old way where each device had interrupt enable > bits that could be controlled independently of the interrupt controller. I > have been told that I should abandon my preference for that type of > antiquated architecture and welcome the brave new world of the unified

Re: [linux-next PATCH] sched: cgroup: enable interrupt before calling threadgroup_change_begin

On 4/25/2016 10:35 AM, Shi, Yang wrote: On 4/23/2016 2:14 AM, Peter Zijlstra wrote: On Fri, Apr 22, 2016 at 08:56:28PM -0700, Yang Shi wrote: When kernel oops happens in some kernel thread, i.e. kcompactd in the test, the below bug might be triggered by the oops handler: What are you trying

Re: [PATCH] mm/zpool: use workqueue for zpool_destroy

On Mon, 25 Apr 2016 17:20:10 -0400 Dan Streetman wrote: > Add a work_struct to struct zpool, and change zpool_destroy_pool to > defer calling the pool implementation destroy. > > The zsmalloc pool destroy function, which is one of the zpool > implementations, may sleep during

Re: [PATCH] mm/zpool: use workqueue for zpool_destroy

On Mon, 25 Apr 2016 17:20:10 -0400 Dan Streetman wrote: > Add a work_struct to struct zpool, and change zpool_destroy_pool to > defer calling the pool implementation destroy. > > The zsmalloc pool destroy function, which is one of the zpool > implementations, may sleep during destruction of the

Re: [linux-next PATCH] sched: cgroup: enable interrupt before calling threadgroup_change_begin

On 4/25/2016 10:35 AM, Shi, Yang wrote: On 4/23/2016 2:14 AM, Peter Zijlstra wrote: On Fri, Apr 22, 2016 at 08:56:28PM -0700, Yang Shi wrote: When kernel oops happens in some kernel thread, i.e. kcompactd in the test, the below bug might be triggered by the oops handler: What are you trying

Re: [PATCH v2] mm: SLAB freelist randomization

On Mon, Apr 25, 2016 at 2:38 PM, Andrew Morton wrote: > On Mon, 25 Apr 2016 14:14:33 -0700 Thomas Garnier wrote: > >> >>> + /* Get best entropy at this stage */ >> >>> + get_random_bytes_arch(, sizeof(seed)); >> >> >> >> See concerns in

Re: [PATCH v2] mm: SLAB freelist randomization

On Mon, Apr 25, 2016 at 2:38 PM, Andrew Morton wrote: > On Mon, 25 Apr 2016 14:14:33 -0700 Thomas Garnier wrote: > >> >>> + /* Get best entropy at this stage */ >> >>> + get_random_bytes_arch(, sizeof(seed)); >> >> >> >> See concerns in other email - isn't this a no-op if

[PATCH v3 1/2] acpi/nfit: Update nfit driver to comply with ACPI 6.1

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as follows. - Valid Fields, Manufacturing Location, and Manufacturing Date are added from reserved range. No change in the structure size. - IDs (SPD values) are stored as arrays of bytes (i.e. big-endian format). The spec

Re: [PATCH v7 05/15] i2c: octeon: Enable High-Level Controller

On Mon, Apr 25, 2016 at 04:33:34PM +0200, Jan Glauber wrote: > From: David Daney > > Use High-Level Controller (HLC) when possible. The HLC can read/write > up to 8 bytes and is completely optional. The most important difference > of the HLC is that it only requires

[PATCH v3 1/2] acpi/nfit: Update nfit driver to comply with ACPI 6.1

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as follows. - Valid Fields, Manufacturing Location, and Manufacturing Date are added from reserved range. No change in the structure size. - IDs (SPD values) are stored as arrays of bytes (i.e. big-endian format). The spec

Re: [PATCH v7 05/15] i2c: octeon: Enable High-Level Controller

On Mon, Apr 25, 2016 at 04:33:34PM +0200, Jan Glauber wrote: > From: David Daney > > Use High-Level Controller (HLC) when possible. The HLC can read/write > up to 8 bytes and is completely optional. The most important difference > of the HLC is that it only requires one interrupt for a transfer

[PATCH v3 2/2] acpi/nfit: Add sysfs "id" for NVDIMM ID

ACPI 6.1, section 5.2.25.9, defines an identifier for an NVDIMM. Change the NFIT driver to add a new sysfs file "id" under nfit directory. Signed-off-by: Toshi Kani Cc: Rafael J. Wysocki Cc: Dan Williams Cc: Robert Moore

Re: [PATCH 3/4] perf/x86/mbm: Fix mbm counting when RMIDs are reused

On Mon, 25 Apr 2016, Peter Zijlstra wrote: On Mon, Apr 25, 2016 at 09:44:53AM -0700, Vikas Shivappa wrote: On Mon, 25 Apr 2016, Peter Zijlstra wrote: On Fri, Apr 22, 2016 at 05:27:20PM -0700, Vikas Shivappa wrote: When multiple instances of perf reuse RMID, then we need to start

[PATCH v3 2/2] acpi/nfit: Add sysfs "id" for NVDIMM ID

ACPI 6.1, section 5.2.25.9, defines an identifier for an NVDIMM. Change the NFIT driver to add a new sysfs file "id" under nfit directory. Signed-off-by: Toshi Kani Cc: Rafael J. Wysocki Cc: Dan Williams Cc: Robert Moore Cc: Robert Elliott --- drivers/acpi/nfit.c | 19 +++

Re: [PATCH 3/4] perf/x86/mbm: Fix mbm counting when RMIDs are reused

On Mon, 25 Apr 2016, Peter Zijlstra wrote: On Mon, Apr 25, 2016 at 09:44:53AM -0700, Vikas Shivappa wrote: On Mon, 25 Apr 2016, Peter Zijlstra wrote: On Fri, Apr 22, 2016 at 05:27:20PM -0700, Vikas Shivappa wrote: When multiple instances of perf reuse RMID, then we need to start

[PATCH v3 0/2] Support ACPI 6.1 update in NFIT Control Region Structure

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as follows. - Valid Fields, Manufacturing Location, and Manufacturing Date are added from reserved range. No change in the structure size. - IDs (SPD values) are stored as arrays of bytes (i.e. big-endian format). The spec

[PATCH v3 0/2] Support ACPI 6.1 update in NFIT Control Region Structure

ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as follows. - Valid Fields, Manufacturing Location, and Manufacturing Date are added from reserved range. No change in the structure size. - IDs (SPD values) are stored as arrays of bytes (i.e. big-endian format). The spec

[PATCH] mfd: ab8500-debugfs: trivial fix of spelling mistake on "between"

From: Colin Ian King fix spelling mistake, beetween -> between Signed-off-by: Colin Ian King --- drivers/mfd/ab8500-debugfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mfd/ab8500-debugfs.c

Re: [PATCH v4] ASoC: docs: add clocking examples for DAI formats

On 2016-04-25 19:36, Mark Brown wrote: > On Mon, Apr 25, 2016 at 04:15:40PM +0200, Peter Rosin wrote: > >> I've searched for a bit, and the best I can find is (IMHO) >> https://web.archive.org/web/20060702004954/http://www.semiconductors.philips.com/acrobat_download/various/I2SBUS.pdf > That looks

[PATCH] mfd: ab8500-debugfs: trivial fix of spelling mistake on "between"

From: Colin Ian King fix spelling mistake, beetween -> between Signed-off-by: Colin Ian King --- drivers/mfd/ab8500-debugfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mfd/ab8500-debugfs.c b/drivers/mfd/ab8500-debugfs.c index 69d9fff..0aecd7b 100644 ---

Re: [PATCH v4] ASoC: docs: add clocking examples for DAI formats

On 2016-04-25 19:36, Mark Brown wrote: > On Mon, Apr 25, 2016 at 04:15:40PM +0200, Peter Rosin wrote: > >> I've searched for a bit, and the best I can find is (IMHO) >> https://web.archive.org/web/20060702004954/http://www.semiconductors.philips.com/acrobat_download/various/I2SBUS.pdf > That looks

Re: [PATCHv8 2/2] selftest/x86: add mremap vdso test

On Mon, Apr 25, 2016 at 4:37 AM, Dmitry Safonov wrote: > Should print on success: > [root@localhost ~]# ./test_mremap_vdso_32 > AT_SYSINFO_EHDR is 0xf773f000 > [NOTE] Moving vDSO: [f773f000, f774] -> [a00, a001000] > [OK] > Or segfault if landing was bad

Re: [PATCHv8 2/2] selftest/x86: add mremap vdso test

On Mon, Apr 25, 2016 at 4:37 AM, Dmitry Safonov wrote: > Should print on success: > [root@localhost ~]# ./test_mremap_vdso_32 > AT_SYSINFO_EHDR is 0xf773f000 > [NOTE] Moving vDSO: [f773f000, f774] -> [a00, a001000] > [OK] > Or segfault if landing was bad (before patches): >

Re: [PATCH v2] mm: SLAB freelist randomization

On Mon, 25 Apr 2016 14:14:33 -0700 Thomas Garnier wrote: > >>> + /* Get best entropy at this stage */ > >>> + get_random_bytes_arch(, sizeof(seed)); > >> > >> See concerns in other email - isn't this a no-op if CONFIG_ARCH_RANDOM=n? > >> > > The arch_* functions

Re: [PATCH v2] mm: SLAB freelist randomization

On Mon, 25 Apr 2016 14:14:33 -0700 Thomas Garnier wrote: > >>> + /* Get best entropy at this stage */ > >>> + get_random_bytes_arch(, sizeof(seed)); > >> > >> See concerns in other email - isn't this a no-op if CONFIG_ARCH_RANDOM=n? > >> > > The arch_* functions will return 0 which will

Re: [PATCHv8 1/2] x86/vdso: add mremap hook to vm_special_mapping

On Mon, Apr 25, 2016 at 4:37 AM, Dmitry Safonov wrote: > Add possibility for userspace 32-bit applications to move > vdso mapping. Previously, when userspace app called > mremap for vdso, in return path it would land on previous > address of vdso page, resulting in

Re: [PATCHv8 1/2] x86/vdso: add mremap hook to vm_special_mapping

On Mon, Apr 25, 2016 at 4:37 AM, Dmitry Safonov wrote: > Add possibility for userspace 32-bit applications to move > vdso mapping. Previously, when userspace app called > mremap for vdso, in return path it would land on previous > address of vdso page, resulting in segmentation violation. > Now

[PATCH] cpupowerutils: bench: trivial fix of spelling mistake on "average"

From: Colin Ian King fix spelling mistake, avarage -> average Signed-off-by: Colin Ian King --- tools/power/cpupower/bench/README-BENCH | 2 +- tools/power/cpupower/bench/benchmark.c | 4 ++-- 2 files changed, 3 insertions(+), 3

[PATCH] cpupowerutils: bench: trivial fix of spelling mistake on "average"

From: Colin Ian King fix spelling mistake, avarage -> average Signed-off-by: Colin Ian King --- tools/power/cpupower/bench/README-BENCH | 2 +- tools/power/cpupower/bench/benchmark.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [RFC PATCH 3/4] intel_pstate: support scheduler cpufreq callbacks on remote CPUs

On Thu, Apr 21, 2016 at 4:20 AM, Steve Muckle wrote: > On Wed, Apr 20, 2016 at 02:37:18PM +0200, Rafael J. Wysocki wrote: > ... >> > @@ -1173,20 +1179,88 @@ static inline void >> > intel_pstate_adjust_busy_pstate(struct cpudata *cpu) >> >

Re: [RFC PATCH 3/4] intel_pstate: support scheduler cpufreq callbacks on remote CPUs

On Thu, Apr 21, 2016 at 4:20 AM, Steve Muckle wrote: > On Wed, Apr 20, 2016 at 02:37:18PM +0200, Rafael J. Wysocki wrote: > ... >> > @@ -1173,20 +1179,88 @@ static inline void >> > intel_pstate_adjust_busy_pstate(struct cpudata *cpu) >> > get_avg_frequency(cpu)); >> > } >> > >> >

Re: [PATCH 2/2] tty: serial: msm_serial add info message

On 04/25, Frank Rowand wrote: > > This is in msm_request_tx_dma(). I should have made the message > "msm_serial: TX DMA not enabled\n" and added a similar message > to msm_request_rx_dma(). > > Then it could print twice, once for TX and once for RX. :-) > For my board it would print twice

Re: [PATCH 2/2] tty: serial: msm_serial add info message

On 04/25, Frank Rowand wrote: > > This is in msm_request_tx_dma(). I should have made the message > "msm_serial: TX DMA not enabled\n" and added a similar message > to msm_request_rx_dma(). > > Then it could print twice, once for TX and once for RX. :-) > For my board it would print twice

Re: [PATCH] perf tools: replace assignment with comparison on assert check

On Sat, 23 Apr 2016 14:45:54 +0100 Colin King wrote: > From: Colin Ian King > > The current assert check is checking an assignment, which will always > be true. Instead, the assert should be checking if scale is equal > to 0.122 > Looks

Re: [PATCH] perf tools: replace assignment with comparison on assert check

On Sat, 23 Apr 2016 14:45:54 +0100 Colin King wrote: > From: Colin Ian King > > The current assert check is checking an assignment, which will always > be true. Instead, the assert should be checking if scale is equal > to 0.122 > Looks good to me. Reviewed-by: Masami Hiramatsu >

Re: [PATCH v7 04/15] i2c: octeon: Add flush writeq helper function

On Mon, Apr 25, 2016 at 04:33:33PM +0200, Jan Glauber wrote: > From: Peter Swain > > Add helper function that reads back a value after writing to > make sure the write is finished and use it in octeon_i2c_write_int(). > > Signed-off-by: Peter Swain >

Re: [PATCH v7 04/15] i2c: octeon: Add flush writeq helper function

On Mon, Apr 25, 2016 at 04:33:33PM +0200, Jan Glauber wrote: > From: Peter Swain > > Add helper function that reads back a value after writing to > make sure the write is finished and use it in octeon_i2c_write_int(). > > Signed-off-by: Peter Swain > Signed-off-by: Jan Glauber Applied to

Re: [PATCH 2/2] tty: serial: msm_serial add info message

On 4/25/2016 1:48 PM, Stephen Boyd wrote: > On 04/23, Frank Rowand wrote: >> From: Frank Rowand >> >> Failure to enable DMA by the msm_serial driver is silent. >> Add a message to report the failure. >> >> Signed-off-by: Frank Rowand >> --- >>

Re: [PATCH 2/2] tty: serial: msm_serial add info message

On 4/25/2016 1:48 PM, Stephen Boyd wrote: > On 04/23, Frank Rowand wrote: >> From: Frank Rowand >> >> Failure to enable DMA by the msm_serial driver is silent. >> Add a message to report the failure. >> >> Signed-off-by: Frank Rowand >> --- >> drivers/tty/serial/msm_serial.c |1 + >> 1 file

Re: [PATCH] nohz_full: Make sched_should_stop_tick() more conservative

On 4/21/2016 12:03 PM, Peter Zijlstra wrote: On Thu, Apr 21, 2016 at 04:42:13PM +0200, Peter Zijlstra wrote: So I think that is indeed the right thing here. But looking at this function I think there's more problems with it. It seems to assume that if there's FIFO tasks, those will run. This

Re: [patch v2] mm, hugetlb_cgroup: round limit_in_bytes down to hugepage size

On Wed, 6 Apr 2016, David Rientjes wrote: > The page_counter rounds limits down to page size values. This makes > sense, except in the case of hugetlb_cgroup where it's not possible to > charge partial hugepages. > > Round the hugetlb_cgroup limit down to hugepage size. > > Signed-off-by:

Re: [PATCH] nohz_full: Make sched_should_stop_tick() more conservative

On 4/21/2016 12:03 PM, Peter Zijlstra wrote: On Thu, Apr 21, 2016 at 04:42:13PM +0200, Peter Zijlstra wrote: So I think that is indeed the right thing here. But looking at this function I think there's more problems with it. It seems to assume that if there's FIFO tasks, those will run. This

Re: [patch v2] mm, hugetlb_cgroup: round limit_in_bytes down to hugepage size

On Wed, 6 Apr 2016, David Rientjes wrote: > The page_counter rounds limits down to page size values. This makes > sense, except in the case of hugetlb_cgroup where it's not possible to > charge partial hugepages. > > Round the hugetlb_cgroup limit down to hugepage size. > > Signed-off-by:

Re: [PATCH v7 02/15] i2c: octeon: Use i2c recovery framework

On Mon, Apr 25, 2016 at 04:33:31PM +0200, Jan Glauber wrote: > Switch to the i2c bus recovery framework using generic SCL recovery. > If this fails try to reset the hardware. The recovery is triggered > during START on timeout of the interrupt or failure to reach > the START / repeated-START

Re: [RFC] perf probe: Fix module probe issue if no dwarf support

On Mon, 25 Apr 2016 16:08:28 +0530 Ravi Bangoria wrote: > Perf is not able to register probe in kernel module when dwarf supprt > is not there(and so it goes for symtab). Perf passes full path of > module where only module name is required which is causing the

Re: [PATCH v7 02/15] i2c: octeon: Use i2c recovery framework

On Mon, Apr 25, 2016 at 04:33:31PM +0200, Jan Glauber wrote: > Switch to the i2c bus recovery framework using generic SCL recovery. > If this fails try to reset the hardware. The recovery is triggered > during START on timeout of the interrupt or failure to reach > the START / repeated-START

Re: [RFC] perf probe: Fix module probe issue if no dwarf support

On Mon, 25 Apr 2016 16:08:28 +0530 Ravi Bangoria wrote: > Perf is not able to register probe in kernel module when dwarf supprt > is not there(and so it goes for symtab). Perf passes full path of > module where only module name is required which is causing the problem. > This patch fixes this

Re: [PATCH] Input: atmel_mxt_ts - use mxt_acquire_irq in mxt_soft_reset

On Mon, Apr 11, 2016 at 10:31:45AM +0100, Nick Dyer wrote: > If using IRQF_TRIGGER_FALLING, then there is a race here: if the reset > completes before we enable the IRQ, then CHG is already low and touch > will be broken. > > This has been seen on Chromebook Pixel 2. > > A workaround is to

Re: [PATCH] Input: atmel_mxt_ts - use mxt_acquire_irq in mxt_soft_reset

On Mon, Apr 11, 2016 at 10:31:45AM +0100, Nick Dyer wrote: > If using IRQF_TRIGGER_FALLING, then there is a race here: if the reset > completes before we enable the IRQ, then CHG is already low and touch > will be broken. > > This has been seen on Chromebook Pixel 2. > > A workaround is to

Re: [RFC PATCH 1/4] cpufreq: governor: support scheduler cpufreq callbacks on remote CPUs

On Mon, Apr 25, 2016 at 9:17 PM, Steve Muckle wrote: > On Wed, Apr 20, 2016 at 02:26:06PM +0200, Rafael J. Wysocki wrote: >> You could have added a cover [0/4] message which would have made it easier >> to reply to the entire series in general. Let me do it here. > >

Re: [RFC PATCH 1/4] cpufreq: governor: support scheduler cpufreq callbacks on remote CPUs

On Mon, Apr 25, 2016 at 9:17 PM, Steve Muckle wrote: > On Wed, Apr 20, 2016 at 02:26:06PM +0200, Rafael J. Wysocki wrote: >> You could have added a cover [0/4] message which would have made it easier >> to reply to the entire series in general. Let me do it here. > > Will add that next time. >

Re: [RFC] perf probe: Fix offline module name missmatch issue

Hi Ravi, On Mon, 25 Apr 2016 16:08:27 +0530 Ravi Bangoria wrote: > Perf can add a probe on kernel module which has not been loaded yet. > Current implementation finds module name from path. But if filename > is different from actual module name then perf fails

Re: [PATCH v2] printk: Add kernel parameter to disable writes to /dev/kmsg

On Mon, 25 Apr 2016 13:45:25 -0700 Linus Torvalds wrote: > On Mon, Apr 25, 2016 at 1:34 PM, Steven Rostedt wrote: > > > > There's a bug somewhere with mine: > > > > # journalctl -k > > No journal files were found. > > -- No entries -- > >

[PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version

The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to

Re: [RFC] perf probe: Fix offline module name missmatch issue

Hi Ravi, On Mon, 25 Apr 2016 16:08:27 +0530 Ravi Bangoria wrote: > Perf can add a probe on kernel module which has not been loaded yet. > Current implementation finds module name from path. But if filename > is different from actual module name then perf fails to register > probe while loading

Re: [PATCH v2] printk: Add kernel parameter to disable writes to /dev/kmsg

On Mon, 25 Apr 2016 13:45:25 -0700 Linus Torvalds wrote: > On Mon, Apr 25, 2016 at 1:34 PM, Steven Rostedt wrote: > > > > There's a bug somewhere with mine: > > > > # journalctl -k > > No journal files were found. > > -- No entries -- > > Is that with your patch? If you don't allow kmsg

[PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version

The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to

Re: [PATCH 11/30] drbd: when receiving P_TRIM, zero-out partial unaligned chunks

On Mon, Apr 25, 2016 at 02:07:38PM +0200, Philipp Reisner wrote: > + max_discard_sectors = min(q->limits.max_discard_sectors, (1U << 22)); > + max_discard_sectors -= max_discard_sectors % granularity; there On Mon, Apr 25, 2016 at 10:32:17PM +0200, Lars Ellenberg wrote: > On Mon,

Re: [PATCH 11/30] drbd: when receiving P_TRIM, zero-out partial unaligned chunks

On Mon, Apr 25, 2016 at 02:07:38PM +0200, Philipp Reisner wrote: > + max_discard_sectors = min(q->limits.max_discard_sectors, (1U << 22)); > + max_discard_sectors -= max_discard_sectors % granularity; there On Mon, Apr 25, 2016 at 10:32:17PM +0200, Lars Ellenberg wrote: > On Mon,

[PATCH v5 1/1] ARM64: ACPI: Update documentation for latest specification version

The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to

[PATCH] mm/zpool: use workqueue for zpool_destroy

Add a work_struct to struct zpool, and change zpool_destroy_pool to defer calling the pool implementation destroy. The zsmalloc pool destroy function, which is one of the zpool implementations, may sleep during destruction of the pool. However zswap, which uses zpool, may call zpool_destroy_pool

[PATCH v5 1/1] ARM64: ACPI: Update documentation for latest specification version

The ACPI 6.1 specification was recently released at the end of January 2016, but the arm64 kernel documentation for the use of ACPI was written for the 5.1 version of the spec. There were significant additions to the spec that had not yet been mentioned -- for example, the 6.0 mechanisms added to

[PATCH] mm/zpool: use workqueue for zpool_destroy

Add a work_struct to struct zpool, and change zpool_destroy_pool to defer calling the pool implementation destroy. The zsmalloc pool destroy function, which is one of the zpool implementations, may sleep during destruction of the pool. However zswap, which uses zpool, may call zpool_destroy_pool

Re: [PATCH v7 01/15] i2c: octeon: Improve error status checking

On Mon, Apr 25, 2016 at 04:33:30PM +0200, Jan Glauber wrote: > Introduce a function that checks for valid status codes depending > on the phase of a transmit or receive. Also add all existing status > codes and improve error handling for various states. > > The Octeon TWSI has an "assert

Re: [PATCH v7 01/15] i2c: octeon: Improve error status checking

On Mon, Apr 25, 2016 at 04:33:30PM +0200, Jan Glauber wrote: > Introduce a function that checks for valid status codes depending > on the phase of a transmit or receive. Also add all existing status > codes and improve error handling for various states. > > The Octeon TWSI has an "assert

Re: [PATCH v8 2/7] Input: cros_ec_keyb - Stop handling interrupts directly

On Tue, Apr 12, 2016 at 02:32:25PM +0200, Tomeu Vizoso wrote: > From: Vic Yang > > Because events other that keyboard ones will be handled by now on by > other drivers, stop directly handling interrupts and instead listen to > the new notifier in the MFD driver. > Hmm,

Re: [PATCH v8 2/7] Input: cros_ec_keyb - Stop handling interrupts directly

On Tue, Apr 12, 2016 at 02:32:25PM +0200, Tomeu Vizoso wrote: > From: Vic Yang > > Because events other that keyboard ones will be handled by now on by > other drivers, stop directly handling interrupts and instead listen to > the new notifier in the MFD driver. > Hmm, where did Vic's sign-off

Re: [PATCH v2] mm: SLAB freelist randomization

On Mon, Apr 25, 2016 at 2:13 PM, Thomas Garnier wrote: > On Mon, Apr 25, 2016 at 2:10 PM, Andrew Morton > wrote: >> On Mon, 25 Apr 2016 13:39:23 -0700 Thomas Garnier >> wrote: >> >>> Provides an optional config

Re: [PATCH v2] mm: SLAB freelist randomization

On Mon, Apr 25, 2016 at 2:13 PM, Thomas Garnier wrote: > On Mon, Apr 25, 2016 at 2:10 PM, Andrew Morton > wrote: >> On Mon, 25 Apr 2016 13:39:23 -0700 Thomas Garnier >> wrote: >> >>> Provides an optional config (CONFIG_FREELIST_RANDOM) to randomize the >>> SLAB freelist. The list is randomized

Re: [PATCH v2] mm: SLAB freelist randomization

On Mon, Apr 25, 2016 at 2:10 PM, Andrew Morton wrote: > On Mon, 25 Apr 2016 13:39:23 -0700 Thomas Garnier wrote: > >> Provides an optional config (CONFIG_FREELIST_RANDOM) to randomize the >> SLAB freelist. The list is randomized during

Re: [PATCH v2] mm: SLAB freelist randomization

On Mon, Apr 25, 2016 at 2:10 PM, Andrew Morton wrote: > On Mon, 25 Apr 2016 13:39:23 -0700 Thomas Garnier wrote: > >> Provides an optional config (CONFIG_FREELIST_RANDOM) to randomize the >> SLAB freelist. The list is randomized during initialization of a new set >> of pages. The order on

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