Re: [PATCH v7 1/9] x86/KASLR: Initialize mapping_info every time

* Yinghai Lu wrote: > On Mon, May 9, 2016 at 3:23 PM, Kees Cook wrote: > >> The exact reason to have assigning in functions. > >> > >> pgt_data address could be changed during kernel relocation. > >> so can not assigned during compiling time. > > > >

Re: [PATCH v7 1/9] x86/KASLR: Initialize mapping_info every time

* Yinghai Lu wrote: > On Mon, May 9, 2016 at 3:23 PM, Kees Cook wrote: > >> The exact reason to have assigning in functions. > >> > >> pgt_data address could be changed during kernel relocation. > >> so can not assigned during compiling time. > > > > Ah-ha, that explains why I had to keep it

Re: [PATCH v2 00/23] ata: sata_dwc_460ex: make it working again

On Mon, May 09, 2016 at 10:59:32PM +0300, Andy Shevchenko wrote: > On Mon, May 9, 2016 at 10:05 PM, Tejun Heo wrote: > > On Mon, May 09, 2016 at 10:13:59AM +0100, Måns Rullgård wrote: > >> Andy Shevchenko writes: > >> > >> > On Mon, May 9, 2016 at 4:09

Re: [PATCH v2 00/23] ata: sata_dwc_460ex: make it working again

On Mon, May 09, 2016 at 10:59:32PM +0300, Andy Shevchenko wrote: > On Mon, May 9, 2016 at 10:05 PM, Tejun Heo wrote: > > On Mon, May 09, 2016 at 10:13:59AM +0100, Måns Rullgård wrote: > >> Andy Shevchenko writes: > >> > >> > On Mon, May 9, 2016 at 4:09 AM, Tejun Heo wrote: > >> >> On Sun, May

[PATCH perf/core v3 6/8] perf pmu: Make pmu_formats_string to check return value of strbuf

Make pmu_formats_string() to check return value of strbuf APIs so that it can detect errors in it. Signed-off-by: Masami Hiramatsu --- tools/perf/util/pmu.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tools/perf/util/pmu.c

[PATCH perf/core v3 3/8] perf help: Make check_emacsclient_version to check strbuf APIs

Make check_emacsclient_version() to check the return value of strbuf APIs so that it can handle errors in strbuf. --- tools/perf/builtin-help.c | 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/tools/perf/builtin-help.c b/tools/perf/builtin-help.c index

[PATCH perf/core v3 7/8] perf help: Do not use ALLOC_GROW in add_cmd_list

Replace ALLOC_GROW with normal realloc code in add_cmd_list() so that it can handle errors directly. Signed-off-by: Masami Hiramatsu --- tools/perf/util/help-unknown-cmd.c | 30 ++ 1 file changed, 22 insertions(+), 8 deletions(-) diff --git

[PATCH perf/core v3 6/8] perf pmu: Make pmu_formats_string to check return value of strbuf

Make pmu_formats_string() to check return value of strbuf APIs so that it can detect errors in it. Signed-off-by: Masami Hiramatsu --- tools/perf/util/pmu.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c index

[PATCH perf/core v3 3/8] perf help: Make check_emacsclient_version to check strbuf APIs

Make check_emacsclient_version() to check the return value of strbuf APIs so that it can handle errors in strbuf. --- tools/perf/builtin-help.c | 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/tools/perf/builtin-help.c b/tools/perf/builtin-help.c index

[PATCH perf/core v3 7/8] perf help: Do not use ALLOC_GROW in add_cmd_list

Replace ALLOC_GROW with normal realloc code in add_cmd_list() so that it can handle errors directly. Signed-off-by: Masami Hiramatsu --- tools/perf/util/help-unknown-cmd.c | 30 ++ 1 file changed, 22 insertions(+), 8 deletions(-) diff --git

[PATCH perf/core v3 5/8] perf header: Make topology checkers to check return value of strbuf

Make topology checkers to check the return value of strbuf APIs so that it can detect errors in it. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Avoid using STRBUF_INIT and return error directly before initalizing strbuf. --- tools/perf/util/header.c | 31

[PATCH perf/core v3 8/8] perf tools: Remove xrealloc and ALLOC_GROW

Remove unused xrealloc() and ALLOC_GROW() from libperf. Signed-off-by: Masami Hiramatsu --- tools/perf/util/Build |1 - tools/perf/util/cache.h | 19 --- tools/perf/util/util.h|6 -- tools/perf/util/wrapper.c | 29

[PATCH perf/core v3 4/8] perf: Make alias handler to check return value of strbuf

Make alias handler and sq_quote_argv to check the return value of strbuf APIs. In sq_quote_argv() calls die(), but this fix handles strbuf failure as a special case and returns to caller, since the caller - handle_alias() also has to check the return value of other strbuf APIs and those checks can

[PATCH perf/core v3 5/8] perf header: Make topology checkers to check return value of strbuf

Make topology checkers to check the return value of strbuf APIs so that it can detect errors in it. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Avoid using STRBUF_INIT and return error directly before initalizing strbuf. --- tools/perf/util/header.c | 31

[PATCH perf/core v3 8/8] perf tools: Remove xrealloc and ALLOC_GROW

Remove unused xrealloc() and ALLOC_GROW() from libperf. Signed-off-by: Masami Hiramatsu --- tools/perf/util/Build |1 - tools/perf/util/cache.h | 19 --- tools/perf/util/util.h|6 -- tools/perf/util/wrapper.c | 29 - 4 files

[PATCH perf/core v3 4/8] perf: Make alias handler to check return value of strbuf

Make alias handler and sq_quote_argv to check the return value of strbuf APIs. In sq_quote_argv() calls die(), but this fix handles strbuf failure as a special case and returns to caller, since the caller - handle_alias() also has to check the return value of other strbuf APIs and those checks can

[PATCH perf/core v3 1/8] perf: Rewrite strbuf not to die

Rewrite strbuf implementation not to use die() nor xrealloc(). Instead of die, now most of the API returns error code or 0 if succeeded. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Use realloc instead of malloc/memcpy/free (Thanks Arnaldo!) ---

[PATCH perf/core v3 0/8] perf tools: Update strbuf to remove xrealloc

Hi Arnaldo, Here is the 3rd version of the strbuf update. I've fixed it according to your suggestion :) - [1/8] Use realloc instead of malloc/memcpy/free (Thanks Arnaldo!) - [2/8] Cleanup code path according to Arnaldo's review. - [5/8] Avoid using STRBUF_INIT and return error directly

[PATCH perf/core v3 2/8] perf probe: Check the return value of strbuf APIs

Check the return value of strbuf APIs in perf-probe related code, so that it can handle errors in strbuf. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Cleanup code path according to Arnaldo's review. Changes in V2: - Rebased on the latest perf/core. ---

[PATCH perf/core v3 1/8] perf: Rewrite strbuf not to die

Rewrite strbuf implementation not to use die() nor xrealloc(). Instead of die, now most of the API returns error code or 0 if succeeded. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Use realloc instead of malloc/memcpy/free (Thanks Arnaldo!) --- tools/perf/util/strbuf.c | 93

[PATCH perf/core v3 0/8] perf tools: Update strbuf to remove xrealloc

Hi Arnaldo, Here is the 3rd version of the strbuf update. I've fixed it according to your suggestion :) - [1/8] Use realloc instead of malloc/memcpy/free (Thanks Arnaldo!) - [2/8] Cleanup code path according to Arnaldo's review. - [5/8] Avoid using STRBUF_INIT and return error directly

[PATCH perf/core v3 2/8] perf probe: Check the return value of strbuf APIs

Check the return value of strbuf APIs in perf-probe related code, so that it can handle errors in strbuf. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Cleanup code path according to Arnaldo's review. Changes in V2: - Rebased on the latest perf/core. ---

Re: [PATCH v2 4/5] ARM: dts: omap5: describe control for ckobuffer

Hi, > Am 09.05.2016 um 13:52 schrieb Tero Kristo : > > On 09/05/16 14:18, H. Nikolaus Schaller wrote: >> Hi, >> >>> Am 28.04.2016 um 15:23 schrieb Tero Kristo : >>> >>> On 28/04/16 12:12, H. Nikolaus Schaller wrote: Hi Tero, > Am 28.04.2016 um

Re: [PATCH v2 4/5] ARM: dts: omap5: describe control for ckobuffer

Hi, > Am 09.05.2016 um 13:52 schrieb Tero Kristo : > > On 09/05/16 14:18, H. Nikolaus Schaller wrote: >> Hi, >> >>> Am 28.04.2016 um 15:23 schrieb Tero Kristo : >>> >>> On 28/04/16 12:12, H. Nikolaus Schaller wrote: Hi Tero, > Am 28.04.2016 um 10:03 schrieb Tero Kristo : >

[PATCH v2] iommu/amd: Set AMD iommu callbacks for platform bus driver

From: Wan Zongshun AMD has more drivers will use ACPI to platform bus driver later, all those devices need iommu support, for example: eMMC driver. For latest AMD eMMC controller, it will utilize sdhci-acpi.c driver, which will rely on platform bus to match device and

[PATCH v2] iommu/amd: Set AMD iommu callbacks for platform bus driver

From: Wan Zongshun AMD has more drivers will use ACPI to platform bus driver later, all those devices need iommu support, for example: eMMC driver. For latest AMD eMMC controller, it will utilize sdhci-acpi.c driver, which will rely on platform bus to match device and driver, where we will set

[PATCH] [media] m88rs2000: initialize status to zero

From: Colin Ian King status is not initialized so it can contain garbage. The check for status containing the FE_HAS_LOCK bit may randomly pass or fail if the read of register 0x8c fails to set status after 25 read attempts. Fix this by initializing status to 0. Issue

[PATCH] [media] m88rs2000: initialize status to zero

From: Colin Ian King status is not initialized so it can contain garbage. The check for status containing the FE_HAS_LOCK bit may randomly pass or fail if the read of register 0x8c fails to set status after 25 read attempts. Fix this by initializing status to 0. Issue found with CoverityScan,

RE: bnx2x in 4.6rc7 with FW 7.13.1.0 not present

> Upgrading a system from kernel 4.2 to 4.6rc7, there is an extra 2 minute delay > while booting due to these problems: > > [ 47.977221] bnx2x :04:00.1: Direct firmware load for > bnx2x/bnx2x-e2- > 7.13.1.0.fw failed with error -2 ... > Could the driver fall back to an older firmware

RE: bnx2x in 4.6rc7 with FW 7.13.1.0 not present

> Upgrading a system from kernel 4.2 to 4.6rc7, there is an extra 2 minute delay > while booting due to these problems: > > [ 47.977221] bnx2x :04:00.1: Direct firmware load for > bnx2x/bnx2x-e2- > 7.13.1.0.fw failed with error -2 ... > Could the driver fall back to an older firmware

Re: [PATCH v2 22/22] ARM: dts: exynos: Add initial support for Odroid XU board

On 05/10/2016 12:02 AM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:06 PM, Krzysztof Kozlowski wrote: >> The Hardkernel's Odroid XU board was first design with big.LITTLE SoC >> from Samsung: the Exynos5410. Comparing now to more popular Odroid XU3 >> the differences

Re: [PATCH v2 22/22] ARM: dts: exynos: Add initial support for Odroid XU board

On 05/10/2016 12:02 AM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:06 PM, Krzysztof Kozlowski wrote: >> The Hardkernel's Odroid XU board was first design with big.LITTLE SoC >> from Samsung: the Exynos5410. Comparing now to more popular Odroid XU3 >> the differences

[PATCH] sched/cputime: add steal time support to full dynticks CPU time accounting

From: Wanpeng Li This patch adds steal guest time support to full dynticks CPU time accounting. After commit ff9a9b4c(sched, time: Switch VIRT_CPU_ACCOUNTING_GEN to jiffy granularity), time is jiffy based sampling even if it's still listened to ring boundaries, so

[PATCH] sched/cputime: add steal time support to full dynticks CPU time accounting

From: Wanpeng Li This patch adds steal guest time support to full dynticks CPU time accounting. After commit ff9a9b4c(sched, time: Switch VIRT_CPU_ACCOUNTING_GEN to jiffy granularity), time is jiffy based sampling even if it's still listened to ring boundaries, so steal_account_process_tick()

Re: [PATCH v2 20/22] ARM: dts: exynos: Move common Exynos5410/542x/5800 nodes to new DTSI

On 05/09/2016 11:53 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:06 PM, Krzysztof Kozlowski wrote: >> The Exynos5410/542x/5800 are very similar designs. Create new new > > s/new new/a new > >> DTSI with common nodes to remove DTS duplication. Although currently >>

Re: [PATCH v2 20/22] ARM: dts: exynos: Move common Exynos5410/542x/5800 nodes to new DTSI

On 05/09/2016 11:53 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:06 PM, Krzysztof Kozlowski wrote: >> The Exynos5410/542x/5800 are very similar designs. Create new new > > s/new new/a new > >> DTSI with common nodes to remove DTS duplication. Although currently >>

Re: [PATCHv5 0/8] 2c: Relax mandatory I2C ID table passing

Hello Kieran, On 05/04/2016 11:14 AM, Kieran Bingham wrote: > This patch set finally pops up again, after a long time stuck somewhere in the > midst of my stack. > > As it stood last year, the requirements were to rename probe2 to probe_new, > and > ensure that it was correctly tested. The

Re: [PATCHv5 0/8] 2c: Relax mandatory I2C ID table passing

Hello Kieran, On 05/04/2016 11:14 AM, Kieran Bingham wrote: > This patch set finally pops up again, after a long time stuck somewhere in the > midst of my stack. > > As it stood last year, the requirements were to rename probe2 to probe_new, > and > ensure that it was correctly tested. The

Re: [PATCH v2 13/22] ARM: dts: exynos: Move common nodes to exynos5.dtsi

On 05/09/2016 11:25 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote: >> Exynos5420 and Exynos5250 share some nodes: the PWM and syscon >> (sysreg_system_controller). Move them to parent DTSI to avoid >> duplication. >> >> Signed-off-by:

Re: [PATCH v2 13/22] ARM: dts: exynos: Move common nodes to exynos5.dtsi

On 05/09/2016 11:25 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote: >> Exynos5420 and Exynos5250 share some nodes: the PWM and syscon >> (sysreg_system_controller). Move them to parent DTSI to avoid >> duplication. >> >> Signed-off-by:

[PATCH] mfd: core: check existence of enable/disable callbacks

Child devices may not know if their MFD cells have enable/disable callbacks. Signed-off-by: Masahiro Yamada --- drivers/mfd/mfd-core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c index

[PATCH] mfd: core: check existence of enable/disable callbacks

Child devices may not know if their MFD cells have enable/disable callbacks. Signed-off-by: Masahiro Yamada --- drivers/mfd/mfd-core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c index 88bd1b1..95dbf3a 100644 ---

Re: [PATCH v2 06/22] ARM: dts: exynos: Remove old fixed-clock provider on SMDK5410

On 05/09/2016 10:24 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote: >> All "fin_pll" clock users are switched to the new one, provided by > > s/are switched/were switched Thanks for spotting this, Krzysztof

Re: [PATCH v2 06/22] ARM: dts: exynos: Remove old fixed-clock provider on SMDK5410

On 05/09/2016 10:24 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote: >> All "fin_pll" clock users are switched to the new one, provided by > > s/are switched/were switched Thanks for spotting this, Krzysztof

Re: [PATCH v2 04/22] clk: samsung: exynos5410: Provide fin_pll external fixed clock

On 05/09/2016 10:19 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote: >> Just like clock driver for Exynos542x/5800, provide the fixed clock here >> so the clock bindings and their consumers would be consistent and >> similar. >> >>

Re: [PATCH v2 04/22] clk: samsung: exynos5410: Provide fin_pll external fixed clock

On 05/09/2016 10:19 PM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote: >> Just like clock driver for Exynos542x/5800, provide the fixed clock here >> so the clock bindings and their consumers would be consistent and >> similar. >> >>

Re: [PATCHv5 8/8] mfd: as3722: Rid driver of superfluous I2C device ID structure

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > Also remove unused second probe() parameter 'i2c_device_id'. > > Acked-by: Grant Likely > Signed-off-by: Lee Jones > Signed-off-by: Kieran Bingham

Re: [PATCHv5 8/8] mfd: as3722: Rid driver of superfluous I2C device ID structure

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > Also remove unused second probe() parameter 'i2c_device_id'. > > Acked-by: Grant Likely > Signed-off-by: Lee Jones > Signed-off-by: Kieran Bingham > > --- > Changes since v4 > - Rename .probe2 to probe_new > --- >

Re: [PATCH v2 00/22] ARM: dts: exynos: Add initial support for Odroid XU

On 05/10/2016 12:05 AM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote: >> >> Hi, >> >> Patchset adds necessary clocks, reorganizes existing stuff and finally >> adds Odroid XU support. >> > > Do you have a branch available so I can pull

Re: [PATCH v2 00/22] ARM: dts: exynos: Add initial support for Odroid XU

On 05/10/2016 12:05 AM, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 05/08/2016 03:05 PM, Krzysztof Kozlowski wrote: >> >> Hi, >> >> Patchset adds necessary clocks, reorganizes existing stuff and finally >> adds Odroid XU support. >> > > Do you have a branch available so I can pull

[PATCH V3 0/4] net-next: mediatek: improve phy support

The current driver did not handle the RGMII delay modes and asymmetric flow control properly. The mii_bus is not freed properly. Also add support for fixed-phy allowing the driver to work on SoCs that have an internal gigabit switch. John Crispin (4): net-next: mediatek: use mdiobus_free() in

[PATCH V3 0/4] net-next: mediatek: improve phy support

The current driver did not handle the RGMII delay modes and asymmetric flow control properly. The mii_bus is not freed properly. Also add support for fixed-phy allowing the driver to work on SoCs that have an internal gigabit switch. John Crispin (4): net-next: mediatek: use mdiobus_free() in

[PATCH V3 2/4] net-next: mediatek: fix gigabit and flow control advertisement

The current code will not setup the PHYs advertisement features correctly. Fix this and properly advertise Gigabit features and properly handle asymmetric pause frames. Signed-off-by: John Crispin --- drivers/net/ethernet/mediatek/mtk_eth_soc.c | 16 ++-- 1 file

[PATCH V3 2/4] net-next: mediatek: fix gigabit and flow control advertisement

The current code will not setup the PHYs advertisement features correctly. Fix this and properly advertise Gigabit features and properly handle asymmetric pause frames. Signed-off-by: John Crispin --- drivers/net/ethernet/mediatek/mtk_eth_soc.c | 16 ++-- 1 file changed, 14

[PATCH V3 1/4] net-next: mediatek: use mdiobus_free() in favour of kfree()

The driver currently uses kfree() to clear the mii_bus. This is not the correct way to clear the memory and mdiobus_free() should be used instead. This patch fixes the two instances where this happens in the driver. Reviewed-by: Andrew Lunn Signed-off-by: John Crispin

[PATCH V3 1/4] net-next: mediatek: use mdiobus_free() in favour of kfree()

The driver currently uses kfree() to clear the mii_bus. This is not the correct way to clear the memory and mdiobus_free() should be used instead. This patch fixes the two instances where this happens in the driver. Reviewed-by: Andrew Lunn Signed-off-by: John Crispin ---

[PATCH V3 4/4] net-next: mediatek: properly handle RGMII modes

If an external Gigabit PHY is connected to either of the MACs we need to be able to tell the PHY to use a delay. Not doing so will result in heavy packet loss and/or data corruption when using PHYs such as the IC+ IP1001. We tell the PHY which MII delay mode to use via the devictree. The ethernet

[PATCH V3 3/4] net-next: mediatek: add fixed-phy support

The MT7623 SoC has a builtin gigabit switch. If we want to use it, GMAC1 needs to be configured using a fixed link speed and flow control settings. The easiest way to do this is to used the fixed-phy driver, allowing us to reuse the existing mdio polling code to setup the MAC. Reviewed-by: Andrew

[PATCH V3 4/4] net-next: mediatek: properly handle RGMII modes

If an external Gigabit PHY is connected to either of the MACs we need to be able to tell the PHY to use a delay. Not doing so will result in heavy packet loss and/or data corruption when using PHYs such as the IC+ IP1001. We tell the PHY which MII delay mode to use via the devictree. The ethernet

[PATCH V3 3/4] net-next: mediatek: add fixed-phy support

The MT7623 SoC has a builtin gigabit switch. If we want to use it, GMAC1 needs to be configured using a fixed link speed and flow control settings. The easiest way to do this is to used the fixed-phy driver, allowing us to reuse the existing mdio polling code to setup the MAC. Reviewed-by: Andrew

Re: [PATCHv5 7/8] mfd: 88pm860x: Move over to new I2C device .probe() call

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > As part of an effort to rid the mostly unused second parameter for I2C > related .probe() functions and to conform to other existing frameworks > we're moving over to a temporary replacement .probe()

Re: [PATCHv5 7/8] mfd: 88pm860x: Move over to new I2C device .probe() call

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > As part of an effort to rid the mostly unused second parameter for I2C > related .probe() functions and to conform to other existing frameworks > we're moving over to a temporary replacement .probe() call-back. > > Acked-by:

Re: [PATCH 1/2] cpufreq: rcar: Add support for R8A7795 SoC

On 10-05-16, 11:57, Khiem Nguyen wrote: > After the commit "a399dc9fc50 cpufreq: shmobile: Use generic platdev > driver", will use cpufreq-dt-platdev driver to enable cpufreq-dt support. > Hence, follow the implementation to support new R8A7795 SoC. > > Signed-off-by: Khiem Nguyen

Re: [PATCH 1/2] cpufreq: rcar: Add support for R8A7795 SoC

On 10-05-16, 11:57, Khiem Nguyen wrote: > After the commit "a399dc9fc50 cpufreq: shmobile: Use generic platdev > driver", will use cpufreq-dt-platdev driver to enable cpufreq-dt support. > Hence, follow the implementation to support new R8A7795 SoC. > > Signed-off-by: Khiem Nguyen > --- >

Re: [PATCH 2/2] cpufreq: rcar: Add support for R8A7796 SoC

On 10-05-16, 11:59, Khiem Nguyen wrote: > Signed-off-by: Khiem Nguyen > --- > drivers/cpufreq/cpufreq-dt-platdev.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c > b/drivers/cpufreq/cpufreq-dt-platdev.c > index

Re: [PATCH 2/2] cpufreq: rcar: Add support for R8A7796 SoC

On 10-05-16, 11:59, Khiem Nguyen wrote: > Signed-off-by: Khiem Nguyen > --- > drivers/cpufreq/cpufreq-dt-platdev.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c > b/drivers/cpufreq/cpufreq-dt-platdev.c > index 32f6dda..7d038fd 100644 > ---

Re: [PATCH] netfilter: conntrack: remove uninitialized shadow variable

From: Arnd Bergmann Date: Mon, 9 May 2016 21:47:23 +0200 > A recent commit introduced an unconditional use of an uninitialized > variable, as reported in this gcc warning: > > net/netfilter/nf_conntrack_core.c: In function '__nf_conntrack_confirm': >

Re: [PATCH] netfilter: conntrack: remove uninitialized shadow variable

From: Arnd Bergmann Date: Mon, 9 May 2016 21:47:23 +0200 > A recent commit introduced an unconditional use of an uninitialized > variable, as reported in this gcc warning: > > net/netfilter/nf_conntrack_core.c: In function '__nf_conntrack_confirm': > net/netfilter/nf_conntrack_core.c:632:33:

Re: [PATCHv5 6/8] i2c: Provide a temporary .probe_new() call-back type

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > This will aid the seamless removal of the current probe()'s, more > commonly unused than used second parameter. Most I2C drivers can > simply switch over to the new interface, others which have DT >

Re: [PATCHv5 6/8] i2c: Provide a temporary .probe_new() call-back type

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > This will aid the seamless removal of the current probe()'s, more > commonly unused than used second parameter. Most I2C drivers can > simply switch over to the new interface, others which have DT > support can use its own

Re: [PATCHv5 5/8] i2c: Export i2c_match_id() for direct use by device drivers

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > When there was no other way to match a I2C device to driver i2c_match_id() > was exclusively used. However, now there are other types of tables which > are commonly supplied, matching on an i2c_device_id

Re: [PATCHv5 5/8] i2c: Export i2c_match_id() for direct use by device drivers

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > When there was no other way to match a I2C device to driver i2c_match_id() > was exclusively used. However, now there are other types of tables which > are commonly supplied, matching on an i2c_device_id table is used less >

Re: pull-request: wireless-drivers 2016-05-09

From: Kalle Valo Date: Mon, 09 May 2016 22:06:42 +0300 > one more iwlwifi fix we would like to get to 4.6 if possible. Please let > me know if there are any problems. Pulled, thanks Kalle.

Re: pull-request: wireless-drivers 2016-05-09

From: Kalle Valo Date: Mon, 09 May 2016 22:06:42 +0300 > one more iwlwifi fix we would like to get to 4.6 if possible. Please let > me know if there are any problems. Pulled, thanks Kalle.

Re: [PATCHv5 4/8] i2c: Make I2C ID tables non-mandatory for DT'ed devices

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > Currently the I2C framework insists on devices supplying an I2C ID > table. Many of the devices which do so unnecessarily adding quite a > few wasted lines to kernel code. This patch allows drivers a

Re: [PATCHv5 4/8] i2c: Make I2C ID tables non-mandatory for DT'ed devices

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > Currently the I2C framework insists on devices supplying an I2C ID > table. Many of the devices which do so unnecessarily adding quite a > few wasted lines to kernel code. This patch allows drivers a means > to 'not' supply

[PATCH 2/2] cpufreq: rcar: Add support for R8A7796 SoC

Signed-off-by: Khiem Nguyen --- drivers/cpufreq/cpufreq-dt-platdev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c index 32f6dda..7d038fd 100644 ---

[PATCH 2/2] cpufreq: rcar: Add support for R8A7796 SoC

Signed-off-by: Khiem Nguyen --- drivers/cpufreq/cpufreq-dt-platdev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c index 32f6dda..7d038fd 100644 --- a/drivers/cpufreq/cpufreq-dt-platdev.c +++

Re: [PATCHv5 3/8] i2c: Match using traditional OF methods, then by vendor-less compatible strings

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > This function provides a single call for all I2C devices which need to > match firstly using traditional OF means i.e by of_node, then if that > fails we attempt to match using the supplied I2C client name

Re: [PATCHv5 3/8] i2c: Match using traditional OF methods, then by vendor-less compatible strings

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > This function provides a single call for all I2C devices which need to > match firstly using traditional OF means i.e by of_node, then if that > fails we attempt to match using the supplied I2C client name with a > list of

[PATCH 1/2] cpufreq: rcar: Add support for R8A7795 SoC

After the commit "a399dc9fc50 cpufreq: shmobile: Use generic platdev driver", will use cpufreq-dt-platdev driver to enable cpufreq-dt support. Hence, follow the implementation to support new R8A7795 SoC. Signed-off-by: Khiem Nguyen ---

[PATCH 1/2] cpufreq: rcar: Add support for R8A7795 SoC

After the commit "a399dc9fc50 cpufreq: shmobile: Use generic platdev driver", will use cpufreq-dt-platdev driver to enable cpufreq-dt support. Hence, follow the implementation to support new R8A7795 SoC. Signed-off-by: Khiem Nguyen --- drivers/cpufreq/cpufreq-dt-platdev.c | 1 + 1 file

Re: [PATCHv5 2/8] i2c: Add the ability to match device to compatible string without an of_node

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > A great deal of I2C devices are currently matched via DT node name, and > as such the compatible naming convention of ',' has gone > somewhat awry - some nodes don't supply one, some supply an arbitrary >

Re: [PATCHv5 2/8] i2c: Add the ability to match device to compatible string without an of_node

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > A great deal of I2C devices are currently matched via DT node name, and > as such the compatible naming convention of ',' has gone > somewhat awry - some nodes don't supply one, some supply an arbitrary > string and others the

[PATCH 0/2] cpufreq: rcar: Enable CPUFreq support

This series enables CPUFreq support in available R-Car Gen3 SoC. It depends on 2 series below: [PATCH 0/4] clk: renesas: cpg-mssr: Add support for R-Car M3-W [RFC 0/4] Add Z clock support All comments are appreciated. Khiem Nguyen (2): cpufreq: rcar: Add support for R8A7795 SoC

[PATCH 0/2] cpufreq: rcar: Enable CPUFreq support

This series enables CPUFreq support in available R-Car Gen3 SoC. It depends on 2 series below: [PATCH 0/4] clk: renesas: cpg-mssr: Add support for R-Car M3-W [RFC 0/4] Add Z clock support All comments are appreciated. Khiem Nguyen (2): cpufreq: rcar: Add support for R8A7795 SoC

Re: [PATCHv5 1/8] i2c: Add pointer dereference protection to i2c_match_id()

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > Here we're providing dereference protection for i2c_match_id(), which > saves us having to do it each time it's called. We're also stripping > out the (now) needless checks in i2c_device_match(). This

Re: [PATCHv5 1/8] i2c: Add pointer dereference protection to i2c_match_id()

On 05/04/2016 11:14 AM, Kieran Bingham wrote: > From: Lee Jones > > Here we're providing dereference protection for i2c_match_id(), which > saves us having to do it each time it's called. We're also stripping > out the (now) needless checks in i2c_device_match(). This patch paves > the way for

RE: [PATCH 0/2] mtd: atmel_nand: remove compatible "atmel,sama5d4-nfc"

> -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: 2016年5月10日 4:13 > To: Yang, Wenyou > Cc: Brian Norris ; David Woodhouse > ; Pawel Moll ; Mark Brown >

RE: [PATCH 0/2] mtd: atmel_nand: remove compatible "atmel,sama5d4-nfc"

> -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: 2016年5月10日 4:13 > To: Yang, Wenyou > Cc: Brian Norris ; David Woodhouse > ; Pawel Moll ; Mark Brown > ; Ian Campbell ; Kumar > Gala ; linux-kernel@vger.kernel.org; linux- > m...@lists.infradead.org;

Re: [PATCH v21 00/22] Richacls

On Tue, May 10, 2016 at 12:02:33AM +0200, Andreas Gruenbacher wrote: > What more can I do to finally get this merged? While I am not the one to comment on kernel specifics, from a pure Samba user space perspective let me say: We need this. NOW. Volker

Re: [PATCH v21 00/22] Richacls

On Tue, May 10, 2016 at 12:02:33AM +0200, Andreas Gruenbacher wrote: > What more can I do to finally get this merged? While I am not the one to comment on kernel specifics, from a pure Samba user space perspective let me say: We need this. NOW. Volker

[PATCH v2 1/3] Documentation: mfd: LP873X: Add information for the mfd and regulator drivers

Add information for the mfd and regulator drivers. Signed-off-by: Keerthy --- Documentation/devicetree/bindings/mfd/lp873x.txt | 55 1 file changed, 55 insertions(+) create mode 100644 Documentation/devicetree/bindings/mfd/lp873x.txt diff --git

[PATCH v2 1/3] Documentation: mfd: LP873X: Add information for the mfd and regulator drivers

Add information for the mfd and regulator drivers. Signed-off-by: Keerthy --- Documentation/devicetree/bindings/mfd/lp873x.txt | 55 1 file changed, 55 insertions(+) create mode 100644 Documentation/devicetree/bindings/mfd/lp873x.txt diff --git

[PATCH v2 3/3] regulator: lp873x: Add support for lp873x PMIC regulators

The regulators set consists of 2 BUCKs and 2 LDOs. The output voltages are configurable and are meant to supply power to the main processor and other components. The ramp delay is configurable for both BUCKs. Signed-off-by: Keerthy --- Changes in v2: * Removed all

[PATCH v2 0/3] mfd: lp873x: Add lp873x PMIC support

The LP873X chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following components: - Regulators. - Configurable General Purpose Output Signals(GPO). PMIC interacts with the main processor through i2c. PMIC has couple of

[PATCH v2 2/3] mfd: lp873x: Add lp873x PMIC support

The LP873X chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following components: - Regulators. - Configurable General Purpose Output Signals(GPO). PMIC interacts with the main processor through i2c. PMIC has couple of

[PATCH v2 3/3] regulator: lp873x: Add support for lp873x PMIC regulators

The regulators set consists of 2 BUCKs and 2 LDOs. The output voltages are configurable and are meant to supply power to the main processor and other components. The ramp delay is configurable for both BUCKs. Signed-off-by: Keerthy --- Changes in v2: * Removed all compatibles and introduced

[PATCH v2 0/3] mfd: lp873x: Add lp873x PMIC support

The LP873X chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following components: - Regulators. - Configurable General Purpose Output Signals(GPO). PMIC interacts with the main processor through i2c. PMIC has couple of

[PATCH v2 2/3] mfd: lp873x: Add lp873x PMIC support

The LP873X chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following components: - Regulators. - Configurable General Purpose Output Signals(GPO). PMIC interacts with the main processor through i2c. PMIC has couple of

  1   2   3   4   5   6   7   8   9   10   >