Re: [PATCH v3] pci: spear: Drop __initdata from spear13xx_pcie_driver

On 02/19/2015 07:41 PM, Matwey V. Kornilov wrote: > spear13xx_pcie_driver.driver is allocated in text.init section > and then the pointer to it is passed futher. This patch is to avoid > crashes like the following, when freed memory is used. > What happened with this patch, could it go as a fix?

Re: [PATCH] proc: show locks in /proc/pid/fdinfo/X

On Thu, Mar 05, 2015 at 06:37:18PM +0300, Andrey Vagin wrote: > Let's show locks which are associated with a file descriptor in > its fdinfo file. > > Currently we don't have a reliable way to determine who holds a lock. > We can find some information in /proc/locks, but PID which is reported >

Re: [PATCH] Documentation: update the of_selftest.txt

On Mon, Mar 2, 2015 at 9:56 PM, Wang Long wrote: > Since the directory "drivers/of/testcase-data" is renamed > to "drivers/of/unittest-data". so we should update the path > in the of_selftest.txt. > > When the kernel is build with OF_SELFTEST enabled, the output s/build/built/ s/SELF/UNIT/ >

Re: [PATCH v4] spi: qup: Add DMA capabilities

On Wed, 2015-03-04 at 12:02 +0200, Stanimir Varbanov wrote: > From: Andy Gross > > This patch adds DMA capabilities to the spi-qup driver. If DMA channels are > present, the QUP will use DMA instead of block mode for transfers to/from SPI > peripherals for transactions larger than the length

Re: Possible lock-less list race in scheduler_ipi()

- Original Message - > From: "Linus Torvalds" > To: "Mathieu Desnoyers" > Cc: "Paul E. McKenney" , "Huang Ying" > , "Lai Jiangshan" > , "Lai Jiangshan" , "Peter Zijlstra" > , "LKML" > , "Ingo Molnar" , "Steven > Rostedt" > Sent: Thursday, March 5, 2015 8:02:06 PM > Subject: Re:

Re: [PATCH v2] dmaengine: qcom_bam_dma: Add support for BAM v1.7.0

On Mon, 2015-02-23 at 09:40 +0530, Archit Taneja wrote: > Add register offset table entry for the newer (v1.7.0) version of the BAM IP > found on MSM8916. Update the DT bindings documentation. > > Signed-off-by: Archit Taneja > --- > Change in v2: Fix wrong execution environment multiplier for

Re: sched: softlockups in multi_cpu_stop

Are you sure about this ? I have a core dump locked on the same place (state machine for powering cpu down for the task swap) from a 3.13 (+ upstream patches) and this commit wasn't backported yet. -> multi_cpu_stop -> do { } while (curstate != MULTI_STOP_EXIT); In my case, curstate is WAY

Re: [RFC PATCH v2] bridge: make it possible for packets to traverse the bridge without hitting netfilter

On Fri, Mar 06, 2015 at 11:34:29AM +0100, Imre Palik wrote: > On 02/26/15 17:34, David Miller wrote: > > From: Imre Palik > > Date: Thu, 26 Feb 2015 11:19:25 +0100 > > > >> If you are looking for peculiarities in my setup then here they are: > >> I am on 4k pages, and perf is not working :-( >

Re: [PATCH v5 16/29] powerpc/pci: Use pci_scan_host_bridge() for simplicity

On Fri, Mar 6, 2015 at 3:33 AM, Yijing Wang wrote: > Now we could use pci_scan_host_bridge() to scan > pci buses, provide powerpc specific pci_host_bridge_ops. > > Suggested-by: Arnd Bergmann > Signed-off-by: Yijing Wang > CC: Benjamin Herrenschmidt > CC: linuxppc-...@lists.ozlabs.org >

Re: [PATCH] proc: show locks in /proc/pid/fdinfo/X

On Thu, Mar 05, 2015 at 02:11:40PM -0500, Jeff Layton wrote: > On Thu, 5 Mar 2015 18:37:18 +0300 > Andrey Vagin wrote: > > > Let's show locks which are associated with a file descriptor in > > its fdinfo file. > > > > Currently we don't have a reliable way to determine who holds a lock. > > We

Re: [PATCH 1/1] x86/fpu: math_state_restore() should not blindly disable irqs

On 03/06, Oleg Nesterov wrote: > > On 03/06, Ingo Molnar wrote: > > > > How about the patch from David Vrabel? That seems to solve the > > irq-disable problem too, right? > > I wasn't cc'ed, I guess you mean > > [PATCHv4] x86, fpu: remove the logic of non-eager fpu mem allocation at > the

[PATCH] regmap: introduce regmap_name to fix syscon regmap trace events

This patch fixes a NULL pointer dereference when enabling regmap event tracing in the presence of a syscon regmap, introduced by commit bdb0066df96e ("mfd: syscon: Decouple syscon interface from platform devices"). That patch introduced syscon regmaps that have their dev field set to NULL. The

Re: [PATCH] drm/exynos: Check for NULL dereference of crtc

On Fri, Mar 06, 2015 at 10:13:42PM +0900, Inki Dae wrote: > On 2015년 02월 18일 02:14, Charles Keepax wrote: > > The commit "drm/exynos: remove exynos_plane_dpms" (d9ea6256) removed the > > use of the enabled flag, which means that the code may attempt to call > > win_enable on a NULL crtc. This

Re: [PATCH 1/1] x86/fpu: math_state_restore() should not blindly disable irqs

On 03/06, Ingo Molnar wrote: > > * Oleg Nesterov wrote: > > > On 03/06, Ingo Molnar wrote: > > > > > > * Oleg Nesterov wrote: > > > > > > > [...] The patch above looks "obviously safe", but perhaps I am > > > > paranoid too much... > > > > > > IMHO your hack above isn't really acceptable, even

Re: [RFC PATCH 0/1] Wrong structure alignment due to compiler attribute "section"

On 05.03.2015 18:33, Dave Martin wrote: On Thu, Mar 05, 2015 at 04:32:28PM +0100, Lino Sanfilippo wrote: On 05.03.2015 14:47, Dave Martin wrote: Source code? That just looks like binaries to me. Oops, youre right, there is no source in that package, sorry. I tried to contact the persons

Re: [PATCH v2 02/15] x86, boot: move ZO to end of buffer

On Wed, Mar 04, 2015 at 12:00:35AM -0800, Yinghai Lu wrote: > bp found data from boot stage can not be used kernel stage. > > Actually those data area is overlapped with VO kernel bss stage, and > clear_bss() "VO kernel bss stage"? I'm sure you can think of a better explanation. Right now I'm

Re: [PATCH v2 1/2] livepatch/module: Apply patch when loaded module is unformed

On Fri 2015-03-06 11:20:32, Petr Mladek wrote: > On Thu 2015-03-05 13:34:33, Josh Poimboeuf wrote: > > On Thu, Mar 05, 2015 at 04:45:13PM +0100, Petr Mladek wrote: > > > Existing live patches are applied to loaded modules using a notify > > > handler. > > > There are two problems with this

Re: [PATCH v2 01/15] x86, kaslr: Use init_size instead of run_size

On Wed, Mar 04, 2015 at 12:00:34AM -0800, Yinghai Lu wrote: > commit e6023367d779 ("x86, kaslr: Prevent .bss from overlaping initrd") > > introduced one run_size for kaslr. > > We do not need to have home grown run_size. > > We should use real runtime size (include copy/decompress) aka

Re: [patch -rt 1/2] KVM: use simple waitqueue for vcpu->wq

* Marcelo Tosatti | 2015-01-14 15:12:52 [-0200]: Against which tree was this prepared? Could please rebase it against v3.18.7-rt2? Because a I see "fuzz 2", the mips file is gone and s390 rejects almost every chunk. And there was that mips chunk Steven noticed. Patch #2 seems to apply but since

Re: Mellanox Technologies MT23108 causes #MC exceptions under heavy load

False alarm, had exactly the same failure with infiniband disabled. Best regards, Maxim Levitsky On Fri, Mar 6, 2015 at 5:35 AM, Maxim Levitsky wrote: > We are running CPU and network heavy test on marmot.pdl.cmu.edu cluster. > It has Mellanox Technologies MT23108 InfiniHost

Bad rpath in cpupower with 4.0-rcX

Hi All, Commit 5c1de006e8e66 (cpupower Makefile change to help run the tool without 'make install') added an rpath to the cpupower binary. From what I can understand, this is to make it easier to run cpupower from the local build directory without having to run make install. It does accomplish

Re: [PATCH net-next v4 0/3] Linn Ethernet Packet Sniffer driver

Hi Richard, On 27/02/15 18:14, Richard Cochran wrote: >> The H/W does have the capability to do that. However, in order to >> implement it there will be some architectural changes needed >> in the kernel. This module cannot really pretend to be a PHY. >> In the real world it sits between the

Re: [PATCH 1/1] x86/fpu: math_state_restore() should not blindly disable irqs

* Oleg Nesterov wrote: > On 03/06, Ingo Molnar wrote: > > > > * Oleg Nesterov wrote: > > > > > [...] The patch above looks "obviously safe", but perhaps I am > > > paranoid too much... > > > > IMHO your hack above isn't really acceptable, even for a backport. > > So lets test the patch below

Re: [PATCH 1/1] x86/fpu: math_state_restore() should not blindly disable irqs

On 03/06, Oleg Nesterov wrote: > > OK, but please note that this patch is not beckportable. If you think > that -stable doesn't need this fix, then I agree. > > If the caller is do_device_not_available(), then we can not enable > irqs before __thread_fpu_begin() + restore_fpu_checking(). > > 1.

Re: [PATCH v2 04/15] x86, kaslr: get kaslr_enabled back correctly

On Wed, Mar 04, 2015 at 01:32:53PM -0800, Yinghai Lu wrote: > On Wed, Mar 4, 2015 at 12:00 PM, Ingo Molnar wrote: > > > > It is totally unacceptable that you don't do proper analysis of the > > patches you submit, and that you don't bother writing proper, readable > > changelogs. > > Sorry,

Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support

Hi all, On 2015년 03월 04일 19:24, Javier Martinez Canillas wrote: > +Gustavo which has been looking at the issues > > Hello, > > On 03/04/2015 09:50 AM, Marek Szyprowski wrote: >> Hello, >> >> On 2015-03-03 21:36, Kevin Hilman wrote: >>> Javier Martinez Canillas writes: >>> Enabling Exynos

Re: [PATCH 1/5] mtd: nand: vf610_nfc: Freescale NFC for VF610, MPC5125 and others

On 2015-03-06 07:15, Sascha Hauer wrote: > Hi Stefan, > > On Thu, Mar 05, 2015 at 12:10:20AM +0100, Stefan Agner wrote: >> + >> +static int vf610_nfc_probe_dt(struct device *dev, struct vf610_nfc_config >> *cfg) >> +{ >> +struct device_node *np = dev->of_node; >> +int buswidth; >> +

[PATCH v2 1/1] mmc: dw_mmc: Add runtime pm to dw_mmc

This patch adds runtime pm handling to dw_mmc. It mainly uses mci_request/mci_request_end for mmc host state information. The goal of the runtime pm in dw_mmc host is mainly for giving an information for containing it power domain about its activity. Signed-off-by: Karol Wrona Acked-by: Kyungmin

Re: [PATCH 1/1] x86/fpu: math_state_restore() should not blindly disable irqs

On 03/06, Ingo Molnar wrote: > > * Oleg Nesterov wrote: > > > [...] The patch above looks "obviously safe", but perhaps I am > > paranoid too much... > > IMHO your hack above isn't really acceptable, even for a backport. > So lets test the patch below (assuming it's the right thing to do) > and

[PATCH v2 0/1] mmc: dw_mmc: Add runtime pm to dw_mmc

Hello, This patch adds runtime pm for dw_mmc. There is no runtime pm callbacks for exynos dw_mmc because the host hardware gates interface clock itself and it is done separately. The reason for runtime is mainly get an info about host state for now. Thanks, Karol Karol Wrona (1): mmc:

Re: Using regmap_update_bits to update a write only register

On Fri, Mar 6, 2015 at 2:45 PM, Lars-Peter Clausen wrote: > On 03/06/2015 12:21 PM, Mark Brown wrote: >> >> On Thu, Mar 05, 2015 at 08:14:14PM +0200, Daniel Baluta wrote: >>> >>> On Mar 5, 2015 7:54 PM, "Mark Brown" wrote: >> >> Probably, or there's a bug. What should happen is that if the

Re: [PATCH 3/3] arm64: dts: mt8173: Add pinctrl/GPIO/EINT node for mt8173.

Hi Hongzhou, 2015-01-27 8:13 GMT+01:00 Hongzhou Yang : > From: Hongzhou Yang > > Add pinctrl,GPIO and EINT node to mt8173.dtsi. > > Signed-off-by: Hongzhou Yang The patch does not apply against v4.0-rc1, do you mind to resend it. Thanks, Matthias > --- >

Re: [PATCH 1/2] arm64: mediatek: Select PINCTRL for Mediatek platform

2015-03-06 7:24 GMT+01:00 Yingjoe Chen : > These 2 patches are fixup for MT8173 pinctrl driver: > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/320066.html > > Arm64 maintainers doesn't want to add MACH_* in Kconfig, this patch > is used to replace the first one in that

Re: [Xen-devel] [PATCH] xen: avoid NULL pointer dereference in dom0 on large machines

On 26/02/15 05:52, Juergen Gross wrote: > Using the pvops kernel a NULL pointer dereference was detected on a > large machine (144 processors) when booting as dom0 in > evtchn_fifo_unmask() during assignment of a pirq. > > The event channel in question was the first to need a new entry in >

Re: [PATCH 1/1] tty: fix up atime/mtime mess, take four

On Fri, 2015-02-27 at 18:40 +0100, Jiri Slaby wrote: > So check the absolute difference of times and if it large than "8 > seconds or so", always update the time. That means we will update > immediatelly when changing time. Ergo, CAP_SYS_TIME can foul the > check, but it was always that way. If I

Re: [PATCH] crypto: RNGs must return 0 in success case

>Change the RNGs to always return 0 in success case. >This patch ensures that seqiv.c works with RNGs other than krng. seqiv >expects that any return code other than 0 is an error. Without the >patch, rfc4106(gcm(aes)) will not work when using a DRBG or an ANSI >X9.31 RNG. For the X9.31 bits:

Re: [PATCH] drm/exynos: Check for NULL dereference of crtc

On 2015년 02월 18일 02:14, Charles Keepax wrote: > The commit "drm/exynos: remove exynos_plane_dpms" (d9ea6256) removed the > use of the enabled flag, which means that the code may attempt to call > win_enable on a NULL crtc. This results in the following oops on Hmm... it's strange.

Re: [PATCH v2 5/6] watchdog: at91sam9: request the irq with IRQF_NO_SUSPEND

> >> > We seem to be conflating some related properties: > >> > > >> > [a] The IRQ will be left unmasked. > >> > [b] The IRQ will be handled immediately when taken. > >> > [c] The IRQ will wake the system from suspend. [...] > > Considering that the use-case of a watchdog is to alert us to

Re: Re: Re: [PATCH 2/2] livepatch: fix patched module loading race

On Fri 2015-03-06 20:37:26, Masami Hiramatsu wrote: > (2015/03/06 19:51), Petr Mladek wrote: > > On Fri 2015-03-06 10:24:27, Masami Hiramatsu wrote: > >> (2015/03/05 23:18), Josh Poimboeuf wrote: > >>> On Thu, Mar 05, 2015 at 09:52:41AM +0900, Masami Hiramatsu wrote: > (2015/03/04 22:17),

[PATCH] coredump: fix cn_printf formatting warnings

Add __printf attributes to cn_*printf functions. With these, gcc says: fs/coredump.c:213:5: warning: format '%d' expects argument of type 'int', but argument 3 has type 'kuid_t' [-Wformat=] err = cn_printf(cn, "%d", cred->uid); ^ fs/coredump.c:217:5: warning: format '%d'

[PATCH] drm: fix sysfs symlinks between driver and module

When registering drivers, the symlinks for mapping between driver and module are created in sysfs. But the drm drivers registered by drm_pci_init() create wrong symlinks, because correct owner module of pci driver is not passed to pci_register_driver(). For example, the i915 driver creates the

Re: [PATCH] clockevents: don't suspend/resume if unused

Ping? On 16/01/2015 at 17:59:14 +0100, Alexandre Belloni wrote : > Hi, > > On 16/01/2015 at 10:20:14 +0100, Sylvain Rochet wrote : > > > + if (dev->suspend && dev->mode != CLOCK_EVT_MODE_UNUSED) > > > > I wonder if we should use > CLOCK_EVT_MODE_SHUTDOWN > > (or CLOCK_EVT_MODE_UNUSED ||

Re: [PATCHv2 00/14] perf tools: Adding xz decompression support

On Fri, Mar 06, 2015 at 12:13:48PM +0100, Jiri Olsa wrote: > hi, > adding support to decompress kernel modules on Fedora 21 > (lzma compression) vaguely continuing in previous RFC: > http://marc.info/?l=linux-kernel=142261340327588=2 > > I'm basically extending he decompression framework

[PATCH] perf hists browser: Fix UI bug after fold/unfold

In perf hists browser, the fold/unfold stat of each hist entry is recorded but hb->nr_callchain_rows loses its value after zoom out and zoom in back. This causes a wrong row cursor range that restrict user to move down anymore. Before: $ perf record -g -e syscalls:* ls $ perf report (select

Re: [PATCH v3] xen-scsiback: define a pr_fmt macro with xen-pvscsi

On 03/06/2015 09:34 PM, Tao Chen wrote: Add the {xen-pvscsi: } prefix in pr_fmt and remove DPRINTK, then replace all DPRINTK with pr_debug. Also fixed up some comments just as eliminate redundant whitespace and format the code. These will make the code easier to read. Signed-off-by: Tao Chen

[PATCH] ARM: mediatek: enable the pin controller

This patch enables the pin controller for Mediatek SoCs. Signed-off-by: Matthias Brugger --- arch/arm/mach-mediatek/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/mach-mediatek/Kconfig b/arch/arm/mach-mediatek/Kconfig index f7e463c..9f59e58 100644 ---

Re: [Xen-devel] [PATCH 3/4] usb: Introduce Xen pvUSB backend

On 2015-03-04 09:09, Juergen Gross wrote: The main question whether it is worth to consider this alternative is the performance aspect. Does anyone have an idea which USB devices would typically be used via pvusb? I'd suspect memory sticks and USB disks and perhaps webcams being the most

Re: [PATCH v2] xen-scsiback: use DRV_PFX in the pr macros and DPRINTK

On Fri, 2015-03-06 at 17:33 +0800, Chentao (Boby) wrote: > #ifdef pr_fmt > #undef pr_fmt > #endif > #define pr_fmt(fmt) "xen-pvscsi: " fmt No, just use add #define pr_fmt(fmt) "xen-pvscsi: " fmt before the first #include. The #ifdef/#undef/#endif isn't necessary. > Then replace all DPRINTK with

Re: [PATCH 12/38] perf tools: Introduce thread__comm_time() helpers

Em Fri, Mar 06, 2015 at 01:38:06PM +0900, Namhyung Kim escreveu: > On Thu, Mar 05, 2015 at 05:08:56PM +0100, Frederic Weisbecker wrote: > > On Wed, Mar 04, 2015 at 09:02:55AM +0900, Namhyung Kim wrote: > > > On Tue, Mar 03, 2015 at 05:28:40PM +0100, Frederic Weisbecker wrote: > > > > On Tue, Mar

Re: Using regmap_update_bits to update a write only register

On 03/06/2015 12:21 PM, Mark Brown wrote: On Thu, Mar 05, 2015 at 08:14:14PM +0200, Daniel Baluta wrote: On Mar 5, 2015 7:54 PM, "Mark Brown" wrote: Probably, or there's a bug. What should happen is that if the register default appeared successfully then the read will get statisfied from

Re: Unwanted delayed execution of _Qxx EC methods

On Friday 06 March 2015 01:52:48 Zheng, Lv wrote: > Hi, Gabriele > > > I couldn't find this in my mail box, but saw it in the spinics.net. > > For EC query, there is no spec definitions around its behavior. > Some EC firmware will have events queued (like edge triggering) while the > others

Re: [PATCH v5 5/5] ARM: dts: mt8135: Add pinctrl/GPIO/EINT node for mt8135.

2015-02-10 9:13 GMT+01:00 Linus Walleij : > On Wed, Jan 21, 2015 at 1:28 PM, Hongzhou Yang > wrote: > >> From: Hongzhou Yang >> >> Add pinctrl,GPIO and EINT node to mt8135.dtsi. >> >> Signed-off-by: Hongzhou Yang > > Acked-by: Linus Walleij merged to v4.0-next/dts > > The pinctrl driver

Re: [PATCH 1/4] PM / Wakeirq: Add minimal device wakeirq helper functions

On Fri, Mar 6, 2015 at 3:02 AM, Rafael J. Wysocki wrote: > Please always CC linux-pm on CC patches. Doh. That was supposed to say "Please always CC linux-pm on PM patches". I really should not reply to email when I'm too tired ... -- To unsubscribe from this list: send the line "unsubscribe

[RFC PATCH] ARM: l2c: Fix prefect settings of parsing

Allow prefect settings overriding by of tree, in case l2x0_cache_size_of_parse() returns value, prefect tuning properties are silently ignored. E.g. arm,double-linefill* and arm,prefetch*. This happens for example, when "cache-size" or "cache-sets" properties haven't been filled in l2c dt node.

Re: [PATCH v2 5/6] watchdog: at91sam9: request the irq with IRQF_NO_SUSPEND

On Fri, Mar 6, 2015 at 12:06 PM, Mark Rutland wrote: > [...] > >> > The request_irq path never results in a call to chip->irq_set_wake(), >> > even with the IRQF_NO_SUSPEND flag. So requesting an irq with >> > IRQF_NO_SUSPEND does not guarantee wakeup; it only guarantees that the >> > CPU can

Re: [PATCH v9 07/21] ACPI / sleep: Introduce arm64 specific acpi_sleep.c

On Thu, Mar 05, 2015 at 12:16:29AM +, Rafael J. Wysocki wrote: > On Thursday, March 05, 2015 12:25:54 AM Rafael J. Wysocki wrote: > > On Wednesday, March 04, 2015 10:49:25 PM G Gregory wrote: > > > On 4 March 2015 at 22:38, Rafael J. Wysocki wrote: > > > > On Wednesday, February 25, 2015

Re: [PATCH 2/3] locking: ww_mutex: Allow to use rt_mutex instead of mutex for the baselock

On 03/06/2015 01:16 PM, Maarten Lankhorst wrote: >> Okay so what I the point made here? It is only about the config option, >> right? What are the preferences here: >> [ ] yes, the way it is now > Is my personal preference, but I'm not a locking expert(TM). Lets see what Mike says. I currently

[PATCH v3] xen-scsiback: define a pr_fmt macro with xen-pvscsi

Add the {xen-pvscsi: } prefix in pr_fmt and remove DPRINTK, then replace all DPRINTK with pr_debug. Also fixed up some comments just as eliminate redundant whitespace and format the code. These will make the code easier to read. Signed-off-by: Tao Chen --- drivers/xen/xen-scsiback.c | 72

Re: [PATCH] xen: avoid NULL pointer dereference in dom0 on large machines

Ping? On 02/26/2015 06:52 AM, Juergen Gross wrote: Using the pvops kernel a NULL pointer dereference was detected on a large machine (144 processors) when booting as dom0 in evtchn_fifo_unmask() during assignment of a pirq. The event channel in question was the first to need a new entry in

Re: sched: softlockups in multi_cpu_stop

* Sasha Levin wrote: > I've bisected this to "locking/rwsem: Check for active lock before bailing on > spinning". Relevant parties Cc'ed. That would be: 1a99367023f6 ("locking/rwsem: Check for active lock before bailing on spinning") attached below. Thanks, Ingo

Re: [PATCH 04/15] MIPS: Add sched_clock support

On Wed, 4 Mar 2015, Deng-Cheng Zhu wrote: > This will provide sched_clock interface to implement individual > read_sched_clock(). Not for CAVIUM_OCTEON_SOC as it defines its own > sched_clock() directly (not using the sched_clock_register interface). > > Signed-off-by: Deng-Cheng Zhu > --- >

[PATCH] zram: do not let user enforce new device dev_id

This patch forbids user to enforce device ids for newly added zram devices, as suggested by Minchan Kim. There seems to be a little interest in this functionality and its use-cases are rather non-obvious. zram_add sysfs attr, thus, is now read only and has only automatic device id assignment

RE: Re: [PATCH v2 3/3] efi: Capsule update with user helper interface

> -Original Message- > From: Andy Lutomirski [mailto:l...@amacapital.net] > Sent: Friday, March 06, 2015 7:09 AM > > On Mar 5, 2015 1:19 AM, "Kweh, Hock Leong" > wrote: > > > > > > This really is not a big deal. User should cope with it. > > > > > > No, it's a big deal, and the user

Re: [PATCHv4 00/24] THP refcounting redesign

On Thu, Mar 05, 2015 at 01:55:15PM +0100, Jerome Marchand wrote: > On 03/04/2015 05:32 PM, Kirill A. Shutemov wrote: > > Hello everybody, > > > > It's bug-fix update of my thp refcounting work. > > > > The goal of patchset is to make refcounting on THP pages cheaper with > > simpler semantics

Re: [PATCH 3.14.25-rt22 1/2] rtmutex Real-Time Linux: Fixing kernel BUG at kernel/locking/rtmutex.c:997!

* Steven Rostedt | 2015-02-26 09:06:10 [-0500]: >If we can pull that off and remove all rtmutex trylocks from hardirq >context, I would much rather do that. > >This hocus pocus coding is just going to lead us down the path of the >black arts. I already have a black cat, so I'm good to go. Okay.

Re: [PATCH v5 1/9] arm64: dts: exynos: Add dts files for 64-bit Exynos5433 SoC

Hi, On 03/06/2015 08:40 PM, Mark Rutland wrote: >> CPU0 (boot CPU) is only well working for CPU_OFF. >> But when I try to turn on the CPU0 after CPU_OFF, I failed it. > > That's rather worrying. Can you look into what's going on here? I'd > rather not have dts describing

Re: [PATCH 2/3] locking: ww_mutex: Allow to use rt_mutex instead of mutex for the baselock

On 06-03-15 13:14, Sebastian Andrzej Siewior wrote: > On 03/02/2015 09:46 AM, Maarten Lankhorst wrote: >> Hey, >> >> Op 02-03-15 om 04:20 schreef Mike Galbraith: >>> On Fri, 2015-02-27 at 17:57 +0100, Sebastian Andrzej Siewior wrote: This patch makes it possible to replace the base mutex by

Re: [PATCH 0/8 v4] ARM OMAP2+ GPMC: fixes and bus children

On 06/03/15 02:58, Tony Lindgren wrote: > * Robert ABEL [150227 08:00]: >> These are the changes I proposed in these patch series: [1], [2], [3], [4] >> rebased to 3.19 as well as new changes for little bugs I noticed while >> preparing this patch series as well as changes introduced via

[GIT PULL] please pull file-locking related change for v4.0 (#3)

Hi Linus, The following changes since commit 6587457b4b3d663b237a0f95ddf6e67d1828c8ea: Merge tag 'dma-buf-for-4.0-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/sumits/dma-buf (2015-03-04 09:59:51 -0800) are available in the git repository at: git://git.samba.org/jlayton/linux.git

Re: [PATCH 2/3] locking: ww_mutex: Allow to use rt_mutex instead of mutex for the baselock

On 03/02/2015 09:46 AM, Maarten Lankhorst wrote: > Hey, > > Op 02-03-15 om 04:20 schreef Mike Galbraith: >> On Fri, 2015-02-27 at 17:57 +0100, Sebastian Andrzej Siewior wrote: >>> This patch makes it possible to replace the base mutex by a rt_mutex. In >>> general one would not do this. >> I

Re: [PATCH] drivers: scsi: Remove null check on sdkp

> "Tapasweni" == Tapasweni Pathak writes: Tapasweni> Remove null check on sdkp as it won't be null at this line. Thanks for the heads up. It's actually a merge snafu. The check is supposed to be if (!sdkp->ATO). I already have a patch in my queue to fix this. -- Martin K. Petersen

Re: [PATCH] mfd: kempld-core: Fix callback return value check

On Thu, 26 Feb 2015, Ameya Palande wrote: > On success, callback function returns 0. So invert the if condition > check so that we can break out of loop. > > Cc: sta...@vger.kernel.org > Signed-off-by: Ameya Palande <2am...@gmail.com> > --- > drivers/mfd/kempld-core.c | 2 +- > 1 file changed,

Re: [PATCH] mfd: rk808: disable the under voltage detect

On Sat, 28 Feb 2015, Chris Zhong wrote: > Rk808 has a under voltage detect function, when the voltage of buck is > under 85% the target voltage, the buck output will reset. But if the > power load is too heavy, this function maybe err, when current over > 4.2A, although the voltage is normal, but

Re: perf probe: can't find unnamed union members

Hi, (2015/03/06 0:32), Arnaldo Carvalho de Melo wrote: > > Hi Masami, > > [root@zoo ~]# perf probe -x ~/bin/perf -L lock__delete > > 0 static void lock__delete(struct ins_operands *ops) > 1 { > 2 struct ins *ins = ops->locked.ins; > > 4 if

Re: [PATCH v4] pinctrl: exynos: Add support for Exynos5433

On Tue, Feb 24, 2015 at 3:47 AM, Chanwoo Choi wrote: > This patch adds driver data for Exynos5433 SoC. Exynos5433 includes 228 multi- > functional input/output port pins and 135 memory port pins. There are 41 > general > port groups and 2 memory port groups. > > Cc: Tomasz Figa > Cc: Thomas

Re: [PATCH 2/2] pinctrl: Add Pistachio SoC pin control driver

On Tue, Feb 24, 2015 at 3:15 AM, Andrew Bresticker wrote: > Add a driver for the pin controller present on the IMG Pistachio SoC. > This driver provides pinmux and pinconfig operations as well as GPIO > and IRQ chips for the GPIO banks. > > Signed-off-by: Damien Horsley > Signed-off-by:

Re: [PATCH v3 0/2] Add support for Broadcom RNG200

On Wed, Mar 04, 2015 at 12:42:12PM -0800, Scott Branden wrote: > This series of patchsets contains the Broadcom Random Number Generator > driver and device tree binding documentation. > > Changes from v2: > added usleep_range instead of cpu_relax > add init and cleanup functions following new

Re: [PATCH v3 1/1] staging: fsl-mc: fsl-mc object allocator driver

On 06.03.15 02:35, J. German Rivera wrote: > The fsl-mc object allocator driver manages "allocatable" fsl-mc > objects such as DPBPs, DPMCPs and DPCONs. It provides services to > other fsl-mc drivers to allocate/deallocate these types of objects. > > Signed-off-by: J. German Rivera >

Re: [PATCH v9 0/3] staging: fsl-mc: Freescale Management Complex bus driver patch series

On 06.03.15 02:29, J. German Rivera wrote: > This patch series introduces Linux support for the Freescale > Management Complex (fsl-mc) hardware. This patch series is dependent > on the patch series "ARM64: Add support for FSL's LS2085A SoC" >

Re: [PATCH v3 0/1] drivers/bus: fsl-mc object allocator driver

On 06.03.15 02:35, J. German Rivera wrote: > This patch series introduces the object allocator driver for the > Freescale Management Complex (fsl-mc) of QorIQ Ls2 SoCs This patch > series is dependent on the patch series drivers/bus: "Freescale > Management Complex bus driver patch series

[PATCHv4] x86, fpu: remove the logic of non-eager fpu mem allocation at the first usage

On 05/03/15 22:08, H. Peter Anvin wrote: > On 06/23/2014 06:08 AM, Konrad Rzeszutek Wilk wrote: >> On Wed, Mar 19, 2014 at 08:02:22AM -0700, H. Peter Anvin wrote: >>> On 03/19/2014 06:21 AM, Konrad Rzeszutek Wilk wrote: > > The following patch does the always eager allocation. It's a

Re: [PATCH] spi: fsl-spi: use of_iomap() to map parameter ram on CPM1

On Wed, Mar 04, 2015 at 09:00:39AM +0100, leroy christophe wrote: > Le 03/03/2015 19:44, Mark Brown a écrit : > >Why are we using of_iomap() rather than a generic I/O mapping function > >here? > because all drivers for powerpc seems to be using of_iomap(), as on powerpc > the HW is described by

RE: Re: [PATCH v2 3/3] efi: Capsule update with user helper interface

> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Friday, March 06, 2015 4:14 PM > > On Thu, Mar 05, 2015 at 03:08:42PM -0800, Andy Lutomirski wrote: > > No. Only root should be able to load capsules, but even root may not > > be able to write to /lib. > > So

Re: [PATCH v5 1/9] arm64: dts: exynos: Add dts files for 64-bit Exynos5433 SoC

> CPU0 (boot CPU) is only well working for CPU_OFF. > But when I try to turn on the CPU0 after CPU_OFF, I failed it. > >>> > >>> That's rather worrying. Can you look into what's going on here? I'd > >>> rather not have dts describing things which are known to be broken. > >> > >> The

Re: [PATCH v5 4/6] arm64: kprobes instruction simulation support

On 17 February 2015 at 23:11, David Long wrote: > From: Sandeepa Prabhu > > Kprobes needs simulation of instructions that cannot be stepped > from different memory location, e.g.: those instructions > that uses PC-relative addressing. In simulation, the behaviour > of the instruction is

Re: [PATCH 1/2] pinctrl: Add Pistachio SoC pin control binding document

On Tue, Feb 24, 2015 at 3:15 AM, Andrew Bresticker wrote: > Add a device-tree binding document for the pin controller present > on the IMG Pistachio SoC. > > Signed-off-by: Damien Horsley > Signed-off-by: Andrew Bresticker (...) > +Note that the GPIO bank sub-nodes *must* be listed in order.

Re: Re: Re: [PATCH 2/2] livepatch: fix patched module loading race

(2015/03/06 19:51), Petr Mladek wrote: > On Fri 2015-03-06 10:24:27, Masami Hiramatsu wrote: >> (2015/03/05 23:18), Josh Poimboeuf wrote: >>> On Thu, Mar 05, 2015 at 09:52:41AM +0900, Masami Hiramatsu wrote: (2015/03/04 22:17), Petr Mladek wrote: > On Tue 2015-03-03 17:02:22, Josh

Re: [PATCH 1/5] soc: mediatek: Add SMI driver

On Fri, 2015-03-06 at 18:48 +0800, yong...@mediatek.com wrote: > --- a/drivers/soc/mediatek/Kconfig > +++ b/drivers/soc/mediatek/Kconfig > @@ -20,3 +20,10 @@ config MT8173_PMIC_WRAP > PMIC wrapper is a proprietary hardware in MT8173 to make > communication protocols to access PMIC

Re: [PATCH 0/2] pinctrl: Support for IMG Pistachio

On Tue, Feb 24, 2015 at 3:15 AM, Andrew Bresticker wrote: > I'd like this to go through the MIPS tree with > Linus'/Alex's ACKs if possible. Why? It will only help creating merge conflicts. There seem to be no compile-related dependencies, just Kconfig symbols, so patches using this can go in

Re: sched: softlockups in multi_cpu_stop

I've bisected this to "locking/rwsem: Check for active lock before bailing on spinning". Relevant parties Cc'ed. Thanks, Sasha On 03/02/2015 02:45 AM, Sasha Levin wrote: > Hi all, > > I'm seeing the following lockup pretty often while fuzzing with trinity: > > [ 880.960250] NMI watchdog:

[PATCH 3.16.y-ckt 014/183] HID: fixup the conflicting keyboard mappings quirk

3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me know. -- From: Jiri Kosina commit 8e7b341037db1835ee6eea64663013cbfcf33575 upstream. The ignore check that got added in 6ce901eb61 ("HID: input: fix confusion on conflicting mappings") needs to

[PATCH 3.16.y-ckt 009/183] ARM: pxa: add regulator_has_full_constraints to corgi board file

3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Eremin-Solenikov commit 271e80176aae4e5b481f4bb92df9768c6075bbca upstream. Add regulator_has_full_constraints() call to corgi board file to let regulator core know that we do

Re: [PATCH 3/3] net: macb: remove #if defined(CONFIG_ARCH_AT91) sections

On Thu, 5 Mar 2015 20:44:18 +0100 Alexandre Belloni wrote: > On 05/03/2015 at 17:27:22 +0100, Boris Brezillon wrote : > > @@ -2388,21 +2392,20 @@ static int macb_probe(struct platform_device *pdev) > > bp->phy_interface = err; > > } > > > > + config = 0; > > if

[PATCH 3.16.y-ckt 013/183] HID: input: fix confusion on conflicting mappings

3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me know. -- From: David Herrmann commit 6ce901eb61aa30ba8565c62049ee80c90728ef14 upstream. On an PC-101/103/104 keyboard (American layout) the 'Enter' key and its neighbours look like this:

[PATCH 3.16.y-ckt 015/183] ARM: dts: tegra20: fix GR3D, DSI unit and reg base addresses

3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Osipenko commit de47699d005996b41cea590c6098078ac12058be upstream. Commit 58ecb23f64ee ("ARM: tegra: add missing unit addresses to DT") added unit address and changed reg base

[PATCH 3.16.y-ckt 018/183] usb: core: buffer: smallest buffer should start at ARCH_DMA_MINALIGN

3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 5efd2ea8c9f4f12916ffc8ba636792ce052f6911 upstream. the following error pops up during "testusb -a -t 10" | musb-hdrc musb-hdrc.1.auto: dma_pool_free

[PATCH 3.16.y-ckt 011/183] ARM: pxa: add regulator_has_full_constraints to spitz board file

3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Eremin-Solenikov commit baad2dc49c5d970ea881d92981a1b76c94a7b7a1 upstream. Add regulator_has_full_constraints() call to spitz board file to let regulator core know that we do

[PATCH 3.16.y-ckt 016/183] megaraid_sas: disable interrupt_mask before enabling hardware interrupts

3.16.7-ckt8 -stable review patch. If anyone has any objections, please let me know. -- From: "sumit.sax...@avagotech.com" commit c2ced1719a1b903350955a511e1666e6d05a7f5b upstream. Update driver "mask_interrupts" before enable/disable hardware interrupt in order to avoid

Re: [PATCH 3/4] pinctrl: baytrail: Rework interrupt handling

On Mon, Feb 23, 2015 at 1:53 PM, Mika Westerberg wrote: > Instead of handling everything in the driver's first level interrupt > handler, we can take advantage of already existing flow handlers that are > provided by the IRQ core. > > This changes the functionality a bit also. Previously the

Re: [PATCH 4/5] dt-bindings: iommu: Add binding for mediatek IOMMU

On Fri, Mar 06, 2015 at 10:48:19AM +, yong...@mediatek.com wrote: > From: Yong Wu > > This patch add mediatek iommu dts binding document. > > Signed-off-by: Yong Wu > --- > .../devicetree/bindings/iommu/mediatek,iommu.txt | 41 > ++ > 1 file changed, 41

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