Re: [PATCHv4 1/2] dt-bindings: Add vendor prefix for Motorola

On 02/03/2017 at 01:27:08 +0100, Sebastian Reichel wrote: > Motorola was involved in semiconductor and mobile phone business. > The "motorola," prefix is already used by a couple of bindings: > > * rtc/rtc-cmos.txt > * mfd/motorola-cpcap.txt > * regulator/cpcap-regulator.txt > > Apart from that

Re: [PATCH] rtc: omap: mark PM methods as __maybe_unused

On 01/03/2017 at 15:34:38 -0800, Dmitry Torokhov wrote: > Instead of using #ifdef guards around PM methods, let's annotate > them as __maybe_unused, as it provides better compile coverage. > > Also drop empty stub for omap_rtc_runtime_resume(). > > Signed-off-by: Dmitry Torokhov

Re: [PATCHv4 2/2] rtc: cpcap: new rtc driver

On 02/03/2017 at 01:27:09 +0100, Sebastian Reichel wrote: > This driver supports the Motorola CPCAP PMIC found on > some of Motorola's mobile phones, such as the Droid 4. > > Tested-by: Tony Lindgren > Signed-off-by: Sebastian Reichel > --- > Changes since

[PATCH] ARM: socfpga: updates for socfpga_defconfig

From: Jia Jie Ho This patch enables Altera TSE support for Arria10 SoC FPGA Signed-off-by: Jia Jie Ho --- arch/arm/configs/socfpga_defconfig |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/arch/arm/configs/socfpga_defconfig

Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions

* Carlos O'Donell [2017-03-08 10:53:00 -0500]: > On 11/11/2016 07:08 AM, Felix Janda wrote: > > fixes the following compiler errors when is included > > after musl : > > > > ./linux/in6.h:32:8: error: redefinition of 'struct in6_addr' > > ./linux/in6.h:49:8: error:

Re: out of range LBA using sg_raw

> "Kashyap" == Kashyap Desai writes: Kashyap, Kashyap> Agree on this point. I am planning to study all possible such Kashyap> sanity in driver for VD and not trying to fix one specific Kashyap> scenario as described here. Do you think fix in this area is

Re: [PATCH 3/4] phy: rockchip-typec: support DP phy switch

On Fri, Feb 10, 2017 at 03:44:13PM +0800, Chris Zhong wrote: > There are 2 Type-c PHYs in RK3399, but only one DP controller. Hence > only one PHY can connect to DP controller at one time, the other should > be disconnected. The GRF_SOC_CON26 register has a switch bit to do it, > set this bit

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

On 03/08/17 at 11:50am, Borislav Petkov wrote: > On Wed, Mar 08, 2017 at 06:17:50PM +0800, Baoquan He wrote: > > All right, I will just update the code comment. Just back ported kaslr > > to our OS product, people reviewed and found the upper boundary of kaslr > > mm region is EFI_VA_START, that's

[PATCH] net: ks8851: Added support for half-duplex SPI

In original driver was implemented support for half- and full-duplex modes, but it was not enabled. Instead of it ks8851_rx_1msg method always returns "true" that means "full-duplex" mode. This patch replaces hard-coded functionality with flexible solution that supports both SPI modes.

Re: [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free}

Hi Brian > > It is a littlle bit strange for me. > > Yes, and honestly I'm a little confused by the inheritance in this > framework. Yes, I agree :) This is 1st prepare for future ALSA SoC framework cleanup It is Lars-Peter's idea > I have a feeling you're checking the wrong thing below for

Re: [PATCH resent] uapi libc compat: allow non-glibc to opt out of uapi definitions

On 03/08/2017 07:14 PM, Szabolcs Nagy wrote: > * Carlos O'Donell [2017-03-08 10:53:00 -0500]: >> On 11/11/2016 07:08 AM, Felix Janda wrote: >>> fixes the following compiler errors when is included >>> after musl : >>> >>> ./linux/in6.h:32:8: error: redefinition of 'struct

[PATCH] drivers: Remove OF dependency in drv260x driver

As the driver is using generic device properties, it should work properly when CONFIG_OF is turned off. This patch removes the ifdef CONFIGOF and make sure the driver always have of_match_table. Signed-off-by: Jingkui Wang --- drivers/input/misc/drv260x.c | 4 +--- 1 file

[PATCH] virtio-pci: Remove affinity hint before freeing the interrupt

virtio-pci registers a per-vq affinity hint when using MSIX, but fails to remove it when freeing the interrupt, resulting in this type of splat: [ 31.111202] WARNING: CPU: 0 PID: 2823 at kernel/irq/manage.c:1503 __free_irq+0x2c4/0x2c8 [ 31.114689] Modules linked in: [ 31.116101] CPU: 0

[PATCH] kernel: convert css_set.refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[v2, 1/4] mtd: spi-nor: Add support for Octal SPI mode.

This patch adds support for Octal SPI data reads in SPI NOR framework. Opcodes for programming using octal interface are also present for the sake of completeness, despite not being used. Micron mt35xu512 flash is added as an example chip supporting that mode. Signed-off-by: Artur Jedrysek

[PATCH RESEND^2] usb: gadget: udc: atmel: fix debug output

The debug output now contains the wrong variable, as seen from the compiler warning: drivers/usb/gadget/udc/atmel_usba_udc.c: In function 'usba_ep_enable': drivers/usb/gadget/udc/atmel_usba_udc.c:632:550: error: 'ept_cfg' may be used uninitialized in this function [-Werror=maybe-uninitialized]

Re: [RFC PATCH 2/2] mm/sparse: add last_section_nr in sparse_init() to reduce some iteration cycle

On Mon, Mar 06, 2017 at 02:42:25PM -0500, Tejun Heo wrote: >Hello, Wei. > >On Fri, Feb 17, 2017 at 10:12:31PM +0800, Wei Yang wrote: >> > And compare the ruling with the iteration for the loop to be (1UL << >> > 5) and (1UL << 19). >> > The runtime is 0.00s and 0.04s respectively. The absolute

Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME

On 03/06/17 at 11:58am, Tom Lendacky wrote: > On 3/1/2017 3:25 AM, Dave Young wrote: > > Hi Tom, > > Hi Dave, > > > > > On 02/17/17 at 10:43am, Tom Lendacky wrote: > > > On 2/17/2017 9:57 AM, Konrad Rzeszutek Wilk wrote: > > > > On Thu, Feb 16, 2017 at 09:47:55AM -0600, Tom Lendacky wrote: > >

Re: [PATCH 0/2] Documentation/EDID fixes

On Tue, 07 Mar 2017, Javi Merino wrote: > On Tue, Mar 07, 2017 at 06:16:51PM +0200, Jani Nikula wrote: >> On Mon, 06 Mar 2017, Javi Merino wrote: >> > I found these two minor issues while building an EDID. I'm not sure >> > whether the second

[PATCH v4 1/7] arm: dts: imx6qdl-icore: Add backlight support for lvds

From: Jagan Teki This patch add support for lvds backlight on i.CoreM6 QDL variant boards. Cc: Domenico Acri Cc: Matteo Lisi Cc: Michael Trimarchi Cc: Shawn Guo

[PATCH] refcount: restore kref_get and kref_put to non-GPL status

From: John Hubbard Originally, kref_get and kref_put were available as standard routines that even non-GPL device drivers could use. However, as an unintended side effect of the recent kref_*() upgrade[1], these calls are now effectively GPL, because they get routed to the

Re: [PATCH] reset: sunxi: fix for 64-bit compilation

Hi, On 08/03/17 04:28, Chen-Yu Tsai wrote: > On Mon, Mar 6, 2017 at 9:35 AM, Andre Przywara wrote: >> The Allwinner reset controller has 32-bit registers, so translating >> the reset cell number into a register and bit offset should not use >> any architecture dependent

Re: About boot time Tux logo with -EPROBE_DEFER

Hi Morimoto-san, On Tue, Mar 7, 2017 at 2:24 AM, Kuninori Morimoto wrote: > I want to ask you about boot time Tux logo. > > For some reasons, current our video driver returns -EPROBE_DEFER when > probe timing, but logo init function doesn't care it. > Thus, our

Re: [PATCH] iio: multiplexer: fix unsigned check with less than zero

On 2017-03-07 16:06, Colin King wrote: > From: Colin Ian King > > Comparing a size_t with less than zero is always false as size_t > is unsigned. The intent of the comparison was to check if the size > was -1 (that is, undefined), so use that instead. > > Detected by

Re: [PATCH v4 0/7] mmc: bcm2835: Add new driver for the sdhost controller

On Mi, 2017-03-08 at 10:19 +0100, Gerd Hoffmann wrote: > Hi, > > Next version if the bcm2835 sdhost patch series. Oops, had some stale qxl patch files laying around which got sent with this series by mistake. Just ignore these, and sorry for the spam. cheers, Gerd

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

On Wed, Mar 08, 2017 at 05:09:55PM +0800, Baoquan He wrote: > Yes, it looks better. I can repost with this change. Thanks. No it doesn't: #define EFI_VA_START ( -4 * (_AC(1, UL) << 30)) #define EFI_VA_END (-68 * (_AC(1, UL) << 30)) That's -4G (the shift by 30) and -68G, respectively.

Re: [PATCH V3 0/4] megachips-stdpxxxx-ge-b850v3-fw

On Mon, Mar 06, 2017 at 03:27:16PM +0530, Archit Taneja wrote: Hi Archit, > Hi, > > On 3/3/2017 9:27 PM, Peter Senna Tschudin wrote: > > The video processing pipeline on the second output on the GE B850v3: > > > > Host -> LVDS|--(STDP4028)--|DP -> DP|--(STDP2690)--|DP++ -> Video output > > >

RE: [PATCH 10/29] drivers, md: convert stripe_head.count from atomic_t to refcount_t

> On Mon, Mar 06, 2017 at 04:20:57PM +0200, Elena Reshetova wrote: > > refcount_t type and corresponding API should be > > used instead of atomic_t when the variable is used as > > a reference counter. This allows to avoid accidental > > refcounter overflows that might lead to use-after-free > >

Re: [GIT pull] CPU hotplug updates for 4.9

Bart, On Tue, 7 Mar 2017, Bart Van Assche wrote: > On Tue, 2017-03-07 at 10:30 +0100, Thomas Gleixner wrote: > > That's odd. There was no change related to the hotplug stuff post 4.10 > > neither in the core nor in that particular driver. > > > > I have no immediate clue what to look for aside

Re: [PATCH] crypto: s5p-sss - Fix completing crypto request in IRQ handler

On Sun, Mar 05, 2017 at 07:14:07PM +0200, Krzysztof Kozlowski wrote: > In a regular interrupt handler driver was finishing the crypt/decrypt > request by calling complete on crypto request. This is disallowed since > converting to skcipher in commit b286d8b1a690 ("crypto: skcipher - Add >

Re: next build: 208 builds: 21 failed, 187 passed, 53 errors, 406 warnings (next-20170308)

* Arnd Bergmann wrote: > > bmips_be_defconfig (mips) — FAIL, 1 error, 1 warning, 0 section mismatches > > > > Errors: > > arch/mips/kernel/smp-bmips.c:183:38: error: implicit declaration of function > > 'task_stack_page' [-Werror=implicit-function-declaration] > > A new

Re: [PATCH 2/2] perf probe: Remove stale func add_perf_probe_events

On Wed, 8 Mar 2017 12:29:08 +0530 Ravi Bangoria wrote: > I don't see any user of this function. This function was being copied > to tools/perf/builtin-probe.c by commit b02137cc6550 ("perf probe: Move > print logic into cmd_probe()"). Since then it has became

Re: [PATCH 1/1] x86/cqm: Cqm requirements

Stephane, On Tue, 7 Mar 2017, Stephane Eranian wrote: > On Tue, Mar 7, 2017 at 12:04 PM, Luck, Tony wrote: > >> That's all nice and good, but I still have no coherent explanation why > >> measuring across allocation domains makes sense. > > > > Is this in reaction to this

[PATCH, RESEND] staging: octeon: remove unused variable

A cleanup patch left one local variable without a reference: drivers/staging/octeon/ethernet-rx.c:339:28: warning: unused variable 'priv' [-Wunused-variable] This removes the declaration too. Fixes: 66812da3a689 ("staging: octeon: Use net_device_stats from struct net_device") Signed-off-by:

RE: [PATCH 08/29] drivers, md: convert mddev.active from atomic_t to refcount_t

> On Mon, Mar 06, 2017 at 04:20:55PM +0200, Elena Reshetova wrote: > > refcount_t type and corresponding API should be > > used instead of atomic_t when the variable is used as > > a reference counter. This allows to avoid accidental > > refcounter overflows that might lead to use-after-free > >

[PATCH 2/2] reset: simple: read back to make sure changes are applied

Read back the register after setting or clearing a reset bit to make sure that the changes are applied to the reset controller hardware. Theoretically, this avoids the write to stay stuck in a store buffer during the delay of an assert-delay-deassert sequence, and makes sure that the reset really

[PATCH v4 0/7] arm: dts: imx6q-icore: Add LVDS display nodes

From: root This series adds support for lvds display, touchscreen nodes on dts for Engicam i.CoreM6 Quad boards along with selecting few touchscreen driver configs to imx_v6_v7_defconfig so-that select by default. Jagan Teki (7): arm: dts: imx6qdl-icore: Add

Re: [RFC PATCH 3/4] xfs: map KM_MAYFAIL to __GFP_RETRY_MAYFAIL

On Tue 07-03-17 09:05:19, Darrick J. Wong wrote: > On Tue, Mar 07, 2017 at 04:48:42PM +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > KM_MAYFAIL didn't have any suitable GFP_FOO counterpart until recently > > so it relied on the default page allocator behavior for the

Re: [PATCH v7 06/07] iommu/ipmmu-vmsa: ARM and ARM64 archdata access

Hi Magnus, On Tue, Mar 7, 2017 at 4:17 AM, Magnus Damm wrote: > From: Magnus Damm > > Not all architectures have an iommu member in their archdata, so > use #ifdefs support build with COMPILE_TEST on any architecture. to support >

[PATCH 1/2] reset: add reset-simple to unify socfpga, stm32, and sunxi

Reset operations for simple reset controllers with reset lines that can be controlled by toggling bits in (mostly) contiguous register ranges using read-modify-write cycles under a spinlock. So far this covers the socfpga, stm32, and sunxi drivers. Signed-off-by: Philipp Zabel

[PATCH] livepatch: make klp_mutex proper part of API

From: Jiri Kosina klp_mutex is shared between core.c and transition.c, and as such would rather be properly located in livepatch.h so that we don't have to play 'extern' games from .c sources. This also silences sparse warning (wrongly) suggesting that klp_mutex should be

Re: [PATCH] mux-core: make it explicitly non-modular

On 2017-03-07 23:41, Paul Gortmaker wrote: > The Kconfig currently controlling compilation of this code is: > > drivers/mux/Kconfig:menuconfig MULTIPLEXER > drivers/mux/Kconfig:bool "Multiplexer subsystem" > > ...meaning that it currently is not being built as a module by anyone. > > Lets

Re: [PATCH v11 2/9] mmc: cavium: Add core MMC driver for Cavium SOCs

[...] >> > Voltage is limited to 3.3v and shared for all slots. >> >> What voltage? The I/O voltage or the voltage for the card? >> >> VMMC or VMMCQ? > > From my understanding both, VMMC and VMMCQ are fixed at 3.3v. Okay, then make sure to explicitly state that here. [...] >> > + if

Re: [PATCH] mm: Do not use double negation for testing page flags

On Wed 08-03-17 08:51:23, Vlastimil Babka wrote: > On 03/08/2017 06:25 AM, Minchan Kim wrote: [...] > > Although we can add a little description > > somewhere in page-flags.h, I believe changing to boolean is more > > clear/not-error-prone so Chen's work is enough worth, I think. > > Agree,

Re: [PATCH] refcount: restore kref_get and kref_put to non-GPL status

On 03/08/2017 01:50 AM, Greg Kroah-Hartman wrote: On Wed, Mar 08, 2017 at 01:25:49AM -0800, john.hubb...@gmail.com wrote: From: John Hubbard Originally, kref_get and kref_put were available as standard routines that even non-GPL device drivers could use. As I stated

Re: [PATCH] mm, vmscan: do not loop on too_many_isolated for ever

On Tue 07-03-17 14:52:36, Rik van Riel wrote: > On Tue, 2017-03-07 at 14:30 +0100, Michal Hocko wrote: > > From: Michal Hocko > > > > Tetsuo Handa has reported [1][2] that direct reclaimers might get > > stuck > > in too_many_isolated loop basically for ever because the last few

Re: [PATCH 1/4] s390: get rid of superfluous __GFP_REPEAT

On Tue, Mar 07, 2017 at 04:48:40PM +0100, Michal Hocko wrote: > From: Michal Hocko > > __GFP_REPEAT has a rather weak semantic but since it has been introduced > around 2.6.12 it has been ignored for low order allocations. > > page_table_alloc then uses the flag for a single

Re: [linux-sunxi] [PATCH 5/15] clk: sunxi-ng: sun5i: Export video PLLs

Hi Julian, On Tue, Mar 07, 2017 at 09:21:19PM +1100, Julian Calaby wrote: > Hi Maxime, > > On Tue, Mar 7, 2017 at 7:56 PM, Maxime Ripard > wrote: > > The video PLLs are used directly by the HDMI controller. Export them so > > that we can use them in our DT

Re: [bdi_unregister] 165a5e22fa INFO: task swapper:1 blocked for more than 120 seconds.

On Tue 07-03-17 17:26:56, Jan Kara wrote: > On Tue 07-03-17 08:10:29, James Bottomley wrote: > > On Tue, 2017-03-07 at 15:41 +0100, Jan Kara wrote: > > > On Mon 06-03-17 09:25:42, James Bottomley wrote: > > > > On Mon, 2017-03-06 at 17:13 +0100, Jan Kara wrote: > > > > > On Mon 06-03-17 07:44:55,

Re: [PATCH v7 04/07] iommu/ipmmu-vmsa: Break out domain allocation code

On Tue, Mar 7, 2017 at 4:17 AM, Magnus Damm wrote: > From: Magnus Damm > > Break out the domain allocation code into a separate function. > This is preparation for future code sharing. > > Signed-off-by: Magnus Damm

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

On 03/08/17 at 02:30pm, Bhupesh Sharma wrote: > Hi Dave, > > On Wed, Mar 8, 2017 at 1:48 PM, Dave Young wrote: > > On 03/08/17 at 03:47pm, Baoquan He wrote: > >> - * We allocate runtime services regions bottom-up, starting from -4G, i.e. > >> + * We allocate runtime services

[PATCH -v2] sched/wait: Add dependency for now

* Ingo Molnar wrote: > I'll do more testing over the day to see how well this approach works. Not > yet > signed off by me. I'll post updated versions over the day if there's any > changes. > > This removes the time pressure to untangle the wait.h mess for v4.11. I've

Re: [PATCH 0/1] refcount: restore kref_get and kref_put to non-GPL status

On Wed, Mar 08, 2017 at 01:25:48AM -0800, john.hubb...@gmail.com wrote: > From: John Hubbard > > Hi, > > Say, I'm 99% sure that this was just an oversight, so > I'm sticking my neck out here and floating a patch to > Put Things Back. I'm hoping that there is not some > firm

Re: [PATCH 1/2] Staging: comedi: comedi_fops: Change comedi_num_legacy_minors type

On Wed, Mar 08, 2017 at 05:38:12PM +0800, Cheah Kok Cheong wrote: > Dear Greg, > Thanks for taking the time to review. > > On Tue, Mar 07, 2017 at 08:01:38PM +0100, Greg KH wrote: > > On Sun, Mar 05, 2017 at 03:22:32AM +0800, Cheah Kok Cheong wrote: > > > Change to unsigned to allow removal of

Re: [PATCH V3 4/4] dts/imx6q-b850v3: Use megachips-stdpxxxx-ge-b850v3-fw bridges (LVDS-DP++)

On Fri, Mar 03, 2017 at 04:57:10PM +0100, Peter Senna Tschudin wrote: Hi Shawn Guo, Now that the driver and binding are in, can you pick this up? Thank you! > Configures the megachips-stdp-ge-b850v3-fw bridges on the GE > B850v3 dts file. > > Cc: Laurent Pinchart

Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on

Hi Jon, On Tue, Mar 7, 2017 at 9:27 PM, Jon Hunter wrote: > On 06/03/17 15:53, Geert Uytterhoeven wrote: >> On Mon, Mar 6, 2017 at 3:28 PM, Peter De Schrijver >> wrote: >>> On Mon, Mar 06, 2017 at 09:58:29AM +, Jon Hunter wrote: On

Re: [PATCH v2] dmaengine: rcar-dmac: enable descriptor mode on 40bit

On Wed, Mar 8, 2017 at 1:42 AM, Kuninori Morimoto wrote: > From: Kuninori Morimoto > > SYS-DMAC can use 40bit address transfer, and it supports Descriptor > Mode too. Current SYS-DMAC driver disables Descriptor Mode if it was >

Re: kasan behavior when built with unsupported compiler

On 7.03.2017 17:54, Dmitry Vyukov wrote: > On Tue, Mar 7, 2017 at 4:35 PM, Nikolay Borisov > wrote: >> Hello, >> >> I've been chasing a particular UAF as reported by kasan >> (https://www.spinics.net/lists/kernel/msg2458136.html). However, one >> thing which I took

[PATCH v3] Input: sparse-keymap - use a managed allocation for keymap copy

Some platform drivers use devm_input_allocate_device() together with sparse_keymap_setup() in their .probe callbacks. While using the former simplifies error handling, using the latter necessitates calling sparse_keymap_free() in the error path and upon module unloading to avoid leaking the copy

[PATCH RESEND] drm: dw_hdmi: Don't rely on the status of the bridge for updating HPD

Currently, the irq handler that monitores changes for HPD anx RX_SENSE relies on the status of the bridge for updating the status of the HPD. The update is done only when the bridge is enabled. However, on Rockchip platforms we have found use cases where it could be a problem. When HDMI is being

Re: [PATCH 01/12] gpio: mockup: use devm_irq_alloc_descs()

On 4 March 2017 at 17:23, Bartosz Golaszewski wrote: > Use the resource managed variant of irq_alloc_descs(). This allows us > to remove gpio_mockup_remove(). > > Signed-off-by: Bartosz Golaszewski Reviewed-by: Bamvor Jian Zhang

[PATCH v5 1/5] trace/kprobes: fix check for kretprobe offset within function entry

perf specifies an offset from _text and since this offset is fed directly into the arch-specific helper, kprobes tracer rejects installation of kretprobes through perf. Fix this by looking up the actual offset from a function for the specified sym+offset. Refactor and reuse existing routines to

[v2, 3/4] mtd: spi-nor: Add Xtensa CPU support for cadence-quadspi.

Cadence Quad SPI driver successfully runs on Xtensa CPU, and Kconfig file is updated to indicate that. Signed-off-by: Artur Jedrysek --- Changelog: v2: This change is extracted from previous patch (updating CQSPI driver). --- drivers/mtd/spi-nor/Kconfig | 2 +- 1 file

[PATCH v5 4/5] perf: kretprobes: offset from reloc_sym if kernel supports it

We indicate support for accepting sym+offset with kretprobes through a line in ftrace README. Parse the same to identify support and choose the appropriate format for kprobe_events. As an example, without this perf patch, but with the ftrace changes: naveen@ubuntu:~/linux/tools/perf$ sudo cat

[PATCH v5 2/5] powerpc: kretprobes: override default function entry offset

With ABIv2, we offset 8 bytes into a function to get at the local entry point. Acked-by: Ananth N Mavinakayanahalli Acked-by: Michael Ellerman Signed-off-by: Naveen N. Rao --- arch/powerpc/kernel/kprobes.c | 9

[PATCH v5 3/5] perf: probe: factor out the ftrace README scanning

Simplify and separate out the ftrace README scanning logic into a separate helper. This is used subsequently to scan for all patterns of interest and to cache the result. Since we are only interested in availability of probe argument type x, we will only scan for that. Acked-by: Masami Hiramatsu

Re: linux-next: build failure after merge of the sunxi tree

On Tue, 07 Mar 2017, Maxime Ripard wrote: > I just rebased my tree on top of the latest drm-misc tag > (drm-misc-next-2017-03-06). It should compile, and not have merge > conflicts anymore. Conflicts happen. Rebasing should not be the standard operating

Re: [PATCH 2/2] x86/mm/KASLR: Correct the upper boundary of KALSR mm regions if adjacent to EFI

On 03/08/17 at 03:47pm, Baoquan He wrote: > EFI allocates runtime services regions top-down, starting from EFI_VA_START > to EFI_VA_END. So EFI_VA_START is bigger than EFI_VA_END and is the end of > EFI region. The upper boundary of memory regions randomized by KASLR should > be EFI_VA_END if it's

Re: [PATCH 2/2] x86/mm/KASLR: Correct the upper boundary of KALSR mm regions if adjacent to EFI

On Wed, Mar 8, 2017 at 1:48 PM, Dave Young wrote: > On 03/08/17 at 03:47pm, Baoquan He wrote: >> EFI allocates runtime services regions top-down, starting from EFI_VA_START >> to EFI_VA_END. So EFI_VA_START is bigger than EFI_VA_END and is the end of >> EFI region. The upper

[v2, 4/4] dt-bindings: mtd: Add Octal SPI support to Cadence QSPI.

This patch updates Cadence QSPI Device Tree documentation to include information about new compatible used to indicate, whether or not Octal SPI transfers are supported by the device. Signed-off-by: Artur Jedrysek --- Changelog: v2: Use new compatible, instead of boolean

Re: [PATCH 1/2] perf probe: Fix concat_probe_trace_events

On Wed, 8 Mar 2017 12:29:07 +0530 Ravi Bangoria wrote: > '*ntevs' contains number of elements present in 'tevs' array. If > there are no elements in array, 'tevs2' can be directly assigned > to 'tevs' without allocating more space. So the condition should > be

[PATCH 2/5] fs, xfs: convert xfs_efi_log_item.efi_refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 5/5] fs, xfs: convert xfs_rui_log_item.rui_refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

Re: [PATCH v2] ARM: mvebu: add support for the Linksys WRT1900ACS (Shelby)

Hi Ralph, On mar., mars 07 2017, Ralph Sennhauser wrote: > On Tue, 07 Mar 2017 18:27:21 +0100 > Gregory CLEMENT wrote: >> >> It is now in mvebu/dt and in the same time I fixed the title to: >> "ARM: dts: armada-385: add support

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

Forgot cc to Boris, add him. On 03/08/17 at 04:18pm, Dave Young wrote: > On 03/08/17 at 03:47pm, Baoquan He wrote: > > EFI allocate runtime services regions down from EFI_VA_START, -4G. > > It should be top-down handling. > > > > Signed-off-by: Baoquan He > > --- > >

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

On 03/08/17 at 09:54am, Borislav Petkov wrote: > On Wed, Mar 08, 2017 at 04:45:13PM +0800, Baoquan He wrote: > > -4G and -68G just a trick which makes people understand easily, still we > > think kernel text mapping region is in higher addr area then vmalloc. I > > personnally think. > > Just

[PATCH 3/4] qxl: read monitors config at boot

Try to read the client monitors config at driver load time, even without explicit notification. So in case that info was filled before the driver loaded and we've missed the notifications because of that the settings will still be used. With that place we now have to take care to properly handle

[PATCH v4 5/7] arm64: set CONFIG_MMC_BCM2835=y in defconfig

We need to enable this controller so that we can switch the SD card's pinmux over to it by default, which will improve storage performance. Read access (dd with 64k blocks on rpi2): CONFIG_MMC_SDHCI_IPROC: 11-12 MB/s CONFIG_MMC_BCM2835: 19-20 MB/s Differences on write access are pretty

[PATCH 4/4] qxl: fix qxl_conn_get_modes

Call qxl_add_monitors_config_modes() unconditionally. Do all sanity checks in that function. Fix sanity checks. monitors_config is the current monitor configuration, whereas client_monitors_config is the configuration requested by the spice client. So when filling the mode list, based on the

[PATCH v4 4/7] arm: set CONFIG_MMC_BCM2835=y in bcm2835_defconfig and multi_v7_defconfig

We need to enable this controller so that we can switch the SD card's pinmux over to it by default, which will improve storage performance. Read access (dd with 64k blocks on rpi2): CONFIG_MMC_SDHCI_IPROC: 11-12 MB/s CONFIG_MMC_BCM2835: 19-20 MB/s Differences on write access are pretty

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

On 03/08/17 at 03:47pm, Baoquan He wrote: > EFI allocate runtime services regions down from EFI_VA_START, -4G. > It should be top-down handling. > > Signed-off-by: Baoquan He > --- > arch/x86/platform/efi/efi_64.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

[PATCH v5 5/5] perf: powerpc: choose local entry point with kretprobes

perf now uses an offset from _text/_stext for kretprobes if the kernel supports it, rather than the actual function name. As such, let's choose the LEP for powerpc ABIv2 so as to ensure the probe gets hit. Do it only if the kernel supports specifying offsets with kretprobes. Signed-off-by: Naveen

[PATCH v5 0/5] kretprobe fixes

Now that I've been carried back in (ugh!), please find the remaining patches from the earlier series (*) here. Patches 1-4 are the same as in v4. Patch 5 in the previous series was dropped and the previous patch 6 has been updated accordingly. - Naveen (*)

[PATCH] target; Drop pointless tfo->check_stop_free check

From: Nicholas Bellinger All in-tree fabric drivers provide a tfo->check_stop_free(), so there is no need to do the extra check within existing transport_cmd_check_stop_to_fabric() code. Just to be sure, add a check in target_fabric_tf_ops_check() to notify any out-of-tree

[PATCH v4 2/7] arm: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual OpenFrame Cap 10.1 initial support

From: Jagan Teki i.CoreM6 Quad/Dual OpenFrame modules are "system on modules plus openframe display carriers" which are good solution for develop user friendly graphic user interface. General features: CPU NXP i.MX6Q rev1.2 at 792 MHz RAM 1GB, 32,

[PATCH] uapi: add missing install of userio.h

While commit 5523662edd4f ("Input: add userio module") added userio.h under the uapi/ directory, it forgot to add the header file to Kbuild. Thus, the file is missing from header installation. This patch just resolve the issue by adding the missing entry. Signed-off-by: Naohiro Aota

[v2, 2/4] mtd: spi-nor: Add Octal SPI support to Cadence QSPI driver.

Recent versions of Cadence QSPI controller support Octal SPI transfers as well. This patch updates existing driver to support such feature. It is not possible to determine whether or not octal mode is supported just by looking at revision register alone. To solve that, an additional compatible in

Re: [RFC 08/11] mm: make ttu's return boolean

On 03/01/2017 10:39 PM, Minchan Kim wrote: try_to_unmap returns SWAP_SUCCESS or SWAP_FAIL so it's suitable for boolean return. This patch changes it. Hi Minchan, So, up until this patch, I definitely like the cleanup, because as you observed, the return values didn't need so many different

[RFC PATCH] sched/wait: Introduce new, more compact wait_event*() primitives

* Linus Torvalds wrote: > On Fri, Mar 3, 2017 at 12:13 PM, Linus Torvalds > wrote: > > > > The fact that you can include , and then cannot use the > > wait event functions because you're missing "signal_pending()" is > > complete

Re: [PATCH] mm: drop "wait" parameter from write_one_page

On 03/05/2017 05:23 AM, Jeff Layton wrote: The callers all have it set to 1 anyway. Also, make it clear that this function will not set any sort of AS_* error, and that the caller must do so if necessary. Hi Jeff, Silly nit: The above bit about not setting AS_* errors seems to not have made

Re: [PATCH v2] staging: wilc1000: Fix sparse warnings incorrect type assignment

Thank you for your time regard, andrea On Wed, Mar 8, 2017 at 7:22 AM, Dan Carpenter wrote: > I think this change is buggy. > > On Tue, Mar 07, 2017 at 10:36:53PM +0100, Andrea Ghittino wrote: >> Fixed sparse warnings related to the conversion of le16 and le32 to u16

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

On 03/08/2017 06:11 AM, Minchan Kim wrote: > And could you test this patch? It avoids split bio so no need new bio > allocations and makes zram code simple. > > From f778d7564d5cd772f25bb181329362c29548a257 Mon Sep 17 00:00:00 2001 > From: Minchan Kim > Date: Wed, 8 Mar 2017

Re: linux-next: build warnings after merge of the overlayfs tree

On Wed, Mar 8, 2017 at 1:16 AM, Stephen Rothwell wrote: > Hi Miklos, > > After merging the overlayfs tree, today's linux-next build (powerpc > ppc64_defconfig) produced these warnings: > > fs/overlayfs/inode.c:322:30: warning: 'ovl_i_mutex_key' defined but not used >

Re: [RFC PATCH v2 09/32] x86: Change early_ioremap to early_memremap for BOOT data

On Thu, Mar 02, 2017 at 10:13:53AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > In order to map BOOT data with the proper encryption bit, the Btw, what does that all-caps spelling "BOOT" denote? Something I'm missing? > early_ioremap() function calls are

Re: next build: 208 builds: 21 failed, 187 passed, 53 errors, 406 warnings (next-20170308)

On Wed, Mar 8, 2017 at 4:40 AM, kernelci.org bot wrote: > next build: 208 builds: 21 failed, 187 passed, 53 errors, 406 warnings > > allmodconfig (arm) — PASS, 0 errors, 6 warnings, 0 section mismatches > > Warnings: > :1325:2: warning: #warning syscall statx not implemented

[PATCH 0/5] fs, xfs refcount conversions

v3: * fixed header file inclusion Now when new refcount_t type and API are finally merged (see include/linux/refcount.h), the following patches convert various refcounters in the xfs susystem from atomic_t to refcount_t. By doing this we prevent intentional or accidental underflows or overflows

[PATCH 1/5] fs, xfs: convert xfs_bui_log_item.bui_refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

Hi David, Inki, Thanks for reporting. On 06.03.2017 11:05, David Binderman wrote: > Hello there, > > linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) > Result of operator '|' is always true if one operand is non-zero. Did you > intend to use '&'? > > Source code is

Re: [PATCH 1/2] x86/efi: Correct a tiny mistake in code comment

Hi Dave, On Wed, Mar 8, 2017 at 1:48 PM, Dave Young wrote: > On 03/08/17 at 03:47pm, Baoquan He wrote: >> EFI allocate runtime services regions down from EFI_VA_START, -4G. >> It should be top-down handling. >> >> Signed-off-by: Baoquan He >> --- >>

Re: [PATCH] mm: Do not use double negation for testing page flags

On 03/08/2017 06:25 AM, Minchan Kim wrote: > Hi Anshuman, > > On Tue, Mar 07, 2017 at 09:31:18PM +0530, Anshuman Khandual wrote: >> On 03/07/2017 12:06 PM, Minchan Kim wrote: >>> With the discussion[1], I found it seems there are every PageFlags >>> functions return bool at this moment so we

<    3   4   5   6   7   8   9   10   11   12   >