Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Thu, 1 Dec 2016 17:12:41 +0100 Michal Marek wrote: > On 2016-12-01 04:39, Nicholas Piggin wrote: > > On Thu, 01 Dec 2016 02:35:54 + > > Ben Hutchings wrote: > >> As I understand it, genksyms incorporates the definitions of a > >> function's

Re: [RFC PATCH v3] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

* Juergen Gross wrote: > On 05/12/16 18:49, Alex Thorlton wrote: > > This is the third pass at my patchset to fix up our problems with > > XENMEM_machine_memory_map on large systems. The only changes on this > > pass were to flesh out the comment above the E820_X_MAX

Re: [PATCH] drm/mxsfb: use bus_format to determine LCD bus width

On 2016-12-08 15:33, Marek Vasut wrote: > On 12/08/2016 11:52 PM, Stefan Agner wrote: >> The LCD bus width does not need to align with the pixel format. The >> LCDIF controller automatically converts between pixel formats and >> bus width by padding or dropping LSBs. >> >> The DRM subsystem has

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Thu, 1 Dec 2016 10:20:39 -0500 Don Zickus wrote: > On Thu, Dec 01, 2016 at 03:32:15PM +1100, Nicholas Piggin wrote: > > > Anyway, MODVERSIONS is our way of protecting our kabi for the last 10 > > > years. > > > It isn't perfect and we have fixed the genksyms tool over the

Re: [PATCH] x86/coredump: always use user_regs_struct for compat_elf_gregset_t

* Andy Lutomirski wrote: > On Nov 23, 2016 10:16 AM, "Dmitry Safonov" wrote: > > > > From commit 90954e7b9407 ("x86/coredump: Use pr_reg size, rather that > > TIF_IA32 flag") elf coredump file is constructed according to register > > set size - and

Re: [patch 5/6] [RFD] timekeeping: Provide optional 128bit math

* Thomas Gleixner wrote: > If the timekeeping CPU is scheduled out long enough by a hypervisor the > clocksource delta multiplication can overflow and as a result time can go > backwards. That's insane to begin with, but people already triggered a > signed multiplication

[PATCH] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS

From: Jean-Jacques Hiblot From: Jean-Jacques Hiblot The DYNAMIC_FTRACE_WITH_REGS configuration makes it possible for a ftrace operation to specify if registers need to saved/restored by the ftrace handler. This is needed by kgraft and

Re: [PATCH v2 4/4] ARM: treewide: Replace uses of virt_to_phys with __pa_symbol

Hi Florian, [auto build test ERROR on linus/master] [also build test ERROR on v4.9-rc8] [cannot apply to arm-soc/for-next next-20161208] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Florian

Re: [PATCH 1/2] net: ethernet: sxgbe: remove private tx queue lock

On Thu 2016-12-08 21:32:12, Lino Sanfilippo wrote: > Hi, > > On 08.12.2016 00:15, Francois Romieu wrote: > > Lino Sanfilippo : > >> The driver uses a private lock for synchronization between the xmit > >> function and the xmit completion handler, but since the NETIF_F_LLTX

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

On Wednesday 23 November 2016 09:12 AM, Tomi Valkeinen wrote: On 23/11/16 10:52, Greg Kroah-Hartman wrote: On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote: Hi, Since the fbdev framework is in maintenance mode and all new display drivers should be made with the DRM framework,

Re: [PATCH 0/3] clkdev: add devm_get_clk_from_child()

On 12/05, Kuninori Morimoto wrote: > > Hi Stephen > > This is v5 of "clkdev: add devm_of_clk_get()", but new series. > I hope my understanding was correct with your idea. Yes this looks good. Given that we're so close to the merge window, perhaps I should just merge the first patch into

Re: [PATCH] ARM: keystone: dts: fix netcp clocks and add names

On 12/8/2016 1:11 PM, Grygorii Strashko wrote: From: Murali Karicheri Fix the pa clock to point to the clkpa which has clock rate of 1/3 of PA PLL clock and add clock names. Signed-off-by: Murali Karicheri Signed-off-by: Grygorii Strashko

Re: [PATCH] ppdev: don't print a free'd string

On Tuesday 06 December 2016 10:51 AM, Greg Kroah-Hartman wrote: On Fri, Dec 02, 2016 at 04:23:55PM +, Colin King wrote: From: Colin Ian King A previous fix of a memory leak now prints the string 'name' that was previously free'd. Fix this by free'ing the string

[PATCH v11 4/5] iio: adc: mxs-lradc: Remove driver

Since the driver has been split into mfd there is no reason for it to stay, so remove it. Signed-off-by: Ksenija Stanojevic Acked-by: Jonathan Cameron --- Changes in v11: - none Changes in v10: - none Changes in v9: - none Changes in v8: -

[PATCH v11 5/5] mfd: Move binding document

The bindings, which are now used in MFD, need also to be documented in the MFD binding document. Signed-off-by: Ksenija Stanojevic --- Changes in v11: - none Changes in v10: - none Changes in v9: - format patch using -M option Changes in v8: - rebase onto

[PATCH v11 2/5] iio: adc: mxs-lradc: Add support for adc driver

Add support for sixteen-channel 12-bit resolution ADC and its functions, which include general-purpose ADC readings, battery voltage measurement, and die temperature measurement. Signed-off-by: Ksenija Stanojevic Reviewed-by: Jonathan Cameron ---

[PATCH v11 3/5] input: touchscreen: mxs-lradc: Add support for touchscreen

Add 4-wire/5-wire touchscreen controller. Signed-off-by: Ksenija Stanojevic --- Changes in v11: - use dev_get_drvdata instead dev_get_platdata - use writel instead mxs_lradc_reg_* functions Changes in v10: - none Changes in v9: - none Changes in v8: - rebase

[PATCH v11 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD

Add core files for low resolution analog-to-digital converter (mxs-lradc) MFD driver. Signed-off-by: Ksenija Stanojevic --- Changes in v11: - create static struct mfd_cells - don't set platform data in mfd cells, set driver data instead - remove mxs_lradc_reg_*

Re: [PATCH] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS

On Thu, Dec 08, 2016 at 09:46:35PM +, Abel Vesa wrote: > From: Jean-Jacques Hiblot > > From: Jean-Jacques Hiblot >From statement twice in the commit message. Will resend. > > The DYNAMIC_FTRACE_WITH_REGS configuration makes it possible

[PATCH] drm/mxsfb: use bus_format to determine LCD bus width

The LCD bus width does not need to align with the pixel format. The LCDIF controller automatically converts between pixel formats and bus width by padding or dropping LSBs. The DRM subsystem has the notion of bus_format which allows to determine what bus_formats are supported by the display.

Re: [patch] x86/ldt: make a size variable unsigned

On Thu, 8 Dec 2016, Dan Carpenter wrote: > My static checker complains that we put an upper bound on the "size" > variable but not a lower bound. The checker is not smart enough to know > the possible ranges of "old_mm->context.ldt->size" from > init_new_context_ldt() so it thinks maybe it could

Re: [PATCH] clk: bcm: Make COMMON_CLK_IPROC into a library

On 11/23, Stephen Boyd wrote: > The broadcom clk driver Kconfig file selects and depends on the > COMMON_CLK_IPROC config for different SoC specific drivers. Let's > simplify this by always selecting the COMMON_CLK_IPROC config, > turning it into a set of library code. We still want to retain >

Re: [PATCH 02/22] m68k/mac: macints - Modernize printing of kernel messages

On Thu, 8 Dec 2016, Geert Uytterhoeven wrote: > On Wed, Dec 7, 2016 at 11:45 PM, Finn Thain > wrote: > > On Wed, 7 Dec 2016, Geert Uytterhoeven wrote: > > > >> - Introduce helpers for printing debug messages, incl. dummies for > >> validating format strings

Re: [RFC][PATCH] HACK: usb: dwc2: Workaround case where GOTGCTL state is wrong

On 12/8/2016 2:43 PM, John Stultz wrote: > On Tue, Dec 6, 2016 at 7:52 PM, John Youn wrote: >> On 12/6/2016 5:48 PM, John Stultz wrote: >>> Hey John, >>> Just wanted to send this by you, as it seems something is >>> slightly off with the GOTGCTL state when removing a otg

[PATCH] gpio/gpiolib.c:Fixing style issues in gpiolib.c

Fixing the following checkpatch.pl error: ERROR: else should follow close brace '}' #2248: FILE: drivers/gpio/gpiolib.c:2248: + } + else if (test_bit(FLAG_OPEN_SOURCE, >flags)) { ERROR: space prohibited after that open parenthesis '(' #2018: FILE: drivers/gpio/gpiolib.c:2018: +

Re: [PATCH 16/16] drivers/fsi: Add GPIO based FSI master

Hi Chris, > +static ssize_t store_scan(struct device *dev, > + struct device_attribute *attr, > + const char *buf, > + size_t count) > +{ > + struct fsi_master_gpio *master = dev_get_drvdata(dev); > + > +

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

On Thu, Dec 8, 2016 at 5:52 PM, Paul Gortmaker wrote: > On Thu, Dec 8, 2016 at 2:00 PM, Kees Cook wrote: >> Hi, >> >> I'd like to get the GCC plugins building under >> allyesconfig/allmodconfig for -next soon (with the intention of >> landing

Re: [PATCH] drm/mxsfb: use bus_format to determine LCD bus width

On 12/09/2016 04:44 AM, Stefan Agner wrote: > On 2016-12-08 15:33, Marek Vasut wrote: >> On 12/08/2016 11:52 PM, Stefan Agner wrote: >>> The LCD bus width does not need to align with the pixel format. The >>> LCDIF controller automatically converts between pixel formats and >>> bus width by

Re: [patch 5/6] [RFD] timekeeping: Provide optional 128bit math

* Ingo Molnar wrote: > > * Thomas Gleixner wrote: > > > If the timekeeping CPU is scheduled out long enough by a hypervisor the > > clocksource delta multiplication can overflow and as a result time can go > > backwards. That's insane to begin with, but

Re: [PATCH] x86/head: Refactor 32-bit pgtable setup

* Boris Ostrovsky wrote: > The new Xen PVH entry point requires page tables to be setup by the > kernel since it is entered with paging disabled. > > Pull the common code out of head_32.S so that mk_early_pgtbl_32 can be > invoked from both the new Xen entry point

Re: [patch 5/6] [RFD] timekeeping: Provide optional 128bit math

On Thu, Dec 8, 2016 at 8:29 PM, Ingo Molnar wrote: > > * Ingo Molnar wrote: > >> >> * Thomas Gleixner wrote: >> >> > If the timekeeping CPU is scheduled out long enough by a hypervisor the >> > clocksource delta multiplication can overflow

[PATCH SND/USB]: Add QuickCam Communicate Deluxe/S7500 to volume_control_quirks.

The Logitech QuickCam Communicate Deluxe/S7500 microphone fails with the following warning. [6.778995] usb 2-1.2.2.2: Warning! Unlikely big volume range (=3072), cval->res is probably wrong. [6.778996] usb 2-1.2.2.2: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1 Adding it to the

RE: [Qemu-devel] [PATCH kernel v5 0/5] Extend virtio-balloon for fast (de)inflating & fast live migration

> > 1. Current patches do a hypercall for each order in the allocator. > >This is inefficient, but independent from the underlying data > >structure in the ABI, unless bitmaps are in play, which they aren't. > > 2. Should we have bitmaps in the ABI, even if they are not in use by the > >

Re: [PATCH net-next 0/2] Initial driver for Synopsys DWC XLGMAC

On 2016/12/8 23:59, Alexandre Torgue wrote: > Hi > > On 12/07/2016 04:57 AM, Jie Deng wrote: >> This series provides the support for 25/40/50/100 GbE >> devices using Synopsys DWC Enterprise Ethernet (XLGMAC). > > Can you explain which GMAC are you targeted ? > > A driver which support some

Re: [patch 5/6] [RFD] timekeeping: Provide optional 128bit math

On Fri, Dec 09, 2016 at 05:08:26AM +0100, Ingo Molnar wrote: > > +#if defined(CONFIG_ARCH_SUPPORTS_INT128) && defined(__SIZEOF_INT128__) > > +static inline u64 timekeeping_delta_to_ns(struct tk_read_base *tkr, u64 > > delta) > > +{ > > + unsigned __int128 nsec; > > + > > + nsec = ((unsigned

Re: [patch 0/6] timekeeping: Cure the signed/unsigned wreckage

On Thu, Dec 8, 2016 at 12:49 PM, Thomas Gleixner wrote: > This series addresses the recently reintroduced signed vs. unsigned > wreckage by cleaning up the whole call chain instead of just making a > simple s64 -> u64 'fix' at one point and keeping the rest signed, which >

Re: [Qemu-devel] [PATCH kernel v5 0/5] Extend virtio-balloon for fast (de)inflating & fast live migration

On 12/08/2016 08:45 PM, Li, Liang Z wrote: > What's the conclusion of your discussion? It seems you want some > statistic before deciding whether to ripping the bitmap from the > ABI, am I right? I think Andrea and David feel pretty strongly that we should remove the bitmap, unless we have some

Re: [regression ?] kbuild: fix building bzImage with CONFIG_TRIM_UNUSED_KSYMS enabled

On (12/08/16 22:40), Nicolas Pitre wrote: > > > after 53924022d8a ("kbuild: fix building bzImage > > > withCONFIG_TRIM_UNUSED_KSYMS > > > enabled") all of my build scripts build the kernel without the modules. > > > > [..] > > > +# For the kernel to actually contain only the needed exported

RE: ATH9 driver issues on ARM64

Hi, Can any one tell, when exactly the chip sends ASSERT & DEASSERT in driver. It might help us to debug issue further. Thanks & Regards, Bharat > > > [+cc Kalle, ath9k list] > > Thanks, but please also CC linux-wireless. Full thread below for the folks > there. > > >> On Thu, Dec 08, 2016

Re: [RFC, PATCHv1 00/28] 5-level paging

* Kirill A. Shutemov wrote: > x86-64 is currently limited to 256 TiB of virtual address space and 64 TiB > of physical address space. We are already bumping into this limit: some > vendors offers servers with 64 TiB of memory today. > > To overcome the

[PATCH] [RFC] drivers: dma-coherent: pass struct dma_attrs to dma_alloc_from_coherent

dma_alloc_from_coherent does not get struct dma_attrs information. If dma_attrs information is passed to dma_alloc_from_coherent, dma_alloc_from_coherent can do more jobs accodring to the information. As a example I added DMA_ATTR_SKIP_ZEROING to skip zeroing. Accoring to driver implementation

Re: [PATCHv3 perf/core 5/7] samples/bpf: Switch over to libbpf

On 2016/12/9 10:46, Joe Stringer wrote: Now that libbpf under tools/lib/bpf/* is synced with the version from samples/bpf, we can get rid most of the libbpf library here. Signed-off-by: Joe Stringer --- v3: First post. --- samples/bpf/Makefile | 60

[PATCH] staging: android: ion: return -ENOMEM in ion_cma_heap allocation failure

Initial Commit 349c9e138551 ("gpu: ion: add CMA heap") returns -1 in allocation failure. The returned value is passed up to userspace through ioctl. So user can misunderstand error reason as -EPERM(1) rather than -ENOMEM(12). This patch simply changed this to return -ENOMEM. Signed-off-by:

Re: net: deadlock on genl_mutex

On Thu, Dec 8, 2016 at 4:32 PM, Cong Wang wrote: > On Thu, Dec 8, 2016 at 9:16 AM, Dmitry Vyukov wrote: >> Chain exists of: >> Possible unsafe locking scenario: >> >>CPU0CPU1 >> >>

Re: [patch 5/6] [RFD] timekeeping: Provide optional 128bit math

On Thu, Dec 08, 2016 at 08:49:39PM -, Thomas Gleixner wrote: > +/* > + * Enabled when timekeeping is supposed to deal with virtualization keeping > + * VMs long enough scheduled out that the 64 * 32 bit multiplication in > + * timekeeping_delta_to_ns() overflows 64bit. > + */ > +#ifdef

[PATCH v4 02/15] x86/dumpstack: Add save_stack_trace()_fast()

In non-oops case, it's usually not necessary to check all words of stack area to extract backtrace. Instead, we can achieve it by tracking frame pointer. So made it possible to save stack trace lightly in normal case. I measured its ovehead and printed its difference of sched_clock() with my QEMU

[PATCH v4 05/15] lockdep: Make check_prev_add can use a separate stack_trace

check_prev_add() saves a stack trace of the current. But crossrelease feature needs to use a separate stack trace of another context in check_prev_add(). So make it use a separate stack trace instead of one of the current. Signed-off-by: Byungchul Park ---

[PATCH v4 01/15] x86/dumpstack: Optimize save_stack_trace

Currently, x86 implementation of save_stack_trace() is walking all stack region word by word regardless of what the trace->max_entries is. However, it's unnecessary to walk after already fulfilling caller's requirement, say, if trace->nr_entries >= trace->max_entries is true. I measured its

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 2016/12/8 17:41, Xunlei Pang wrote: > On 12/08/2016 at 10:37 AM, zhongjiang wrote: >> From: zhong jiang >> >> A soft lookup will occur when I run trinity in syscall kexec_load. >> the corresponding stack information is as follows. >> >> [ 237.235937] BUG: soft lockup -

[PATCH v4 13/15] lockdep: Apply lock_acquire(release) on __Set(__Clear)PageLocked

Usually PG_locked bit is updated by lock_page() or unlock_page(). However, it can be also updated through __SetPageLocked() or __ClearPageLockded(). They have to be considered, to get paired between acquire and release. Furthermore, e.g. __SetPageLocked() in add_to_page_cache_lru() is called

[PATCH v4 08/15] lockdep: Make crossrelease use save_stack_trace_fast()

Currently crossrelease feature uses save_stack_trace() to save backtrace. However, it has much overhead. So this patch makes it use save_stack_trace_norm() instead, which has smaller overhead. Signed-off-by: Byungchul Park --- kernel/locking/lockdep.c | 2 +- 1 file

[PATCH v4 09/15] lockdep: Make print_circular_bug() crosslock-aware

Friends of print_circular_bug() reporting circular bug assumes that target hlock is owned by the current. However, in crossrelease feature, target hlock can be owned by any context. In this case, the circular bug is caused by target hlock which cannot be released since its dependent lock cannot

[PATCH v4 14/15] lockdep: Move data used in CONFIG_LOCKDEP_PAGELOCK from page to page_ext

CONFIG_LOCKDEP_PAGELOCK is keeping data, with which lockdep can check and detect deadlock by page lock, e.g. lockdep_map and cross_lock in struct page. But move it to page_ext since it's a debug feature so it's preferred to keep it in struct page_ext than struct page. Signed-off-by: Byungchul

[PATCH v4 07/15] lockdep: Implement crossrelease feature

Crossrelease feature calls a lock 'crosslock' if it is releasable in any context. For crosslock, all locks having been held in the release context of the crosslock, until eventually the crosslock will be released, have dependency with the crosslock. Using crossrelease feature, we can detect

[PATCH v4 00/15] lockdep: Implement crossrelease feature

I checked if crossrelease feature works well on my qemu-i386 machine. There's no problem at all to work on mine. But I wonder if it's also true even on other machines. Especially, on large system. Could you let me know if it doesn't work on yours? Or Could you let me know if crossrelease feature

[PATCH v4 15/15] lockdep: Crossrelease feature documentation

This document describes the concept of crossrelease feature, which generalizes what causes a deadlock and how can detect a deadlock. Signed-off-by: Byungchul Park --- Documentation/locking/crossrelease.txt | 1053 1 file changed, 1053

[PATCH v4 12/15] lockdep: Apply crossrelease to PG_locked lock

lock_page() and its family can cause deadlock. Nevertheless, it cannot use the lock correctness validator becasue unlock_page() can be called in different context from the context calling lock_page(), which violates lockdep's assumption without crossrelease feature. However, thanks to

Re: [PATCH] x86/tsc: RFC: re-synchronize TSCs to boot cpu TSC

On Thu, 8 Dec 2016, srol...@vmware.com wrote: > From: Roland Scheidegger > > Some bios (Dell T5810 here) mess up the perfectly synced TSCs on boot > and resume (probably trying to set some continuous time, but writing > TSC directly instead of TSC_ADJUST which can only result in failure). >

Re: [RFC PATCH 0/3] staging: remove fbdev drivers

On 08/12/16 03:01, Benjamin Herrenschmidt wrote: > On Wed, 2016-11-23 at 10:03 +0200, Tomi Valkeinen wrote: >> Hi, >> >> Since the fbdev framework is in maintenance mode and all new display drivers >> should be made with the DRM framework, remove the fbdev drivers from staging. >> >> Note: the

Re: [patch] mm, compaction: add vmstats for kcompactd work

On 12/08/2016 02:50 AM, David Rientjes wrote: A "compact_daemon_wake" vmstat exists that represents the number of times kcompactd has woken up. This doesn't represent how much work it actually did, though. It's useful to understand how much compaction work is being done by kcompactd versus

[PATCH] pci-error-recover: doc cleanup

Include typo fix; white space shooting; mistake correction. Signed-off-by: Cao jin --- Documentation/PCI/pci-error-recovery.txt | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/PCI/pci-error-recovery.txt b/Documentation/PCI/pci-error-recovery.txt

Re: [PATCH v2] inotify: Convert to using per-namespace limits

On 8.12.2016 08:58, Nikolay Borisov wrote: > > > On 8.12.2016 03:40, Eric W. Biederman wrote: >> Nikolay Borisov writes: >> >>> Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully >>> resolved. >> >> After getting slowed down by some fixes I am now taking a hard look at

Re: [PATCH 5/8] efi: Get the secure boot status [ver #5]

How about the attached? Thanks, David --- commit 6788837a26d517d10d00138aadd338cc73d69237 Author: David Howells Date: Mon Nov 21 23:55:55 2016 + efi: Get the secure boot status Get the firmware's secure-boot status in the kernel boot wrapper and stash it somewhere that

Re: [PATCH 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

Hello, On 12-08-16, Baoquan He wrote: > X86 64 kernel takes KERNEL_IMAGE_SIZE as the kernel text mapping size, > and it's fixed as compiling time, changing from 512M to 1G as long as > CONFIG_RANDOMIZE_BASE is enabled, though people specify kernel option > "nokaslr" explicitly. > > This could be

Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7

On Wed, 7 Dec 2016 23:25:31 + Mel Gorman wrote: > On Wed, Dec 07, 2016 at 09:19:58PM +, Mel Gorman wrote: > > At small packet sizes on localhost, I see relatively low page allocator > > activity except during the socket setup and other unrelated activity > > (khugepaged, irqbalance, some

Re: [PATCH 1/2] x86/64: Make kernel text mapping always take one whole page table in early boot code

On 12-08-16, Baoquan He wrote: > In early boot code level2_kernel_pgt is used to map kernel text. And its > size varies according to KERNEL_IMAGE_SIZE and fixed at compiling time. > In fact we can make it always takes 512 entries of one whople page table, > because later function cleanup_highmap

Re: [PATCH 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On 12/08/16 at 02:17pm, Alexnader Kuleshov wrote: > Hello, > > On 12-08-16, Baoquan He wrote: > > #define KERNEL_MAPPING_SIZE_EXT(1024 * 1024 * 1024) > > -#if defined(CONFIG_RANDOMIZE_BASE) > > -#define KERNEL_IMAGE_SIZE KERNEL_MAPPING_SIZE_EXT > > -#else > > -#define KERNEL_IMAGE_SIZE

[PATCH v5 1/5] dt-bindings: Document the STM32 I2C bindings

This patch adds documentation of device tree bindings for the STM32 I2C controller. Signed-off-by: M'boumba Cedric Madianga Acked-by: Rob Herring --- .../devicetree/bindings/i2c/i2c-stm32.txt | 33 ++ 1 file changed, 33 insertions(+) create mode 100644

[PATCH v5 2/5] i2c: Add STM32F4 I2C driver

This patch adds support for the STM32F4 I2C controller. Signed-off-by: M'boumba Cedric Madianga --- drivers/i2c/busses/Kconfig | 10 + drivers/i2c/busses/Makefile | 1 + drivers/i2c/busses/i2c-stm32f4.c | 851 +++ 3 files changed, 862

[PATCH v5 5/5] ARM: configs: Add I2C support for STM32 defconfig

Signed-off-by: M'boumba Cedric Madianga --- arch/arm/configs/stm32_defconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index e7b56d4..9494eaf 100644 --- a/arch/arm/configs/stm32_defconfig +++

Re: [PATCH] extcon: palmas: Fail gracefully if invalid configuration

Hi Chanwoo, On 07/12/16 14:46, Chanwoo Choi wrote: > Hi Roger, > > Looks good to me. > But I have some comment. > > How about changing the subject as following? > > - old : Fail gracefully if invalid configuration > - new : Check the parent instance to prevent the NULL pointer error I'm OK

[PATCH v5 0/5] Add support for the STM32F4 I2C

This patchset adds support for the I2C controller embedded in STM32F4xx SoC. It enables I2C transfer in interrupt mode with Standard-mode and Fast-mode bus speed. Changes since v4: - Use clamp() function to use a value in a given range as it was missed in V4 M'boumba Cedric Madianga (5):

[PATCH v5 4/5] ARM: dts: Add I2C1 support for STM32429 eval board

Signed-off-by: M'boumba Cedric Madianga --- arch/arm/boot/dts/stm32429i-eval.dts | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/stm32429i-eval.dts b/arch/arm/boot/dts/stm32429i-eval.dts index afb90bc..74e0045 100644 --- a/arch/arm/boot/dts/stm32429i-eval.dts +++

[PATCH v5 3/5] ARM: dts: Add I2C1 support for STM32F429 SoC

Signed-off-by: Patrice Chotard Signed-off-by: M'boumba Cedric Madianga --- arch/arm/boot/dts/stm32f429.dtsi | 23 +++ 1 file changed, 23 insertions(+) diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi index 7de52ee..cbdece7 100644 ---

Re: [PATCH] x86/vm86: fix compilation warning on a unused variable

On Wed, Dec 07, 2016 at 11:38:33PM -0500, Jérémy Lefaure wrote: > When CONFIG_TRANSPARENT_HUGEPAGE is disabled, split_huge_pmd is a no-op > stub. In such case, vma is unused and a compiler raises a warning: > > arch/x86/kernel/vm86_32.c: In function ‘mark_screen_rdonly’: >

[PATCH] fbdev: remove current maintainer

Remove Tomi Valkeinen from fbdev maintainer and mark fbdev as orphan. Signed-off-by: Tomi Valkeinen --- I just don't have time to even pretend I maintain fbdev, so mark it as Orphan. Anyone want to pick fbdev maintainership? MAINTAINERS | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

Re: [PATCH v5 5/5] ARM: configs: Add I2C support for STM32 defconfig

Hi Cedric, On 12/08/2016 09:26 AM, M'boumba Cedric Madianga wrote: Signed-off-by: M'boumba Cedric Madianga --- arch/arm/configs/stm32_defconfig | 3 +++ 1 file changed, 3 insertions(+) Can you change the commit header by ARM: configs: stm32: Add I2C support Thx alex diff --git

Re: [PATCH v5 4/5] ARM: dts: Add I2C1 support for STM32429 eval board

Hi Cedric, On 12/08/2016 09:26 AM, M'boumba Cedric Madianga wrote: Signed-off-by: M'boumba Cedric Madianga --- arch/arm/boot/dts/stm32429i-eval.dts | 6 ++ 1 file changed, 6 insertions(+) Can you change the commit header by: ARM: dts: stm32: Add I2C1 support for STM32429 eval board

Re: [BUG 4.9] New led trigger usbport gets the kernel to panic

Hi Rafał, On 12/06/2016 06:29 PM, Rafał Miłecki wrote: On 6 December 2016 at 18:26, Pavel Machek wrote: On Fri 2016-12-02 09:48:18, Ralph Sennhauser wrote: On Thu, 1 Dec 2016 17:56:07 +0100 Rafał Miłecki wrote: On 12/01/2016 03:28 PM, Ralph Sennhauser wrote: Below the oops with your

Re: [PATCH 1/2] x86/64: Make kernel text mapping always take one whole page table in early boot code

On 12/08/16 at 02:24pm, Alexnader Kuleshov wrote: > On 12-08-16, Baoquan He wrote: > > In early boot code level2_kernel_pgt is used to map kernel text. And its > > size varies according to KERNEL_IMAGE_SIZE and fixed at compiling time. > > In fact we can make it always takes 512 entries of one

[PATCH v2] extcon: palmas: Check the parent instance to prevent the NULL

extcon-palmas must be child of palmas and expects parent's drvdata to be valid. Check for non NULL parent drvdata and fail if it is NULL. Not doing so will result in a NULL pointer dereference later in the probe() parent drvdata is NULL (e.g. misplaced extcon-palmas node in device tree).

Re: [PATCH v5 5/5] ARM: configs: Add I2C support for STM32 defconfig

Hi Alex, 2016-12-08 9:38 GMT+01:00 Alexandre Torgue : > Hi Cedric, > > On 12/08/2016 09:26 AM, M'boumba Cedric Madianga wrote: >> >> Signed-off-by: M'boumba Cedric Madianga >> --- >> arch/arm/configs/stm32_defconfig | 3 +++ >> 1 file changed, 3 insertions(+) >> > Can you change the commit

Re: [PATCH] platform: Introduce button support for the Surface 3

On Dec 07 2016 or thereabouts, Dmitry Torokhov wrote: > On Mon, Dec 05, 2016 at 04:10:33PM +0100, Benjamin Tissoires wrote: > > The Surface 3 is not following the ACPI spec for PNP0C40, but nearly. > > The device is connected to a I2C device that might have some magic > > but we don't know about.

Re: [PATCH v5 4/5] ARM: dts: Add I2C1 support for STM32429 eval board

Hi Alex, 2016-12-08 9:39 GMT+01:00 Alexandre Torgue : > Hi Cedric, > > On 12/08/2016 09:26 AM, M'boumba Cedric Madianga wrote: >> >> Signed-off-by: M'boumba Cedric Madianga >> --- >> arch/arm/boot/dts/stm32429i-eval.dts | 6 ++ >> 1 file changed, 6 insertions(+) >> > Can you change the

Re: [PATCH v3 2/6] net: stmmac: simplify the common DMA init API

Hi Niklas, On 12/07/2016 03:20 PM, Niklas Cassel wrote: From: Niklas Cassel Use struct stmmac_dma_cfg *dma_cfg as an argument rather than using all the struct members as individual arguments. Signed-off-by: Niklas Cassel Thanks for this patch. You can add my Acked-by. Regards Alex ---

Re: [PATCH] MAINTAINERS: clarify that "B:" is the URI where to file bugs

On Thu, 08 Dec 2016, "Rafael J. Wysocki" wrote: > On Wednesday, December 07, 2016 10:35:07 AM Jani Nikula wrote: >> On Wed, 07 Dec 2016, "Rafael J. Wysocki" wrote: >> > On Monday, December 05, 2016 02:03:59 PM Jani Nikula wrote: >> >> Different subsystems and drivers have different preferences

Re: [PATCH v3 3/6] net: stmmac: stmmac_platform: fix parsing of DT binding

Hi Niklas On 12/07/2016 03:20 PM, Niklas Cassel wrote: From: Niklas Cassel commit 64c3b252e9fc ("net: stmmac: fixed the pbl setting with DT") changed the parsing of the DT binding. Before 64c3b252e9fc, snps,fixed-burst and snps,mixed-burst were parsed regardless if the property snps,pbl

Re: Question about ctr mode 3des-ede IV len

On Wed, Dec 07, 2016 at 08:43:16PM +0800, Longpeng (Mike) wrote: > Hi Jussi and Herbert, > > I saw serveral des3-ede testcases(in crypto/testmgr.h) has 16-bytes IV, and > the > libgcrypt/nettle/RFC1851 said the IV-len is 8-bytes. > > Would you please tell me why these testcases has 16-bytes IV

Re: [PATCH v1 1/2] Add crypto driver support for some MediaTek chips

Hello, On Mon, 2016-12-05 at 09:52 +0100, Corentin Labbe wrote: > Hello > > I have two minor comment. > > On Mon, Dec 05, 2016 at 03:01:23PM +0800, Ryder Lee wrote: > > This adds support for the MediaTek hardware accelerator on > > mt7623/mt2701/mt8521p SoC. > > > > This driver currently

Re: [PATCH v2] crypto: sun4i-ss: support the Security System PRNG

On Wed, Dec 07, 2016 at 01:51:27PM +0100, Corentin Labbe wrote: > > So I must expose it as a crypto_rng ? If it is to be exposed at all then algif_rng would be the best place. > Could you explain why PRNG must not be used as hw_random ? The hwrng interface was always meant to be an interface

[PATCH] x86/smpboot: Make logical package management more robust

The logical package management has several issues: - The APIC ids provided by ACPI are not required to be the same as the initial APIC id which can be retrieved by CPUID. The APIC ids provided by ACPI are those which are written by the BIOS into the APIC. The initial id is set by

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

On Thu, Dec 08, 2016 at 08:31:16AM +1100, Stephen Rothwell wrote: > Hi Herbert, > > After merging the crypto-current tree, today's linux-next build (x86_64 > allmodconig) produced this warning: > > crypto/algif_aead.c: In function 'aead_recvmsg': > crypto/algif_aead.c:539:9: warning: 'outlen'

Re: [PATCH] doc: Explain light-handed markup preference a bit better

Em Wed, 7 Dec 2016 12:39:24 -0700 Jonathan Corbet escreveu: > On Wed, 7 Dec 2016 16:42:58 +0100 > Daniel Vetter wrote: > > > We already had a super-short blurb, but worth extending it I think: > > We're still pretty far away from anything like a consensus, but > > there's clearly a lot of

Re: [PATCH v3 4/6] net: stmmac: dwmac1000: fix define DMA_BUS_MODE_RPBL_MASK

Hi Niklas On 12/07/2016 03:20 PM, Niklas Cassel wrote: From: Niklas Cassel DMA_BUS_MODE_RPBL_MASK is really 6 bits, just like DMA_BUS_MODE_PBL_MASK. Signed-off-by: Niklas Cassel --- drivers/net/ethernet/stmicro/stmmac/dwmac1000.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH] x86/smpboot: Make logical package management more robust

On Thu, Dec 08, 2016 at 10:04:25AM +0100, Thomas Gleixner wrote: > The logical package management has several issues: > > - The APIC ids provided by ACPI are not required to be the same as the >initial APIC id which can be retrieved by CPUID. The APIC ids provided >by ACPI are those

[tip:smp/urgent] hotplug: Make register and unregister notifier API symmetric

Commit-ID: 777c6e0daebb3fcefbbd6f620410a946b07ef6d0 Gitweb: http://git.kernel.org/tip/777c6e0daebb3fcefbbd6f620410a946b07ef6d0 Author: Michal Hocko AuthorDate: Wed, 7 Dec 2016 14:54:38 +0100 Committer: Thomas Gleixner CommitDate: Thu, 8 Dec 2016 10:08:41 +0100 hotplug: Make register

Re: Question about ctr mode 3des-ede IV len

On 2016/12/8 17:04, Herbert Xu wrote: > On Wed, Dec 07, 2016 at 08:43:16PM +0800, Longpeng (Mike) wrote: >> Hi Jussi and Herbert, >> >> I saw serveral des3-ede testcases(in crypto/testmgr.h) has 16-bytes IV, and >> the >> libgcrypt/nettle/RFC1851 said the IV-len is 8-bytes. >> >> Would you

Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7

On Thu, Dec 08, 2016 at 09:22:31AM +0100, Jesper Dangaard Brouer wrote: > On Wed, 7 Dec 2016 23:25:31 + > Mel Gorman wrote: > > > On Wed, Dec 07, 2016 at 09:19:58PM +, Mel Gorman wrote: > > > At small packet sizes on localhost, I see relatively low page allocator > > > activity except

Re: [PATCH v1 2/2] crypto: mediatek - add DT bindings documentation

Hello, On Mon, 2016-12-05 at 11:18 +0100, Matthias Brugger wrote: > > On 05/12/16 08:01, Ryder Lee wrote: > > Add DT bindings documentation for the crypto driver > > > > Signed-off-by: Ryder Lee > > --- > > .../devicetree/bindings/crypto/mediatek-crypto.txt | 32 > > ++ > >

Re: [PATCH 2/5] x86: remove idle_notifier

On Wed, 7 Dec 2016, Pavel Machek wrote: > On Wed 2016-12-07 12:46:12, Thomas Gleixner wrote: > > On Tue, 6 Dec 2016, Pavel Machek wrote: > > > > From: Len Brown > > > > > > > > Upon removal of the i7300_idle driver, the idle_notifer is unused. > > > > > > Actually... do we want to keep this

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