Re: [B.A.T.M.A.N.] [RFC v2 2/6] batman-adv: Rename batman-adv.h to batadv_genl.h

2017-12-15 Thread Sven Eckelmann
On Freitag, 15. Dezember 2017 11:32:05 CET Sven Eckelmann wrote: > On Mittwoch, 6. Dezember 2017 11:58:14 CET Willem de Bruijn wrote: > [...] > > >> > --- > > >> > MAINTAINERS| 2 +- > > >> > include/uapi/linux/{batman_adv.h => batadv_genl.h} | 6 +++--- > >

Re: [PATCH 5/5] PCI: cadence: add EndPoint Controller driver for Cadence PCIe controller

2017-12-15 Thread Cyrille Pitchen
Hi Kishon, Le 15/12/2017 à 06:49, Kishon Vijay Abraham I a écrit : > Hi Cyrille, > > On Thursday 14 December 2017 10:33 PM, Cyrille Pitchen wrote: >> Le 13/12/2017 à 17:50, Cyrille Pitchen a écrit : >>> Hi Kishon, >>> >>> Le 05/12/2017 à 10:19, Kishon Vijay Abraham I a écrit : Hi,

Re: [PATCH v2 2/3] backlight: tdo24m: add the reset line gpio

2017-12-15 Thread Daniel Thompson
On Fri, Oct 13, 2017 at 09:42:48PM +0200, Robert Jarzmik wrote: > The Toppoly panels have a global reset line. Add an optional gpio > control for this line, for platforms which have the ability to drive it. > > Signed-off-by: Robert Jarzmik > --- > drivers/video/backlight/tdo24m.c | 3 +++ > 1 f

Re: [RFC PATCH 1/2] ASoC: add support of mclk clock providers in wm8894 driver

2017-12-15 Thread Charles Keepax
On Thu, Dec 14, 2017 at 05:30:25PM +, Mark Brown wrote: > On Thu, Dec 14, 2017 at 05:53:57PM +0100, Olivier Moysan wrote: > > > + pdata->mclk1 = devm_clk_get(wm8994->dev, "MCLK1"); > > + if (IS_ERR(pdata->mclk1)) > > + pdata->mclk1 = NULL; > > These should special case -EPROBE_D

Re: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest`

2017-12-15 Thread Paul Menzel
[Adding Rafael and Len as they, to my knowledge, also use or have a access to a Dell XPS 13 9360. With latest Linux master do you get TPM self-test errors, when cold starting the system without the power supply plugged in?] Dear Mario, dear Alexander, the added line breaks to the quoted part

Re: [PATCH v2 1/3] backlight: tdo24m: fix the spi cs between transfers

2017-12-15 Thread Daniel Thompson
On Thu, Dec 14, 2017 at 09:03:00PM +0100, Robert Jarzmik wrote: > Robert Jarzmik writes: > > > Currently the LCD display (TD035S) on the cm-x300 platform is broken and > > remains blank. > ... blablabla ... > > Could I know when this serie can be cherry-picked please ? Sorry. This got put on th

[PATCH 0/2] Use SPDX-License-Identifier for rockchip devicetree files

2017-12-15 Thread Klaus Goger
This patch series replaces all the license text in rockchip devicetree files text with a proper SPDX-License-Identifier. It follows the guidelines submitted[1] by Thomas Gleixner that are not yet merged. These series also fixes the issue with contradicting statements in most licenses. The introduc

[PATCH 2/2] ARM: dts: rockchip: use SPDX-License-Identifier

2017-12-15 Thread Klaus Goger
Update all 32bit rockchip devicetree files to use SPDX-License-Identifiers. All files except rk3288-veyron-analog-audio.dtsi (which is GPL 2.0 only) claim to be GPL and X11 while the actual license text is MIT. Use the MIT SPDX tag for them. Signed-off-by: Klaus Goger --- arch/arm/boot/dts/rk

Re: [PATCH V2] ACPI / LPSS: Add device link for CHT SD card dependency on I2C

2017-12-15 Thread Adrian Hunter
On 15/12/17 11:10, Adrian Hunter wrote: > On 14/12/17 16:16, Andy Shevchenko wrote: >> On Thu, 2017-12-07 at 11:03 +0200, Adrian Hunter wrote: >>> Some Cherry Trail boards have a dependency between the SDHCI host >>> controller used for SD cards and an external PMIC accessed via I2C. >>> Add a >>>

[PATCH 1/2] arm64: dts: rockchip: use SPDX-License-Identifier

2017-12-15 Thread Klaus Goger
Update all 64bit rockchip devicetree files to use SPDX-License-Identifiers. All devicetrees claim to be either GPL or X11 while the actual license text is MIT. Therefore we use MIT for the SPDX tag as X11 is clearly wrong. Signed-off-by: Klaus Goger --- arch/arm64/boot/dts/rockchip/rk3328-evb.

Re: [Y2038] [PATCH v2 08/10] fix get_timespec64() for y2038 safe compat interfaces

2017-12-15 Thread Arnd Bergmann
On Fri, Dec 15, 2017 at 1:21 AM, Ben Hutchings wrote: > On Mon, 2017-11-27 at 11:30 -0800, Deepa Dinamani wrote: >> get/put_timespec64() interfaces will eventually be used for >> conversions between the new y2038 safe struct __kernel_timespec >> and struct timespec64. >> >> The new y2038 safe sysc

Re: [PATCH] tpm: remove type and name fields from the I2C Infineon OF table entries

2017-12-15 Thread Jarkko Sakkinen
Hi Some basic questions about DT, which I'm not expert of. On Mon, Dec 04, 2017 at 06:39:16PM +0100, Javier Martinez Canillas wrote: > The commit 21dc02eab989 ("tpm/tpm_i2c_infineon.c: Add OF attributes type > and name to the of_device_id table entries") added type and name fields > to the OF dev

Re: [PATCH v2 2/4] sched/fair: add util_est on top of PELT

2017-12-15 Thread Patrick Bellasi
On 13-Dec 18:03, Peter Zijlstra wrote: > On Wed, Dec 13, 2017 at 04:36:53PM +, Patrick Bellasi wrote: > > On 13-Dec 17:19, Peter Zijlstra wrote: > > > On Tue, Dec 05, 2017 at 05:10:16PM +, Patrick Bellasi wrote: > > > > @@ -562,6 +577,12 @@ struct task_struct { > > > > > > > > con

Re: [PATCH] xen/balloon: Mark unallocated host memory as UNUSABLE

2017-12-15 Thread Juergen Gross
On 12/12/17 23:51, Boris Ostrovsky wrote: > Commit f5775e0b6116 ("x86/xen: discard RAM regions above the maximum > reservation") left host memory not assigned to dom0 as available for > memory hotplug. > > Unfortunately this also meant that those regions could be used by > others. Specifically, co

Re: [mainline] rcu stalls on CPU when unbinding mpt3sas driver

2017-12-15 Thread Hannes Reinecke
On 12/12/2017 11:38 AM, Abdul Haleem wrote: > Hi, > > Off late we are seeing cpu stalls messages while mpt3sas driver unbind > on powerpc machine for both mainline and linux-next kernels > > Machine Type: Power 8 Bare-metal > Kernel version: 4.15.0-rc2 > config: attached. > test: driver unbind >

Re: [PATCH v2 2/4] sched/fair: add util_est on top of PELT

2017-12-15 Thread Patrick Bellasi
On 13-Dec 17:16, Peter Zijlstra wrote: > On Tue, Dec 05, 2017 at 05:10:16PM +, Patrick Bellasi wrote: > > +static inline void util_est_dequeue(struct task_struct *p, int flags) > > +{ > > + struct cfs_rq *cfs_rq = &task_rq(p)->cfs; > > + unsigned long util_last = task_util(p); > > + bool

Re: [PATCH v5 1/7] scsi: libsas: Use dynamic alloced work to avoid sas event lost

2017-12-15 Thread Hannes Reinecke
On 12/08/2017 10:42 AM, Jason Yan wrote: > Now libsas hotplug work is static, every sas event type has its own > static work, LLDD driver queues the hotplug work into shost->work_q. > If LLDD driver burst posts lots hotplug events to libsas, the hotplug > events may pending in the workqueue like >

Re: [PATCH v5 2/7] scsi: libsas: shut down the PHY if events reached the threshold

2017-12-15 Thread Hannes Reinecke
On 12/08/2017 10:42 AM, Jason Yan wrote: > If the PHY burst too many events, we will alloc a lot of events for the > worker. This may leads to memory exhaustion. > > Dan Williams suggested to shut down the PHY if the events reached the > threshold, because in this case the PHY may have gone into s

Re: [PATCH] drm/amd/display: remove redundant null check of array 'data'

2017-12-15 Thread Christian König
Am 15.12.2017 um 11:53 schrieb Colin King: From: Colin Ian King The null check on aconnector->base.edid_blob_ptr->data is redundant since data is an array and can never be null. Remove it. Detected by CoverityScan, CID#1460369 ("Array compared against 0") Signed-off-by: Colin Ian King Ack

Re: [PATCH v5 3/7] scsi: libsas: make the event threshold configurable

2017-12-15 Thread Hannes Reinecke
On 12/08/2017 10:42 AM, Jason Yan wrote: > Add a sysfs attr that LLDD can configure it for every host. We made > a example in hisi_sas. Other LLDDs using libsas can implement it if > they want. > > Suggested-by: Hannes Reinecke > Signed-off-by: Jason Yan > CC: John Garry > CC: Johannes Thumshir

Re: [PATCH] arm: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
On Fri, Dec 15, 2017 at 12:19 PM, Mathieu Malaterre wrote: > On Fri, Dec 15, 2017 at 9:59 AM, Krzysztof Kozlowski wrote: >> On Thu, Dec 14, 2017 at 5:53 PM, Mathieu Malaterre wrote: >>> Improve the DTS files by removing all the leading "0x" and zeros to fix the >>> following dtc warnings: >>> >>

[PATCH] arm64: rockchip: enable Rockchip IO domain support

2017-12-15 Thread Klaus Goger
Make sure the IO domain support is active. This requires to enable Adaptive Voltage Scaling class support too. Without Rockchip IO domain support the internal level shifter on the RK3399 will be misconfigured if used in the other voltage domain then the default. Signed-off-by: Klaus Goger ---

Re: [patch v2 1/2] mm, mmu_notifier: annotate mmu notifiers with blockable invalidate callbacks

2017-12-15 Thread Christian König
Am 14.12.2017 um 22:30 schrieb David Rientjes: Commit 4d4bbd8526a8 ("mm, oom_reaper: skip mm structs with mmu notifiers") prevented the oom reaper from unmapping private anonymous memory with the oom reaper when the oom victim mm had mmu notifiers registered. The rationale is that doing mmu_noti

Re: [PATCH v5 4/7] scsi: libsas: Use new workqueue to run sas event and disco event

2017-12-15 Thread Hannes Reinecke
On 12/08/2017 10:42 AM, Jason Yan wrote: > Now all libsas works are queued to scsi host workqueue, > include sas event work post by LLDD and sas discovery > work, and a sas hotplug flow may be divided into several > works, e.g libsas receive a PORTE_BYTES_DMAED event, > currently we process it as f

Re: [PATCH v5 5/7] scsi: libsas: use flush_workqueue to process disco events synchronously

2017-12-15 Thread Hannes Reinecke
On 12/08/2017 10:42 AM, Jason Yan wrote: > Now we are processing sas event and discover event in different workqueues. > It's safe to wait the discover event done in the sas event work. Use > flush_workqueue() to insure the disco and revalidate events processed > synchronously so that the whole dis

Re: [PATCH v5 6/7] scsi: libsas: direct call probe and destruct

2017-12-15 Thread Hannes Reinecke
On 12/08/2017 10:42 AM, Jason Yan wrote: > In commit 87c8331fcf72 ("[SCSI] libsas: prevent domain rediscovery > competing with ata error handling") introduced disco mutex to prevent > rediscovery competing with ata error handling and put the whole > revalidation in the mutex. But the rphy add/remov

Re: [PATCH v5 7/7] scsi: libsas: notify event PORTE_BROADCAST_RCVD in sas_enable_revalidation()

2017-12-15 Thread Hannes Reinecke
On 12/08/2017 10:42 AM, Jason Yan wrote: > There are two places queuing the disco event DISCE_REVALIDATE_DOMAIN. > One is in sas_porte_broadcast_rcvd() and uses sas_chain_event() to queue > the event. The other is in sas_enable_revalidation() and uses > sas_queue_event() to queue the event. We have

Re: [PATCH 1/9] ASoC: Intel: Fix Kconfig with top-level selector

2017-12-15 Thread Pierre-Louis Bossart
On 12/15/17 5:07 AM, Takashi Iwai wrote: On Fri, 15 Dec 2017 01:44:43 +0100, Pierre-Louis Bossart wrote: +config SND_SOC_ACPI_INTEL_MATCH + tristate + depends on X86 && ACPI + select SND_SOC_ACPI An item that is selected by others can only select, not depend. The depends nee

Re: [PATCH 1/3] dt-bindings: chosen: Add clocksource and clockevent selection

2017-12-15 Thread Boris Brezillon
On Fri, 15 Dec 2017 11:40:04 + Mark Rutland wrote: > Hi, > > On Thu, Dec 14, 2017 at 09:01:20PM +0100, Boris Brezillon wrote: > > On Wed, 13 Dec 2017 16:57:50 -0600 > > Rob Herring wrote: > > > On Wed, Dec 13, 2017 at 12:53 PM, Alexandre Belloni > > > wrote: > > > > > The clocksource

Re: [PATCH 2/9] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies

2017-12-15 Thread Pierre-Louis Bossart
On 12/15/17 4:58 AM, Andy Shevchenko wrote: On Thu, 2017-12-14 at 18:44 -0600, Pierre-Louis Bossart wrote: PCI/ACPI selections should not happen in Kconfig for machine drivers, move to SOC selections. Add distinction between PCI and ACPI HiFi2 platforms and help text. There should be no functi

Naming of tag operations in the XArray

2017-12-15 Thread Matthew Wilcox
On Thu, Dec 14, 2017 at 08:22:14PM -0800, Matthew Wilcox wrote: > On Mon, Dec 11, 2017 at 03:10:22PM -0800, Randy Dunlap wrote: > > > +A freshly-initialised XArray contains a ``NULL`` pointer at every index. > > > +Each non-``NULL`` entry in the array has three bits associated with > > > +it called

Re: [PATCH v2] x86: update/correct opcodes map

2017-12-15 Thread Ingo Molnar
* Randy Dunlap wrote: > From: Randy Dunlap > > Update x86-opcode-map.txt based on the October 2017 Intel SDM publication. > Correct INVPID to INVVPID. > Add UD0 and UD1 instruction opcodes. > > Signed-off-by: Randy Dunlap > Cc: Masami Hiramatsu > Cc: Masami Hiramatsu > Cc: Josh Poimboeuf

Re: [PATCH] arm: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Krzysztof Kozlowski
On Fri, Dec 15, 2017 at 1:18 PM, Mathieu Malaterre wrote: >> As discussed with Krzysztof, I've split the ARM patch into subarch. >> Please drop this one. > > Hum...looks like my internet provider just blacklisted me for too many > recipient in the mail. I'll do my best to resolve this, and send th

[PATCH 01/25] arm: artpec: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 16/25] arm: zx: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 25/25] arm: ste: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 05/25] arm: imx: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 06/25] arm: integrator: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 10/25] arm: orion5x: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH] x86/fixmap: Set the debugstore fixmap entries on Intel only

2017-12-15 Thread Borislav Petkov
From: Borislav Petkov No need to setup those during boot on !Intel vendors. Signed-off-by: Borislav Petkov Cc: Linus Torvalds Cc: Andy Lutomirsky Cc: Peter Zijlstra Cc: Dave Hansen Cc: Greg KH Cc: keesc...@google.com Cc: hu...@google.com Cc: Brian Gerst Cc: Josh Poimboeuf Cc: Denys Vlase

[PATCH 24/25] arm: dm8: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 21/25] arm: realview: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 23/25] arm: da8: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 22/25] arm: atlas: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH] misc: mic: remove unused label

2017-12-15 Thread Arnd Bergmann
A cleanup left an unused label behind: drivers/misc/mic/vop/vop_vringh.c: In function 'vop_ioctl': drivers/misc/mic/vop/vop_vringh.c:1001:1: error: label 'done' defined but not used [-Werror=unused-label] This cleans it up as well. Fixes: 30b7a2c19e29 ("misc: mic: Use memdup_user() as a cleanup

[PATCH V3] ACPI / LPSS: Add device link for CHT SD card dependency on I2C

2017-12-15 Thread Adrian Hunter
Some Cherry Trail boards have a dependency between the SDHCI host controller used for SD cards and an external PMIC accessed via I2C. Add a device link between the SDHCI host controller (consumer) and the I2C adapter (supplier). This patch depends on a fix to devices links, namely commit 0ff26c662

[PATCH 17/25] arm: rk3: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH] pinctrl: axp209: add CONFIG_OF dependency

2017-12-15 Thread Arnd Bergmann
The pinconf_generic_dt_free_map and pinconf_generic_dt_node_to_map_group functions are only defined when CONFIG_OF is set: drivers/pinctrl/pinctrl-axp209.c:312:21: error: 'pinconf_generic_dt_node_to_map_group' undeclared here (not in a function); did you mean 'pinconf_generic_params'? drivers/pi

[PATCH 18/25] arm: am3/am4/dra7/omap: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 19/25] arm: mt7: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 20/25] arm: kirkwood: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 14/25] arm: stm32: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

Re: [PATCH 05/25] arm: imx: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Fabio Estevam
Hi Mathieu, On Fri, Dec 15, 2017 at 10:46 AM, Mathieu Malaterre wrote: reg = <0x6C>; > diff --git a/arch/arm/boot/dts/imx7d.dtsi b/arch/arm/boot/dts/imx7d.dtsi > index 4d308d17f040..369d5a166b3e 100644 > --- a/arch/arm/boot/dts/imx7d.dtsi > +++ b/arch/arm/boot/dts/imx7d.dtsi > @@

Re: Warning in i915/intel_audio.c

2017-12-15 Thread Mika Kahola
Hi, This is a known issue. Could you try out this patch to see if that would fix this issue for you? https://patchwork.freedesktop.org/series/35389/ On Fri, 2017-12-15 at 17:08 +0530, Jaswinder Singh Rajput wrote: > Hello friends, > > I am getting multiple warnings in i915/intel_audio.c . I am

[PATCH 12/25] arm: socfpga: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 15/25] arm: versatile: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 04/25] arm: exynos/s3c: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 13/25] arm: spear: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH] drm/tegra: mark t186 display hub PM functions __maybe_unused

2017-12-15 Thread Arnd Bergmann
The newly introduced driver has optional suspend/resume functions, causing a warning when CONFIG_PM is disabled: drivers/gpu/drm/tegra/hub.c:749:12: error: 'tegra_display_hub_resume' defined but not used [-Werror=unused-function] drivers/gpu/drm/tegra/hub.c:733:12: error: 'tegra_display_hub_suspe

[PATCH] mm: thp: avoid uninitialized variable use

2017-12-15 Thread Arnd Bergmann
When the down_read_trylock() fails, 'vma' has not been initialized yet, which gcc now warns about: mm/khugepaged.c: In function 'khugepaged': mm/khugepaged.c:1659:25: error: 'vma' may be used uninitialized in this function [-Werror=maybe-uninitialized] Presumable we are not supposed to call find

[PATCH 11/25] arm: prima2: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

Re: [PATCH] pinctrl: axp209: add CONFIG_OF dependency

2017-12-15 Thread Quentin Schulz
Hi Arnd, On 15/12/2017 13:48, Arnd Bergmann wrote: > The pinconf_generic_dt_free_map and pinconf_generic_dt_node_to_map_group > functions are only defined when CONFIG_OF is set: > > drivers/pinctrl/pinctrl-axp209.c:312:21: error: > 'pinconf_generic_dt_node_to_map_group' undeclared here (not in a

[PATCH 09/25] arm: nspire: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 02/25] arm: at91/sama: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 07/25] arm: keystone: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

Re: [PATCH v2 2/4] sched/fair: add util_est on top of PELT

2017-12-15 Thread Peter Zijlstra
On Fri, Dec 15, 2017 at 12:14:17PM +, Patrick Bellasi wrote: > On 13-Dec 17:16, Peter Zijlstra wrote: > > > + /* > > > + * Skip update of task's estimated utilization when its EWMA is already > > > + * ~1% close to its last activation value. > > > + */ > > > + util_est = p->util_est.ewma; >

[PATCH 08/25] arm: lpc32: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

[PATCH 03/25] arm: bcm: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Mathieu Malaterre
Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit name should not have leading 0s Converted using the following com

stack traces and zombie tasks

2017-12-15 Thread Miroslav Benes
Hi, commit 1959a60182f4 ("x86/dumpstack: Pin the target stack when dumping it") slightly changed the behaviour of stack traces dumping for zombie tasks. Before the commit (well, this is older SLE12 kernel, but that should not matter), if one called 'cat /proc//stack', they would get something

Re: [PATCH 3.18 00/64] 3.18.88-stable review

2017-12-15 Thread Greg Kroah-Hartman
On Fri, Dec 15, 2017 at 12:22:06PM +0100, Sebastian Gottschall wrote: > kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.88-rc1.gz > > is missing. > same for > 4.4 Very odd. I've pushed all of the -rc patches out again, maybe the mirroring is taking a while to hit the public side of the

Re: [PATCH 01/25] arm: artpec: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Jesper Nilsson
On Fri, Dec 15, 2017 at 01:46:21PM +0100, Mathieu Malaterre wrote: > Improve the DTS files by removing all the leading "0x" and zeros to fix the > following dtc warnings: > > Warning (unit_address_format): Node /XXX unit name should not have leading > "0x" > > and > > Warning (unit_address_form

Re: [PATCH v2 2/4] sched/fair: add util_est on top of PELT

2017-12-15 Thread Peter Zijlstra
On Fri, Dec 15, 2017 at 12:03:31PM +, Patrick Bellasi wrote: > So, by moving util_est right after sched_avg, here is what we get (with some > lines to better highlight 64B boundaries): > > const struct sched_class * sched_class; >/* 152

Re: [PATCH 16/19] fs: only set S_VERSION when updating times if necessary

2017-12-15 Thread Jeff Layton
On Wed, 2017-12-13 at 09:20 -0500, Jeff Layton wrote: > From: Jeff Layton > > We only really need to update i_version if someone has queried for it > since we last incremented it. By doing that, we can avoid having to > update the inode if the times haven't changed. > > If the times have changed

sysfs_kf_seq_show() spends 87% of time in memset()

2017-12-15 Thread Christophe LEROY
Hello Tejun, Doing a 'perf record' on an application using GPIOs a lot, I discovered that most of the time spent in the read() system call of the 'value' sysfs file of that GPIO (which returns "0\n" or "1\n") is indeed spent in memset() zeroing a buffer of size PAGE_SIZE for a 2 bytes read:

Re: [PATCH 10/25] arm: orion5x: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Andrew Lunn
On Fri, Dec 15, 2017 at 01:46:42PM +0100, Mathieu Malaterre wrote: > Improve the DTS files by removing all the leading "0x" and zeros to fix the ... > }; > > - uboot_env@3F000 { > + uboot_env@3f000 { > r

Re: [PATCH] mm: thp: avoid uninitialized variable use

2017-12-15 Thread Michal Hocko
On Fri 15-12-17 13:51:04, Arnd Bergmann wrote: > When the down_read_trylock() fails, 'vma' has not been initialized > yet, which gcc now warns about: > > mm/khugepaged.c: In function 'khugepaged': > mm/khugepaged.c:1659:25: error: 'vma' may be used uninitialized in this > function [-Werror=maybe-

Re: [PATCH 20/25] arm: kirkwood: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Andrew Lunn
> Warning (unit_address_format): Node /XXX unit name should not have leading > "0x" > > and > > Warning (unit_address_format): Node /XXX unit name should not have leading 0s Humm, it actually looks like the compiler is broken. None of the lines you are changing in this, or the orion5x file, hav

Re: [PATCH 18/19] btrfs: only dirty the inode in btrfs_update_time if something was changed

2017-12-15 Thread Jeff Layton
On Wed, 2017-12-13 at 09:20 -0500, Jeff Layton wrote: > From: Jeff Layton > > At this point, we know that "now" and the file times may differ, and we > suspect that the i_version has been flagged to be bumped. Attempt to > bump the i_version, and only mark the inode dirty if that actually > occur

Re: [PATCH] rtc: ds1307: call the platform's logic for handle IRQs.

2017-12-15 Thread Alexandre Belloni
Hi, On 15/12/2017 at 12:44:49 +0100, Enric Balletbo Serra wrote: > Hi, > > 2017-08-24 12:30 GMT+02:00 Enric Balletbo i Serra > : > > On some systems the nIRQ pin is often connect to a GPIO, then, if a given > > interrupt line is supposed to wake up the system, the corresponding input > > of that

Re: [PATCH linux ipmi for BMC] ipmi: add an Aspeed KCS IPMI BMC driver

2017-12-15 Thread Corey Minyard
On 12/14/2017 09:07 PM, Haiyue Wang wrote: Thanks Corey, yes, I ran through checkpatch. Fix most of warnings and errors. I thought 2 and 3 would be acceptable, will fix it in new patch,and together with fix for comments from all of you. And how to fix item 1 ? 1. WARNING: added, moved or delet

Re: [PATCH 4.14 00/52] 4.14.7-stable review

2017-12-15 Thread Greg Kroah-Hartman
On Fri, Dec 15, 2017 at 11:09:00AM +0100, Nikola Ciprich wrote: > Hi Greg, > > On Fri, Dec 15, 2017 at 10:51:37AM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.7 release. > > There are 52 patches in this series, all will be posted as a response > >

Re: [PATCH 4.4 000/105] 4.4.106-stable review

2017-12-15 Thread Greg Kroah-Hartman
On Fri, Dec 15, 2017 at 03:01:10AM -0700, Nathan Chancellor wrote: > > Merged, compiled, and flashed onto my Pixel 2 XL and OnePlus 5. > > No initial issues noticed in general usage or dmesg. Wonderful, thanks for testing and letting me know. greg k-h

Re: [PATCH] drm/tegra: mark t186 display hub PM functions __maybe_unused

2017-12-15 Thread Dmitry Osipenko
On 15.12.2017 15:51, Arnd Bergmann wrote: > The newly introduced driver has optional suspend/resume functions, > causing a warning when CONFIG_PM is disabled: > > drivers/gpu/drm/tegra/hub.c:749:12: error: 'tegra_display_hub_resume' defined > but not used [-Werror=unused-function] > drivers/gpu/d

Re: linux-next: build warning after merge of the cgroup tree

2017-12-15 Thread Tejun Heo
On Fri, Dec 15, 2017 at 10:58:04AM +0100, Arnd Bergmann wrote: > As long as cft->name is guaranteed to be NUL-terminated, using strlcpy() would > work just as well and avoid that warning, so the change below could be folded > into that commit. > > Signed-off-by: Arnd Bergmann Applied to cgroup/f

Re: [PATCH v6] mfd: syscon: Add hardware spinlock support

2017-12-15 Thread Arnd Bergmann
On Fri, Dec 15, 2017 at 11:42 AM, Lee Jones wrote: >> @@ -87,6 +88,30 @@ static struct syscon *of_syscon_register(struct >> device_node *np) >> if (ret) >> reg_io_width = 4; >> >> + ret = of_hwspin_lock_get_id(np, 0); >> + if (ret > 0) { >> + syscon_config

[PATCH] x86: Remove unused parameter of prepare_switch_to

2017-12-15 Thread rodrigosiqueira
Commit e37e43a497d5 ("x86/mm/64: Enable vmapped stacks (CONFIG_HAVE_ARCH_VMAP_STACK=y)") added prepare_switch_to with one extra parameter which is not used by the function, remove it. Signed-off-by: Rodrigo Siqueira --- arch/x86/include/asm/switch_to.h | 5 ++--- 1 file changed, 2 insertions(+),

Re: [PATCH 03/25] arm: bcm: dts: Remove leading 0x and 0s from bindings notation

2017-12-15 Thread Stefan Wahren
[Add Eric] Am 15.12.2017 um 13:46 schrieb Mathieu Malaterre: Improve the DTS files by removing all the leading "0x" and zeros to fix the following dtc warnings: Warning (unit_address_format): Node /XXX unit name should not have leading "0x" and Warning (unit_address_format): Node /XXX unit na

Re: [PATCH] drm/tegra: mark t186 display hub PM functions __maybe_unused

2017-12-15 Thread Arnd Bergmann
On Fri, Dec 15, 2017 at 2:10 PM, Dmitry Osipenko wrote: > On 15.12.2017 15:51, Arnd Bergmann wrote: >> --- a/drivers/gpu/drm/tegra/hub.c >> +++ b/drivers/gpu/drm/tegra/hub.c >> @@ -730,7 +730,7 @@ static int tegra_display_hub_remove(struct >> platform_device *pdev) >> return err; >> } >> >

Re: sysfs_kf_seq_show() spends 87% of time in memset()

2017-12-15 Thread Tejun Heo
Hello, On Fri, Dec 15, 2017 at 01:59:55PM +0100, Christophe LEROY wrote: > Doing a 'perf record' on an application using GPIOs a lot, I > discovered that most of the time spent in the read() system call of > the 'value' sysfs file of that GPIO (which returns "0\n" or "1\n") > is indeed spent in me

[PATCH] cgroup, docs: document the root cgroup behavior of cpu and io controllers

2017-12-15 Thread Maciej S. Szmigiero
Currently, cgroups v2 documentation contains only a generic remark that "How resource consumption in the root cgroup is governed is up to each controller", which isn't really telling users much, who need to dig in the code and / or commit messages to learn the exact behavior. In cgroups v1 at leas

[GIT PULL] tee dynamic shm for v4.16

2017-12-15 Thread Jens Wiklander
Hello arm-soc maintainers, Please pull these tee driver changes. This implements support for dynamic shared memory support in OP-TEE. More specifically is enables mapping of user space memory in secure world to be used as shared memory. This has been reviewed and refined by the OP-TEE community a

[PATCH 0/8] ARM: dts: keystone*: Stage 1 cleanup for W=1

2017-12-15 Thread Nishanth Menon
Hi, Series to squash some of the build warnings with dts. At least try and get through 2/3rd of the warnings low hanging ones with this series. Warning status: As of master: http://pastebin.ubuntu.com/26188581/ After this series: http://pastebin.ubuntu.com/26188578/ Diff: 243 warnings squashed.

[PATCH 4/8] ARM: dts: keystone: Add missing unit name to interrupt controller

2017-12-15 Thread Nishanth Menon
Add base address for GIC as unit address. This also squashes the following warnings when built with W=1: arch/arm/boot/dts/keystone-k2hk-evm.dtb: Warning (unit_address_vs_reg): Node /interrupt-controller has a reg or ranges property, but no unit name arch/arm/boot/dts/keystone-k2l-evm.dtb: Warning

Re: [PATCH] cgroup/cpuset: fix circular locking dependency

2017-12-15 Thread Tejun Heo
Hello, Prateek. On Fri, Dec 15, 2017 at 02:24:55PM +0530, Prateek Sood wrote: > Following are two ways to improve cgroup_transfer_tasks(). In > both cases task in PF_EXITING state would be left in source > cgroup. It would be removed from cgroup_exit() in exit path. > > diff --git a/kernel/cgroup

Re: [PATCH v2] PCI: keystone: fix interrupt-controller-node lookup

2017-12-15 Thread Lorenzo Pieralisi
On Fri, Nov 17, 2017 at 02:38:31PM +0100, Johan Hovold wrote: > Fix child-node lookup during initialisation which was using the wrong > OF-helper and ended up searching the whole device tree depth-first > starting at the parent rather than just matching on its children. > > To make things worse, t

[PATCH 6/8] ARM: dts: keystone-hk-clocks: Add missing unit name to clock nodes that have regs

2017-12-15 Thread Nishanth Menon
Add the control register as the base for the clock nodes which are missing them. This squashes some 36 warnings of the effect when built with W=1. Reported-by: Rob Herring Signed-off-by: Nishanth Menon --- arch/arm/boot/dts/keystone-k2hk-clocks.dtsi | 74 ++--- 1 file ch

[PATCH 8/8] ARM: dts: keystone-k2l-clocks: Add missing unit name to clock nodes that have regs

2017-12-15 Thread Nishanth Menon
Add the control register as the base for the clock nodes which are missing them. This squashes some 22 warnings of the effect when built with W=1. Reported-by: Rob Herring Signed-off-by: Nishanth Menon --- arch/arm/boot/dts/keystone-k2l-clocks.dtsi | 44 +++--- 1 file c

[PATCH 7/8] ARM: dts: keystone-k2e-clocks: Add missing unit name to clock nodes that have regs

2017-12-15 Thread Nishanth Menon
Add the control register as the base for the clock nodes which are missing them. This squashes the following warnings of the effect when built with W=1: arch/arm/boot/dts/keystone-k2e-evm.dtb: Warning (unit_address_vs_reg): Node /soc@0/clocks/clkusb1 has a reg or ranges property, but no unit name

[PATCH 1/8] ARM: dts: keystone*: Standardize license with SPDX tag

2017-12-15 Thread Nishanth Menon
Standardize the licenses with SPDX license tag and standardize TI's copyright statement to be consistent. Signed-off-by: Nishanth Menon --- arch/arm/boot/dts/keystone-clocks.dtsi | 7 ++- arch/arm/boot/dts/keystone-k2e-clocks.dtsi | 7 ++- arch/arm/boot/dts/keystone-k2e-evm.dts

[PATCH 2/8] ARM: dts: keystone*: Use a single soc0 instance

2017-12-15 Thread Nishanth Menon
Provide and soc0 node and reference the same to simplify dts. This also resolves the following warnings when built with W=1: arch/arm/boot/dts/keystone-k2hk-evm.dtb: Warning (unit_address_vs_reg): Node /soc has a reg or ranges property, but no unit name arch/arm/boot/dts/keystone-k2l-evm.dtb: Warn

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