[tip:core/stacktrace] backtrace-test: Simplify stack trace handling

Commit-ID: 1b59562d3ab09dcef188eb8055d05f0336380394 Gitweb: https://git.kernel.org/tip/1b59562d3ab09dcef188eb8055d05f0336380394 Author: Thomas Gleixner AuthorDate: Thu, 25 Apr 2019 11:44:57 +0200 Committer: Thomas Gleixner CommitDate: Mon, 29 Apr 2019 12:37:47 +0200 backtrace-test:

[tip:core/stacktrace] mm/page_owner: Simplify stack trace handling

Commit-ID: af52bf6b92f7d8783c1e712cad6ef7d37cd773b2 Gitweb: https://git.kernel.org/tip/af52bf6b92f7d8783c1e712cad6ef7d37cd773b2 Author: Thomas Gleixner AuthorDate: Thu, 25 Apr 2019 11:45:03 +0200 Committer: Thomas Gleixner CommitDate: Mon, 29 Apr 2019 12:37:50 +0200 mm/page_owner:

[tip:core/stacktrace] mm/kmemleak: Simplify stacktrace handling

Commit-ID: 07984aad1c7ed679596f849c0e7d5e029f76e0eb Gitweb: https://git.kernel.org/tip/07984aad1c7ed679596f849c0e7d5e029f76e0eb Author: Thomas Gleixner AuthorDate: Thu, 25 Apr 2019 11:45:01 +0200 Committer: Thomas Gleixner CommitDate: Mon, 29 Apr 2019 12:37:49 +0200 mm/kmemleak:

[tip:core/stacktrace] stacktrace: Provide helpers for common stack trace operations

Commit-ID: e9b98e162aa53cbea7c8b0d6c9d5dc6e0f822b9c Gitweb: https://git.kernel.org/tip/e9b98e162aa53cbea7c8b0d6c9d5dc6e0f822b9c Author: Thomas Gleixner AuthorDate: Thu, 25 Apr 2019 11:44:55 +0200 Committer: Thomas Gleixner CommitDate: Mon, 29 Apr 2019 12:37:46 +0200 stacktrace:

[tip:core/stacktrace] proc: Simplify task stack retrieval

Commit-ID: e988e5ec18d6081efbef645fc2690298ee23a8db Gitweb: https://git.kernel.org/tip/e988e5ec18d6081efbef645fc2690298ee23a8db Author: Thomas Gleixner AuthorDate: Thu, 25 Apr 2019 11:44:58 +0200 Committer: Thomas Gleixner CommitDate: Mon, 29 Apr 2019 12:37:48 +0200 proc: Simplify

[tip:core/stacktrace] lib/stackdepot: Provide functions which operate on plain storage arrays

Commit-ID: c0cfc337264c5e02e0bc79de6b62857999588879 Gitweb: https://git.kernel.org/tip/c0cfc337264c5e02e0bc79de6b62857999588879 Author: Thomas Gleixner AuthorDate: Thu, 25 Apr 2019 11:44:56 +0200 Committer: Thomas Gleixner CommitDate: Mon, 29 Apr 2019 12:37:47 +0200 lib/stackdepot:

[tip:core/stacktrace] tracing: Cleanup stack trace code

Commit-ID: 3d9a8072915366b5932beeed97f158f8d4955768 Gitweb: https://git.kernel.org/tip/3d9a8072915366b5932beeed97f158f8d4955768 Author: Thomas Gleixner AuthorDate: Thu, 25 Apr 2019 11:44:54 +0200 Committer: Thomas Gleixner CommitDate: Mon, 29 Apr 2019 12:37:46 +0200 tracing: Cleanup

Re: [RFC PATCH 2/7] x86/sci: add core implementation for system call isolation

On Sat, 27 Apr 2019, Ingo Molnar wrote: > - A C language runtime that is a subset of current C syntax and >semantics used in the kernel, and which doesn't allow access outside >of existing objects and thus creates a strictly enforced separation >between memory used for data, and

Re: [PATCH v2 4/7] mmc: meson-gx: disable HS400

Hi Jerome, On Mon, Apr 29, 2019 at 10:29 AM Jerome Brunet wrote: > > On Sat, 2019-04-27 at 22:02 +0200, Martin Blumenstingl wrote: > > Hi Jerome, > > > > On Tue, Apr 23, 2019 at 11:03 AM Jerome Brunet wrote: > > > At the moment, all our attempts to enable HS400 on Amlogic chipsets have > > >

Re: [PATCH] ASoC: Intel: avoid Oops if DMA setup fails

On Fri, Apr 26, 2019 at 06:52:45PM +, Sasha Levin wrote: > Hi, > > [This is an automated email] > > This commit has been processed because it contains a -stable tag. > The stable tag indicates that it's relevant for the following trees: all > > The bot has tested the following trees:

Re: [PATCH 3/4] x86/ftrace: make ftrace_int3_handler() not to skip fops invocation

On Mon, Apr 29, 2019 at 11:06 AM Linus Torvalds wrote: > > > It does *not* emulate the "call" in the BP handler itself, instead if > replace the %ip (the same way all the other BP handlers replace the > %ip) with a code sequence that just does > > push %gs:bp_call_return > jmp

[PATCH v2] ASoC: Intel: avoid Oops if DMA setup fails

Currently in sst_dsp_new() if we get an error return from sst_dma_new() we just print an error message and then still complete the function successfully. This means that we are trying to run without sst->dma properly set up, which will result in NULL pointer dereference when sst->dma is later

Re: [PATCH] driver core: platform: Fix the usage of platform device name(pdev->name)

lowed by a crash in tty_init_dev(). Bisect log for m68k attached below. Reverting this patch fixes the problem at least for arm, m68k, and mips images. Guenter --- # bad: [3d17a1de96a233cf89bfbb5a77ebb1a05c420681] Add linux-next specific files for 20190429 # good: [085b7755808aa11f78ab9377257e1dad2e

Re: [GIT PULL] Please pull rdma.git

On Mon, 2019-04-29 at 21:00 +0300, Leon Romanovsky wrote: > On Mon, Apr 29, 2019 at 01:13:01PM -0400, Doug Ledford wrote: > > On Mon, 2019-04-29 at 09:48 -0700, Linus Torvalds wrote: > > > On Mon, Apr 29, 2019 at 9:29 AM Doug Ledford wrote: > > > > drivers/infiniband/core/uverbs_main.c | 2 +- >

Re: [PATCH 2/6] dt-bindings: riscv: sifive: add YAML documentation for the SiFive FU540

On Mon, 29 Apr 2019, Rob Herring wrote: > On Thu, Apr 11, 2019 at 01:43:00AM -0700, Paul Walmsley wrote: > > Add YAML DT binding documentation for the SiFive FU540 SoC. This > > SoC is documented at: > > > > https://static.dev.sifive.com/FU540-C000-v1.0.pdf > > > > Passes dt-doc-validate,

Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia)

On Mon 2019-04-29 19:51:40, Enrico Weigelt, metux IT consult wrote: > On 29.04.19 18:53, Pavel Machek wrote: > >>> Theoretically. But we both now that probability of that is very low, > >>> and that likely driver would need other updates, too... right? > >> > >> What would be the benefit to add

Re: [PATCH 3/4] x86/ftrace: make ftrace_int3_handler() not to skip fops invocation

On Sun, Apr 28, 2019 at 10:38 AM Steven Rostedt wrote: > > For optimization reasons, if there's only a single user of a function > it gets its own trampoline that sets up the call to its callback and > calls that callback directly: So this is the same issue as the static calls, and it has

Re: [PATCH 1/1] clk: stm32mp1: Add ddrperfm clock

Quoting Gerald BAEZA (2019-04-29 02:54:44) > From: Gabriel Fernandez > > Add ddrperfm clock for DDR Performance Monitor driver > > Signed-off-by: Gabriel Fernandez > Signed-off-by: Gerald Baeza > --- Applied to clk-next

Re: [PATCH 2/6] dt-bindings: riscv: sifive: add YAML documentation for the SiFive FU540

On Thu, Apr 11, 2019 at 01:43:00AM -0700, Paul Walmsley wrote: > Add YAML DT binding documentation for the SiFive FU540 SoC. This > SoC is documented at: > > https://static.dev.sifive.com/FU540-C000-v1.0.pdf > > Passes dt-doc-validate, as of yaml-bindings commit 4c79d42e9216. > >

Re: [GIT PULL] Please pull rdma.git

On Mon, Apr 29, 2019 at 01:13:01PM -0400, Doug Ledford wrote: > On Mon, 2019-04-29 at 09:48 -0700, Linus Torvalds wrote: > > On Mon, Apr 29, 2019 at 9:29 AM Doug Ledford wrote: > > > > > > drivers/infiniband/core/uverbs_main.c | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > >

Re: [PATCH v2 5/6] dt-bindings: leds: Add LED bindings for the LM36274

On Wed, 10 Apr 2019 08:38:32 -0500, Dan Murphy wrote: > Add the LM36274 LED specific bindings. > > Signed-off-by: Dan Murphy > --- > > v2 - Changed 29-V to 29V - https://lore.kernel.org/patchwork/patch/1058779/ > > .../devicetree/bindings/leds/leds-lm36274.txt | 82 +++ > 1

Re: [PATCH v2 2/6] dt-bindings: mfd: Add lm36274 bindings to ti-lmu

On Wed, 10 Apr 2019 08:38:29 -0500, Dan Murphy wrote: > Add the LM36274 backlight driver with regulator support. > This is a multi-function device for backlight applications. > > Backlight properties will be documented in it's a supplemental > bindings document. > > Regulator support is

[PATCH 1/1] thermal: Fix build error of missing devm_ioremap_resource on UM

The devres.o gets linked if HAS_IOMEM is present so on ARCH=um allyesconfig (COMPILE_TEST) failed on many files with: drivers/thermal/thermal_mmio.o: In function 'thermal_mmio_probe':thermal_mmio.c:(.text+0xe1): undefined reference to `devm_ioremap_resource' The users of devm_ioremap_resource()

Re: [PATCH v2] ALSA: usx2y: fix a double free bug

On Mon, 29 Apr 2019 19:45:40 +0200, Wenwen Wang wrote: > > In usX2Y_In04_init(), a new urb is firstly created through usb_alloc_urb() > and saved to 'usX2Y->In04urb'. Then, a buffer is allocated through > kmalloc() and saved to 'usX2Y->In04Buf'. If the allocation of the buffer > fails, the error

[PATCH] staging: iio: adt7316: match parenthesis alignment

This patch solves the following checkpatch.pl message: CHECK: Alignment should match open parenthesis. This makes the file more compliant with the preferred coding style for the Linux kernel. Signed-off-by: João Seckler --- drivers/staging/iio/addac/adt7316.c | 2 +- 1 file changed, 1

Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia)

On 29.04.19 18:53, Pavel Machek wrote: >>> Theoretically. But we both now that probability of that is very low, >>> and that likely driver would need other updates, too... right? >> >> What would be the benefit to add ARM dependency? So that distro >> compilations don't ship the turris_omnia

Re: [PATCH] of: del redundant type conversion

On Wed, Apr 10, 2019 at 04:29:41PM +0800, xiaojiangfeng wrote: > The type of variable l in early_init_dt_scan_chosen is > int, there is no need to convert to int. > > Signed-off-by: xiaojiangfeng > --- > drivers/of/fdt.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Applied. Rob

Re: [PATCH 1/2] dt-bindings: arm: fsl: Add support for imx6ul-pico-nymph

On Tue, 9 Apr 2019 22:00:12 -0300, Otavio Salvador wrote: > From: Fabio Estevam > > Add support for TechNexion's imx6ul-pico-nymph board. > > Signed-off-by: Fabio Estevam > Signed-off-by: Otavio Salvador > --- > > Documentation/devicetree/bindings/arm/fsl.yaml | 1 + > 1 file changed, 1

Re: [PATCHv1 2/6] dt-bindings, firmware: add Intel Stratix10 remote system update binding

On Tue, Apr 09, 2019 at 01:45:58PM -0500, richard.g...@linux.intel.com wrote: > From: Richard Gong > > Add a device tree binding for the Intel Stratix10 remote system > update (RSU) driver > > Signed-off-by: Richard Gong > Reviewed-by: Alan Tull > --- >

Re: [PATCH] driver core: platform: Fix the usage of platform device name(pdev->name)

quot;vexpress-syscfg.6.auto". The effect - none of > AMBA devices are registered, including missing MMC device (mmci.c, > arm,pl180). > > One can see the error of missing root device: > [ 13.458982] VFS: Cannot open root device "mmcblk0" or > unknown-block(0,0

[PATCH v2] ALSA: usx2y: fix a double free bug

In usX2Y_In04_init(), a new urb is firstly created through usb_alloc_urb() and saved to 'usX2Y->In04urb'. Then, a buffer is allocated through kmalloc() and saved to 'usX2Y->In04Buf'. If the allocation of the buffer fails, the error code ENOMEM is returned after usb_free_urb(), which frees the

Re: [PATCH 2/6] dt-bindings: media: sun6i-csi: Add compatible string for A83T variant

On Tue, 9 Apr 2019 00:57:40 +0800, Chen-Yu Tsai wrote: > From: Chen-Yu Tsai > > The A83T SoC has a camera sensor interface (known as CSI in Allwinner > lingo), which is similar to the one found on the A64 and H3. The only > difference seems to be that support of MIPI CSI through a connected >

Re: [PATCH v2 35/36] [RFC] coresight: add return value for fixup connections

On Mon, Apr 15, 2019 at 05:04:18PM +0100, Suzuki K Poulose wrote: > Handle failures in fixing up connections for a newly registered > device. This will be useful to handle cases where we fail to expose > the links via sysfs for the connections. > > Cc: Mathieu Poirier > Signed-off-by: Suzuki K

Re: [PATCH] PCI: Add link_change error handler and vfio-pci user

On Mon, Apr 29, 2019 at 08:51:04AM -0600, Alex Williamson wrote: > On Wed, 24 Apr 2019 12:57:58 -0500 > Bjorn Helgaas wrote: > > > On Tue, Apr 23, 2019 at 04:42:28PM -0600, Alex Williamson wrote: > > > The PCIe bandwidth notification service generates logging any time a > > > link changes speed

Re: [PATCH v2 34/36] [RFC] coresight: Pass coresight_device for coresight_release_platform_data

On Mon, Apr 15, 2019 at 05:04:17PM +0100, Suzuki K Poulose wrote: > As we prepare to expose the links between the devices in > sysfs, pass the coresight_device instance to the > coresight_release_platform_data in order to free up the connections > when the device is removed. > > No functional

Re: [PATCH] dt-bindings: mfd: axp20x: Add fallback for axp805

On Tue, Apr 09, 2019 at 06:05:50PM +0200, Clément Péron wrote: > axp805 is actually compatible and used with axp806 as fallback. > But it's actually undocumented and trig a warning with checkpatch. > > DT compatible string "x-powers,axp805" appears un-documented. > > Add this compatible in the

[PATCH 1/2] arm64: fix pte_unmap() -Wunused-but-set-variable

Many compilation warnings due to pte_unmap() compiles away. Fixed it by making it an static inline function. mm/gup.c: In function 'gup_pte_range': mm/gup.c:1727:16: warning: variable 'ptem' set but not used [-Wunused-but-set-variable] mm/gup.c: At top level: mm/memory.c: In function

Re: [PATCH v2 2/2] net: phy: realtek: Change TX-delay setting for RGMII modes only

On 4/26/19 4:35 PM, Serge Semin wrote: > On Fri, Apr 26, 2019 at 11:46:31PM +0200, Andrew Lunn wrote: >> On Sat, Apr 27, 2019 at 12:21:12AM +0300, Serge Semin wrote: >>> It's prone to problems if delay is cleared out for other than RGMII >>> modes. So lets set/clear the TX-delay in the config

[PATCH 1/2] ARM: exynos: Make ARCH_EXYNOS3 a default option

By default for ARMv7 Exynos platform we select all flavors. One kernel image simplifies testing and maintenance. However Exynos3 was not selected by default so far (thus it lacked in multi_v7 kernel). Signed-off-by: Krzysztof Kozlowski --- arch/arm/mach-exynos/Kconfig | 1 + 1 file changed, 1

[PATCH 2/2] arm64: remove pte_unmap_nested()

Due to the commit ece0e2b6406a ("mm: remove pte_*map_nested()"), pte_unmap_nested() is not used anymore. Signed-off-by: Qian Cai --- arch/arm64/include/asm/pgtable.h | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h index

[PATCH 2/2] ARM: exynos_defconfig: Trim and reorganize with savedefconfig

Trim and reorganize the defconfig with savedefconfig on latest linux-next. The ARCH_EXYNOS3 is removed because it become the default. Signed-off-by: Krzysztof Kozlowski --- arch/arm/configs/exynos_defconfig | 62 ++- 1 file changed, 27 insertions(+), 35 deletions(-)

Re: [PATCH v2 2/6] dt-bindings: mfd: LMU: Add ti,brightness-resolution

On Fri, 5 Apr 2019 09:28:51 -0500, Dan Murphy wrote: > Add ti,brightness-resolution to the TI LMU binding to define > whether the device uses 8-bit brightness or 11-bit brightness. > > Signed-off-by: Dan Murphy > --- > > v2 - New patch. Add brightness resolution to ti-lmu.txt. See patch

Re: RFC: on adding new CLONE_* flags [WAS Re: [PATCH 0/4] clone: add CLONE_PIDFD]

On 29.04.19 17:49, Serge E. Hallyn wrote: >> * all users are equal - no root at all. the only exception is the>> >> initial process, which gets the kernel devices mounted into his>> namespace.> > This does not match my understanding, but I'm most likely wrong. (I thought> there was an actual

[PATCH] ARM: dts: exynos: Move CPU OPP tables out of SoC node on Exynos5420

The cpus node is a top-level node, not inside the soc. Therefore its OPP tables should be there as well. This also fixes the DTC warnings like: arch/arm/boot/dts/exynos5420.dtsi:46.37-109.5: Warning simple_bus_reg): /soc/opp_table0: missing or empty reg/ranges property

Re: [PATCH 1/2] dt-bindings: arm: fsl: Add support for imx6ul-pico-dwarf

On Sun, 7 Apr 2019 16:37:22 -0300, Otavio Salvador wrote: > From: Fabio Estevam > > Add support for TechNexion's imx6ul-pico-dwarf board. > > Signed-off-by: Fabio Estevam > Signed-off-by: Otavio Salvador > --- > > Documentation/devicetree/bindings/arm/fsl.yaml | 1 + > 1 file changed, 1

Re: [PATCH v2 1/6] dt-bindings: mfd: LMU: Add the ramp up/down property

On Fri, 5 Apr 2019 09:28:50 -0500, Dan Murphy wrote: > Document the ramp-up and ramp-down property in the binding. > Removing the "sec" from the property definition as seconds is > implied. > > Signed-off-by: Dan Murphy > --- > > v2 - Fixed commit message as this was not just a modification but

Re: [PATCH v2 4/6] dt-bindings: ti-lmu: Modify dt bindings for the LM3697

On Fri, 5 Apr 2019 09:28:53 -0500, Dan Murphy wrote: > The LM3697 is a single function LED driver. The single function LED > driver needs to reside in the LED directory as a dedicated LED driver > and not as a MFD device. The device does have common brightness and ramp > features and those can be

Re: [PATCH 11/10] arm64: unbreak DYNAMIC_DEBUG=y build with clang

On Fri, Apr 26, 2019 at 12:06 PM Rasmus Villemoes wrote: > > Current versions of clang does not like the %c modifier in inline > assembly for targets other than x86, so any DYNAMIC_DEBUG=y build > fails on arm64. A fix is likely to land in 9.0 (see >

[PATCH v3] mmc: core: Verify SD bus width

The SD Physical Layer Spec says the following: Since the SD Memory Card shall support at least the two bus modes 1-bit or 4-bit width, then any SD Card shall set at least bits 0 and 2 (SD_BUS_WIDTH="0101"). This change verifies the card has specified a bus width. AMD SDHC Device 7806 can get

[PATCH v2] ext4: bad mount opts in no journal mode

Fixes: commit 1e381f60dad9 ("ext4: do not allow journal_opts for fs w/o journal") Instead of removing EXT4_MOUNT_JOURNAL_CHECKSUM from s_def_mount_opt as I assume was intended, all other options were blown away leading to _ext4_show_options() output being incorrect. Signed-off-by: Debabrata

Re: [PATCH] dt-bindings: mfd: LMU: Fix lm3632 dt binding example

On Fri, 5 Apr 2019 09:19:07 -0500, Dan Murphy wrote: > Fix the lm3632 dt binding examples as the LCM enable GPIOs > are defined as enable GPIOs per the regulator/lm363x-regulator.txt > bindings document. > > Signed-off-by: Dan Murphy > --- > Documentation/devicetree/bindings/mfd/ti-lmu.txt | 4

Re: [PATCH RFC 3/8] dt-bindings: exynos: Add ASV tables binding documentation

On Thu, Apr 04, 2019 at 07:17:30PM +0200, Sylwester Nawrocki wrote: > This patch adds documentation of the Exynos ASV (Adaptive Voltage Supply) > tables DT binding. > > Signed-off-by: Sylwester Nawrocki > --- > .../devicetree/bindings/arm/samsung/asv.txt | 76 +++ > 1 file

Re: [PATCH v2] soc: add aspeed folder and misc drivers

On Mon, Apr 29, 2019 at 10:19 AM Olof Johansson wrote: > > On Mon, Apr 29, 2019 at 10:16 AM Patrick Venture wrote: > > > > On Mon, Apr 29, 2019 at 10:13 AM Olof Johansson wrote: > > > > > > On Mon, Apr 29, 2019 at 10:08 AM Olof Johansson wrote: > > > > > > > > On Thu, Apr 25, 2019 at

[PATCH v2 2/3] mm: clean up is_device_*_page() definitions

Refactor is_device_{public,private}_page() with is_pci_p2pdma_page() to make them all consistent in depending on their respective config options even when CONFIG_DEV_PAGEMAP_OPS is enabled for other reasons. This allows a little more compile-time optimisation as well as the conceptual and cosmetic

Verificación de la cuenta

Aviso de seguridad: Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a todos nuestros clientes de correo web. Su cuenta de correo electrónico se actualizará a una nueva y mejorada interfaz de

[PATCH v2 0/3] Device-memory-related cleanups

Hi all, This is essentially just a repost, with the trivial typo fix plus all the acks/reviews collected. There's no direct dependency between the patches here, so hopefully at least #1 and #3 might sneak into 5.2 if there's still time, as that would save some bother for follow-up arm64 work next

[PATCH v2 1/3] mm/memremap: Rename and consolidate SECTION_SIZE

Trying to activate ZONE_DEVICE for arm64 reveals that memremap's internal helpers for sparsemem sections conflict with and arm64's definitions for hugepages, which inherit the name of "sections" from earlier versions of the ARM architecture. Disambiguate memremap (and now HMM too) by propagating

Re: [PATCH v2] soc: add aspeed folder and misc drivers

On Mon, Apr 29, 2019 at 10:16 AM Patrick Venture wrote: > > On Mon, Apr 29, 2019 at 10:13 AM Olof Johansson wrote: > > > > On Mon, Apr 29, 2019 at 10:08 AM Olof Johansson wrote: > > > > > > On Thu, Apr 25, 2019 at 07:25:49PM +0200, Greg KH wrote: > > > > On Tue, Apr 23, 2019 at 08:28:14AM

Re: [PATCH] arm64: fix pte_unmap() -Wunused-but-set-variable

On Mon, 2019-04-29 at 17:49 +0100, Will Deacon wrote: > >  arch/arm64/include/asm/pgtable.h | 4 ++-- > >  1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/arch/arm64/include/asm/pgtable.h > > b/arch/arm64/include/asm/pgtable.h > > index de70c1eabf33..7543e345e078 100644 > >

Re: [PATCH v2] soc: add aspeed folder and misc drivers

On Mon, Apr 29, 2019 at 10:13 AM Olof Johansson wrote: > > On Mon, Apr 29, 2019 at 10:08 AM Olof Johansson wrote: > > > > On Thu, Apr 25, 2019 at 07:25:49PM +0200, Greg KH wrote: > > > On Tue, Apr 23, 2019 at 08:28:14AM -0700, Patrick Venture wrote: > > > > On Tue, Apr 23, 2019 at 8:22 AM

[PATCH 2/2] memcg, fsnotify: no oom-kill for remote memcg charging

The commit d46eb14b735b ("fs: fsnotify: account fsnotify metadata to kmemcg") added remote memcg charging for fanotify and inotify event objects. The aim was to charge the memory to the listener who is interested in the events but without triggering the OOM killer. Otherwise there would be

[PATCH 1/2] memcg, oom: no oom-kill for __GFP_RETRY_MAYFAIL

The documentation of __GFP_RETRY_MAYFAIL clearly mentioned that the OOM killer will not be triggered and indeed the page alloc does not invoke OOM killer for such allocations. However we do trigger memcg OOM killer for __GFP_RETRY_MAYFAIL. Fix that. This flag will used later to not trigger

Re: [GIT PULL] Please pull rdma.git

On Mon, 2019-04-29 at 09:48 -0700, Linus Torvalds wrote: > On Mon, Apr 29, 2019 at 9:29 AM Doug Ledford wrote: > > > > drivers/infiniband/core/uverbs_main.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > This trivial one-liner is actually incorrect. > > It should use

Re: [PATCH v2] soc: add aspeed folder and misc drivers

On Mon, Apr 29, 2019 at 10:08 AM Olof Johansson wrote: > > On Thu, Apr 25, 2019 at 07:25:49PM +0200, Greg KH wrote: > > On Tue, Apr 23, 2019 at 08:28:14AM -0700, Patrick Venture wrote: > > > On Tue, Apr 23, 2019 at 8:22 AM Patrick Venture > > > wrote: > > > > > > > > On Tue, Apr 23, 2019 at

Re: [PATCH] rtc: snvs: Use __maybe_unused instead of #if CONFIG_PM_SLEEP

On Mon, 2019-04-29 at 07:02 +, Anson Huang wrote: > Use __maybe_unused for power management related functions > instead of #if CONFIG_PM_SLEEP to simply the code. > > Signed-off-by: Anson Huang This will result in the functions always being included, even if PM_SLEEP is off... > > @@

Re: [PATCH v2] soc: add aspeed folder and misc drivers

On Mon, Apr 29, 2019 at 10:08 AM Olof Johansson wrote: > > On Thu, Apr 25, 2019 at 07:25:49PM +0200, Greg KH wrote: > > On Tue, Apr 23, 2019 at 08:28:14AM -0700, Patrick Venture wrote: > > > On Tue, Apr 23, 2019 at 8:22 AM Patrick Venture > > > wrote: > > > > > > > > On Tue, Apr 23, 2019 at

Re: [PATCH 1/2] ARM: dts: aspeed: Add aspeed-p2a-ctrl node

On Thu, Apr 25, 2019 at 12:48:53PM -0700, Patrick Venture wrote: > Add a node for the aspeed-p2a-ctrl module. This node, when enabled will > disable the PCI-to-AHB bridge and then allow control of this bridge via > ioctls, and access via mmap. > > Signed-off-by: Patrick Venture Patrick,

Re: [PATCH v2] soc: add aspeed folder and misc drivers

On Mon, Apr 22, 2019 at 12:24:28PM -0700, Patrick Venture wrote: > On Mon, Apr 22, 2019 at 10:54 AM Patrick Venture wrote: > > > > Create a SoC folder for the ASPEED parts and place the misc drivers > > currently present into this folder. These drivers are not generic part > > drivers, but

Re: [PATCH] soc: add aspeed folder and misc drivers

On Tue, Apr 23, 2019 at 10:08:11AM +0200, Arnd Bergmann wrote: > On Mon, Apr 22, 2019 at 7:38 PM Patrick Venture wrote: > > > > Create a SoC folder for the ASPEED parts and place the misc drivers > > currently present into this folder. These drivers are not generic part > > drivers, but rather

Re: [PATCH] soc: add aspeed folder and misc drivers

On Tue, Apr 23, 2019 at 08:40:25AM -0700, Patrick Venture wrote: > On Tue, Apr 23, 2019 at 8:33 AM Arnd Bergmann wrote: > > > > On Tue, Apr 23, 2019 at 4:24 PM Patrick Venture wrote: > > > > > > On Tue, Apr 23, 2019 at 1:08 AM Arnd Bergmann wrote: > > > > > > > > On Mon, Apr 22, 2019 at 7:38 PM

Re: [PATCH v2] soc: add aspeed folder and misc drivers

On Thu, Apr 25, 2019 at 07:25:49PM +0200, Greg KH wrote: > On Tue, Apr 23, 2019 at 08:28:14AM -0700, Patrick Venture wrote: > > On Tue, Apr 23, 2019 at 8:22 AM Patrick Venture wrote: > > > > > > On Tue, Apr 23, 2019 at 7:26 AM Patrick Venture > > > wrote: > > > > > > > > Create a SoC folder for

Re: [PATCH] ASoC: Intel: avoid Oops if DMA setup fails

On Fri, Apr 26, 2019 at 04:03:47PM -0500, Pierre-Louis Bossart wrote: > On 4/26/19 11:47 AM, Ross Zwisler wrote: > > Currently in sst_dsp_new() if we get an error return from sst_dma_new() > > we just print an error message and then still complete the function > > successfully. This means that we

Re: [PATCH for 5.2 12/12] rseq/selftests: add -no-integrated-as for clang

On Mon, Apr 29, 2019 at 8:29 AM Mathieu Desnoyers wrote: > > Ongoing work for asm goto support from clang requires the > -no-integrated-as compiler flag. > > This compiler flag is present in the toplevel kernel Makefile, > but is not replicated for selftests. Add it specifically for > the rseq

Re: [PATCH] PCI: Add link_change error handler and vfio-pci user

On Mon, 29 Apr 2019 09:45:28 -0700 Sinan Kaya wrote: > On 4/29/2019 10:51 AM, Alex Williamson wrote: > > So where do we go from here? I agree that dmesg is not necessarily a > > great choice for these sorts of events and if they went somewhere else, > > maybe I wouldn't have the same concerns

Re: [PATCH 2/4] perf: Add filter_match() as a parameter for pinned/flexible_sched_in()

On Mon, Apr 29, 2019 at 11:31:26AM -0400, Liang, Kan wrote: > > > On 4/29/2019 11:12 AM, Mark Rutland wrote: > > On Mon, Apr 29, 2019 at 07:44:03AM -0700, kan.li...@linux.intel.com wrote: > > > From: Kan Liang > > > > > > A fast path will be introduced in the following patches to speed up the

RE: DISCONTIGMEM is deprecated

> ia64 has a such a huge number of memory model choices. Maybe we > need to cut it down to a small set that actually work. SGI systems had extremely discontiguous memory (they used some high order physical address bits in the tens/hundreds of terabyte range for the node number ... so there would

Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia)

On Mon 2019-04-29 18:44:39, Marek Behun wrote: > On Mon, 29 Apr 2019 18:37:53 +0200 > Pavel Machek wrote: > > > On Mon 2019-04-29 17:38:42, Marek Behun wrote: > > > I am sending patch only adding the I2C dep. Theoretically it is > > > possible that someone uses the same I2C API in their

[PATCH] thermal: broadcom: Remove ACPI support

Unlike DT framework, thermal-zones and its parameters can't be parsed using ACPI framework. So that ACPI support is removed in this driver. Signed-off-by: Srinath Mannam Reported-by: David Woodhouse --- drivers/thermal/broadcom/sr-thermal.c | 8 1 file changed, 8 deletions(-) diff

Re: [PATCH] thermal/drivers/of: Add a get_temp_id callback function

On 24/04/2019 01:08, Daniel Lezcano wrote: > On 23/04/2019 17:44, Eduardo Valentin wrote: >> Hello, >> >> On Tue, Apr 16, 2019 at 07:22:03PM +0200, Daniel Lezcano wrote: >>> Currently when we register a sensor, we specify the sensor id and a data >>> pointer to be passed when the get_temp function

Re: [PATCH v7 3/4] s390: ap: implement PAPQ AQIC interception in kernel

On Fri, 26 Apr 2019 15:01:27 +0200 Pierre Morel wrote: > +static struct ap_queue_status vfio_ap_setirq(struct vfio_ap_queue *q) > +{ > + struct ap_qirq_ctrl aqic_gisa = {}; > + struct ap_queue_status status = {}; > + struct kvm_s390_gisa *gisa; > + struct kvm *kvm; > +

Verificación de la cuenta

Aviso de seguridad: Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a todos nuestros clientes de correo web. Su cuenta de correo electrónico se actualizará a una nueva y mejorada interfaz de

Verificación de la cuenta

Aviso de seguridad: Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a todos nuestros clientes de correo web. Su cuenta de correo electrónico se actualizará a una nueva y mejorada interfaz de

Re: [PATCH] arm64: fix pte_unmap() -Wunused-but-set-variable

On Fri, Apr 26, 2019 at 09:28:42PM -0400, Qian Cai wrote: > Many compilation warnings due to pte_unmap() compiles away. Fixed it by > making it an static inline function. > > mm/gup.c: In function 'gup_pte_range': > mm/gup.c:1727:16: warning: variable 'ptem' set but not used >

Re: [GIT PULL] Please pull rdma.git

On Mon, Apr 29, 2019 at 9:29 AM Doug Ledford wrote: > > > drivers/infiniband/core/uverbs_main.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) This trivial one-liner is actually incorrect. It should use 'vmf->address', because the point of the ZERO_PAGE argument is to pick the page

Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia)

On Mon, 29 Apr 2019 18:37:53 +0200 Pavel Machek wrote: > On Mon 2019-04-29 17:38:42, Marek Behun wrote: > > I am sending patch only adding the I2C dep. Theoretically it is > > possible that someone uses the same I2C API in their microcontroller on > > another architecture. > > Theoretically.

Re: [PATCH] PCI: Add link_change error handler and vfio-pci user

On 4/29/2019 10:51 AM, Alex Williamson wrote: So where do we go from here? I agree that dmesg is not necessarily a great choice for these sorts of events and if they went somewhere else, maybe I wouldn't have the same concerns about them generating user confusion or contributing to DoS vectors

Zdravstvuyte! Vas interesuyut kliyentskiye bazy dannykh?

Zdravstvuyte! Vas interesuyut kliyentskiye bazy dannykh?

Re: [PATCH v6 06/10] dt-bindings: memory-controllers: add Exynos5422 DMC device description

On Mon, Apr 29, 2019 at 7:14 AM Lukasz Luba wrote: > > Hi Rob, > > On 4/25/19 9:57 PM, Rob Herring wrote: > > On Fri, Apr 19, 2019 at 04:19:24PM +0200, Lukasz Luba wrote: > >> The patch adds description for DT binding for a new Exynos5422 Dynamic > >> Memory Controller device. > >> > >>

[PATCH] x86/fpu: Fault-in user stack if copy_fpstate_to_sigframe() fails

In the compacted form, the XSAVES may save only XMM+SSE but skip FP. This is denoted by header->xfeatures = 6. The fastpath (copy_fpregs_to_sigframe()) does that but _also_ initialises the FP state (cwd to 0x37f, mxcsr as we do, remaining fields to 0). The slowpath (copy_xstate_to_user()) leaves

Re: [PATCH -next] lib/vsprintf: Make function pointer_string static

On Mon, 2019-04-29 at 10:39 -0400, Steven Rostedt wrote: > [ added Joe ] > > Good question. I have just double checked it. And pointer_string() with > > "noinline_for_stack" does not make any difference in the stack > > usage here. > > > > I actually played with this before: > > > >

Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia)

On Mon 2019-04-29 17:38:42, Marek Behun wrote: > I am sending patch only adding the I2C dep. Theoretically it is > possible that someone uses the same I2C API in their microcontroller on > another architecture. Theoretically. But we both now that probability of that is very low, and that likely

Re: [PATCH v6 04/10] Documentation: dt: device tree bindings for LPDDR3 memories

On Mon, Apr 29, 2019 at 7:05 AM Lukasz Luba wrote: > > Hi Rob, > > On 4/25/19 9:51 PM, Rob Herring wrote: > > On Fri, Apr 19, 2019 at 04:19:22PM +0200, Lukasz Luba wrote: > >> The device tree bindings for LPDDR3 SDRAM memories. > >> > >> For specifying the AC timing parameters of the memory

Re: [PATCH v1 1/2] Add polling support to pidfd

On Mon, Apr 29, 2019 at 04:20:30PM +0200, Oleg Nesterov wrote: > On 04/29, Joel Fernandes wrote: > > > > However, in your code above, it is avoided because we get: > > > > Task A (poller) Task B (exiting task being polled) > > > > poll() called

Re: [GIT PULL] Please pull RDMA subsystem changes

On Mon, 2019-04-29 at 11:42 -0400, Doug Ledford wrote: > On Mon, 2019-04-29 at 08:40 +, Jason Gunthorpe wrote: > > On Mon, Apr 29, 2019 at 08:09:47AM +0200, Heiko Carstens wrote: > > > On Sun, Apr 28, 2019 at 11:52:12AM +, Jason Gunthorpe wrote: > > > > Hi Linus, > > > > > > > > Third rc

Re: [PATCH] spi: zynqmp: Fix build break

On 29. 04. 19 9:22, Olof Johansson wrote: > Missing include: > drivers/spi/spi-zynqmp-gqspi.c:1025:13: error: implicit declaration of > function 'zynqmp_pm_get_eemi_ops'; did you mean > 'zynqmp_process_dma_irq'? [-Werror=implicit-function-declaration] > > Fixes: 3d0313786470a ('drivers: Defer

[GIT PULL] Please pull rdma.git

Hi Linus, As per the thread on our last pull request, this is the two line build fix for s390 and mips. The following changes since commit 2557fabd6e29f349bfa0ac13f38ac98aa5eafc74: RDMA/hns: Bugfix for mapping user db (2019-04-25 10:40:04 -0300) are available in the Git repository at:

Re: [PATCH v2] tty: serial: 8250: Fix type field in format string

On Mon, 29 Apr 2019 at 22:31, Greg KH wrote: > This causes build warnings when applied, I'm having to drop it now. > > Please be more careful, when submitting patches, always test-build them > first. I have found my mistake. Although I have built a kernel to test my patch, I forget to turn on

[PATCH v3] tty: serial: 8250: Fix type field in format string

The dev_dbg statement should print the value of uart.port.mapbase instead of its address. Besides that, uart.port.irq and uart.port.iotype are all unsigned types, so using %u is more appropriate. Signed-off-by: Hao Lee --- drivers/tty/serial/8250/8250_pnp.c | 4 ++-- 1 file changed, 2

[PATCH] spi: zynqmp: Fix build break

Missing include: drivers/spi/spi-zynqmp-gqspi.c:1025:13: error: implicit declaration of function 'zynqmp_pm_get_eemi_ops'; did you mean 'zynqmp_process_dma_irq'? [-Werror=implicit-function-declaration] Fixes: 3d0313786470a ('drivers: Defer probe if firmware is not ready') Cc: Rajan Vaja Cc:

Re: [PATCH v3 2/2] dt-bindings: cpufreq: Document allwinner,cpu-operating-points-v2

On Sun, Apr 28, 2019 at 4:53 AM Frank Lee wrote: > > On Sat, Apr 27, 2019 at 5:15 AM Rob Herring wrote: > > > > On Wed, Apr 10, 2019 at 01:41:39PM -0400, Yangtao Li wrote: > > > Allwinner Process Voltage Scaling Tables defines the voltage and > > > frequency value based on the speedbin blown in

<    1   2   3   4   5   6   7   8   >