[PATCH v3 08/14] rwsem: avoid taking wait_lock in rwsem_down_write_failed

In rwsem_down_write_failed(), if there are active locks after we wake up (i.e. the lock got stolen from us), skip taking the wait_lock and go back to sleep immediately. Signed-off-by: Michel Lespinasse Reviewed-by: Peter Hurley Acked-by: Davidlohr Bueso Acked-by: Rik van Riel --- lib/rwsem.c

[PATCH v3 10/14] rwsem: simplify __rwsem_do_wake

This is mostly for cleanup value: - We don't need several gotos to handle the case where the first waiter is a writer. Two simple tests will do (and generate very similar code). - In the remainder of the function, we know the first waiter is a reader, so we don't have to double check that.

Re: [PATCH] menuconfig: fix NULL pointer dereference when searching a symbol

On 7.5.2013 15:21, Yann E. MORIN wrote: > Li, All, > > On Tue, May 07, 2013 at 10:40:59AM +0800, Li Zefan wrote: >> Searching PPC_EFIKA results segmentation fault, and it's because >> get_symbol_prop() returns NULL. >> >> In this case CONFIG_PPC_EFIKA is defined in arch/powerpc/platforms/ >>

[PATCH v3 12/14] rwsem: do not block readers at head of queue if other readers are active

This change fixes a race condition where a reader might determine it needs to block, but by the time it acquires the wait_lock the rwsem has active readers and no queued waiters. In this situation the reader can run in parallel with the existing active readers; it does not need to block until the

[PATCH v3 13/14] x86 rwsem: avoid taking slow path when stealing write lock

modify __down_write[_nested] and __down_write_trylock to grab the write lock whenever the active count is 0, even if there are queued waiters (they must be writers pending wakeup, since the active count is 0). Note that this is an optimization only; architectures without this optimization will

[PATCH] powerpc/fsl_msi: fix error return code in fsl_of_msi_probe()

From: Wei Yongjun Fix to return a negative error code in the MSI bitmap alloc error handling case instead of 0, as done elsewhere in this function. Signed-off-by: Wei Yongjun --- arch/powerpc/sysdev/fsl_msi.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH v3 14/14] rwsem: no need for explicit signed longs

From: Davidlohr Bueso Change explicit "signed long" declarations into plain "long" as suggested by Peter Hurley. Signed-off-by: Davidlohr Bueso Reviewed-by: Michel Lespinasse Signed-off-by: Michel Lespinasse --- lib/rwsem.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff

[PATCH v3 11/14] rwsem: implement support for write lock stealing on the fastpath

When we decide to wake up readers, we must first grant them as many read locks as necessary, and then actually wake up all these readers. But in order to know how many read shares to grant, we must first count the readers at the head of the queue. This might take a while if there are many readers,

[PATCH v3 06/14] rwsem: more agressive lock stealing in rwsem_down_write_failed

Some small code simplifications can be achieved by doing more agressive lock stealing: - When rwsem_down_write_failed() notices that there are no active locks (and thus no thread to wake us if we decided to sleep), it used to wake the first queued process. However, stealing the lock is also

[PATCH v3 09/14] rwsem: skip initial trylock in rwsem_down_write_failed

We can skip the initial trylock in rwsem_down_write_failed() if there are known active lockers already, thus saving one likely-to-fail cmpxchg. Signed-off-by: Michel Lespinasse Reviewed-by: Peter Hurley Acked-by: Davidlohr Bueso Acked-by: Rik van Riel --- lib/rwsem.c | 17 +

[PATCH v3 05/14] rwsem: simplify rwsem_down_write_failed

When waking writers, we never grant them the lock - instead, they have to acquire it themselves when they run, and remove themselves from the wait_list when they succeed. As a result, we can do a few simplifications in rwsem_down_write_failed(): - We don't need to check for !waiter.task since

[PATCH 108/118] arm: set the page table freeing ceiling to TASK_SIZE

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Catalin Marinas commit 104ad3b32d7a71941c8ab2dee78eea38e8a23309 upstream. ARM processors with LPAE enabled use 3 levels of page tables, with an entry in the top level (pgd) covering 1GB

[PATCH 110/118] drivers/rtc/rtc-at91rm9200.c: fix missing iounmap

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 3427de92ac70a064098ff843c72ac76c420bb1cb upstream. Add missing iounmap to probe error path and remove. Signed-off-by: Johan Hovold Acked-by: Nicolas Ferre

[PATCH 113/118] fs/dcache.c: add cond_resched() to shrink_dcache_parent()

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Greg Thelen commit 421348f1ca0bf17769dee0aed4d991845ae0536d upstream. Call cond_resched() in shrink_dcache_parent() to maintain interactivity. Before this patch: void

[PATCH 109/118] drivers/rtc/rtc-cmos.c: don't disable hpet emulation on suspend

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Derek Basehore commit e005715efaf674660ae59af83b13822567e3a758 upstream. There's a bug where rtc alarms are ignored after the rtc cmos suspends but before the system finishes suspend.

[PATCH 117/118] Revert "drm/i915: GFX_MODE Flush TLB Invalidate Mode must be '1' for scanline waits"

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Luis Henriques This reverts commit 899b5509abbdfee2eab408e7178e559346091ad3, which is commit f05bb0c7b624252a5e768287e340e8e45df96e42 in Linus' tree. This commit has been shown to cause

[PATCH 111/118] md: bad block list should default to disabled.

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 486adf72ccc0c235754923d47a2270c5dcb0c98b upstream. Maintenance of a bad-block-list currently defaults to 'enabled' and is then disabled when it cannot be supported.

[PATCH 106/118] fs/fscache/stats.c: fix memory leak

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Anurup m commit ec686c9239b4d472052a271c505d04dae84214cc upstream. There is a kernel memory leak observed when the proc file /proc/fs/fscache/stats is read. The reason is that in

[PATCH 103/118] ixgbe: fix EICR write in ixgbe_msix_other

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Jacob Keller commit d87d830720a1446403ed38bfc2da268be0d356d1 upstream. Previously, the ixgbe_msix_other was writing the full 32bits of the set interrupts, instead of only the ones which

[PATCH] drm/exynos: fix error return code in exynos_drm_load()

From: Wei Yongjun Fix to return -ENOMEM in the exynos_plane_init() error handling case instead of 0, as done elsewhere in this function. Signed-off-by: Wei Yongjun --- drivers/gpu/drm/exynos/exynos_drm_drv.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH 118/118] ARM: 7699/1: sched_clock: Add more notrace to prevent recursion

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit cea15092f098b7018e89f64a5a14bb71955965d5 upstream. cyc_to_sched_clock() is called by sched_clock() and cyc_to_ns() is called by cyc_to_sched_clock(). I suspect that

[PATCH 116/118] ipc: sysv shared memory limited to 8TiB

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Robin Holt commit d69f3bad4675ac519d41ca2b11e1c00ca115cecd upstream. Trying to run an application which was trying to put data into half of memory using shmget(), we found that having a

[PATCH 114/118] exec: do not abuse ->cred_guard_mutex in threadgroup_lock()

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Oleg Nesterov commit e56fb2874015370e3b7f8d85051f6dce26051df9 upstream. threadgroup_lock() takes signal->cred_guard_mutex to ensure that thread_group_leader() is stable. This doesn't

[PATCH 112/118] inotify: invalid mask should return a error number but not set it

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Zhao Hongjiang commit 04df32fa10ab9a6f0643db2949d42efc966bc844 upstream. When we run the crackerjack testsuite, the inotify_add_watch test is stalled. This is caused by the invalid

[PATCH 115/118] tty: fix up atime/mtime mess, take three

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit b0b885657b6c8ef63a46bc9299b2a7715d19acde upstream. We first tried to avoid updating atime/mtime entirely (commit b0de59b5733d: "TTY: do not update atime/mtime on

[PATCH 100/118] USB: ftdi_sio: enable two UART ports on ST Microconnect Lite

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Adrian Thomasset commit 71d9a2b95fc9c9474d46d764336efd7a5a80 upstream. The FT4232H used in the ST Micro Connect Lite has four hi-speed UART ports. The first two ports are reserved

[PATCH 078/118] USB: add ftdi_sio USB ID for GDM Boost V1.x

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Stefani Seibold commit 58f8b6c4fa5a13cb2ddb400e26e9e65766d71e38 upstream. This patch add a missing usb device id for the GDMBoost V1.x device The patch is against 3.9-rc5

[PATCH 056/118] net: rate-limit warn-bad-offload splats.

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Ben Greear commit c846ad9b880ece01bb4d8d07ba917734edf0324f upstream. If one does do something unfortunate and allow a bad offload bug into the kernel, this the skb_warn_bad_offload can

[PATCH 037/118] netrom: fix info leak via msg_name in nr_recvmsg()

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Mathias Krause commit 3ce5efad47b62c57a4f5c54248347085a750ce0e upstream. In case msg_name is set the sockaddr info gets filled out, as requested, but the code fails to initialize the

[PATCH 017/118] vm: convert fb_mmap to vm_iomap_memory() helper

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit fc9bbca8f650e5f738af8806317c0a041a48ae4a upstream. This is my example conversion of a few existing mmap users. The fb_mmap() case is a good example because it is

[PATCH 001/118] ath9k_htc: accept 1.x firmware newer than 1.3

3.5.7.12 -stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit 319e7bd96aca64a478f3aad40711c928405b8b77 upstream. Since the firmware has been open sourced, the minor version has been bumped to 1.4 and the API/ABI will stay

Re: h8300 SYMBOL_NAME() breakage

On 06/05/13 13:31, Geert Uytterhoeven wrote: > Commit e1b5bb6d1236d4ad2084c53aa83dde7cdf6f8eea ("consolidate cond_syscall > and SYSCALL_ALIAS declarations") broke the h8300 build because it removed > the duplicate SYMBOL_NAME from arch/h8300/include/asm/linkage.h, and all > the h8300 asm files

[RFC] regmap: debugfs: Fix start_reg calculation

From: Srinivas Kandagatla If we dump syscon regmap registers via debufs you will notice that the dump contains lot of values at the end. An example configuration is: syscon@fdde{ compatible = "syscon"; reg = <0xfdde 0x15c>; }; example dump: cat

Re: [PATCH V2 01/20] thermal: exynos: Moving exynos thermal files into samsung directory

On Tuesday 07 of May 2013 18:48:46 amit daniel kachhap wrote: > Hi Tomasz Figa, > > On Tue, May 7, 2013 at 3:51 PM, Tomasz Figa wrote: > > On Monday 06 of May 2013 23:05:06 Zhang Rui wrote: > >> On Fri, 2013-04-26 at 16:07 +0530, Amit Daniel Kachhap wrote: > >> > This movement of files is done

Re: [Xen-devel] [PATCH RFC v2 2/4] arm: introduce CONFIG_PARAVIRT and pv_time_ops

On Tue, 7 May 2013, Ian Campbell wrote: > On Tue, 2013-05-07 at 13:15 +0100, Stefano Stabellini wrote: > > On Tue, 7 May 2013, Ian Campbell wrote: > > > On Mon, 2013-05-06 at 15:51 +0100, Stefano Stabellini wrote: > > > > Introduce CONFIG_PARAVIRT on ARM. > > > > > > What about

Re: [Xen-devel] [PATCH RFC v2 4/4] xen/arm: account for stolen ticks

On Tue, May 07, 2013 at 12:58:32PM +0100, Stefano Stabellini wrote: > On Tue, 7 May 2013, Ian Campbell wrote: > > On Mon, 2013-05-06 at 15:51 +0100, Stefano Stabellini wrote: > > > Register the runstate_memory_area with the hypervisor. > > > Use pv_time_ops.steal_clock to account for stolen ticks.

Re: WARNING at drivers/pci/search.c:214 for 3.9

On Tue, 7 May 2013 12:38:30 +0200 Borislav Petkov wrote: > On Tue, May 07, 2013 at 08:52:05AM +0200, Bruno Prémont wrote: > > Better that way (log_buf_len=10M)! > > > > The full boot log is available at: > > http://pastebin.com/hVVne14C > > (the Hardware Error message is there right before the

Re: [PATCH V2 02/20] thermal: exynos: Bifurcate exynos thermal common and tmu controller code

Hi Rui, On Mon, May 6, 2013 at 8:46 PM, Zhang Rui wrote: > On Fri, 2013-04-26 at 16:07 +0530, Amit Daniel Kachhap wrote: >> This code bifurcates exynos thermal implementation into common and sensor >> specific parts. The common thermal code interacts with core thermal layer and >> core cpufreq

Re: [PATCH] pinctrl: single: fix error return code in pcs_parse_one_pinctrl_entry()

On 7 May 2013 20:57, Wei Yongjun wrote: > On 05/07/2013 08:11 PM, Haojian Zhuang wrote: >> On 7 May 2013 20:06, Wei Yongjun wrote: >>> From: Wei Yongjun >>> >>> Fix to return a negative error code from the error handling >>> case instead of 0, as done elsewhere in this function. >>> >>>

Re: 3.9.0: WARNING: at drivers/base/core.c:575

On Tue, May 07, 2013 at 01:52:54PM +0530, Srivatsa S. Bhat wrote: > For the x86-64 case, does the patch posted here fix the issue? > http://marc.info/?l=linux-edac=136731542432210=2 CAI, can I have your Tested-by before I pick it up? Thanks. -- Regards/Gruss, Boris. Sent from a fat crate

[PATCH] drm/exynos: fix error return code in exynos_drm_ipp_set_property()

From: Wei Yongjun Fix to return a negative error code from the error handling case instead of 0, as done elsewhere in this function. ipp_create_cmd_work() return ERR_PTR() on error and never return NULL, so use IS_ERR() instead of IS_ERR_OR_NULL(). Signed-off-by: Wei Yongjun ---

Re: [PATCH] menuconfig: fix NULL pointer dereference when searching a symbol

Li, All, On Tue, May 07, 2013 at 10:40:59AM +0800, Li Zefan wrote: > Searching PPC_EFIKA results segmentation fault, and it's because > get_symbol_prop() returns NULL. > > In this case CONFIG_PPC_EFIKA is defined in arch/powerpc/platforms/ > 52xx/Kconfig, so it won't be parsed if ARCH!=PPC, but

[PATCH] x86, setup: Removed spaces, trailing character and suspect code indent warnings and errors in a20.c This is a patch to the a20.c file that fixes following warnings/errors found by the checkpat

Signed-off-by: Syed Salman Mansoor --- arch/x86/boot/a20.c | 48 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/arch/x86/boot/a20.c b/arch/x86/boot/a20.c index 64a31a6..4565f4d 100644 --- a/arch/x86/boot/a20.c +++

Re: [PATCH V2 01/20] thermal: exynos: Moving exynos thermal files into samsung directory

Hi Tomasz Figa, On Tue, May 7, 2013 at 3:51 PM, Tomasz Figa wrote: > On Monday 06 of May 2013 23:05:06 Zhang Rui wrote: >> On Fri, 2013-04-26 at 16:07 +0530, Amit Daniel Kachhap wrote: >> > This movement of files is done for easy maintenance and adding more >> > new sensor's support for exynos

Re: [RESEND][PATCH 1/3] arm: dts: introduce config HAS_BANDGAP

Hello Jason, On 06-05-2013 20:36, Jason Gunthorpe wrote: > On Mon, May 06, 2013 at 08:23:13PM -0400, Eduardo Valentin wrote: > >>> I get the impression it is desired to minimize driver kconfig >>> dependencies to the minimum required to compile to increase build >>> testing coverage, so maybe it

Re: [PATCH V2 01/20] thermal: exynos: Moving exynos thermal files into samsung directory

Hi Rui, On Mon, May 6, 2013 at 8:35 PM, Zhang Rui wrote: > On Fri, 2013-04-26 at 16:07 +0530, Amit Daniel Kachhap wrote: >> This movement of files is done for easy maintenance and adding more >> new sensor's support for exynos platform easily . This will also help in >> bifurcating exynos

[PATCH 1/2] regulator: support operating mode in the device tree structure

For better power efficiency, regulator subsystem provides operating mode. (fast, normal, idle and standby) The operating mode is selective by a regulator consumer. With this patch, regulator operating mode can be set in the DT structure. If any operating mode is configured, then 'valid_ops_mask'

[PATCH 2/2] regulator: lp872x: support the device tree feature

This patch creates the DT structure of the LP8720 and LP8725 device. The LP872x platform data is generated when the device tree is configured. Even if the platform data is NULL, it is no issue at all because the driver is configured with the default mode. Change on the DVS initialization: When

[RESEND PATCH V3 01/21] thermal: exynos: Moving exynos thermal files into samsung directory

This movement of files is done for easy maintenance and adding more new sensor's support for exynos platform easily . This will also help in bifurcating exynos common, sensor driver and sensor data related parts. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap ---

[PATCH V3 06/21] thermal: exynos: Add missing definations and code cleanup

This patch adds some extra register bitfield definations and cleans up the code to prepare for moving register macros and definations inside the TMU data section. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap --- drivers/thermal/samsung/exynos_tmu.c | 62

[PATCH V3 05/21] thermal: exynos: Bifurcate exynos tmu driver and configuration data

This code splits the exynos tmu driver code into SOC specific data parts. This will simplify adding new SOC specific data to the same TMU controller. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap --- drivers/thermal/samsung/Kconfig | 13 -

[PATCH V3 03/21] thermal: exynos: Rename exynos_thermal.c to exynos_tmu.c

This patch renames exynos_thermal.c to exynos_tmu.c. This change is needed as this file now just contains exynos tmu driver related codes and thermal zone or cpufreq cooling registration related changes are not there anymore. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap ---

[PATCH V3 07/21] thermal: exynos: Add extra entries in the tmu platform data

This patch adds entries min_efuse_value, max_efuse_value, default_temp_offset, trigger_type, cal_type, trim_first_point, trim_second_point and trigger_enable in the TMU platform data structure. Also the driver is modified to use the data passed by these new platform memebers instead of the

[PATCH V3 08/21] thermal: exynos: Support thermal tripping

TMU urgently sends active-high signal (thermal trip) to PMU, and thermal tripping by hardware logic. Thermal tripping means that PMU cuts off the whole power of SoC by controlling external voltage regulator. Acked-by: Kukjin Kim Signed-off-by: Jonghwan Choi Signed-off-by: Amit Daniel Kachhap

[PATCH V3 13/21] thermal: exynos: Return success even if no cooling data supplied

This patch removes the error return in the bind/unbind routine as the platform may not register any cpufreq cooling data. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap --- drivers/thermal/samsung/exynos_thermal_common.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

[PATCH V3 11/21] thermal: exynos: Add support for instance based register/unregister

This code modifies the thermal driver to have multiple thermal zone support by replacing the global thermal zone variable with device data member of thermal_zone_device. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap --- drivers/thermal/samsung/exynos_thermal_common.c | 36

[PATCH V3 12/21] thermal: exynos: Modify private_data to appropriate name driver_data

This patch renames member private_data to driver_data of the thermal zone registration structure as this item stores the driver related data and uses it to call the driver related callbacks. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap ---

[PATCH V3 09/21] thermal: exynos: Move register definitions from driver file to data file

This patch migrates the TMU register definition/bitfields to data file. This is needed to support SoC's which use the same TMU controller but register validity, offsets or bitfield may slightly vary across SOC's. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap ---

[PATCH V3 19/21] Documentation: thermal: Explain the exynos thermal driver model

This patch updates the documentation to explain the driver model and file layout. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap --- Documentation/thermal/exynos_thermal | 43 ++--- 1 files changed, 34 insertions(+), 9 deletions(-) diff --git

[PATCH V3 21/21] ARM: dts: Add device tree node for exynos5440 TMU controller

This patch adds device node for TMU controller. There are 3 instances of the controllers so 3 nodes are created. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap --- arch/arm/boot/dts/exynos5440.dtsi | 30 ++ 1 files changed, 30 insertions(+), 0

[PATCH V3 20/21] thermal: exynos: Support for TMU regulator defined at device tree

TMU probe function now checks for a device tree defined regulator. For compatibility reasons it is allowed to probe driver even without this regulator defined. Signed-off-by: Lukasz Majewski Signed-off-by: Kyungmin Park Signed-off-by: Amit Daniel Kachhap ---

[PATCH V3 18/21] thermal: exynos: Add support for exynos5440 TMU sensor.

This patch modifies TMU controller to add changes needed to work with exynos5440 platform. Also register definitions and required configuration data are added. This sensor registers 3 instance of the tmu controller with the thermal zone and hence reports 3 temperature output. This controller

[PATCH V3 17/21] ARM: dts: thermal: exynos4: Add documentation for Exynos SoC thermal bindings

From: Lukasz Majewski Proper description for Exynos4 bindings added to Documentation/devicetree/ bindings Signed-off-by: Lukasz Majewski Signed-off-by: Kyungmin Park --- .../devicetree/bindings/thermal/exynos-thermal.txt | 25 1 files changed, 25 insertions(+), 0

[PATCH V3 16/21] thermal: exynos: Add features to check instead of using SOC type

This patch adds several features supported by TMU as bitfields. This features varies across different SOC type and comparing the features present in the TMU is more logical than comparing the soc itself. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap ---

[PATCH V3 14/21] thermal: exynos: Make the zone handling dependent on trip count

This code simplifies the zone handling to use the trip count passed by the TMU driver. This also helps in adding more zone support. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap --- drivers/thermal/samsung/exynos_thermal_common.c | 55 ---

[PATCH V3 15/21] thermal: exynos: Add support to handle many instances of TMU

This patch adds support to handle multiple instances of the TMU controllers. This is done by removing the static structure to register with the core thermal and creating it dynamically for each instance of the TMU controller. The interrupt is made shared type to handle interrupts for all the TMU.

[PATCH V3 10/21] thermal: exynos: Fix to clear only the generated interrupts

This patch uses the TMU status register to know the generated interrupts and only clear them in the interrupt handler. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap --- drivers/thermal/samsung/exynos_tmu.c | 10 -- drivers/thermal/samsung/exynos_tmu_data.c |2 ++ 2

[PATCH V3 04/21] thermal: exynos: Move exynos_thermal.h from include/* to driver/* folder

This patch renames and moves include/linux/platform_data/exynos_thermal.h to drivers/thermal/samsung/exynos_tmu.h. This file movement is needed as exynos SOC's are not supporting non-DT based platforms. Also the rename is needed as this file now just contains exynos tmu driver related

[PATCH V3 02/21] thermal: exynos: Bifurcate exynos thermal common and tmu controller code

This code bifurcates exynos thermal implementation into common and sensor specific parts. The common thermal code interacts with core thermal layer and core cpufreq cooling parts and is independent of SOC specific driver. This change is needed to cleanly add support for new TMU sensors. Acked-by:

[PATCH V3 01/21] thermal: exynos: Moving exynos thermal files into samsung directory

This movement of files is done for easy maintenance and adding more new sensor's support for exynos platform easily . This will also help in bifurcating exynos common, sensor driver and sensor data related parts. Acked-by: Kukjin Kim Signed-off-by: Amit Daniel Kachhap ---

[PATCH V3 0/20] thermal: exynos: Add thermal driver for exynos5440

Changes in V3: * Added proper dependency of different exynos thermal Kconfig symbols. Basically 3 Kconfig can be enabled now and corresponds to tmu driver. exynos common part and exynos configuration data. This issue was raised by Rui Zhang. Changes in V2: * Separated SOC data from TMU driver.

[GIT] kbuild misc change for v3.10-rc1

Hi Linus, please pull these non-critical kbuild changes for v3.10-rc1: * make coccicheck improvements, but no new semantic patches this time * make rpm improvements * make tar-pkg change to include the architecture in the filename. This is a deliberate incompatibility, but nobody has

Re: [PATCH] pinctrl: single: fix error return code in pcs_parse_one_pinctrl_entry()

On 05/07/2013 08:11 PM, Haojian Zhuang wrote: > On 7 May 2013 20:06, Wei Yongjun wrote: >> From: Wei Yongjun >> >> Fix to return a negative error code from the error handling >> case instead of 0, as done elsewhere in this function. >> >> Introduced by commit

Re: [Xen-devel] [PATCH RFC v2 4/4] xen/arm: account for stolen ticks

> > > @@ -301,6 +320,10 @@ static int __init xen_init_events(void) > > > > > > on_each_cpu(xen_percpu_init, NULL, 0); > > > > > > + pv_time_ops.steal_clock = xen_stolen_accounting; > > > + static_key_slow_inc(_steal_enabled); > > > + static_key_slow_inc(_steal_rq_enabled); > > > > We don't

Re: [Xen-devel] [PATCH RFC v2 2/4] arm: introduce CONFIG_PARAVIRT and pv_time_ops

On Tue, 2013-05-07 at 13:15 +0100, Stefano Stabellini wrote: > On Tue, 7 May 2013, Ian Campbell wrote: > > On Mon, 2013-05-06 at 15:51 +0100, Stefano Stabellini wrote: > > > Introduce CONFIG_PARAVIRT on ARM. > > > > What about PARAVIRT_TIME_ACCOUNTING? I'm not sure what it is but it > > looks

Re: [PATCH 0/5] drivers: bus: omap_l3: Conversion to devm_*

On Thursday 02 May 2013 05:39 PM, Peter Ujfalusi wrote: > Hi, > > Cleanup of platform probe and remove (removing the remove function at the end) > with converting the driver to use the devm_* versions kzalloc, ioremap and > request_irq. > Thanks Peter. All patches looks fine to my eyes. In the

Re: [PATCH] Reset PCIe devices to stop ongoing DMA

On 05/07/2013 03:09 AM, Takao Indoh wrote: > Sorry for the delayed response. > > (2013/04/30 23:54), Sumner, William wrote: >> I have installed your original patch set (from last November) and tested >> with three platforms, each with a different IO configuration. On the first >> platform

[GIT] kconfig changes for v3.10-rc1

Hi Linus, please pull the following kconfig bits for v3.10-rc1: * use pkg-config to detect curses libraries * clean up the way curses headers are searched * Some randconfig fixes, of which one had to be reverted * KCONFIG_SEED for randconfig debugging * memuconfig memory leak plugged *

Re: [PATCHv3 0/4] perf, signal x86: Fix breakpoint events overflow handling

On Wed, May 01, 2013 at 05:25:40PM +0200, Jiri Olsa wrote: > hi, > sending v3 for initial patchset: > https://lkml.org/lkml/2013/3/1/324 > > basically just sending remaining (not pulled) patches, > with '*-by: *' tags updated. > > v3 changes: > - perf test patches already pulled in > - added

RE: [PATCH] futex: bugfix for futex-key conflict when futex use hugepage

Hi, The futex-keys of processes share futex determined by page-offset, mapping-host, and mapping-index of the user space address. User appications using hugepage for futex may lead to futex-key conflict. Assume there are two or more futexes in diffrent normal pages of the hugepage, and each

[GIT] kbuild changes for v3.10-rc1

Hi Linus, please pull these kbuild commits for v3.10-rc1: * Fix make mrproper after mod/file2alias rework * Fix ld-option Makefile function * Rewrite headers_install to shell to drop Perl dependency. There are some more patches I have to look at, so I might send another pull request later. Or

[PATCH] w1: ds2408: add magic sequence to disable P0 test mode

extract from http://datasheets.maximintegrated.com/en/ds/DS2408.pdf: Power-up timing The DS2408 is sensitive to the power-on slew rate and can inadvertently power up with a test mode feature enabled. When this occurs, the P0 port does not respond to the Channel Access Write command. For most

Fix ds2408 P0 output not working after power-on

This issue is described in the v2 datasheet of ds2408 (see commit message). On our board (9 ds2408 and 2 ds2433 on a ds1wm mastered bus), the problem affects only 2 out of 9 chips 2408 and only after a long power off. Adding the magic sequence described in the datasheet fixes the issue as

[PATCH REBASE] irqchip: Add TB10x interrupt controller driver

The SOC interrupt controller driver for the Abilis Systems TB10x series of SOCs based on ARC700 CPUs. This driver is required to boot the arch/arc/plat-tb10x platform already present in linux-next. Please consider this patch for inclusion in 3.10. This is the rebase of a previous version on

RE: [PATCH] futex: bugfix for futex-key conflict when futex use hugepage

It is OK that I send the mail to myself , but there are some wrong while sending to you. Ignore this mail ,please, I will check and send it again. > -Original Message- > From: Zhang Yi [mailto:wet...@gmail.com] > Sent: Tuesday, May 07, 2013 8:24 PM > To: 'Thomas Gleixner' > Cc:

Re: [094/126] TTY: fix atime/mtime regression

On Tue, 2013-05-07 at 09:03 +0200, Jiri Slaby wrote: > On 05/07/2013 05:58 AM, Steven Rostedt wrote: > > 3.6.11.3 stable review patch. > > If anyone has any objections, please let me know. > > > > -- > > > > From: Jiri Slaby > > > > [ Upstream commit

Re: [PATCH] [media] davinci: vpfe: fix error return code in vpfe_probe()

Hi Wei, Thanks for the patch. On Tue, May 7, 2013 at 5:21 PM, Wei Yongjun wrote: > From: Wei Yongjun > > Fix to return a negative error code from the error handling > case instead of 0, as done elsewhere in this function. > > Signed-off-by: Wei Yongjun Acked-by: Lad, Prabhakar Regards,

Re: [PATCH v3 04/16] lockdep: check that no locks held at freeze time

On Mon 2013-05-06 16:50:09, Colin Cross wrote: > From: Mandeep Singh Baines > > We shouldn't try_to_freeze if locks are held. Holding a lock can cause a > deadlock if the lock is later acquired in the suspend or hibernate path > (e.g. by dpm). Holding a lock can also cause a deadlock in the

Re: [PATCH v3 02/16] freezer: add unsafe versions of freezable helpers for CIFS

On Mon 2013-05-06 16:50:07, Colin Cross wrote: > CIFS calls wait_event_freezekillable_unsafe with a VFS lock held, > which is unsafe and will cause lockdep warnings when 6aa9707 > "lockdep: check that no locks held at freeze time" is reapplied > (it was reverted in dbf520a). CIFS shouldn't be

Re: [PATCH v3 03/16] lockdep: remove task argument from debug_check_no_locks_held

On Mon 2013-05-06 16:50:08, Colin Cross wrote: > The only existing caller to debug_check_no_locks_held calls it > with 'current' as the task, and the freezer needs to call > debug_check_no_locks_held but doesn't already have a current > task pointer, so remove the argument. It is already assuming

RE: [PATCH] futex: bugfix for futex-key conflict when futex use hugepage

> -Original Message- > From: Thomas Gleixner [mailto:t...@linutronix.de] > Sent: Saturday, April 27, 2013 2:26 AM > To: Zhang Yi > Cc: linux-kernel@vger.kernel.org; 'Peter Zijlstra'; 'Darren Hart'; 'Ingo > Molnar'; 'Dave Hansen'; zhang.y...@zte.com.cn; > wet...@163.com > Subject: Re:

Re: [Qemu-devel] [PATCH 0/4] madvise(MADV_USERFAULT) & sys_remap_anon_pages()

On Tue, May 07, 2013 at 01:38:10PM +0200, Andrew Jones wrote: > What about instead of adding a new syscall (remap_anon_pages) to > instead extend mremap with new flags giving it a strict mode? I actually thought about this and it's a very interesting argument. When I thought about it, I felt the

Re: Build errors caused by modalias generation patch

On Tue, May 7, 2013 at 12:58 PM, Geert Uytterhoeven wrote: > On Tue, May 7, 2013 at 12:04 PM, Ralf Baechle wrote: >> On Mon, May 06, 2013 at 07:19:53PM +0200, Andreas Schwab wrote: >>> Please try the patch in >>> . >> >> No change in observed

Re: [PATCH 0/2] Early printk support for virtio console devices.

On 7 May 2013 05:46, Rusty Russell wrote: > Peter Maydell writes: >> That all looks like sensible QEMU implementation possibilities >> but it seems to be a bit of a non-sequitur from "how do we >> tell the kernel to actually use this?" > > You enable the feature in the virtio console device, and

[GIT PULL] remoteproc for 3.10

There's a trivial merge conflict with a Kconfig typo that got fixed during the rc cycle, but otherwise: The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9: Linux 3.9-rc2 (2013-03-10 16:54:19 -0700) are available in the git repository at:

Re: [Xen-devel] [PATCH RFC v2 2/4] arm: introduce CONFIG_PARAVIRT and pv_time_ops

On Tue, 7 May 2013, Ian Campbell wrote: > On Mon, 2013-05-06 at 15:51 +0100, Stefano Stabellini wrote: > > Introduce CONFIG_PARAVIRT on ARM. > > What about PARAVIRT_TIME_ACCOUNTING? I'm not sure what it is but it > looks like a more lightweight version of pv stolen time?

Re: [PATCH] h8300: Hardcode symbol prefixes in asm sources

On Tue, May 7, 2013 at 2:02 PM, Al Viro wrote: > On Tue, May 07, 2013 at 11:52:00AM +0200, Geert Uytterhoeven wrote: >> arch/h8300/kernel/syscalls.S | 646 >> +++--- > > NAK on this part - either turn it into array initialized in something.c, > or at least do

Re: Add missing module license tag to vring helpers.

Dave Jones writes: > On Mon, May 06, 2013 at 05:06:23PM +0930, Rusty Russell wrote: > > Dave Jones writes: > > > [ 624.286653] vringh: module license 'unspecified' taints kernel. > > > > > > Signed-off-by: Dave Jones > > > > Thanks! This is exactly right. > > > > But note that the

Re: [PATCH 0/2] Early printk support for virtio console devices.

Peter Maydell writes: > On 6 May 2013 06:11, Rusty Russell wrote: >> Peter Maydell writes: >>> To be actually useful we need to also specify something in >>> the device tree to say "here is where you will find your >>> emergency output and what it is". >> >> Hmm, I'm not sure that's true. It

Re: [PATCH] pinctrl: single: fix error return code in pcs_parse_one_pinctrl_entry()

On 7 May 2013 20:06, Wei Yongjun wrote: > From: Wei Yongjun > > Fix to return a negative error code from the error handling > case instead of 0, as done elsewhere in this function. > > Introduced by commit 9dddb4df90d136429b6d6ddefceb49a9b93f6cd1 > (pinctrl: single: support generic pinconf) > >

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