Re: scripts/basic/bin2c: Complete error handling in main()

On 2016-11-03 20:48, SF Markus Elfring wrote: >> You could define an xprintf() macro that checks if the return value >> is < 0 and simply calls perror() and exit(1) in such case. > > Does such a macro belong to any general header file from the Linux > software library? No. Michal

Re: scripts/basic/bin2c: Complete error handling in main()

On 2016-11-03 20:48, SF Markus Elfring wrote: >> You could define an xprintf() macro that checks if the return value >> is < 0 and simply calls perror() and exit(1) in such case. > > Does such a macro belong to any general header file from the Linux > software library? No. Michal

Re: [PATCH 00/14] pinctrl-sx150x: Various bug-fixes and code simplifications

On Thu, Nov 3, 2016 at 11:22 PM, Andrey Smirnov wrote: >>> This is good, you went faster than me ! >>> >>> Small point, could you add Kconfig dependency on REGMAP ? > > Good catch! Will fix in v2 of the set. OK I wait for a v2 with the ACK/test tags then I'll apply

Re: [PATCH 00/14] pinctrl-sx150x: Various bug-fixes and code simplifications

On Thu, Nov 3, 2016 at 11:22 PM, Andrey Smirnov wrote: >>> This is good, you went faster than me ! >>> >>> Small point, could you add Kconfig dependency on REGMAP ? > > Good catch! Will fix in v2 of the set. OK I wait for a v2 with the ACK/test tags then I'll apply that. Yours, Linus Walleij

[RFC] ARCv2: MCIP: Deprecate setting of affinity in Device Tree

Ignore value of interrupt distribution mode for common interrupts in IDU since setting an affinity using value from Device Tree is deprecated in ARC. Originially it is done in idu_irq_xlate function and it is semantically wrong and does not guaranty that an affinity value will be set properly.

[RFC] ARCv2: MCIP: Deprecate setting of affinity in Device Tree

Ignore value of interrupt distribution mode for common interrupts in IDU since setting an affinity using value from Device Tree is deprecated in ARC. Originially it is done in idu_irq_xlate function and it is semantically wrong and does not guaranty that an affinity value will be set properly.

Re: [PATCH net] r8152: Fix broken RX checksums.

On 16-11-02 02:29 PM, Mark Lord wrote: I have poked at it some more, and thus far it appears that it is only necessary to disable TCP rx checksums. The system doesn't crash when only IP/UDP checksums are enabled, but does when TCP checksums are on. This happens regardless of whether RX_AGG is

Re: [PATCH net] r8152: Fix broken RX checksums.

On 16-11-02 02:29 PM, Mark Lord wrote: I have poked at it some more, and thus far it appears that it is only necessary to disable TCP rx checksums. The system doesn't crash when only IP/UDP checksums are enabled, but does when TCP checksums are on. This happens regardless of whether RX_AGG is

[PATCH] Revert "console: don't prefer first registered if DT specifies stdout-path"

This reverts commit 05fd007e4629 ("console: don't prefer first registered if DT specifies stdout-path"). The reverted commit changes existing behavior on which many ARM boards rely. Many ARM small-board-computers, like e.g. the Raspberry Pi have both a video output and a serial console. Depending

[REGRESSION] "console: don't prefer first registered if DT specifies stdout-path" breaks console on video outputs of various ARM boards

Hi All, While booting 4.9-rc# for the first time on an Allwinner A33 tablet, I noticed that after u-boot the LCD display stayed black. It turns out that there was an issue which caused X to never get up, and all kernel (and other startup) messages prior to that only went to ttyS0 which consists

[PATCH] Revert "console: don't prefer first registered if DT specifies stdout-path"

This reverts commit 05fd007e4629 ("console: don't prefer first registered if DT specifies stdout-path"). The reverted commit changes existing behavior on which many ARM boards rely. Many ARM small-board-computers, like e.g. the Raspberry Pi have both a video output and a serial console. Depending

[REGRESSION] "console: don't prefer first registered if DT specifies stdout-path" breaks console on video outputs of various ARM boards

Hi All, While booting 4.9-rc# for the first time on an Allwinner A33 tablet, I noticed that after u-boot the LCD display stayed black. It turns out that there was an issue which caused X to never get up, and all kernel (and other startup) messages prior to that only went to ttyS0 which consists

Re: [PATCH 3/3] tpm: move documentation under Documentation/security

On Fri, 04 Nov 2016, Jarkko Sakkinen wrote: > In order too make Documentation root directory cleaner move the tpm > directory under Documentation/security. FWIW I like this. BR, Jani. > > Signed-off-by: Jarkko Sakkinen > --- >

Re: [PATCH 3/3] tpm: move documentation under Documentation/security

On Fri, 04 Nov 2016, Jarkko Sakkinen wrote: > In order too make Documentation root directory cleaner move the tpm > directory under Documentation/security. FWIW I like this. BR, Jani. > > Signed-off-by: Jarkko Sakkinen > --- > Documentation/index.rst | 2 +- >

Re: [PATCH] leds: Add mutex protection in brightness_show()

Hi, On 04-11-16 08:52, Jacek Anaszewski wrote: Initially the claim about no need for lock in brightness_show() was valid as the function was just returning unchanged LED brightness. After the addition of led_update_brightness() this is no longer true, as the function can change the brightness

Re: [PATCH] leds: Add mutex protection in brightness_show()

Hi, On 04-11-16 08:52, Jacek Anaszewski wrote: Initially the claim about no need for lock in brightness_show() was valid as the function was just returning unchanged LED brightness. After the addition of led_update_brightness() this is no longer true, as the function can change the brightness

[PATCH 0/3] ARM: cache-uniphier: slight cleanups and trivial coding style fix

The cache-uniphier is a full-custom outer-cache for Socionext UniPhier SoC family. This series includes SoC-specific cleanups and a trivial coding style fix suggested by Documentation/CodingStyle. Masahiro Yamada (3): ARM: cache-uniphier: call kzalloc() after DT property parsing ARM:

[PATCH 2/3] ARM: cache-uniphier: refactor jump label to follow coding style guideline

Documentation/CodingStyle recommends to use label names which say what the goto does or why the goto exists. Just in case, split it up into three labels because the CodingStyle says "one err bugs" is a common type of bug (although, I do not believe the current code includes such a bug). During

[PATCH 0/3] ARM: cache-uniphier: slight cleanups and trivial coding style fix

The cache-uniphier is a full-custom outer-cache for Socionext UniPhier SoC family. This series includes SoC-specific cleanups and a trivial coding style fix suggested by Documentation/CodingStyle. Masahiro Yamada (3): ARM: cache-uniphier: call kzalloc() after DT property parsing ARM:

[PATCH 2/3] ARM: cache-uniphier: refactor jump label to follow coding style guideline

Documentation/CodingStyle recommends to use label names which say what the goto does or why the goto exists. Just in case, split it up into three labels because the CodingStyle says "one err bugs" is a common type of bug (although, I do not believe the current code includes such a bug). During

[PATCH 3/3] ARM: cache-uniphier: clean up active way setup code

Now, the active way setup function is called with a fixed value zero for the second argument only when enabling the outer-cache. The code can be simpler. Signed-off-by: Masahiro Yamada --- arch/arm/mm/cache-uniphier.c | 20 +++- 1 file changed, 7

[PATCH 3/3] ARM: cache-uniphier: clean up active way setup code

Now, the active way setup function is called with a fixed value zero for the second argument only when enabling the outer-cache. The code can be simpler. Signed-off-by: Masahiro Yamada --- arch/arm/mm/cache-uniphier.c | 20 +++- 1 file changed, 7 insertions(+), 13 deletions(-)

[PATCH 1/3] ARM: cache-uniphier: call kzalloc() after DT property parsing

Allocate memory after DT property parsing that has more possibility of failure. This will decrease the number of bail-out points for kfree(). Signed-off-by: Masahiro Yamada --- arch/arm/mm/cache-uniphier.c | 34 -- 1 file changed,

[PATCH 1/3] ARM: cache-uniphier: call kzalloc() after DT property parsing

Allocate memory after DT property parsing that has more possibility of failure. This will decrease the number of bail-out points for kfree(). Signed-off-by: Masahiro Yamada --- arch/arm/mm/cache-uniphier.c | 34 -- 1 file changed, 16 insertions(+), 18

[PATCH net-next v3] cadence: Add LSO support.

New Cadence GEM hardware support Large Segment Offload (LSO): TCP segmentation offload (TSO) as well as UDP fragmentation offload (UFO). Support for those features was added to the driver. Signed-off-by: Rafal Ozieblo --- Changed in v2: macb_lso_check_compatibility() changed

[PATCH net-next v3] cadence: Add LSO support.

New Cadence GEM hardware support Large Segment Offload (LSO): TCP segmentation offload (TSO) as well as UDP fragmentation offload (UFO). Support for those features was added to the driver. Signed-off-by: Rafal Ozieblo --- Changed in v2: macb_lso_check_compatibility() changed to

Re: [PATCH 2/2] kbuild: add -fno-PIE

On 2016-11-03 21:08, Al Viro wrote: On Thu, Nov 03, 2016 at 04:50:55PM -0600, Ben Hutchings wrote: On Wed, 2016-11-02 at 18:20 +0100, Sebastian Andrzej Siewior wrote: Debian started to build the gcc with -fPIE by default so the kernel build ends before it starts properly with:

Re: [PATCH 2/2] kbuild: add -fno-PIE

On 2016-11-03 21:08, Al Viro wrote: On Thu, Nov 03, 2016 at 04:50:55PM -0600, Ben Hutchings wrote: On Wed, 2016-11-02 at 18:20 +0100, Sebastian Andrzej Siewior wrote: Debian started to build the gcc with -fPIE by default so the kernel build ends before it starts properly with:

[RFC v2 8/8] iommu/arm-smmu: implement add_reserved_regions callback

The function populates the list of reserved regions with the PCI host bridge windows and the MSI IOVA range. At the moment an arbitray MSI IOVA window is set at 0x800 of size 1MB. Signed-off-by: Eric Auger --- RFC v1 -> v2: use defines for MSI IOVA base and length

[RFC v2 8/8] iommu/arm-smmu: implement add_reserved_regions callback

The function populates the list of reserved regions with the PCI host bridge windows and the MSI IOVA range. At the moment an arbitray MSI IOVA window is set at 0x800 of size 1MB. Signed-off-by: Eric Auger --- RFC v1 -> v2: use defines for MSI IOVA base and length ---

[RFC v2 3/8] iommu/dma: Allow MSI-only cookies

From: Robin Murphy IOMMU domain users such as VFIO face a similar problem to DMA API ops with regard to mapping MSI messages in systems where the MSI write is subject to IOMMU translation. With the relevant infrastructure now in place for managed DMA domains, it's actually

[RFC v2 6/8] iommu: Handle the list of reserved regions

A new callback is introduced, add_reserved_regions. This function aims at populating the iommu domain reserved region list with regions associated with the device. The function is called on device attachment. The list is freed on iommu_domain_free(). Signed-off-by: Eric Auger

[RFC v2 5/8] vfio/type1: Introduce RESV_IOVA_RANGE capability

This patch allows the user-space to retrieve the reserved IOVA range(s), if any. The implementation is based on capability chains, now also added to VFIO_IOMMU_GET_INFO. Signed-off-by: Eric Auger --- RFC v1 -> v2: - add resv_mutex lock/unlock ---

[RFC v2 7/8] iommu/vt-d: Implement add_reserved_regions callback

Implement the add_reserved_regions callback by registering the [FEE0_h - FEF0_000h] 1MB range as a reserved region (MSI address space). Signed-off-by: Eric Auger --- RFC v1 -> RFC v2: - fix intel_iommu_add_reserved_regions name - use IOAPIC_RANGE_START and

[RFC v2 3/8] iommu/dma: Allow MSI-only cookies

From: Robin Murphy IOMMU domain users such as VFIO face a similar problem to DMA API ops with regard to mapping MSI messages in systems where the MSI write is subject to IOMMU translation. With the relevant infrastructure now in place for managed DMA domains, it's actually really simple for

[RFC v2 6/8] iommu: Handle the list of reserved regions

A new callback is introduced, add_reserved_regions. This function aims at populating the iommu domain reserved region list with regions associated with the device. The function is called on device attachment. The list is freed on iommu_domain_free(). Signed-off-by: Eric Auger ---

[RFC v2 5/8] vfio/type1: Introduce RESV_IOVA_RANGE capability

This patch allows the user-space to retrieve the reserved IOVA range(s), if any. The implementation is based on capability chains, now also added to VFIO_IOMMU_GET_INFO. Signed-off-by: Eric Auger --- RFC v1 -> v2: - add resv_mutex lock/unlock --- drivers/vfio/vfio_iommu_type1.c | 70

[RFC v2 7/8] iommu/vt-d: Implement add_reserved_regions callback

Implement the add_reserved_regions callback by registering the [FEE0_h - FEF0_000h] 1MB range as a reserved region (MSI address space). Signed-off-by: Eric Auger --- RFC v1 -> RFC v2: - fix intel_iommu_add_reserved_regions name - use IOAPIC_RANGE_START and IOAPIC_RANGE_END defines - return

[RFC v2 4/8] iommu: Add a list of iommu_reserved_region in iommu_domain

Introduce a new iommu_reserved_region struct. This embodies an IOVA reserved region that cannot be used along with the IOMMU API. The list is protected by a dedicated mutex. An iommu domain now owns a list of those. Signed-off-by: Eric Auger --- ---

[RFC v2 4/8] iommu: Add a list of iommu_reserved_region in iommu_domain

Introduce a new iommu_reserved_region struct. This embodies an IOVA reserved region that cannot be used along with the IOMMU API. The list is protected by a dedicated mutex. An iommu domain now owns a list of those. Signed-off-by: Eric Auger --- --- drivers/iommu/iommu.c | 2 ++

[RFC v2 1/8] vfio: fix vfio_info_cap_add/shift

Capability header next field is an offset relative to the start of the INFO buffer. tmp->next is assigned the proper value but iterations implemented in vfio_info_cap_add and vfio_info_cap_shift use next as an offset between the headers. When coping with multiple capabilities this leads to an

[RFC v2 1/8] vfio: fix vfio_info_cap_add/shift

Capability header next field is an offset relative to the start of the INFO buffer. tmp->next is assigned the proper value but iterations implemented in vfio_info_cap_add and vfio_info_cap_shift use next as an offset between the headers. When coping with multiple capabilities this leads to an

[RFC v2 0/8] KVM PCIe/MSI passthrough on ARM/ARM64 - Alt II

Following Will & Robin's suggestions, this series attempts to propose an alternative to [1] where the host would arbitrarily decide the location of the IOVA MSI window and would be able to report to the userspace the list of reserved IOVA regions that cannot be used along with VFIO_IOMMU_MAP_DMA.

[RFC v2 0/8] KVM PCIe/MSI passthrough on ARM/ARM64 - Alt II

Following Will & Robin's suggestions, this series attempts to propose an alternative to [1] where the host would arbitrarily decide the location of the IOVA MSI window and would be able to report to the userspace the list of reserved IOVA regions that cannot be used along with VFIO_IOMMU_MAP_DMA.

[RFC v2 2/8] iommu/iova: fix __alloc_and_insert_iova_range

Fix the size check within start_pfn and limit_pfn. Signed-off-by: Eric Auger --- the issue was observed when playing with 1 page iova domain with higher iova reserved. --- drivers/iommu/iova.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[RFC v2 2/8] iommu/iova: fix __alloc_and_insert_iova_range

Fix the size check within start_pfn and limit_pfn. Signed-off-by: Eric Auger --- the issue was observed when playing with 1 page iova domain with higher iova reserved. --- drivers/iommu/iova.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iommu/iova.c

Re: [PATCH v3] EDAC: expose per-dimm error counts in sysfs

On Thu, Nov 03, 2016 at 03:01:53PM -0700, Aaron Miller wrote: > The old 'csrowX' sysfs directories had per-csrow error counters, but the > new 'dimmX' directories do not currently expose error counts. > > EDAC already keeps these counts, add them to sysfs so per-dimm counts > are still available

Re: [PATCH v3] EDAC: expose per-dimm error counts in sysfs

On Thu, Nov 03, 2016 at 03:01:53PM -0700, Aaron Miller wrote: > The old 'csrowX' sysfs directories had per-csrow error counters, but the > new 'dimmX' directories do not currently expose error counts. > > EDAC already keeps these counts, add them to sysfs so per-dimm counts > are still available

Re: [PATCH 0/10] mmc: Add support to Marvell Xenon SD Host Controller

Hi, On lun., oct. 31 2016, Gregory CLEMENT wrote: > Hello, > > This the second version of the series adding support for the SDHCI > Xenon controller. It can be currently found on the Armada 37xx and the > Armada 7K/8K but will be also used in more Marvell

Re: [PATCH 0/10] mmc: Add support to Marvell Xenon SD Host Controller

Hi, On lun., oct. 31 2016, Gregory CLEMENT wrote: > Hello, > > This the second version of the series adding support for the SDHCI > Xenon controller. It can be currently found on the Armada 37xx and the > Armada 7K/8K but will be also used in more Marvell SoC (and not only > the mvebu ones

Re: [PATCH 10/13] ARM: dts: exynos: replace to "max-frequecy" instead of "clock-freq-min-max"

Hi Jaehoon, Am Freitag, 4. November 2016, 19:21:30 CET schrieb Jaehoon Chung: > On 11/04/2016 03:41 AM, Krzysztof Kozlowski wrote: > > On Thu, Nov 03, 2016 at 03:21:32PM +0900, Jaehoon Chung wrote: > >> In drivers/mmc/core/host.c, there is "max-frequency" property. > >> It should be same

Re: [PATCH 10/13] ARM: dts: exynos: replace to "max-frequecy" instead of "clock-freq-min-max"

Hi Jaehoon, Am Freitag, 4. November 2016, 19:21:30 CET schrieb Jaehoon Chung: > On 11/04/2016 03:41 AM, Krzysztof Kozlowski wrote: > > On Thu, Nov 03, 2016 at 03:21:32PM +0900, Jaehoon Chung wrote: > >> In drivers/mmc/core/host.c, there is "max-frequency" property. > >> It should be same

Re: [PATCH 6/6] ARM: dts: rockchip: add rockchip RK1108 Evaluation board

Am Freitag, 4. November 2016, 18:54:35 CET schrieb Andy Yan: > Hi Heiko: > > On 2016年11月04日 18:03, Heiko Stuebner wrote: > > Am Donnerstag, 3. November 2016, 20:43:59 CET schrieb Andy Yan: > >> RK1108EVB is designed by Rockchip for CVR field. > >> This patch add basic support for it, which can

Re: [PATCH 6/6] ARM: dts: rockchip: add rockchip RK1108 Evaluation board

Am Freitag, 4. November 2016, 18:54:35 CET schrieb Andy Yan: > Hi Heiko: > > On 2016年11月04日 18:03, Heiko Stuebner wrote: > > Am Donnerstag, 3. November 2016, 20:43:59 CET schrieb Andy Yan: > >> RK1108EVB is designed by Rockchip for CVR field. > >> This patch add basic support for it, which can

Re: [PATCH] virtio-net: drop legacy features in virtio 1 mode

On Fri, 4 Nov 2016 12:55:36 +0200 "Michael S. Tsirkin" wrote: > Virtio 1.0 spec says VIRTIO_F_ANY_LAYOUT and VIRTIO_NET_F_GSO are > legacy-only feature bits. Do not negotiate them in virtio 1 mode. Note > this is a spec violation so we need to backport it to stable/downstream >

Re: [PATCH] virtio-net: drop legacy features in virtio 1 mode

On Fri, 4 Nov 2016 12:55:36 +0200 "Michael S. Tsirkin" wrote: > Virtio 1.0 spec says VIRTIO_F_ANY_LAYOUT and VIRTIO_NET_F_GSO are > legacy-only feature bits. Do not negotiate them in virtio 1 mode. Note > this is a spec violation so we need to backport it to stable/downstream > kernels. > >

Re: [PATCH v3 3/5] dt/bindings: Add a new property to DA8xx USB PHY

On 11/03/2016 06:50 PM, Kishon Vijay Abraham I wrote: > Hi, > > On Thursday 03 November 2016 10:56 PM, Alexandre Bailon wrote: >> On 11/03/2016 05:34 PM, Kishon Vijay Abraham I wrote: >>> Hi, >>> >>> On Thursday 03 November 2016 08:56 PM, Alexandre Bailon wrote: The USB PHY is able to

Re: [PATCH v3 3/5] dt/bindings: Add a new property to DA8xx USB PHY

On 11/03/2016 06:50 PM, Kishon Vijay Abraham I wrote: > Hi, > > On Thursday 03 November 2016 10:56 PM, Alexandre Bailon wrote: >> On 11/03/2016 05:34 PM, Kishon Vijay Abraham I wrote: >>> Hi, >>> >>> On Thursday 03 November 2016 08:56 PM, Alexandre Bailon wrote: The USB PHY is able to

Re: Coding Style: Reverse XMAS tree declarations ? (was Re: [PATCH net-next v6 02/10] dpaa_eth: add support for DPAA Ethernet)

Hi, On 04.11.2016 07:53, Joe Perches wrote: CHECK:REVERSE_XMAS_TREE: Prefer ordering declarations longest to shortest #446: FILE: drivers/net/ethernet/ethoc.c:446: + int size = bd.stat >> 16; + struct sk_buff *skb; should not this case be valid?

Re: Coding Style: Reverse XMAS tree declarations ? (was Re: [PATCH net-next v6 02/10] dpaa_eth: add support for DPAA Ethernet)

Hi, On 04.11.2016 07:53, Joe Perches wrote: CHECK:REVERSE_XMAS_TREE: Prefer ordering declarations longest to shortest #446: FILE: drivers/net/ethernet/ethoc.c:446: + int size = bd.stat >> 16; + struct sk_buff *skb; should not this case be valid?

Re: [PATCH v3] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest

Please CC me on your future submissions, thanks. On Fri, Nov 04, 2016 at 03:07:19PM +0800, He Chen wrote: > The spec can be found in Intel Software Developer Manual or in > Instruction Set Extensions Programming Reference. This commit message is completely useless. Write commit messages in the

Re: [PATCH v3] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest

Please CC me on your future submissions, thanks. On Fri, Nov 04, 2016 at 03:07:19PM +0800, He Chen wrote: > The spec can be found in Intel Software Developer Manual or in > Instruction Set Extensions Programming Reference. This commit message is completely useless. Write commit messages in the

[PATCH] virtio-net: drop legacy features in virtio 1 mode

Virtio 1.0 spec says VIRTIO_F_ANY_LAYOUT and VIRTIO_NET_F_GSO are legacy-only feature bits. Do not negotiate them in virtio 1 mode. Note this is a spec violation so we need to backport it to stable/downstream kernels. Cc: sta...@vger.kernel.org Signed-off-by: Michael S. Tsirkin

[PATCH] virtio-net: drop legacy features in virtio 1 mode

Virtio 1.0 spec says VIRTIO_F_ANY_LAYOUT and VIRTIO_NET_F_GSO are legacy-only feature bits. Do not negotiate them in virtio 1 mode. Note this is a spec violation so we need to backport it to stable/downstream kernels. Cc: sta...@vger.kernel.org Signed-off-by: Michael S. Tsirkin ---

Re: [RFC PATCH v2 0/5] ARM64: Add Internal PHY support for Meson GXL

On 10/31/2016 05:56 PM, Neil Armstrong wrote: > The Amlogic Meson GXL SoCs have an internal RMII PHY that is muxed with the > external RGMII pins. > > In order to support switching between the two PHYs links, extended registers > size for mdio-mux-mmioreg must be added. > > Finally, the internal

Re: [RFC PATCH v2 0/5] ARM64: Add Internal PHY support for Meson GXL

On 10/31/2016 05:56 PM, Neil Armstrong wrote: > The Amlogic Meson GXL SoCs have an internal RMII PHY that is muxed with the > external RGMII pins. > > In order to support switching between the two PHYs links, extended registers > size for mdio-mux-mmioreg must be added. > > Finally, the internal

Re: [PATCH 6/6] ARM: dts: rockchip: add rockchip RK1108 Evaluation board

Hi Heiko: On 2016年11月04日 18:03, Heiko Stuebner wrote: Am Donnerstag, 3. November 2016, 20:43:59 CET schrieb Andy Yan: RK1108EVB is designed by Rockchip for CVR field. This patch add basic support for it, which can boot with initramfs into shell. Signed-off-by: Andy Yan

Re: [PATCH 6/6] ARM: dts: rockchip: add rockchip RK1108 Evaluation board

Hi Heiko: On 2016年11月04日 18:03, Heiko Stuebner wrote: Am Donnerstag, 3. November 2016, 20:43:59 CET schrieb Andy Yan: RK1108EVB is designed by Rockchip for CVR field. This patch add basic support for it, which can boot with initramfs into shell. Signed-off-by: Andy Yan looks good, the only

Re: [RFC 00/17] clk: Add per-controller locks to fix deadlocks

Hi Stephen, Krzysztof has left Samsung, but we would like to continue this task, because the ABBA dead-locks related to global prepare lock becomes more and more problematic for us to workaround. On 2016-09-09 02:24, Stephen Boyd wrote: On 08/16, Krzysztof Kozlowski wrote: RFC, please, do not

Re: [RFC 00/17] clk: Add per-controller locks to fix deadlocks

Hi Stephen, Krzysztof has left Samsung, but we would like to continue this task, because the ABBA dead-locks related to global prepare lock becomes more and more problematic for us to workaround. On 2016-09-09 02:24, Stephen Boyd wrote: On 08/16, Krzysztof Kozlowski wrote: RFC, please, do not

[PATCH 2/2] i2c: uniphier-f: rename jump label to follow coding style guideline

Documentation/CodingStyle recommends to use label names which say what the goto does or why the goto exists. Signed-off-by: Masahiro Yamada --- drivers/i2c/busses/i2c-uniphier-f.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 1/2] i2c: uniphier: rename jump label to follow coding style guideline

Documentation/CodingStyle recommends to use label names which say what the goto does or why the goto exists. Signed-off-by: Masahiro Yamada --- drivers/i2c/busses/i2c-uniphier.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 2/2] i2c: uniphier-f: rename jump label to follow coding style guideline

Documentation/CodingStyle recommends to use label names which say what the goto does or why the goto exists. Signed-off-by: Masahiro Yamada --- drivers/i2c/busses/i2c-uniphier-f.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/i2c/busses/i2c-uniphier-f.c

[PATCH 1/2] i2c: uniphier: rename jump label to follow coding style guideline

Documentation/CodingStyle recommends to use label names which say what the goto does or why the goto exists. Signed-off-by: Masahiro Yamada --- drivers/i2c/busses/i2c-uniphier.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/i2c/busses/i2c-uniphier.c

[PATCH 12/22] mtd: nand: fsmc: return error code of nand_scan_ident/tail() on error

The nand_scan_ident/tail() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/fsmc_nand.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git

[PATCH 09/22] mtd: nand: plat_nand: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/plat_nand.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 09/22] mtd: nand: plat_nand: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/plat_nand.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/mtd/nand/plat_nand.c

[PATCH 12/22] mtd: nand: fsmc: return error code of nand_scan_ident/tail() on error

The nand_scan_ident/tail() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/fsmc_nand.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/mtd/nand/fsmc_nand.c

[PATCH 15/22] mtd: nand: mxc: return error code of nand_scan_ident/tail() on error

The nand_scan_ident/tail() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/mxc_nand.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff

[PATCH 15/22] mtd: nand: mxc: return error code of nand_scan_ident/tail() on error

The nand_scan_ident/tail() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/mxc_nand.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/drivers/mtd/nand/mxc_nand.c

[PATCH 01/22] mtd: nand: ams-delta: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/ams-delta.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 16/22] mtd: nand: omap2: return error code of nand_scan_ident/tail() on error

The nand_scan_ident/tail() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/omap2.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git

[PATCH 07/22] mtd: nand: orion: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/orion_nand.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 01/22] mtd: nand: ams-delta: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/ams-delta.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/mtd/nand/ams-delta.c

[PATCH 16/22] mtd: nand: omap2: return error code of nand_scan_ident/tail() on error

The nand_scan_ident/tail() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/omap2.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/mtd/nand/omap2.c

[PATCH 07/22] mtd: nand: orion: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/orion_nand.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/mtd/nand/orion_nand.c

[PATCH 10/22] mtd: nand: atmel: return error code of nand_scan_ident/tail() on error

The nand_scan_ident/tail() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/atmel_nand.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff

[PATCH 10/22] mtd: nand: atmel: return error code of nand_scan_ident/tail() on error

The nand_scan_ident/tail() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/atmel_nand.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git

[PATCH 08/22] mtd: nand: pasemi: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/pasemi_nand.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 08/22] mtd: nand: pasemi: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/pasemi_nand.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/mtd/nand/pasemi_nand.c

[PATCH 04/22] mtd: nand: gpio: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/gpio.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 04/22] mtd: nand: gpio: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/gpio.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/mtd/nand/gpio.c b/drivers/mtd/nand/gpio.c

[PATCH 02/22] mtd: nand: cmx270: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/cmx270_nand.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 02/22] mtd: nand: cmx270: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/cmx270_nand.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mtd/nand/cmx270_nand.c

[PATCH 03/22] mtd: nand: cs553x: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/cs553x_nand.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 06/22] mtd: nand: tmio: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENODEV. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/tmio_nand.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 03/22] mtd: nand: cs553x: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/cs553x_nand.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/mtd/nand/cs553x_nand.c

[PATCH 06/22] mtd: nand: tmio: return error code of nand_scan() on error

The nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENODEV. Signed-off-by: Masahiro Yamada --- drivers/mtd/nand/tmio_nand.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/mtd/nand/tmio_nand.c

[PATCH 00/22] mtd: nand: return error code of nand_scan(_ident,_tail) on error

nand_scan(), nand_scan_ident(), nand_scan_tail() return an appropriate negative value on error. Most of drivers return the value from them on error, but some of them return the fixed error code -ENXIO (and a few return -ENODEV). This series make those drivers return more precise error code.

[PATCH 22/22] mtd: nand: socrates: use nand_scan() for nand_scan_ident/tail() combo

For this driver, there is nothing between nand_scan_ident() and nand_scan_tail(). They can be merged into nand_scan(). Also, nand_scan() returns an appropriate error value when it fails. Use it instead of the fixed error code -ENXIO. Signed-off-by: Masahiro Yamada

<    3   4   5   6   7   8   9   10   >