[tip:locking/core] locking/lockdep: Move sanity check to inside lockdep_print_held_locks()

Commit-ID: 8cc05c71ba5f793690bb72aeb404dce65b5d4b52 Gitweb: https://git.kernel.org/tip/8cc05c71ba5f793690bb72aeb404dce65b5d4b52 Author: Tetsuo Handa AuthorDate: Fri, 6 Apr 2018 19:41:19 +0900 Committer: Ingo Molnar CommitDate: Mon, 14 May 2018 09:15:02 +0200 locking/lockdep: Move sanit

[tip:locking/core] locking/lockdep: Use for_each_process_thread() for debug_show_all_locks()

Commit-ID: 0f736a52e4be86476eec1d5adbcbd9c2809ac4b4 Gitweb: https://git.kernel.org/tip/0f736a52e4be86476eec1d5adbcbd9c2809ac4b4 Author: Tetsuo Handa AuthorDate: Fri, 6 Apr 2018 19:41:18 +0900 Committer: Ingo Molnar CommitDate: Mon, 14 May 2018 09:15:02 +0200 locking/lockdep: Use for_ea

[PATCH v1 6/7] drm/mediatek: add a error return value when clock driver has been prepared

DRM driver get the comp->clk by of_clk_get(), we only assign NULL to comp->clk when error happened, but do not return the error number. Signed-off-by: Bibby Hsieh --- drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/m

Re: [Ksummit-discuss] bug-introducing patches

On Thu, May 10, 2018 at 6:47 PM, Sasha Levin via Ksummit-discuss wrote: > On Thu, May 10, 2018 at 06:03:22PM +0200, Jiri Kosina wrote: >>On Wed, 9 May 2018, Daniel Vetter wrote: >>> >> Then, why don't we have a pre-integration tree for fixes? That would >>> >> at least simply automated testing of

[tip:sched/core] sched/core: Distinguish between idle_cpu() calls based on desired effect, introduce available_idle_cpu()

Commit-ID: 943d355d7feef380e15a95892be3dff1095ef54b Gitweb: https://git.kernel.org/tip/943d355d7feef380e15a95892be3dff1095ef54b Author: Rohit Jain AuthorDate: Wed, 9 May 2018 09:39:48 -0700 Committer: Ingo Molnar CommitDate: Mon, 14 May 2018 09:12:26 +0200 sched/core: Distinguish betwe

[PATCH v1 5/7] drm/mediatek: implement connection from BLS to DPI0

Modify display driver to support connection from BLS to DPI. Signed-off-by: Bibby Hsieh --- drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c b/drivers/gpu/drm/mediatek/mtk_drm_ddp.c i

Re: [PATCH 13/18 v2] regulator: wm8994: Pass descriptor instead of GPIO number

On Mon, Apr 23, 2018 at 5:28 PM, Mark Brown wrote: > On Mon, Apr 23, 2018 at 01:07:37AM +0200, Linus Walleij wrote: >> Instead of passing a global GPIO number for the enable GPIO, pass >> a descriptor looked up from the device tree node or the board file >> decriptor table for the regulator. > > T

[PATCH v1 3/7] drm/mediatek: add dpi driver for mt2701 and mt7623

From: chunhui dai This patch adds dpi driver suppot for both mt2701 and mt7623. And also support other (existing or future) chips that use the same binding and driver. Signed-off-by: chunhui dai --- drivers/gpu/drm/mediatek/mtk_dpi.c | 24 ++-- drivers/gpu/drm/mediatek/

[PATCH v1 1/7] drm/mediatek: move dpi private data to device

From: chunhui dai move clock factor and edge enable setting to private data. Signed-off-by: chunhui dai --- drivers/gpu/drm/mediatek/mtk_dpi.c | 82 ++--- drivers/gpu/drm/mediatek/mtk_dpi_regs.h | 2 +- 2 files changed, 66 insertions(+), 18 deletions(-) diff

[PATCH 3.18 12/23] netlink: fix uninit-value in netlink_sendmsg

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 6091f09c2f79730d895149bcfe3d66140288cd0e upstream. syzbot reported : BUG: KMSAN: uninit-value in ffs arch/x86/include/asm/bitops.h:432 [inline] BUG: KMSAN: uninit-value in

[PATCH 3.18 05/23] ALSA: seq: Fix races at MIDI encoding in snd_virmidi_output_trigger()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 8f22e52528cc372b218b5f100457469615c733ce upstream. The sequencer virmidi code has an open race at its output trigger callback: namely, virmidi keeps only one event packet f

[PATCH 3.18 00/23] 3.18.109-stable review

This is the start of the stable review cycle for the 3.18.109 release. There are 23 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed May 16 06:46:49 UTC 2018. Anything recei

[PATCH 3.18 06/23] ALSA: aloop: Mark paused device as inactive

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Robert Rosengren commit 306a4f3ca7f3c7dfa473ebd19d66e40e59d99734 upstream. Show paused ALSA aloop device as inactive, i.e. the control "PCM Slave Active" set as false. Notification sent upon s

[PATCH 3.18 02/23] perf/core: Fix the perf_cpu_time_max_percent check

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tan Xiaojun commit 1572e45a924f254d9570093abde46430c3172e3d upstream. Use "proc_dointvec_minmax" instead of "proc_dointvec" to check the input value from user-space. If not, we can set a big

Re: Allwinner A64: Issue on external rtc clock to wifi chip

Hi, On Mon, May 14, 2018 at 12:37:49PM +0530, Jagan Teki wrote: > Hi Maxime and All, > > We are trying to bring-up AP6330 Wifi chip for A64 board. We noticed > to have an external rtc clock has driven from wifi chip. > > So the devicetree is configured according to this as below. > > / { >

Re: [PATCH 10/18 v2] regulator: s2mps11: Pass descriptor instead of GPIO number

On Mon, Apr 23, 2018 at 1:07 AM, Linus Walleij wrote: > Instead of passing a global GPIO number for the enable GPIO, pass > a descriptor looked up with the standard devm_gpiod_get_optional() > call. > > This regulator supports passing platform data, but enable/sleep > regulators are looked up from

Re: [PATCH] net: mvpp2: fix mvpp2_tx()'s return type

Hi Luc, On Tue, Apr 24, 2018 at 03:16:53PM +0200, Luc Van Oostenryck wrote: > The method ndo_start_xmit() is defined as returning an 'netdev_tx_t', > which is a typedef for an enum type, but the implementation in this > driver returns an 'int'. > > Fix this by returning 'netdev_tx_t' in this driv

Re: Are media drivers abusing of GFP_DMA? - was: Re: [LSF/MM TOPIC NOTES] x86 ZONE_DMA love

On 07/05/18 17:19, Mauro Carvalho Chehab wrote: > Em Mon, 07 May 2018 16:26:08 +0300 > Laurent Pinchart escreveu: > >> Hi Mauro, >> >> On Saturday, 5 May 2018 19:08:15 EEST Mauro Carvalho Chehab wrote: >>> There was a recent discussion about the use/abuse of GFP_DMA flag when >>> allocating memo

Re: bug-introducing patches

On Tue, May 1, 2018 at 10:00 PM, Sasha Levin wrote: > On Tue, May 01, 2018 at 03:44:50PM -0400, Theodore Y. Ts'o wrote: >>On Tue, May 01, 2018 at 04:38:21PM +, Sasha Levin wrote: >>> - A merge window commit spent 50% more days, on average, in -next than a >>> -rc >>>commit. >> >>So it *u

[PATCH v2] ARM: dts: exynos: Add support for audio over HDMI for Odroid X/X2/U3

This patch switches Odroid X/X2/U3 to use dedicated Odroid audio subsystem DT bindings instead of the simple-card in order to add support for audio over HDMI. Signed-off-by: Sylwester Nawrocki --- arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 33 +++-- arch/arm/boot/dts/e

Re: [PATCH] ARM: dts: exynos: Use dedicated DT bindings for Odroid X/X2, U3

On 05/13/2018 02:24 PM, Krzysztof Kozlowski wrote: > On Fri, May 11, 2018 at 10:09:47AM +0200, Sylwester Nawrocki wrote: >> Use dedicated Odroid audio subsystem DT bindings instead of the simple-card. >> This adds support for audio on the HDMI interface. > How about changing the subject to "Add su

Re: [PATCH 3.18 00/23] 3.18.109-stable review

On Mon, May 14, 2018 at 08:48:29AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.109 release. > There are 23 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me kno

Re: [PATCH -resend 01/27] linkage: new macros for assembler symbols

* Jiri Slaby wrote: > Documentation/asm-annotations.rst | 218 > arch/x86/include/asm/linkage.h| 10 +- > include/linux/linkage.h | 257 > -- > 3 files changed, 475 insertions(+), 10 deletions(-) > create mode

[PATCH] mailbox: arm_mhu: add support for mhuv2

ARM has launched a next version of MHU i.e. MHUv2 with its latest subsystems. The main change is that the MHUv2 is now a distributed IP with different peripheral views (registers) for the sender and receiver. Another main difference is that MHUv1 duplex channels are now split into simplex/half dup

Re: Allwinner A64: Issue on external rtc clock to wifi chip

On Mon, May 14, 2018 at 1:27 PM, Maxime Ripard wrote: > Hi, > > On Mon, May 14, 2018 at 12:37:49PM +0530, Jagan Teki wrote: >> Hi Maxime and All, >> >> We are trying to bring-up AP6330 Wifi chip for A64 board. We noticed >> to have an external rtc clock has driven from wifi chip. >> >> So the devi

Re: drivers/edac/skx_edac.c:399: undefined reference to `nfit_get_smbios_id'

On Sun, 13 May 2018 04:51:21 +0800, kbuild test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 427fbe89261d8f11cd20b5a4ba94e977061f69d6 > commit: 58ca9ac1463d07d24b9fa8befe065192abca6f76 EDAC, skx_edac: Detect > non-volatile DIMMs > da

Re: [PATCH -resend 02/27] x86: assembly, use SYM_DATA for data

* Jiri Slaby wrote: > We make proper use of SYM_DATA on global data instead of marking them as > ENTRY. ENTRY is intended for functions and shall be paired with ENDPROC. > ENTRY also aligns symbols which creates unnecessary holes here between > data. > > ENTRY from saved_eip in wakeup_32 and ma

[PATCH 00/19 v3] Refactor fixed and GPIO regulators

This pulls the fixed and GPIO regulators into the gpiolib descriptor framework, at least more than what is currently the case. This is also available as a git branch: git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-regulator-4.18 Charles Keepax (1): ARM: s3c64xx: Tidy up

Re: [PATCH] mailbox: arm_mhu: add support for mhuv2

Hi Jassi, As suggested by you, I have moved the MHUv2 related changes to a new file arm_mhu_v2.c. I have sent an updated patch, can you please review it? Regards, Samarth On 02/05/18, 5:34 PM, "Jassi Brar" wrote: On Wed, May 2, 2018 at 12:44 PM, Samarth Parikh wrote: > Hi Jassi,

[PATCH 18/19 v3] regulator: gpio: Simplify probe path

Use devm_* managed device resources and create a local struct device *dev variable to simplify the code inside probe(). Signed-off-by: Linus Walleij --- ChangeLog v2->v3: - Resending. ChangeLog v1->v2: - Rebase the patch on the other changes. --- drivers/regulator/gpio-regulator.c | 56 +

[PATCH 09/19 v3] regulator: pfuze100: Delete reference to ena_gpio

We now pass a GPIO descriptor to the core instead of a global GPIO number, if this descriptor is NULL the GPIO line is not used. Just delete the assignment of an invalid GPIO line. Signed-off-by: Linus Walleij --- ChangeLog v2->v3: - Resending. ChangeLog v1->v2: - Rebase the patch on the other ch

[PATCH 03/19 v3] regulator: arizona-ldo1: Look up a descriptor and pass to the core

Instead of passing a global GPIO number, pass a descriptor looked up with the standard devm_gpiod_get_optional() call. We have augmented the GPIO core to look up the regulator special GPIO "wlf,ldoena" in commit 6a537d48461d "gpio: of: Support regulator nonstandard GPIO properties". Cc: patc...@o

[PATCH 08/19 v3] regulator: max8952: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number for the enable GPIO, pass a descriptor looked up with the standard devm_gpiod_get_optional() call. All users of this regulator use device tree so the transition is pretty smooth. Cc: MyungJoo Ham Signed-off-by: Linus Walleij --- ChangeLog v2->v3: - Resend

[PATCH 16/19 v3] regulator: fixed/gpio: Update device tree bindings

Deprecate the open drain binding for fixed regulator and indicate that we prefer this to be passed in the GPIO phandle flags. Clarify that the line inversion semantics for fixed and GPIO regulators completely overrides the active low flags in the phandle flags. Unfortunately this can not be chang

[PATCH 19/19 v3] ARM: s3c64xx: Tidy up handling of regulator GPIO lookups

From: Charles Keepax Rather than unconditionally registering the GPIO lookup table only do so for devices that require it. Signed-off-by: Charles Keepax [Fixed up to also handle wm5102 and wm5102 reva] Signed-off-by: Linus Walleij --- ChangeLog v2->v3: - Including this in my patch series. ---

[PATCH 17/19 v3] regulator: gpio: Convert to fully use descriptors

This converts the GPIO regulator driver to use decriptors only. We have to let go of the array gpio handling: the fetched descriptors are handled individually anyway, and the array retrieveal function does not make it possible to retrieve each GPIO descriptor with unique flags. Instead get them one

[PATCH 15/19 v3] regulator: fixed/gpio: Pull inversion/OD into gpiolib

This pushes the handling of inversion semantics and open drain settings to the GPIO descriptor and gpiolib. All affected board files are also augmented. This is especiallt nice since we don't have to have any confusing flags passed around to the left and right littering the fixed and GPIO regulato

Re: [PATCH 4.4 00/56] 4.4.132-stable review

On Mon, May 14, 2018 at 08:48:05AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.132 release. > There are 56 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know

[PATCH 11/19 v3] regulator: s5m8767: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number for the enable GPIO, pass a descriptor looked up from the device tree node for the regulator. This regulator supports passing platform data, but enable/sleep regulators are looked up from the device tree exclusively, so we can need not touch other files. Ac

[PATCH 14/19 v3] regulator: core: Only support passing enable GPIO descriptors

Now that we changed all providers to pass descriptors into the core for enable GPIOs instead of a global GPIO number, delete the support for passing GPIO numbers in, and we get a cleanup and size reduction in the core, and from a GPIO point of view we use the modern, cleaner interface. Signed-off-

[PATCH 10/19 v3] regulator: s2mps11: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number for the enable GPIO, pass a descriptor looked up with the standard devm_gpiod_get_optional() call. This regulator supports passing platform data, but enable/sleep regulators are looked up from the device tree exclusively, so we can need not touch other files

Re: [PATCH -resend 00/27] New macros for assembler symbols

* Jiri Slaby wrote: > This series introduces new macros for assembly as was discussed [1]. > The macros are introduced in the first patch of the series. The rest > of patches start using these new macros in x86, converting *all* uses > of the old macros to the new ones throughout the last patch.

[PATCH 13/19 v3] regulator: wm8994: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number for the enable GPIO, pass a descriptor looked up from the device tree node or the board file decriptor table for the regulator. There is a single board file passing the GPIOs for LDO1 and LDO2 through platform data, so augment this to pass descriptors associ

[PATCH 12/19 v3] regulator: tps65090: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number for the enable GPIO, pass a descriptor looked up from the device tree node for the regulator. This regulator supports passing platform data, but enable/sleep regulators are looked up from the device tree exclusively, so we can need not touch other files. Ac

[PATCH 07/19 v3] regulator: lp8788-ldo: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number, pass a descriptor looked up with the standard devm_gpiod_get_index_optional() call. This driver has supported passing a LDO enable GPIO for years, yet this facility has never been put to use in the upstream kernel. If someone desires to put in place GPIO co

Re: [GIT PULL] ARM: uniphier: fixes for v4.17

On Sun, Apr 29, 2018 at 12:47:00AM +0900, Masahiro Yamada wrote: > Hi Arnd, Olof, > > Please pull some fixes of ARM UniPhier DT. > > > > The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: > > Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) > > are available in the git r

Re: drivers/edac/skx_edac.c:399: undefined reference to `nfit_get_smbios_id'

On Mon, May 14, 2018 at 10:05:30AM +0200, Jean Delvare wrote: > I'll send a candidate fix shortly. https://lkml.kernel.org/r/3af91354-8e19-d2af-1bba-ced8dce05...@infradead.org -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnb

Re: [PATCH fixes-for-current] arm64: dts: exynos: Fix interrupt type for I2S1 device on Exynos5433

On Sun, May 06, 2018 at 04:55:24PM +0200, Krzysztof Kozlowski wrote: > From: Marek Szyprowski > > All interrupts from SoC internal modules are level triggered, so fix > incorrect trigger type for I2S1 device on Exynos5433 SoCs. > > This fixes following kernel warning: > > WARNING: CPU: 2 PID: 1

[PATCH 0/3] docs/vm: transhuge: split userspace bits to admin-guide/mm

Hi, Here are minor updates to transparent hugepage docs. Except from minor formatting and spelling updates, these patches re-arrange the transhuge.rst so that userspace interface description will not be interleaved with the implementation details and it would be possible to split the userspace rel

[PATCH 3/3] ARM: dts: imx: add cooling-cells for cpufreq cooling device

Add #cooling-cells for i.MX6/7 SoCs for cpufreq cooling device usage. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6dl.dtsi | 1 + arch/arm/boot/dts/imx6q.dtsi | 1 + arch/arm/boot/dts/imx6sl.dtsi | 1 + arch/arm/boot/dts/imx6sx.dtsi | 1 + arch/arm/boot/dts/imx6ul.dtsi | 1 + arch/arm/b

[PATCH 1/3] thermal: imx: remove cpufreq cooling registration

This patch removes cpufreq cooling registration in thermal .probe function, cpufreq cooling should be done in cpufreq driver when it is ready. Signed-off-by: Anson Huang --- drivers/thermal/imx_thermal.c | 16 1 file changed, 16 deletions(-) diff --git a/drivers/thermal/imx_the

[PATCH 1/3] docs/vm: transhuge: change sections order

so that userspace interface and implementation description will be grouped together Signed-off-by: Mike Rapoport --- Documentation/vm/transhuge.rst | 82 +- 1 file changed, 41 insertions(+), 41 deletions(-) diff --git a/Documentation/vm/transhuge.rst b/Do

[PATCH 2/3] docs/vm: transhuge: minor updates

Some formatting changes and addition of a sentence introducing khugepaged Signed-off-by: Mike Rapoport --- Documentation/vm/transhuge.rst | 47 -- 1 file changed, 36 insertions(+), 11 deletions(-) diff --git a/Documentation/vm/transhuge.rst b/Documentatio

[PATCH 3/3] docs/vm: transhuge: split userspace bits to admin-guide/mm/transhuge

Signed-off-by: Mike Rapoport --- Documentation/admin-guide/kernel-parameters.txt | 3 +- Documentation/admin-guide/mm/index.rst | 1 + Documentation/admin-guide/mm/transhuge.rst | 418 Documentation/vm/transhuge.rst | 414 +--

[PATCH 2/3] cpufreq: imx6q: add cpufreq cooling device based on device tree

Register the imx6q cpufreq driver as a cooling device based on the thermal device tree framework. When temperature exceeds the passive trip point, cpufreq driver will be used to throttle CPUs. Signed-off-by: Anson Huang --- drivers/cpufreq/imx6q-cpufreq.c | 9 + 1 file changed, 9 insert

[no subject]

пользователь веб-почты Обратите внимание, что 95% ваших писем, полученных после обновления сервера веб-почты в последнее время в нашей базе данных, были отложены. Регулярно получать и отправлять свои сообщения. Техническая команда нашей веб-почты обновит вашу учетную запись в течение 3 рабочи

Re: [GIT PULL] tee driver fixes for v4.17

On Mon, May 07, 2018 at 02:47:31PM +0200, Jens Wiklander wrote: > Hello arm-soc maintainers, > > Please pull these tee driver fixes. Of particular interest is a fix for a > use-after-free issue. There's also a fix making sure that memory references > are kept within the used shm object. > > Thank

Re: [Ksummit-discuss] bug-introducing patches

On Mon, 14 May 2018 10:00:30 +0200 Geert Uytterhoeven wrote: > On Tue, May 1, 2018 at 10:00 PM, Sasha Levin > wrote: > > On Tue, May 01, 2018 at 03:44:50PM -0400, Theodore Y. Ts'o wrote: > >>On Tue, May 01, 2018 at 04:38:21PM +, Sasha Levin wrote: > >>> - A merge window commit spent 50%

Re: [PATCH net-next] net: phy: sfp: handle cases where neither BR,min nor BR,max is given

Hi Russell, On Tue, May 08, 2018 at 01:30:26PM +0100, Russell King - ARM Linux wrote: > > The electronic engineer in me says that using zero isn't really valid > because there are coupling capacitors in the SFP module that block DC. > These blocking capacitors are required by the SFP+ specs to ha

[PATCH 01/19 v3] regulator: fixed: Convert to use GPIO descriptor only

As we augmented the regulator core to accept a GPIO descriptor instead of a GPIO number, we can augment the fixed GPIO regulator to look up and pass that descriptor directly from device tree or board GPIO descriptor look up tables. Some boards just auto-enumerate their fixed regulator platform dev

Re: [PATCH v5 17/23] iommu/vt-d: report non-recoverable faults to device

Hi, On 05/12/2018 04:54 AM, Jacob Pan wrote: > Currently, dmar fault IRQ handler does nothing more than rate > limited printk, no critical hardware handling need to be done > in IRQ context. Not exactly. dmar_fault() needs to clear all the faults so that the subsequent faults could be logged. >

[PATCH 06/19 v3] regulator: lm363x: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number, pass a descriptor looked up with the standard devm_gpiod_get_index_optional() call. Signed-off-by: Linus Walleij --- ChangeLog v2->v3: - Resending. ChangeLog v1->v2: - Rebase the patch on the other changes. --- drivers/regulator/lm363x-regulator.c | 20 ++

[PATCH 05/19 v3] regulator: max77686: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number, pass a descriptor looked up from the device tree configuration node. Cc: Chanwoo Choi Cc: Krzysztof Kozlowski Cc: Bartlomiej Zolnierkiewicz Signed-off-by: Linus Walleij --- ChangeLog v2->v3: - Name the regulator "max77686-regulator" - Set the regulator

[PATCH 04/19 v3] regulator: max8973: Pass descriptor instead of GPIO number

Instead of passing a global GPIO number, pass a descriptor looked up with the standard devm_gpiod_get_optional() call. Cc: Mikko Perttunen Cc: Laxman Dewangan Signed-off-by: Linus Walleij --- ChangeLog v2->v3: - Resending. ChangeLog v1->v2: - Rebase the patch on the other changes. --- drivers/

[PATCH 02/19 v3] regulator: gpio: Get enable GPIO using GPIO descriptor

We augment the GPIO regulator to get the *enable* regulator GPIO line (not the other lines) using a descriptor rather than a global number. We then pass this into the regulator core which has been prepared to hande enable descriptors in a separate patch. Switch over the two boardfiles using this

Re: drivers/edac/skx_edac.c:399: undefined reference to `nfit_get_smbios_id'

On Mon, 14 May 2018 10:12:00 +0200, Borislav Petkov wrote: > On Mon, May 14, 2018 at 10:05:30AM +0200, Jean Delvare wrote: > > I'll send a candidate fix shortly. > > https://lkml.kernel.org/r/3af91354-8e19-d2af-1bba-ced8dce05...@infradead.org Thanks for the link, apparently I'm late to the part

Re: [PATCH v2 0/9] Input: support for latest Lenovo thinkpads (series 80)

Hi Dmitry, This is your monthly reminder of the Lenov 80 pending series :) Could you consider taking this series and Aaron's patch? Cheers, Benjamin On Tue, Apr 17, 2018 at 1:42 PM, Aaron Ma wrote: > Hi Dmitry and Benjamin: > > Could you apply my patch too? > > It add LEN0096 that Benjamin's pa

Re: [PATCH 03/21] clk: sunxi-ng: Enable DE2_CCU for Allwinner 64-bit SoCs

On Tue, May 1, 2018 at 9:53 PM, Chen-Yu Tsai wrote: > On Mon, Apr 30, 2018 at 7:40 PM, Jagan Teki > wrote: >> Allwinner 64-bit SoC like H5/A64 has DE2 CCU so enable them >> as default. >> >> Signed-off-by: Jagan Teki >> --- >> drivers/clk/sunxi-ng/Kconfig | 2 ++ >> 1 file changed, 2 insertion

[PATCH] PM / core: refactor PM_OPS initializers

With current implementation of PM_OPS initializers users should annotate all PM callbacks with __maybe_unused attribute to prevent compiler from complaining in case respective option is not enabled. Using ternary operator with IS_ENABLED(symbol) as a condition allows to avoid marking these function

Re: [PATCH] md/raid1: add error handling of read error from FailFast device

On Wed, May 9, 2018 at 10:58 AM, Jack Wang wrote: > -- Forwarded message -- > From: Gioh Kim > Date: 2018-05-02 13:08 GMT+02:00 > Subject: [PATCH] md/raid1: add error handling of read error from FailFast > device > To: s...@kernel.org > 抄送： linux-r...@vger.kernel.org, linux-kerne

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

On Mon, May 14, 2018 at 12:51:39PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: The look entirely correct, but oddly enough my compiler did not bother to warn. Fix below: -- >From 6610bd5bbbf05

Re: Allwinner A64: Issue on external rtc clock to wifi chip

On Mon, May 14, 2018 at 01:34:56PM +0530, Jagan Teki wrote: > On Mon, May 14, 2018 at 1:27 PM, Maxime Ripard > wrote: > > Hi, > > > > On Mon, May 14, 2018 at 12:37:49PM +0530, Jagan Teki wrote: > >> Hi Maxime and All, > >> > >> We are trying to bring-up AP6330 Wifi chip for A64 board. We noticed >

Re: [PATCH 4.14 00/62] 4.14.41-stable review

On Mon, May 14, 2018 at 08:48:16AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.41 release. > There are 62 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know

Re: [Ksummit-discuss] bug-introducing patches

Hi Boris, On Mon, May 14, 2018 at 10:12 AM, Boris Brezillon wrote: > On Mon, 14 May 2018 10:00:30 +0200 > Geert Uytterhoeven wrote: >> On Tue, May 1, 2018 at 10:00 PM, Sasha Levin >> wrote: >> > On Tue, May 01, 2018 at 03:44:50PM -0400, Theodore Y. Ts'o wrote: >> >>On Tue, May 01, 2018 at 04:38

Re: [PATCH 00/13] [v4] x86, pkeys: two protection keys bug fixes

* Dave Hansen wrote: > Hi x86 maintainers, > > This set has been seen quite a few changes and additions since the > last post. Details below. > > Changes from v3: > * Reordered patches following Ingo's recommendations: Introduce >failing selftests first, then the kernel code to fix the t

Re: [PATCH] HID: i2c-hid: check if device is there before really probing

On Wed, May 9, 2018 at 9:12 PM, Dmitry Torokhov wrote: > From: Dmitry Torokhov > > On many Chromebooks touch devices are multi-sourced; the components are > electrically compatible and one can be freely swapped for another without > changing the OS image or firmware. > > To avoid bunch of scary m

Build regressions/improvements in v4.17-rc5

Below is the list of build error/warning regressions/improvements in v4.17-rc5[1] compared to v4.16[2]. Summarized: - build errors: +6/-11 - build warnings: +1214/-1580 JFYI, when comparing v4.17-rc5[1] to v4.17-rc4[3], the summaries are: - build errors: +4/-1 - build warnings: +214/-244

Re: [PATCH RFC 10/19] perf tools: Create maps for x86_64 KPTI entry trampolines

* Adrian Hunter wrote: > Create maps for x86_64 KPTI entry trampolines, based on symbols found in > kallsyms. It is also necessary to keep track of whether the trampolines > have been mapped particularly when the kernel dso is kcore. > > Signed-off-by: Adrian Hunter > --- > tools/perf/util/ma

Re: [PATCH 09/21] arm64: dts: allwinner: a64: Add HDMI support

On Wed, May 2, 2018 at 5:04 PM, Maxime Ripard wrote: > Hi, > > On Mon, Apr 30, 2018 at 05:10:46PM +0530, Jagan Teki wrote: >> + hdmi_phy: hdmi-phy@1ef { >> + compatible = "allwinner,sun50i-a64-hdmi-phy", >> + "allwinner,sun8i-h3-

Re: [PATCH 6/7] psi: pressure stall information for CPU, memory, and IO

On Thu, May 10, 2018 at 09:41:32AM -0400, Johannes Weiner wrote: > So there is a reason I'm tracking productivity states per-cpu and not > globally. Consider the following example periods on two CPUs: > > CPU 0 > Task 1: | EXECUTING | memstalled | > Task 2: | runqueued | EXECUTING | > >

Re: [PATCH 1/3] thermal: imx: remove cpufreq cooling registration

On Mon, May 14, 2018 at 04:09:17PM +0800, Anson Huang wrote: > This patch removes cpufreq cooling registration in > thermal .probe function, cpufreq cooling should be > done in cpufreq driver when it is ready. > > Signed-off-by: Anson Huang > --- Acked-by: Daniel Lezcano --

Re: [Ksummit-discuss] bug-introducing patches

On Mon, 14 May 2018 10:29:04 +0200 Geert Uytterhoeven wrote: > Hi Boris, > > On Mon, May 14, 2018 at 10:12 AM, Boris Brezillon > wrote: > > On Mon, 14 May 2018 10:00:30 +0200 > > Geert Uytterhoeven wrote: > >> On Tue, May 1, 2018 at 10:00 PM, Sasha Levin > >> wrote: > >> > On Tue, May 01,

Re: Build regressions/improvements in v4.17-rc5

On Mon, May 14, 2018 at 10:31 AM, Geert Uytterhoeven wrote: > JFYI, when comparing v4.17-rc5[1] to v4.17-rc4[3], the summaries are: > - build errors: +4/-1 + /kisskb/src/arch/sh/boards/mach-landisk/setup.c: error: implicit declaration of function 'ioremap_prot' [-Werror=implicit-function-decl

Re: [Ksummit-discuss] bug-introducing patches

On 9 May 2018 at 12:47, Stephen Rothwell wrote: > On Wed, 9 May 2018 18:03:46 +0900 Mark Brown wrote: >> >> On Wed, May 09, 2018 at 10:47:57AM +0200, Daniel Vetter wrote: >> > On Wed, May 9, 2018 at 10:44 AM, Mark Brown wrote: >> >> > > I think this is an excellent idea, copying in Stephen for h

Re: [PATCH net-next v2 06/13] phy: add 2.5G SGMII mode to the phy_mode enum

Hi Russell, On Tue, May 08, 2018 at 01:34:08PM +0100, Russell King - ARM Linux wrote: > On Fri, May 04, 2018 at 03:56:36PM +0200, Antoine Tenart wrote: > > This patch adds one more generic PHY mode to the phy_mode enum, to allow > > configuring generic PHYs to the 2.5G SGMII mode by using the set_

Re: [PATCH 1/4] drm/panel: otm8009a: fix backlight updates

Hi Philippe, Reviewed-by: Vincent Abriou BR Vincent On 04/23/2018 04:10 PM, Philippe Cornu wrote: > Backlight updates was not working anymore since the good > implementation of the dsi lpm mode in the dsi host driver. > After a longer analysis, the backlight updates in dsi video > mode require

Re: [PATCH v5 5/7] proc: instantiate only pids that we can ptrace on 'limit_pids=1' mount option

On Fri, May 11, 2018 at 09:45:33AM -0700, Linus Torvalds wrote: > On Fri, May 11, 2018 at 2:46 AM Alexey Gladkov > wrote: > > > + /* Limit procfs to only ptracable tasks */ > > + if (limit_pids == PROC_LIMIT_PIDS_PTRACE) { > > + cond_resched(); > > + if (!h

Re: [PATCH 2/4] drm/panel: otm8009a: fix glitches by moving backlight enable to otm8009a_enable()

Hi Philippe, Reviewed-by: Vincent Abriou BR Vincent On 04/23/2018 04:10 PM, Philippe Cornu wrote: > The backlight 1st update was in the otm8009a_prepare() function > for a bad reason: backlight was not working in video mode and the > otm8009a_prepare() is in command mode for the init sequence.

Re: [PATCH 1/3] thermal: imx: remove cpufreq cooling registration

Hi, On 05/14/2018 10:09 AM, Anson Huang wrote: This patch removes cpufreq cooling registration in thermal .probe function, cpufreq cooling should be done in cpufreq driver when it is ready. Signed-off-by: Anson Huang It seems you are trying to achieve something similar to a patch I sent a co

Re: [PATCH 3/4] drm/panel: otm8009a: no message if probe success

Hi Philippe, Reviewed-by: Vincent Abriou BR Vincent On 04/23/2018 04:10 PM, Philippe Cornu wrote: > Remove the message in case of probe success. This comes from > a suggestion followed in the recent integration of the > raydium rm68200 panel. > > Signed-off-by: Philippe Cornu > --- > driver

Re: [PATCH 4/4] drm/panel: otm8009a: use new backlight api

Hi Philippe, Reviewed-by: Vincent Abriou BR Vincent On 04/23/2018 04:10 PM, Philippe Cornu wrote: > Use the new backlight api. > > Signed-off-by: Philippe Cornu > --- > drivers/gpu/drm/panel/panel-orisetech-otm8009a.c | 26 > > 1 file changed, 9 insertions(+), 17

Re: [PATCH 1/2] USB: dwc3: get extcon device by OF graph bindings

On 31.01.2018 16:57, Andrzej Hajda wrote: > extcon device is used to detect host/device connection. Since extcon > OF property is deprecated, alternative method should be added. > This method uses OF graph bindings to locate extcon. > > Signed-off-by: Andrzej Hajda Ping, 3.5 months passed. Regar

Re: [GIT PULL 1/2] ARM: SOC driver update v4.18

On Tue, May 08, 2018 at 02:41:36PM -0700, Santosh Shilimkar wrote: > The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: > > Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/ssant

Re: [GIT PULL 1/2] ARM: SOC driver update v4.18

Hi Santosh, On Tue, May 08, 2018 at 02:41:36PM -0700, Santosh Shilimkar wrote: > The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: > > Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/ker

Re: [PATCH 09/21] arm64: dts: allwinner: a64: Add HDMI support

On Mon, May 14, 2018 at 02:03:36PM +0530, Jagan Teki wrote: > On Wed, May 2, 2018 at 5:04 PM, Maxime Ripard > wrote: > > Hi, > > > > On Mon, Apr 30, 2018 at 05:10:46PM +0530, Jagan Teki wrote: > >> + hdmi_phy: hdmi-phy@1ef { > >> + compatible = "allwinner,sun50

Re: [PATCH v3] bus: arm-cci: remove unnecessary unreachable()

On Tue, May 08, 2018 at 04:27:26PM +0200, Stefan Agner wrote: > Mixing asm and C code is not recommended in a naked function by > gcc and leads to an error when using clang: > drivers/bus/arm-cci.c:2107:2: error: non-ASM statement in naked > function is not supported > unreachable(); >

Re: [Ksummit-discuss] bug-introducing patches

Hi Boris, On Mon, May 14, 2018 at 10:34 AM, Boris Brezillon wrote: > On Mon, 14 May 2018 10:29:04 +0200 > Geert Uytterhoeven wrote: >> On Mon, May 14, 2018 at 10:12 AM, Boris Brezillon >> wrote: >> > On Mon, 14 May 2018 10:00:30 +0200 >> > Geert Uytterhoeven wrote: >> >> On Tue, May 1, 2018 at

Re: [PATCH v5 5/7] proc: instantiate only pids that we can ptrace on 'limit_pids=1' mount option

On Fri, May 11, 2018 at 09:09:04AM -0700, Randy Dunlap wrote: > On 05/11/2018 02:36 AM, Alexey Gladkov wrote: > > From: Djalal Harouni > > > > If "limit_pids=1" mount option is set then do not instantiate pids that > > we can not ptrace. "limit_pids=1" means that procfs should only contain > > pi

Re: [PATCH] gpu: host1x: Fix compiler errors

On Mon, Mar 26, 2018 at 04:44:14PM +0200, Emil Goode wrote: > The compiler is complaining with the following errors: > > drivers/gpu/host1x/cdma.c:94:48: error: > passing argument 3 of ‘dma_alloc_wc’ from incompatible pointer type > [-Werror=incompatible-pointer-types] > > drivers/gpu

Re: [PATCH v1] gpu: host1x: Fix dma_free_wc() argument in the error path

On Mon, Apr 23, 2018 at 12:54:56PM +0300, Dmitry Osipenko wrote: > If IOVA allocation or IOMMU mapping fails, dma_free_wc() is invoked with > size=0 because of a typo, that triggers "kernel BUG at mm/vmalloc.c:124!". > > Signed-off-by: Dmitry Osipenko > --- > drivers/gpu/host1x/cdma.c | 2 +- >

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