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

On 08/03/17 08:59, Peter Rosin wrote: > 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,

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

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 stale. Signed-off-by: Ravi Bangoria ---

[PATCH 1/4] qxl: drop mode_info.modes & related code.

very old qxl hardware revisions (predating qxl ksm support by a few years) supported a fixed list of video modes only. The list is still provided by the virtual hardware, for backward compatibility reasons. The qxl kms driver never ever looks at it, except for dumping it to the kernel log at

[PATCH 2/4] qxl: limit monitor config read retries

When reading the monitor config fails, don't retry forever. If it fails ten times in a row just give up to avoid the driver hangs. Also add a small delay after each attempt, so the host has a chance to complete a partial update. Signed-off-by: Gerd Hoffmann ---

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

Hi, Next version if the bcm2835 sdhost patch series. New in v4: * squashed in more cleanups by Stefan. * removed the long cleanup patch list from commit message (patch 2). * rebased to (and tested with) 4.11-rc1. * minor fixes pointed out in review. New in v3: * squashed in cleanups

[PATCH v4 3/7] mmc: bcm2835: add sdhost controller to devicetree

Signed-off-by: Gerd Hoffmann Acked-by: Eric Anholt --- arch/arm/boot/dts/bcm2835-rpi.dtsi | 6 ++ arch/arm/boot/dts/bcm283x.dtsi | 10 ++ 2 files changed, 16 insertions(+) diff --git a/arch/arm/boot/dts/bcm2835-rpi.dtsi

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

From: Eric Anholt The 2835 has two SD controllers: The Arasan sdhci controller (supported by the iproc driver) and a custom sdhost controller. This patch adds a driver for the latter. The sdhci controller supports both sdcard and sdio. The sdhost controller supports the

[PATCH v4 1/7] dt-bindings: Add binding for brcm,bcm2835-sdhost.

From: Eric Anholt This is the other SD controller on the platform, which can be swapped to the role of SD card host using pin muxing. Signed-off-by: Eric Anholt Signed-off-by: Gerd Hoffmann Acked-by: Rob Herring ---

[PATCH v4 6/7] arm: dts: bcm283x: switch from to

sdcard access with the sdhost controller is faster. 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 much in the noise. Signed-off-by: Gerd Hoffmann Acked-by: Eric

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

Hi Morimoto-san, Thank you for the patch. On Wednesday 08 Mar 2017 00:42:54 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

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: > >> EFI allocate runtime services regions down from EFI_VA_START, -4G. > >> It should be top-down handling. > >> > >>

[PATCH v4 7/7] arm64: dts: bcm2837: add and

For the raspberry pi 3 we'll need both sdhci (handles sdio wifi) and sdhost (handles sdcard). Signed-off-by: Gerd Hoffmann Acked-by: Eric Anholt --- arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts | 17 + 1 file changed, 17 insertions(+)

Re: [PATCH v2 1/2] sched/loadavg: Avoid loadavg spikes caused by delayed NO_HZ accounting

2017-02-17 20:07 GMT+08:00 Matt Fleming : > If we crossed a sample window while in NO_HZ we will add LOAD_FREQ to > the pending sample window time on exit, setting the next update not > one window into the future, but two. > > This situation on exiting NO_HZ is described

[RFC PATCH] sched/wait: Add dependency for now

* Ingo Molnar wrote: > In any case, it's clear that this stuff is in no way v4.11 material, so as a > bridging fix I propose we add a sched/signal.h include to wait.h (or just > move > signal_pending() temporarily), until it's all resolved for real for v4.12. I.e. I

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

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 reason to GPL-protect the basic kref_get and kref_put routines, because when designing

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

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 in my response to the 0/1 of this patch, this

[PATCH 1/2] perf probe: Fix concat_probe_trace_events

'*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 '*ntevs == 0' not 'ntevs == 0'. Fixes: 42bba263eb58 ("perf probe: Allow wildcard for cached

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

On 2017年03月08日 16:09, Marc Zyngier wrote: 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 [

Re: [PATCH 2/2] Staging: comedi: comedi_fops: Fix "out of minor numbers for board device files"

Dear Dan, Thanks for reviewing this patch. On Wed, Mar 08, 2017 at 08:54:47AM +0300, Dan Carpenter wrote: > On Sun, Mar 05, 2017 at 03:22:33AM +0800, Cheah Kok Cheong wrote: > > If comedi module is loaded with the following max allowed parameter > > [comedi_num_legacy_minors=48], subsequent

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

On Wed, Mar 08, 2017 at 10:45:26AM +0100, Greg KH wrote: > 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,

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

On Wed, Mar 08, 2017 at 01:59:33AM -0800, John Hubbard wrote: > > > On 03/08/2017 01:48 AM, Greg Kroah-Hartman wrote: > > 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

Re: [Outreachy kernel] [PATCH 1/3] staging: rtl8192u: Replace "is is" with "is"

On 04/03/17 16:18, Julia Lawall wrote: On Sat, 4 Mar 2017, simran singhal wrote: This patch replace "is is " with "is". The replacement couldn't be automated because sometimes the first "is" was meant to be another word. Signed-off-by: simran singhal ---

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

On Wed, Mar 08, 2017 at 09:42:09AM +, Reshetova, Elena wrote: > > 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

[PATCH] video/logo: tidyup fb_logo_late_init initcall timing

From: Takeshi Kihara Some video driver might returns -EPROBE_DEFER when probe timing, but logo init function doesn't care it. Thus, such kernel can't have logo when boot time. This patch solves this issue by exchanging current late_initcall to late_initcall_sync

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

On Wed, Mar 08, 2017 at 10:26:54AM +0200, Jani Nikula wrote: > 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. > >

Re: counting file descriptors with a cgroup controller

On 03/08/2017 03:59 AM, Parav Pandit wrote: Hi, On Tue, Mar 7, 2017 at 2:48 PM, Tejun Heo wrote: Hello, On Tue, Mar 07, 2017 at 09:06:49PM +0100, Krzysztof Opasiak wrote: Personally, I don't want to use rlimit for this as it ends up returning error code from for example

Re: [PATCH v3 1/6] drm: bridge: dw-hdmi: Extract PHY interrupt setup to a function

Hi Jose, On 03/07/2017 06:12 PM, Jose Abreu wrote: > Hi Neil, > > > On 07-03-2017 16:42, Neil Armstrong wrote: >> From: Laurent Pinchart >> >> In preparation for adding PHY operations to handle RX SENSE and HPD, >> group all the PHY interrupt setup

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

On 03/08/17 at 10:35am, Borislav Petkov wrote: > 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: All right, I will just update the code comment. Just back ported kaslr to our OS product, people

Re: [PATCH v5 01/15] stacktrace/x86: add function for detecting reliable stack traces

On Tue, 2017-03-07 at 10:12 -0600, Josh Poimboeuf wrote: > On Tue, Mar 07, 2017 at 05:50:55PM +1100, Balbir Singh wrote: > > On Mon, 2017-02-13 at 19:42 -0600, Josh Poimboeuf wrote: > > > For live patching and possibly other use cases, a stack trace is only > > > useful if it can be assured that

[PATCH] staging: android: ashmem: lseek failed due to no FMODE_LSEEK.

From: zhangshuxiao vfs_llseek will check whether the file mode has FMODE_LSEEK, no return failure. But ashmem can be lseek, so add FMODE_LSEEK to ashmem file. Signed-off-by: zhangshuxiao --- drivers/staging/android/ashmem.c | 1 + 1 file

Re: [PATCH] storvsc: workaround for virtual DVD SCSI version

On 03/07/2017 06:15 PM, Stephen Hemminger wrote: > Hyper-V host emulation of SCSI for virtual DVD device reports SCSI > version 0 (UNKNOWN) but is still capable of supporting REPORTLUN. > > Without this patch, a GEN2 Linux guest on Hyper-V will not boot 4.11 > successfully with virtual DVD ROM

Re: staging/atomsip: undefined Kconfig symbols

On Wed, 2017-03-08 at 09:39 +0100, Valentin Rothberg wrote: > > Hi Alan, > > > > your commit a49d25364dfb ("staging/atomisp: Add support for the > > Intel IPU v2") has shown up in linux-next.  I run daily checks on > > linux-next with scripts/checkkconfigsymbols.py, which complained > > about the

Re: [PATCH] mm, vmalloc: use __GFP_HIGHMEM implicitly

On 03/07/2017 03:10 PM, Michal Hocko wrote: > From: Michal Hocko > > __vmalloc* allows users to provide gfp flags for the underlying > allocation. This API is quite popular > $ git grep "=[[:space:]]__vmalloc\|return[[:space:]]*__vmalloc" | wc -l > 77 > > the only problem is

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

On Wed, 8 Mar 2017 13:56:10 +0530 "Naveen N. Rao" wrote: > 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

Re: [PATCH v5 00/15] livepatch: hybrid consistency model

On Mon, 13 Feb 2017, Josh Poimboeuf wrote: > Here's v5 of the consistency model I have ammended the patches with all the received ACKs and applied to 'for-4.12/klp-hybrid-consistency-model' branch of livepatching.git. Thanks, -- Jiri Kosina SUSE Labs

v4.11-rc1 boot time regression

+Cc: Felipe and missed LKML On Tue, Mar 7, 2017 at 9:02 PM, Andy Shevchenko wrote: > Hi! > > Frankly don't know whom to blame (maybe even me). That's why a list in > To is kinda (semi-) random. > > I have two branches on my Github: > >

Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI call chain

* Mike Travis wrote: > > > On 3/6/2017 11:42 PM, Ingo Molnar wrote: > > > > * Mike Travis wrote: > > > >> Add a new NMI call chain that is called last after all other NMI handlers > >> have been checked and did not "handle" the NMI. This mimics

Re: Applied "spi: davinci: enable DMA when channels are defined in DT" to the spi tree

Hello Mark, To avoid data corruption issues with UBIFS volume over SPI NOR, DMA should not be used for vmalloc'ed buffers. The 5'th patch in my series fixes that: 0003-spi-davinci-use-rx-buffer-as-dummy-tx-buffer.patch 0004-spi-davinci-do-not-use-DMA-if-transfer-length-is-les.patch

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

Hi, On 08/03/17 09:54, Philipp Zabel wrote: > 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

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

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 negative value check in > > init section. > > Why? > User can input a -ve

Re: [PATCH] mm, vmalloc: use __GFP_HIGHMEM implicitly

On Tue 07-03-17 15:08:45, Andrew Morton wrote: > On Tue, 7 Mar 2017 15:10:20 +0100 Michal Hocko wrote: > > > __vmalloc* allows users to provide gfp flags for the underlying > > allocation. This API is quite popular > > $ git grep

Re: [RESEND PATCH 1/6] trace/kprobes: fix check for kretprobe offset within function entry

On 2017/03/07 03:47PM, Steven Rostedt wrote: > > Please start a new thread. When sending patches as replies to other > patch threads, especially this deep into the thread, they will most > likely get ignored. Sorry, got carried off. I will re-post in a new series. - Naveen

Re: [PATCH] mm, vmalloc: use __GFP_HIGHMEM implicitly

On Wed 08-03-17 08:33:58, Vlastimil Babka wrote: > On 03/07/2017 03:10 PM, Michal Hocko wrote: [...] > > index dece26f119d4..a804a4107fbc 100644 > > --- a/drivers/block/drbd/drbd_bitmap.c > > +++ b/drivers/block/drbd/drbd_bitmap.c > > @@ -409,7 +409,7 @@ static struct page

Re: [PATCH 3/3] cpufreq: schedutil: remove redundant code from sugov_next_freq_shared()

On Wed, Mar 8, 2017 at 5:18 AM, Viresh Kumar wrote: > On 07-03-17, 14:19, Rafael J. Wysocki wrote: >> On Tue, Mar 7, 2017 at 11:31 AM, Viresh Kumar >> wrote: >> > Why do you think so? I thought all CPU in the policy can have the RT/DL >> > flag

Re: [PATCH v1 3/3] staging: comedi: Replace "is is" with "is"

On 04/03/17 17:41, simran singhal wrote: This patch replace "is is " with "is". The replacement couldn't be automated because sometimes the first "is" was meant to be another word. Signed-off-by: simran singhal Acked-by: Julia Lawall ---

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

On Wed, 2017-03-08 at 09:26 +, Andre Przywara wrote: > 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

[PATCH v3 5/7] PCI: dwc: all: Modify dbi accessors to access data of 4/2/1 bytes

Previously dbi accessors can be used to access data of size 4 bytes. But there might be situations (like accessing MSI_MESSAGE_CONTROL in order to set/get the number of required MSI interrupts in EP mode) where dbi accessors must be used to access data of size 2. This is in preparation for adding

[PATCH v3 4/7] PCI: dwc: all: Modify dbi accessors to take dbi_base as argument

dwc has 2 dbi address space labeled dbics and dbics2. The existing helper to access dbi address space can access only dbics. However dbics2 has to be accessed for programming the BAR registers in the case of EP mode. This is in preparation for adding EP mode support to dwc driver. Cc: Jingoo Han

[PATCH v3 2/7] PCI: dwc: dra7xx: Populate cpu_addr_fixup ops

Populate cpu_addr_fixup ops to extract the least 28 bits of the corresponding cpu address. Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/dwc/pci-dra7xx.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/drivers/pci/dwc/pci-dra7xx.c

Re: [PATCH 0/3] ASoC: add dio2125 amplifier support

On Tue, Mar 07, 2017 at 05:26:17PM +0100, Jerome Brunet wrote: > Hi Mark, Please don't top post, reply in line with needed context. This allows readers to readily follow the flow of conversation and understand what you are talking about and also helps ensure that everything in the discussion is

[PATCH v3 3/7] PCI: dwc: artpec6: Populate cpu_addr_fixup ops

Populate cpu_addr_fixup ops to extract the least 28 bits of the corresponding cpu address. Cc: Niklas Cassel Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/dwc/pcie-artpec6.c | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-)

Re: [PATCH 2/2] iproute2: add support for invisible qdisc dumping

On Mon, 27 Feb 2017, Phil Sutter wrote: > > Support the new TCA_DUMP_INVISIBLE netlink attribute that allows asking > > kernel to perform 'full qdisc dump', as for historical reasons some of the > > default qdiscs are being hidden by the kernel. > > > > The command syntax is being extended by

[PATCH v3 7/7] PCI: dwc: dra7xx: Push request_irq call to the bottom of probe

From: Keerthy Currently devm_request_irq is being called before base, pci fields of dra7xx_pcie structure are populated. It is called even before pm_runtime_enable and pm_runtime_get_sync are called. This will lead to exceptions if in case an interrupt is triggered before the

[PATCH v3 6/7] PCI: dwc: designware: Move _unroll configurations to a separate function

No functional change. Rename dw_pcie_writel_unroll/dw_pcie_readl_unroll to dw_pcie_writel_ob_unroll/dw_pcie_readl_ob_unroll respectively as these functions are used to perform only outbound configurations. Also move these _unroll configurations to a separate function. Signed-off-by: Kishon Vijay

[PATCH v3 01/09] iommu/ipmmu-vmsa: Introduce features, break out alias

From: Magnus Damm Introduce struct ipmmu_features to track various hardware and software implementation changes inside the driver for different kinds of IPMMU hardware. Add use_ns_alias_offset as a first example of a feature to control if the secure register bank

Re: [PATCH 1/2] usb: xhci-mtk: check hcc_params after adding primary hcd

On 08.03.2017 02:51, Chunfeng Yun wrote: On Tue, 2017-03-07 at 17:10 +0200, Mathias Nyman wrote: On 07.03.2017 05:32, Chunfeng Yun wrote: hcc_params is set in xhci_gen_setup() called from usb_add_hcd(), so checks the Maximum Primary Stream Array Size in the hcc_params register after adding

[PATCH v3 00/09] iommu/ipmmu-vmsa: r8a7795 support V3

iommu/ipmmu-vmsa: r8a7795 support V3 [PATCH v3 01/09] iommu/ipmmu-vmsa: Introduce features, break out alias [PATCH v3 02/09] iommu/ipmmu-vmsa: Add optional root device feature [PATCH v3 03/09] iommu/ipmmu-vmsa: Enable multi context support [PATCH v3 04/09] iommu/ipmmu-vmsa: Make use of

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

[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]

[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: Hans Liljestrand

[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

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 (Add O= to support) is upstream material, but

[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 Signed-off-by: Jagan Teki --- Changes for v4, v3, v2: - none arch/arm/boot/dts/imx6qdl-icore.dtsi | 20 1

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(-) > > diff --git

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 > 40bit address today. But it can use Descriptor Mode with 40bit if >

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 notice of rather lately is

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 > --- > drivers/gpio/gpio-mockup.c | 16 +--- > 1

[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

[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 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 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 + 1 file changed, 9 insertions(+) diff --git

[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 changed, 1 insertion(+), 1

[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 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

[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 procedure for fixing them. BR, Jani. --

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

[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 drivers that might be

[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, 64 bit, DDR3-800/1066 NAND

[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 ---

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 boundary of memory

[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 garbage. This needs to be fixed. > > Here's a (totally

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 and >> u32, during the

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 > [-Wunused-variable] >

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 13:35:29 +0900 >

[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 property, to indicate

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 '*ntevs == 0' not 'ntevs == 0'.

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 changed to early_memremap()

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 [-Wcpp] The syscall

[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: Hans Liljestrand

[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: Hans Liljestrand

[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: Hans Liljestrand

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

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