[PATCH v2 3/3] ARM: dts: k2g-evm: Add pinmuxing for UART0

From: Lokesh Vutla Avoid depending on the bootloader or the ROM for configuring the pinmux by explicitly setting the pinmux here. Signed-off-by: Lokesh Vutla Signed-off-by: Franklin S Cooper Jr Signed-off-by: Tero Kristo

Re: [RESEND PATCH v5 1/5] mfd: RK808: Add RK818 support

On Thu, 09 Jun 2016, Wadim Egorov wrote: > > > On 09.06.2016 13:12, Lee Jones wrote: > > On Thu, 09 Jun 2016, Wadim Egorov wrote: > >> On 08.06.2016 16:17, Lee Jones wrote: > >>> On Thu, 02 Jun 2016, Wadim Egorov wrote: > >>> > The RK818 chip is a power management IC for multimedia and

[PATCH 6/8] tty: serial: fsl-lpuart: Use scatter/gather DMA for Tx Drop PIO to DMA switching and use scatter/gather DMA for Tx path to improve performance.

Some part of the code is borrowed from imx serial driver. Signed-off-by: Bhuvanchandra DV --- drivers/tty/serial/fsl_lpuart.c | 257 ++-- 1 file changed, 113 insertions(+), 144 deletions(-) diff --git

Re: [PATCH v3 2/2] arm64: dts: Fix broken architected timer interrupt trigger

On 06/06/2016 12:56 PM, Marc Zyngier wrote: > The ARM architected timer specification mandates that the interrupt > associated with each timer is level triggered (which corresponds to > the "counter >= comparator" condition). > > A number of DTs are being remarkably creative, declaring the

[PATCH v11 1/2] Documentation: DT: dma: Add Xilinx zynqmp dma device tree binding documentation

Device-tree binding documentation for Xilinx zynqmp dma engine used in Zynq UltraScale+ MPSoC. Acked-by: Rob Herring Signed-off-by: Punnaiah Choudary Kalluri Signed-off-by: Kedareswara rao Appana --- Changes in v11: - None. Changes in

Re: [PATCH v10 11/14] usb: otg: use dev_dbg() instead of VDBG()

On Thu, 2016-06-09 at 10:55 +0300, Roger Quadros wrote: > Now that we have a device reference in struct usb_otg > let's use dev_vdbg() for debug messages instead of VDBG(). > > Signed-off-by: Roger Quadros > Acked-by: Peter Chen > --- > v10: > - in the commit

Re: [PATCH] x86/microcode/intel: Quieten down microcode updates on large systems

On Thu, 09 Jun 2016, Elliott, Robert (Persistent Memory) wrote: > > + if (val[1] != prev_rev) { > > + pr_info("CPU updated to revision 0x%x, date = %04x-%02x- > > %02x\n", > > "CPU(s)" would help convey that the messages now apply to one or > more CPUs. Agreed, especially because

Re: [PATCH trivial] include/linux/memcontrol.h: Clean up code only

On Thu 09-06-16 23:23:52, cheng...@emindsoft.com.cn wrote: > From: Chen Gang > > Merge several statements to one return statement, since the new return > statement is still simple enough. > > Try to let the second line function parameters almost align with the > first

Re: [PATCH 2/2] soc: qcom: add l2 cache perf events driver

On Wed, Jun 08, 2016 at 11:16:06AM -0400, Neil Leeder wrote: > On 6/6/2016 05:51 AM, Mark Rutland wrote: > > On Fri, Jun 03, 2016 at 05:03:32PM -0400, Neil Leeder wrote: > >> +/* > >> + * The cache is made-up of one or more slices, each slice has its own PMU. > >> + * This structure represents one

Re: [PATCH v6 0/8] block: prepare for multipage bvecs

On 05/30/2016 07:34 AM, Ming Lei wrote: Hi, Interests[1] have been shown in multipage bvecs, so this patchset try to prepare for the support and do two things: 1) the 1st 4 patches use bvec iterator to implement iterate_bvec(), then we can drop the non-standard way for iterating bvec, which

Re: [PATCH v2 29/38] kernel-doc: limit the "section header:" detection to a select few

On Sat, 4 Jun 2016 14:37:30 +0300 Jani Nikula wrote: > kernel-doc currently identifies anything matching "section header:" > (specifically a string of word characters and spaces followed by a > colon) as a new section in the documentation comment, and renders the >

Re: [PATCH] mm: mempool: kasan: don't poot mempool objects in quarantine

On Thu, Jun 9, 2016 at 4:05 PM, Andrey Ryabinin wrote: > On 06/01/2016 07:22 PM, Andrey Ryabinin wrote: >> >> >> On 06/01/2016 03:53 PM, Alexander Potapenko wrote: >>> To avoid draining the mempools, KASAN shouldn't put the mempool elements >>> into the quarantine upon

[PATCH v11 2/2] dmaengine: Add Xilinx zynqmp dma engine driver support

Added the driver for zynqmp dma engine used in Zynq UltraScale+ MPSoC. This dma controller supports memory to memory and I/O to I/O buffer transfers. Signed-off-by: Punnaiah Choudary Kalluri Signed-off-by: Kedareswara rao Appana --- Changes for v11: -

Re: [PATCH V2 1/2] regmap: irq: Add support to call client specific pre/post interrupt service

On Thu, Jun 09, 2016 at 08:43:06PM +0530, Laxman Dewangan wrote: > Regmap irq implements the generic interrupt service routine which > is common for most of devices. Some devices, like MAX77620, MAX20024 > needs the special handling before and after servicing the interrupt > as generic. For the

Re: [PATCH 1/1] mm/swap.c: flush lru_add pvecs on compound page arrival

On 06/09/2016 01:50 AM, Odzioba, Lukasz wrote: > On 08-06-16 17:31:00, Dave Hansen wrote: >> Do we have any statistics that tell us how many pages are sitting the >> lru pvecs? Although this helps the problem overall, don't we still have >> a problem with memory being held in such an opaque

Re: [PATCH 10/10] mm, oom: hide mm which is shared with kthread or global init

On Fri 10-06-16 00:15:18, Tetsuo Handa wrote: [...] > Nobody will set MMF_OOM_REAPED flag if can_oom_reap == true on > CONFIG_MMU=n kernel. If a TIF_MEMDIE thread in CONFIG_MMU=n kernel > is blocked before exit_oom_victim() in exit_mm() from do_exit() is > called, the system will lock up. This is

Re: [PATCH v2 10/10] x86, asm: Use CC_SET()/CC_OUT() and static_cpu_has() in archrandom.h

On Wed, Jun 08, 2016 at 12:38:46PM -0700, H. Peter Anvin wrote: > Use CC_SET()/CC_OUT() and static_cpu_has(). This produces code good > enough to eliminate ad hoc use of alternatives in , > greatly simplifying the code. > > While we are at it, make x86_init_rdrand() compile out completely if >

Re: [PATCH v3 3/3] mfd: lpc_ich: Add support for Intel Apollo Lake GPIO pinctrl in non-ACPI system

On Tue, 07 Jun 2016, Tan Jui Nee wrote: > This driver uses the P2SB hide/unhide mechanism cooperatively > to pass the PCI BAR address to the gpio platform driver. > > Signed-off-by: Tan Jui Nee > --- You really need to supply a changelog here when you send subsequent

Re: general preparation for NVMe over Fabrics support

On Thu, Jun 09, 2016 at 12:38:55PM -0400, Keith Busch wrote: > For patch ordering, I had thought there were no issues with these > I submitted: > > http://lists.infradead.org/pipermail/linux-nvme/2016-May/004704.html > http://lists.infradead.org/pipermail/linux-nvme/2016-May/004709.html > >

Re: [PATCH] pvclock: introduce seqcount-like API

On Thu, Jun 9, 2016 at 6:45 AM, Paolo Bonzini wrote: > > > On 09/06/2016 15:35, Roman Kagan wrote: >> On Thu, Jun 09, 2016 at 02:47:54PM +0200, Paolo Bonzini wrote: >>> On 09/06/2016 14:43, Roman Kagan wrote: On Thu, Jun 09, 2016 at 01:23:23PM +0200, Paolo Bonzini wrote:

Re: [PATCH 1/4] dt-bindings: Add A10 I2S controller binding documentation

Hi Rob, On Mon, Jun 06, 2016 at 08:08:18AM -0500, Rob Herring wrote: > On Wed, Jun 01, 2016 at 07:54:27PM +0200, Maxime Ripard wrote: > > Introduce the device tree binding for the I2S controller found in the > > Allwinner A10 and later SoCs. > > > > Signed-off-by: Maxime Ripard

Re: [PATCH 2/2] perf stat: Remove nmi watchdog check code again

Em Thu, Jun 09, 2016 at 08:17:16AM -0700, Andi Kleen escreveu: > On Thu, Jun 09, 2016 at 10:42:08AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Thu, Jun 09, 2016 at 06:14:39AM -0700, Andi Kleen escreveu: > > > Now that the NMI watchdog runs with reference cycles, and does not > > Now as in

Re: [PATCH v3] powerpc: spinlock: Fix spin_unlock_wait()

On Thu, Jun 09, 2016 at 10:23:28PM +1000, Michael Ellerman wrote: > On Wed, 2016-06-08 at 15:59 +0200, Peter Zijlstra wrote: > > On Wed, Jun 08, 2016 at 11:49:20PM +1000, Michael Ellerman wrote: > > > > > > Ok; what tree does this go in? I have this dependent series which I'd > > > > like to get

Re: [PATCH 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32)

On Jun 6, 2016 3:21 PM, "Oleg Nesterov" wrote: > > On 06/01, Dmitry Safonov wrote: > > > > Note, that this will work only if application has changed it's CS. > > So, suppose it changes it's CS and crashes, > > > If the application does 32-bit syscall with __USER_CS, ptrace > > @@

Re: SIGSYS annoyance

On Mon, Jun 6, 2016 at 9:03 AM, Kees Cook wrote: > On Fri, Jun 3, 2016 at 10:16 PM, Andy Lutomirski wrote: >> https://bugzilla.mozilla.org/show_bug.cgi?id=1176099 >> >> Should SIGSYS be delivered to the handler even if blocked? What, if >> anything,

Re: [PATCH 27/32] gpio: Add support for the FXL6408 GPIO expander.

Linus Walleij writes: > On Wed, Jun 1, 2016 at 11:43 PM, Gerd Hoffmann wrote: > >> +#define FXL6408_OUTPUT 0x05 >> +/* Bits here make the output High-Z, instead of the OUTPUT value. */ >> +#define FXL6408_OUTPUT_HIGH_Z 0x07 >

Re: [PATCH v8 02/12] kthread: Kthread worker API cleanup

On Thu, Jun 09, 2016 at 03:51:56PM +0200, Petr Mladek wrote: > -#define DEFINE_KTHREAD_WORKER(worker) > \ > - struct kthread_worker worker = KTHREAD_WORKER_INIT(worker) > +#define KTHREAD_DECLARE_WORKER(worker) > \

[PATCH v2] LSM: module hierarchy in /proc/.../attr

Subject: [PATCH v2] LSM: module hierarchy in /proc/.../attr v2: Rebase on security-next Change to Loadpin for add hook interface change Fix comment formatting Back in 2007 I made what turned out to be a rather serious mistake in the implementation of the Smack security

Re: [PATCH 3/4] mtd: nand: Add support for Evatronix NANDFLASH-CTRL

On 6/9/16, Ricard Wanderlof wrote: > The designers of this IP apparantly did not have Linux in mind when they > designed the controller, since it does all the low level stuff > autonomously (in the right IP configuration it can even remap flash blocks > transparently),

Re: [PATCH 2/2] x86/entry: Inline enter_from_user_mode

On Mon, Jun 6, 2016 at 9:01 AM, Paolo Bonzini wrote: > > > On 04/06/2016 07:08, Andy Lutomirski wrote: >> On May 30, 2016 5:30 AM, "Paolo Bonzini" wrote: >>> >>> This matches what is already done for prepare_exit_to_usermode, >>> and saves about 60 clock

[PATCH 1/1] MAINTAINERS: Update Calgary IOMMU

Update the contact info for Muli, clean-up my name, and update the mailing list to the IOMMU mailing list. Signed-off-by: Jon Mason Cc: Muli Ben-Yehuda --- MAINTAINERS | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/MAINTAINERS

Re: [RFC 05/13] x86/mm: Add barriers and document switch_mm-vs-flush synchronization

On Fri, Jun 3, 2016 at 10:42 AM, Nadav Amit wrote: > Following this patch, if (current->active_mm != mm), flush_tlb_page() still > doesn’t call smp_mb() before checking mm_cpumask(mm). > > In contrast, flush_tlb_mm_range() does call smp_mb(). > > Is there a reason for this

Re: [kernel-hardening] Re: [PATCH v2 1/3] Add the latent_entropy gcc plugin

On 7 Jun 2016 at 9:58, Theodore Ts'o wrote: > On Tue, Jun 07, 2016 at 02:19:14PM +0200, PaX Team wrote: > > (i believe that) latent entropy is found in more than just interrupt > > timing, there're > > also data dependent computations that can have entropy, either on a single > > system or > >

Re: [PATCH v3] storvsc: use small sg_tablesize on x86

On Thu, 2016-06-09 at 18:25 +0200, Olaf Hering wrote: > Reducing the sg_tablesize allows booting of 32bit kernels in VMs, > after > commit be0cf6ca301c61458dc4aa1a37acf4f58d2ed3d6 ("scsi: storvsc: Set > the > tablesize based on the information given by the host") > > [5.567138] hv_storvsc

Re: [PATCH] intel_menlow: prevent NULL pointer dereference

On Wed, Jun 08, 2016 at 01:38:46PM -0700, Darren Hart wrote: > Under what circumstances can the .remove op be called with a NULL struct > acpi_device * as a parameter? From what I can see, most acpi_* calls accpeting > an acpi_device rely on it not being null, and they are regularly called from >

[PATCH 0/1] MAINTAINERS: Update Calgary IOMMU

This was originally sent in Feb 2014, and then promptly forgotten. See https://lists.linuxfoundation.org/pipermail/iommu/2014-February/007690.html Krzysztof Kozlowski sent a similar patch last week. See http://www.spinics.net/lists/kernel/msg2268572.html This prompted a discussion, which

Re: [PATCH] x86/mm: Change barriers before TLB flushes to smp_mb__after_atomic

On Fri, May 27, 2016 at 8:16 PM, Nadav Amit wrote: > When (current->active_mm != mm), flush_tlb_page() does not perform a > memory barrier. In practice, this memory barrier is not needed since in > the existing call-sites the PTE is modified using atomic-operations. > This patch

Re: [PATCH] staging: fbtft: do not allocate huge txbuf

Hello, On 9 June 2016 at 18:20, Noralf Trønnes wrote: > > Den 09.06.2016 17:08, skrev Michal Suchanek: >> >> txbuflen can be set to arbitrary value by user and it is also set >> automagically to the maximum transfer size of the SPI master controller. > > > AFAICT this is a

Re: [PATCH] autofs: don't stuck in a loop if vfs_write returns an error

On Wed, Jun 8, 2016 at 6:23 PM, Ian Kent wrote: > On Mon, 2016-05-30 at 13:52 +0800, Ian Kent wrote: >> On Tue, 2016-05-24 at 09:34 +0800, Ian Kent wrote: >> > On Mon, 2016-05-23 at 14:50 -0700, Andrei Vagin wrote: >> > > Hi Ian, >> > > >> > > When are you going to apply this

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

On Thu, 9 Jun 2016 12:57:16 +0200 Michal Marek wrote: > Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a): > > On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote: > >> Ah, yes, that should default to off. We'll get a fix landed ASAP. > > > > Note that this

Re: 4.6-rc*: Kernel unaligned access at pci_bus_read_config_dword+0x64/0x80

On Thu, Jun 2, 2016 at 10:11 PM, Meelis Roos wrote: > Between 4.5.0 and 4.6.0-rc3, my Spar Enterprise T5120 has started > showing the following messages during bootup: > > [ 64.564608] Kernel unaligned access at TPC[69fb04] > pci_bus_read_config_dword+0x64/0x80 > [ 64.564688]

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

On Thu, 9 Jun 2016 12:22:58 +1000 Stephen Rothwell wrote: > Hi Michal, > > After merging the kbuild tree, today's linux-next build (x86_64 > allmodconfig) produced these warnings: > > Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main > Cyclomatic Complexity

Re: [RFC 1/1] ARM: print MHz in /proc/cpuinfo

On Thu, Jun 9, 2016 at 5:09 AM, Sudeep Holla wrote: > > > On 08/06/16 20:31, Jon Mason wrote: >> >> On Wed, Jun 08, 2016 at 09:34:06AM +0100, Sudeep Holla wrote: >>> >>> >>> >>> On 07/06/16 22:08, Jon Mason wrote: Query the CPU core clock in the device tree to

[PATCH RFC 2/2] MAINTAINERS: Add support for FDP driver

Signed-off-by: Kieran Bingham --- MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 66de4da2d244..bc083b58e478 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -7312,6 +7312,15 @@ S: Supported F:

[PATCH RFC 0/2] v4l: platform: Add Renesas R-Car FDP1 Driver

This early version of the driver, is submitted for review, and functions only as a pixel format converter. The FDP1, (Fine Display Processor) is a de-interlacer device, with capability to convert from various YCbCr/YUV formats to both YCbCr/YUV and RGB formats at the same time as converting

Re: [RFC 10/12] x86, rwsem: simplify __down_write

On Thu, Jun 09, 2016 at 03:40:58PM +0100, David Howells wrote: > Peter Zijlstra wrote: > > > Blergh; so looking at more asm there's still a few tricks we cannot do. > > So while overall size is down, some paths do end up more expensive. (It > > typically boils down to

[PATCH RFC 1/2] v4l: platform: Add Renesas R-Car FDP1 Driver

The FDP1 driver performs advanced de-interlacing on a memory 2 memory based video stream, and supports conversion from YCbCr/YUV to RGB pixel formats Signed-off-by: Kieran Bingham --- drivers/media/platform/Kconfig | 13 + drivers/media/platform/Makefile|1 +

Re: [PATCH 1/2] mfd: sm-usb-dig: Add support for the TI SM-USB-DIG

On Thu, 09 Jun 2016, Andrew F. Davis wrote: > On 06/09/2016 09:23 AM, Lee Jones wrote: > > On Wed, 08 Jun 2016, Andrew F. Davis wrote: > > > >> On 06/08/2016 08:06 AM, Lee Jones wrote: > >>> On Tue, 31 May 2016, Andrew F. Davis wrote: > >>> > The TI SM-USB-DIG is a USB to SPI/I2C/1Wire/GPIO

[PATCH] clk: renesas: r8a7795: Provide FDP1 clocks

Reviewed-by: Geert Uytterhoeven Reviewed-by: Laurent Pinchart Signed-off-by: Kieran Bingham --- drivers/clk/renesas/r8a7795-cpg-mssr.c | 3 +++ 1 file changed, 3 insertions(+) diff --git

Re: [RFC PATCH v1 10/18] x86/efi: Access EFI related tables in the clear

On 06/08/2016 05:07 AM, Matt Fleming wrote: > (Sorry for the delay) No worries, thanks for all the feedback. > > On Thu, 26 May, at 08:45:58AM, Tom Lendacky wrote: >> >> The patch in question is patch 6/18 where PAGE_KERNEL is changed to >> include the _PAGE_ENC attribute (the encryption mask).

Re: [PATCH] staging: fbtft: do not allocate huge txbuf

Den 09.06.2016 17:08, skrev Michal Suchanek: txbuflen can be set to arbitrary value by user and it is also set automagically to the maximum transfer size of the SPI master controller. AFAICT this is a result of your previous patch. Please make a new version of your previous patch with this

Re: [PATCH 2/2] iommu/amd: Destroy api_lock mutex when freeing domain

On Sat, 2016-05-21 at 14:11 -0400, Jan Vesely wrote: > From: Jan Vesely > > Signed-off-by: Jan Vesely > --- >  drivers/iommu/amd_iommu.c | 1 + >  1 file changed, 1 insertion(+) > > diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c >

[PATCH V2 4/5] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge

Add a driver that create a drm_bridge and a drm_connector for the LVDS to DP++ display bridge of the GE B850v3. There are two physical bridges on the video signal pipeline: a STDP4028(LVDS to DP) and a STDP2690(DP to DP++). The hardware and firmware made it complicated for this binding to

Re: general preparation for NVMe over Fabrics support

On Mon, Jun 06, 2016 at 11:20:42PM +0200, Christoph Hellwig wrote: > This patch set adds some needed preparations for the upcoming NVMe over > Fabrics support. > > Contains: > - Allow transfer size limitations for NVMe transports > - Add the get_log_page command definition required by the NVMe

Re: [PATCH] md: use a mutex to protect a global list

On Wed, Jun 08, 2016 at 09:20:16AM -0700, Cong Wang wrote: > We saw a list corruption in the list all_detected_devices: > > WARNING: CPU: 16 PID: 226 at lib/list_debug.c:29 __list_add+0x3c/0xa9() > list_add corruption. next->prev should be prev (880859d58320), but was > 880859ce74c0.

[RESEND PATCH 0/2] arm64: dts: r8a7795: Add FCPF and FDP1 device nodes

Appologies for the resend, I very cleverly sent this cover letter detailing the dependencies only to my e-mail address. And I already know the dependencies! Following two patches are the same, sorry for the noise. These are dependent upon the FCP bindings from Laurent [0], and the FCPF update to

[PATCH 2/6] ARM: multi_v7_defconfig: Enable OMAP GPMC

OMAP_GPMC will soon not be forcibly enabled by ARCH_OMAP2PLUS. It needs to be manually selected by the config. Enable it by default so features like NAND boot will work. Signed-off-by: Franklin S Cooper Jr --- arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1

[PATCH] [V2] net: diag: add missing declarations

The functions inet_diag_msg_common_fill and inet_diag_msg_attrs_fill seem to have been missed from the include/linux/inet_diag.h header file. Add them to fix the following warnings: net/ipv4/inet_diag.c:69:6: warning: symbol 'inet_diag_msg_common_fill' was not declared. Should it be static?

[PATCH] drm/rockchip: fix compile warnings for 64-bit

Rockchip DRM does not yet build properly for ARM64, but we might as well get the printf formatting correct now, to avoid the following warnings: drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c: In function 'rockchip_drm_fbdev_create': drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c:111:2: warning:

Re: [PATCH] pvclock: introduce seqcount-like API

On 09/06/2016 19:12, Andy Lutomirski wrote: > On Thu, Jun 9, 2016 at 6:45 AM, Paolo Bonzini wrote: >> On 09/06/2016 15:35, Roman Kagan wrote: >>> On Thu, Jun 09, 2016 at 02:47:54PM +0200, Paolo Bonzini wrote: On 09/06/2016 14:43, Roman Kagan wrote: >>> Has it landed in

[PATCH 15/27] mm, page_alloc: Consider dirtyable memory in terms of nodes

Historically dirty pages were spread among zones but now that LRUs are per-node it is more appropriate to consider dirty pages in a node. Signed-off-by: Mel Gorman Signed-off-by: Johannes Weiner --- include/linux/mmzone.h| 12 +++---

[PATCH 24/27] mm, page_alloc: Remove fair zone allocation policy

The fair zone allocation policy interleaves allocation requests between zones to avoid an age inversion problem whereby new pages are reclaimed to balance a zone. Reclaim is now node-based so this should no longer be an issue and the fair zone allocation policy is not free. This patch removes it.

[PATCH] events/uprobes: move smp_read_barrier_depends() where needed

There is no need to use the barrier if there is no dereference/ memory access; move it where needed (currently, affecting only Alpha). While touching this, also make the reads _ONCE(). Signed-off-by: Andrea Parri --- kernel/events/uprobes.c | 9 + 1 file changed,

Re: [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps

On Thu, Jun 9, 2016 at 11:45 AM, Linus Torvalds wrote: > > All existing users and all the ones in this patch (and the others too, > although I didn't go through them very carefully) really would prefer > just passing in the inode directly, rather than the

Re: [PATCH 1/2] clk: imx: do not sleep if IRQ's are still disabled

On Tue, 7 Jun 2016, Dong Aisheng wrote: > Then it may need introduce a lot changes and increase many new core APIs. > Is that a problem? No. That's all better than each driver having broken workarounds. It's a common problem so it wants to be addressed at the core level. There you have a central

RE: performance delta after VFS i_mutex=>i_rwsem conversion

>> Ok, these enhancements are now in the locking tree and are queued up for >v4.8: >> >>git pull git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git >> locking/core >> >> Dave, you might want to check your numbers with these changes: is >> rwsem performance still significantly worse than

Re: [PATCH 2/3] i2c: octeon: Add retry logic after receiving STAT_RXADDR_NAK

On Wed, Jun 08, 2016 at 08:51:18AM +0200, Jan Glauber wrote: > The controller specification states that when receiving STAT_RXADDR_NAK > the START should be sent again. Retry several times before finally > failing with -ENXIO. > > Without this change the IPMI SSIF driver fails executing several

[PATCH] [media] s5p-mfc: use vb2_is_streaming() to check vb2 queue status

The streaming field in struct vb2_queue is meant to be private and should not be used by drivers directly, instead the vb2_is_streaming() function should be used to check the videobuf2 queue streaming status. Signed-off-by: Javier Martinez Canillas ---

Re: [PATCH] NVMe: Only release requested regions

On 06/08/2016 01:16 AM, Johannes Thumshirn wrote: On Tue, May 10, 2016 at 03:14:28PM +0200, Johannes Thumshirn wrote: The NVMe driver only requests the PCIe device's memory regions but releases all possible regions (including eventual I/O regions). This leads to a stale warning entry in dmesg

RE: [PATCH v4 09/29] staging: unisys: visorinput: remove unnecessary locking

> -Original Message- > From: Thomas Gleixner [mailto:t...@linutronix.de] > Sent: Thursday, June 09, 2016 3:56 PM > To: Sell, Timothy C > Cc: cor...@lwn.net; mi...@redhat.com; h...@zytor.com; > gre...@linuxfoundation.org; Arfvidson, Erik; hof...@osadl.org; > dzic...@redhat.com;

[PATCH] nfsd: Close a race between access checking/setting in nfs4_get_vfs_file

Currently there's an unprotected access mode check in nfs4_upgrade_open that then calls nfs4_get_vfs_file which in turn assumes whatever access mode was present in the state is still valid which is racy. Two nfs4_get_vfs_file van enter the same path as result and get two references to nfs4_file,

[PATCH 13/14] tile/ptrace: run seccomp after ptrace

Close the hole where ptrace can change a syscall out from under seccomp. Signed-off-by: Kees Cook Cc: Chris Metcalf --- arch/tile/kernel/ptrace.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git

[PATCH 14/14] um/ptrace: run seccomp after ptrace

Close the hole where ptrace can change a syscall out from under seccomp. Signed-off-by: Kees Cook Cc: Jeff Dike Cc: Richard Weinberger Cc: user-mode-linux-de...@lists.sourceforge.net --- arch/um/kernel/skas/syscall.c | 9 - 1

[PATCH 11/14] s390/ptrace: run seccomp after ptrace

Close the hole where ptrace can change a syscall out from under seccomp. Signed-off-by: Kees Cook Cc: Heiko Carstens Cc: Martin Schwidefsky Cc: linux-s...@vger.kernel.org --- arch/s390/kernel/ptrace.c | 21

Re: [PATCH v3 1/6] watchdog: add set_pretimeout interface

> I agree, your version is obviously more advanced, I will take it for v4. Thanks! signature.asc Description: PGP signature

Re: [PATCH 18/21] fs: nfs: Make nfs boot time y2038 safe

>>boot_time is represented as a struct timespec. >>struct timespec and CURRENT_TIME are not y2038 safe. >>Overall, the plan is to use timespec64 for all internal >>kernel representation of timestamps. >>CURRENT_TIME will also be removed. >>Use struct timespec64 to represent boot_time. >>And,

[PATCH 4.2.y-ckt 204/206] uapi glibc compat: fix compilation when !__USE_MISC in glibc

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Nicolas Dichtel commit f0a3fdca794d1e68ae284ef4caefe681f7c18e89 upstream. These structures are defined only

[PATCH 4.2.y-ckt 205/206] drivers/hwspinlock: use correct radix tree API

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Matthew Wilcox commit b76ba4af4ddd6a06f7f65769e7be1bc56556cdf5 upstream. radix_tree_is_indirect_ptr() is an

[PATCH 4.2.y-ckt 206/206] RDMA/cxgb3: device driver frees DMA memory with different size

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Honggang Li commit 0de4cbb3dddca35ecd06b95918f38439c9c6401f upstream. [ 598.852037] [ cut here

[PATCH 4.2.y-ckt 203/206] tuntap: correctly wake up process during uninit

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Jason Wang commit addf8fc4acb1cf79492ac64966f07178793cb3d7 upstream. We used to check dev->reg_state against

[PATCH 4.2.y-ckt 191/206] IB/srp: Print "ib_srp: " prefix once

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Bart Van Assche commit cf1acab7d75652a372ee5b9c996689d518914e83 upstream. pr_debug() already prints prefix

[PATCH 4.2.y-ckt 150/206] ARM: dts: kirkwood: add kirkwood-ds112.dtb to Makefile

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Heinrich Schuchardt commit fc5c796e12511a7c027b5a4438719dde2f796208 upstream. Commit 2d0a7addbd10 ("ARM: Kirkwood:

[PATCH] ecryptfs: fix spelling mistakes

Noticed some minor spelling errors when looking through the code. Signed-off-by: Chris J Arges --- fs/ecryptfs/crypto.c | 8 fs/ecryptfs/file.c | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/fs/ecryptfs/crypto.c

Re: [PATCH V3 1/2] i2c: qup: Fix broken dma when CONFIG_DEBUG_SG is enabled

> The coherency is not dropped here. dma_map/unmap used > makes the buffer coherent before passing it to > dmaengine. Previously it was not required. > I can add this in description if its not clear. Please do. > > >> @@ -1268,6 +1260,8 @@ static int qup_i2c_xfer_v2(struct i2c_adapter

[PATCH v4 5/5] intel_idle: Add S0ix validation

From: Derek Basehore This adds validation of S0ix entry and enables it on Skylake. Using the new timed_freeze function, we program the CPU to wake up X seconds after entering freeze. After X seconds, it will wake the CPU to check the S0ix residency counters and make sure

[PATCH 07/14] arm/ptrace: run seccomp after ptrace

Close the hole where ptrace can change a syscall out from under seccomp. Signed-off-by: Kees Cook Cc: Russell King Cc: linux-arm-ker...@lists.infradead.org --- arch/arm/kernel/ptrace.c | 11 ++- 1 file changed, 6 insertions(+), 5

[PATCH 06/14] x86/ptrace: run seccomp after ptrace

This moves seccomp after ptrace on x86 to that seccomp can catch changes made by ptrace. Emulation should skip the rest of processing too. We can get rid of test_thread_flag because there's no longer any opportunity for seccomp to mess with ptrace state before invoking ptrace. Suggested-by: Andy

Re: [ibm-acpi-devel] [PATCH v2] thinkpad_acpi: Add support for HKEY version 0x200

On Thu, 09 Jun 2016, Darren Hart wrote: > On Thu, Jun 09, 2016 at 01:05:12AM -0400, Marco Trevisan (Treviño) wrote: > > 2016-06-08 10:54 GMT-04:00 Lyude : > > > From: Dennis Wassenberg > > > > > > Lenovo Thinkpad devices T460, T460s, T460p, T560,

Re: [PATCH 2/4] ASoC: sunxi: Add Allwinner A10 Digital Audio driver

Hi Mark, On Thu, Jun 02, 2016 at 11:26:51AM +0100, Mark Brown wrote: > > +static int sun4i_i2s_params_to_sr(struct snd_pcm_hw_params *params) > > +{ > > + switch (params_width(params)) { > > + case 16: > > + return 0; > > + } > > + > > + return -EINVAL; > > +} > > The switch

[PATCH 08/14] arm64/ptrace: run seccomp after ptrace

Close the hole where ptrace can change a syscall out from under seccomp. Signed-off-by: Kees Cook Cc: Catalin Marinas Cc: Will Deacon Cc: Mark Rutland Cc: linux-arm-ker...@lists.infradead.org ---

[PATCH 01/14] seccomp: add tests for ptrace hole

One problem with seccomp was that ptrace could be used to change a syscall after seccomp filtering had completed. This was a well documented limitation, and it was recommended to block ptrace when defining a filter to avoid this problem. This can be quite a limitation for containers or other

[PATCH v4 2/5] clockevents: Add timed freeze

From: Derek Basehore Adds a new feature to clockevents to schedule wakeups on a CPU during freeze. These won't fully wake up the system, but allow simple platform callbacks that don't require device support to be run during freeze with little power impact. This

Re: [PATCH v3 4/6] watchdog: add watchdog pretimeout framework

> >> * removed support of sleepable watchdog pretimeout governors > > > > This does. > > Same as above. Just to make sure: I meant this does make reviewing easier since the bottom half handling is the biggest thing to discuss and it is good to seperate it out. signature.asc Description: PGP

[PATCH 4.2.y-ckt 198/206] sched/preempt: Fix preempt_count manipulations

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Peter Zijlstra commit 2e636d5e66c35dfcbaf617aa8fa963f6847478fe upstream. Vikram reported that his ARM64 compiler

[PATCH 4.2.y-ckt 194/206] blk-mq: fix undefined behaviour in order_to_size()

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Bartlomiej Zolnierkiewicz commit b3a834b1596ac668df206aa2bb1f191c31f5f5e4 upstream. When this_order variable

[PATCH 4.2.y-ckt 200/206] sunrpc: Update RPCBIND_MAXNETIDLEN

4.2.8-ckt12 -stable review patch. If anyone has any objections, please let me know. ---8< From: Chuck Lever commit 4b9c7f9db9a003f5c342184dc4401c1b7f2efb39 upstream. Commit 176e21ee2ec8 ("SUNRPC: Support for

Re: [PATCH v3 5/6] watchdog: pretimeout: add panic pretimeout governor

> > Did you look at my patches at all? To me, it looks like you didn't or > > you are intentionally trying to leave my changes out. I don't think they > > were all bad. > > No, they are not, and I'll include some of the changes to v4, if you don't > mind. Quite the contrary, I'd be happy :)

Re: [tip:x86/urgent] x86/quirks: Add early quirk to reset Apple AirPort card

On Thu, Jun 09, 2016 at 09:37:53AM -0700, Yinghai Lu wrote: > On Thu, Jun 9, 2016 at 4:04 AM, Lukas Wunner wrote: > > --- a/arch/x86/kernel/early-quirks.c > > +++ b/arch/x86/kernel/early-quirks.c > > @@ -747,7 +747,8 @@ static int __init check_dev_quirk(int num, int slot, > >

Re: [PATCH] mtd: nand: add ESMT manufacturer

On Thu, 9 Jun 2016 20:10:11 +0200 Rafał Miłecki wrote: > I got device with ESMT (Elite Semiconductor Memory Technology Inc) > F59L1G81MA flash that was detected as: > [0.852034] nand: device found, Manufacturer ID: 0xc8, Chip ID: 0xd1 > [0.858402] nand: Unknown NAND

[PATCH] x86/microcode/intel: Quieten down microcode updates on large systems

From: Andi Kleen On large systems the microcode driver is very noisy, because it prints a line for each CPU. The lines are redundant because because usually all CPUs are updated to the same microcode revision. All other subsystems have been patched previously to not print

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