On Wed, 19 Feb 2014, Michal Hocko wrote:
I strongly suspect that the patch is correct since powerpc node distances
are different than the architectures you're talking about and get doubled
for every NUMA domain that the hardware supports.
Even if the units of the distance is different
Hello,
On 2014-02-18 17:56, Grant Likely wrote:
On Tue, 18 Feb 2014 14:37:57 +0100, Marek Szyprowski m.szyprow...@samsung.com
wrote:
This patch adds device tree support for contiguous and reserved memory
regions defined in device tree.
Large memory blocks can be reliably reserved only
Subject: [PATCHv9 1/4] pwm: Add Freescale FTM PWM driver support
The FTM PWM device can be found on Vybrid VF610 Tower and Layerscape LS-1
SoCs.
Signed-off-by: Xiubo Li li.xi...@freescale.com
---
For this patch series,
Reviewed-by: Yuan Yao yao.y...@freescale.com
Thanks.
Hi
On Tue 18-02-14 15:34:05, Nishanth Aravamudan wrote:
Hi Michal,
On 18.02.2014 [10:06:58 +0100], Michal Hocko wrote:
Hi,
I have just noticed that ppc has RECLAIM_DISTANCE reduced to 10 set by
56608209d34b (powerpc/numa: Set a smaller value for RECLAIM_DISTANCE to
enable zone reclaim).
Hi Hannes,
Sorry to bother you.
Months ago, you made a patch to fix this scsi_scan abort error found on
zfssa storage. Though it's only a specific storage, the logic -- not
abort scsi scan process because of an inquiry failure of a LU in the
middle, is helpful as a way to make our scanning more
Fixes below build error:
FATAL: drivers/regulator/tps65218-regulator: struct of_device_id is not
terminated with a NULL entry!
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/tps65218-regulator.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Current code uses devm_regulator_register() so the we don't need to explicitly
call regulator_unregister() in .remove.
And then we don't need to save rdev pointer to tps-rdev[id].
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/tps65218-regulator.c | 18 --
1
We currently include linux/irqreturn.h in linux/pci.h, but I'm about to
remove that from linux/pci.h, so add explicit includes where needed.
Signed-off-by: Bjorn Helgaas bhelg...@google.com
---
drivers/misc/mei/hw-me.h |1 +
1 file changed, 1 insertion(+)
diff --git
Cc: Tejun Heo t...@kernel.org
Cc: linux-...@vger.kernel.org
Signed-off-by: Lee Jones lee.jo...@linaro.org
Please consider basing it on top of Hans' refactored ahci_platform.
http://www.spinics.net/lists/linux-ide/msg47628.html
Okay, looks reasonable. I'm happy to do the extra work.
On Tue 18-02-14 17:43:38, David Rientjes wrote:
On Tue, 18 Feb 2014, Nishanth Aravamudan wrote:
How about the following?
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 5de4337..1a0eced 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -1854,7 +1854,8 @@ static void
Fixes below build error:
FATAL: drivers/regulator/tps65218-regulator: struct of_device_id is not
terminated with a NULL entry!
Signed-off-by: Axel Lin axel@ingics.com
---
I'm sorry that I just found I CC wrong developers in my previous mail.
So here is a resend.
Current code uses devm_regulator_register() so the we don't need to explicitly
call regulator_unregister() in .remove.
And then we don't need to save rdev pointer to tps-rdev[id].
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/tps65218-regulator.c | 18 --
1
This is a DT-only driver, so make it depend on OF and remove of_match_ptr in
the code.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/regulator/Kconfig | 2 +-
drivers/regulator/tps65218-regulator.c | 14 ++
2 files changed, 7 insertions(+), 9 deletions(-)
On Wednesday 19 February 2014 02:03 PM, Axel Lin wrote:
Fixes below build error:
FATAL: drivers/regulator/tps65218-regulator: struct of_device_id is not
terminated with a NULL entry!
Signed-off-by: Axel Lin axel@ingics.com
---
I'm sorry that I just found I CC wrong developers in my
On Wednesday 19 February 2014 02:04 PM, Axel Lin wrote:
Current code uses devm_regulator_register() so the we don't need to explicitly
call regulator_unregister() in .remove.
And then we don't need to save rdev pointer to tps-rdev[id].
Acked-by: Keerthy j-keer...@ti.com
Signed-off-by: Axel
On 19/02/2014 03:07, Bo Shen :
In sama5d3 SoC, there are 16 endpoints, which is different with
earlier SoCs (only have 7 endpoints). The USBA_NR_ENDPOINTS micro
you should read macro.
is not suitable for sama5d3. So, get the endpoints number through
the udc-num_ep, which get from platform
On Tue, Feb 18, 2014 at 03:11:59PM -0800, Dave Hansen wrote:
I noticed that perf's dTLB-load-misses even t isn't working on my
Ivybridge system:
Performance counter stats for 'system wide':
0 dTLB-load-misses
On 19/02/2014 03:07, Bo Shen :
The SoCs earlier than sama5d3, they have the same number endpoints
and DMA channels. In driver code, they use the same definition
USBA_NR_ENDPOINTS for both endpoints and dma channels. However,
in sama5d3, it has different number for endpoints and DMA channels.
On Tue, Feb 18, 2014 at 09:50:12PM -0500, Steven Rostedt wrote:
Rationale for this odd behavior is that, when a task is throttled, it
is removed only from the dl_rq, but we keep it on_rq (as this is not
a full dequeue, that is the task is not actually sleeping). But, it
is also true
Add audio card DT node support for Vybird-TWR board.
Xiubo Li (4):
ARM: dts: vf610: Add edma mux Tx and Rx support for SAI node.
ARM: dts: vf610-twr: Enable SAI ALSA SoC DAI device
ARM: dts: vf610-twr: Enable SGTL5000 codec.
ARM: dts: vf610-twr: Add simple-card support.
This patch adds the SAI's edma mux Tx and Rx support.
Signed-off-by: Xiubo Li li.xi...@freescale.com
Cc: Shawn Guo shawn@linaro.org
---
arch/arm/boot/dts/vf610.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/vf610.dtsi b/arch/arm/boot/dts/vf610.dtsi
index
This patch adds and enables the SAI device.
Signed-off-by: Xiubo Li li.xi...@freescale.com
Cc: Shawn Guo shawn@linaro.org
---
arch/arm/boot/dts/vf610-twr.dts | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts
This patch adds and enables simple-card support in DT node.
Signed-off-by: Xiubo Li li.xi...@freescale.com
Cc: Shawn Guo shawn@linaro.org
---
arch/arm/boot/dts/vf610-twr.dts | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts
This patch adds and enables SGTL5000 codec support.
Signed-off-by: Xiubo Li li.xi...@freescale.com
Cc: Shawn Guo shawn@linaro.org
---
arch/arm/boot/dts/vf610-twr.dts | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts
On Tue, Feb 18, 2014 at 07:42:20PM -0500, Waiman Long wrote:
On 02/18/2014 04:28 PM, Peter Zijlstra wrote:
On Tue, Feb 18, 2014 at 02:30:12PM -0500, Waiman Long wrote:
I will start looking at how to make it work with paravirt. Hopefully, it
won't take too long.
The cheap way out is to simply
On Tue, Feb 18, 2014 at 07:50:13PM -0500, Waiman Long wrote:
On 02/18/2014 04:34 PM, Peter Zijlstra wrote:
On Tue, Feb 18, 2014 at 02:39:31PM -0500, Waiman Long wrote:
The #ifdef is harder to take away here. The point is that doing a 32-bit
exchange may accidentally steal the lock with the
On 19.02.2014 08:06, Yuan Pengfei wrote:
From: Yuan Pengfei cool...@qq.com
If -fprofile-values option is used, ctr-num and sci_ptr-num
may be zero, resulting in zero size and cv_size, which will
cause ENOMEM when opening gcov data files in debugfs.
Signed-off-by: Yuan Pengfei cool...@qq.com
On 02/18/2014 10:32 PM, Bjorn Helgaas wrote:
[+cc Arnd]
On Sun, Feb 16, 2014 at 8:33 AM, Srikanth Thokala stho...@xilinx.com wrote:
This is the driver for Xilinx AXI PCIe Host Bridge Soft IP
Signed-off-by: Srikanth Thokala stho...@xilinx.com
---
- Rebased on v3.14.0-rc2
---
On Tue, Feb 18, 2014 at 07:58:49PM -0500, Waiman Long wrote:
On 02/18/2014 04:37 PM, Peter Zijlstra wrote:
On Tue, Feb 18, 2014 at 02:39:31PM -0500, Waiman Long wrote:
+ /*
+ * At the head of the wait queue now
+ */
+ while (true) {
+ u32 qcode;
+ int retval;
+
+
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Jens Axboe ax...@kernel.dk
Cc: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Cc: linux-...@vger.kernel.org
---
drivers/block/skd_main.c |3 +--
1 files changed, 1 insertions(+), 2
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Mike Miller mike.mil...@hp.com
Cc: iss_storage...@hp.com
Cc: linux-...@vger.kernel.org
---
drivers/block/cciss.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Cc: Jens Axboe ax...@kernel.dk
Cc: Mike Miller
When enabling MSI-X, interrupts are requested for SKD_MAX_MSIX_COUNT
entries in skdev-msix_entries array, while the number of actually
allocated entries is skdev-msix_count. This might lead to an out of
boundary access in case number of allocated entries is less than
SKD_MAX_MSIX_COUNT. This
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
When enabling MSI-X interrupts fails due to lack of memory
the call to pci_disable_msix() is missed and the device is
left with MSI-X interrupts enabled while the driver assumes
otherwise. This update fixes the described misbehaviour and
cleans up the code of skd_release_msix() function.
There is no need to call pci_disable_msi() in case
the previous call to pci_enable_msi() failed
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Jens Axboe ax...@kernel.dk
Cc: Asai Thambi S P asamymuth...@micron.com
Cc: linux-...@vger.kernel.org
---
drivers/block/mtip32xx/mtip32xx.c |
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
On 02/19/2014 03:33 PM, Matthew Garrett wrote:
On Wed, Feb 19, 2014 at 03:31:29PM +0800, Aaron Lu wrote:
DID2 is in system memory region and has some assigned value like 0x400
when we read it. For this case it is easy since there is only one output
device that is of type LVDS so we can match
On Tue, Feb 18, 2014 at 05:12:43PM -0500, r...@redhat.com wrote:
The NUMA scanning code can end up iterating over many gigabytes
of unpopulated memory, especially in the case of a freshly started
KVM guest with lots of memory.
This results in the mmu notifier code being called even when
On Wed, Feb 19, 2014 at 01:20:30PM +0800, Lei Wen wrote:
Since cpu which is put into quiescent mode, would remove itself
from kernel's sched_domain. So we could use search sched_domain
method to check whether this cpu don't want to be disturbed as
idle load balance would send IPI to it.
This patch add the time support for 32 bit a VDSO to a 32 bit kernel.
For 32 bit programs running on a 32 bit kernel, the same mechanism is
used as for 64 bit programs running on a 64 bit kernel.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
arch/x86/include/asm/vdso.h | 3
There a currently more than 30 users of the gtod macro, so replace the
last VVAR(vsyscall_gtod_data) by gtod macro.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
arch/x86/vdso/vclock_gettime.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fast and a reliable way,
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c to make the functionality
available for x86 32 bit kernel.
It also adds a new vsyscall_32.c which setup the VVAR page.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
The _install_special_mapping() is the new base function for
install_special_mapping(). This function will return a pointer of the
created VMA or a error code in an ERR_PTR()
This new function will be needed by the for the vdso 32 bit support to map the
additonal vvar and hpet pages into the 32
On Tue, 2014-02-18 at 23:29 +0100, Rafael J. Wysocki wrote:
On Tuesday, February 18, 2014 10:52:54 AM Yinghai Lu wrote:
On Tue, Feb 18, 2014 at 2:08 AM, Steven Newbury st...@snewbury.org.uk
wrote:
There's no pci bridge/bus hotplug though. Docking doesn't reveal the
pci-e-pci
This patch do a little cleanup for the __vdso_gettimeofday() function.
It kick out an unneeded ret local variable and makes the code faster if
only the timezone is needed.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
arch/x86/vdso/vclock_gettime.c | 7 ++-
1 file changed, 2
This patch is a small code cleanup for the __vdso_clock_gettime() function.
It removes the unneeded return values from do_monotonic_coarse() and
do_realtime_coarse() and add a fallback label for doing the kernel
gettimeofday() system call.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
This patch add the VDSO time support for the IA32 Emulation Layer.
Due the nature of the kernel headers and the LP64 compiler where the
size of a long and a pointer differs against a 32 bit compiler, there
is some type hacking necessary for optimal performance.
The vsyscall_gtod_data struture
This patch revamp the vvar.h for introduce the VVAR macro for vdso32.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
arch/x86/include/asm/vvar.h | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/vvar.h b/arch/x86/include/asm/vvar.h
This intermediate patch revamps the vclock_gettime.c by moving some functions
around. It is only for spliting purpose, to make whole the 32 bit vdso timer
patch easier to review.
Signed-off-by: Stefani Seibold stef...@seibold.net
---
arch/x86/vdso/vclock_gettime.c | 85
On Wed 19-02-14 00:20:21, David Rientjes wrote:
On Wed, 19 Feb 2014, Michal Hocko wrote:
I strongly suspect that the patch is correct since powerpc node distances
are different than the architectures you're talking about and get doubled
for every NUMA domain that the hardware
On 02/16/2014 03:59 PM, Daniel Borkmann wrote:
From: Vlastimil Babka vba...@suse.cz
[ 4366.519657] [ cut here ]
[ 4366.519709] kernel BUG at mm/mlock.c:528!
[ 4366.519742] invalid opcode: [#1] SMP
[ 4366.519782] Modules linked in: ccm arc4 iwldvm [...]
[
On Tue 18-02-14 17:55:48, Tejun Heo wrote:
Hello,
On Fri, Feb 14, 2014 at 08:12:17PM -0800, Derek Basehore wrote:
bdi_wakeup_thread_delayed used the mod_delayed_work function to schedule
work
to writeback dirty inodes. The problem with this is that it can delay work
that
is
Subject: RE: [PATCHv9 1/4] pwm: Add Freescale FTM PWM driver support
Subject: [PATCHv9 1/4] pwm: Add Freescale FTM PWM driver support
The FTM PWM device can be found on Vybrid VF610 Tower and Layerscape LS-1
SoCs.
Signed-off-by: Xiubo Li li.xi...@freescale.com
---
For this
At the end of the recovery procedure, write_checkpoint is called and updates
the cp count which is managed by f2fs stat.
But, previously build_stat() is called after the recovery procedure, which
results in:
BUG: unable to handle kernel NULL pointer dereference at 012c
IP:
On Tue, 2014-02-18 at 14:06 -0800, Andrew Morton wrote:
On Mon, 17 Feb 2014 14:20:47 +0200 Sougata Santra soug...@tuxera.com wrote:
Concurrent access to alloc_blocks in hfsplus_inode_info is
protected by extents_lock mutex. This patch fixes two
instances where alloc_blocks modification
Hello Josh,
On Tue, Feb 18, 2014 at 05:02:10PM -0600, Josh Cartwright wrote:
Hello Johannes,
On Tue, Feb 18, 2014 at 04:34:12PM +0100, Johannes Thumshirn wrote:
[..]
+++ b/drivers/mcb/mcb-core.c
@@ -0,0 +1,420 @@
+/*
+ * MEN Chameleon Bus.
+ *
+ * Copyright (C) 2013 MEN
On 2014/2/19 15:49, David Rientjes wrote:
On Wed, 19 Feb 2014, Xishi Qiu wrote:
Hi all,
CONFIG_KMEMCHECK=y and set command-line kmemcheck=1, I find OS
boot failed. The kernel is v3.14.0-rc3
If set kmemcheck=1 nowatchdog, OS will boot successfully.
I have automated kernel boots that
On Tue, Feb 04, 2014 at 04:58:42PM +0100, Ulf Hansson wrote:
Convert to the SET_PM_RUNTIME_PM macro while defining the runtime PM
callbacks. This means the callbacks becomes available for both
CONFIG_PM_SLEEP and CONFIG_PM_RUNTIME, which is needed by drivers and
power domains.
This patch is
This adds devicetree node for VF610, and there are 8 channels
supported.
Signed-off-by: Xiubo Li li.xi...@freescale.com
Reviewed-by: Sascha Hauer s.ha...@pengutronix.de
Reviewed-by: Yuan Yao yao.y...@freescale.com
---
arch/arm/boot/dts/vf610.dtsi | 13 +
1 file changed, 13
Resend this patch series, just adding the missing and new Reviewed-by and
Acked-by infomation of this patch series.
Xiubo Li (4):
pwm: Add Freescale FTM PWM driver support
ARM: dts: vf610: Add Freescale FTM PWM node.
ARM: dts: vf610-twr: Enables FTM PWM device.
Documentation: Add device
Signed-off-by: Xiubo Li li.xi...@freescale.com
Reviewed-by: Sascha Hauer s.ha...@pengutronix.de
Reviewed-by: Yuan Yao yao.y...@freescale.com
---
arch/arm/boot/dts/vf610-twr.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts
The FTM PWM device can be found on Vybrid VF610 Tower and
Layerscape LS-1 SoCs.
Signed-off-by: Xiubo Li li.xi...@freescale.com
Signed-off-by: Alison Wang b18...@freescale.com
Signed-off-by: Jingchang Lu b35...@freescale.com
Reviewed-by: Sascha Hauer s.ha...@pengutronix.de
Reviewed-by: Yuan Yao
This adds the binding documentation for Freescale FlexTimer Module
(FTM) PWM driver under Documentation/devicetree/bindings/pwm/.
Signed-off-by: Xiubo Li li.xi...@freescale.com
Reviewed-by: Sascha Hauer s.ha...@pengutronix.de
Reviewed-by: Yuan Yao yao.y...@freescale.com
Acked-by: Kumar Gala
On Tue, 2014-02-18 at 23:48 +, Peter Sewell wrote:
On 18 February 2014 20:43, Torvald Riegel trie...@redhat.com wrote:
On Tue, 2014-02-18 at 12:12 +, Peter Sewell wrote:
Several of you have said that the standard and compiler should not
permit speculative writes of atomics, or
On Tue, Feb 18, 2014 at 05:20:17PM -0600, Josh Cartwright wrote:
On Tue, Feb 18, 2014 at 04:34:13PM +0100, Johannes Thumshirn wrote:
Add support for MCB over PCI devices. Both PCI attached on-board Chameleon
FPGAs
as well as CompactPCI based MCB carrier cards are supported with this
Hello everyone,
I am trying to determine what fraction of the whole system's user and
sys time are consumed by a specific process, over a period of time.
Hence, I read the respective tick counts from the first lines
of /proc/stat and /proc/pid/stat at the start and end of that period
and compute
On Tue, 2014-02-18 at 12:16 -0800, Luis R. Rodriguez wrote:
On Mon, Feb 17, 2014 at 6:36 AM, Zoltan Kiss zoltan.k...@citrix.com wrote:
Also, the backend is not necessarily Dom0, you can connect two guests with
backend/frontend pairs.
Can you elaborate a bit more on this type of setup?
The
Hi Maarten,
Forgot to refresh my working tree. Please help to
apply this patch on top of previous one to solve a compilation bug.
diff --git a/drivers/gpu/drm/nouveau/nouveau_acpi.c
b/drivers/gpu/drm/nouveau/no
index c6c7d0d..83face3 100644
--- a/drivers/gpu/drm/nouveau/nouveau_acpi.c
+++
On Tue, 2014-02-18 at 11:43 -0800, Luis R. Rodriguez wrote:
New motivation: removing IPv4 and IPv6 from the backend interfaces can
save up a lot of boiler plate run time code, triggers from ever taking
place, and simplifying the backend interaces. If there is no use for
IPv4 and IPv6
On Fri, 14 Feb 2014, Fernando Lopez-Lezcano wrote:
I could try to boot one of the machines into 3.12.xrtyy, replicate the
conditions and wait. What should I look for if I can catch this in the act?
dmesg and sysrq-t output would be a good start I guess.
Thanks,
tglx
--
To unsubscribe
On Mon, 2014-01-20 at 21:24 +, Zoltan Kiss wrote:
A long known problem of the upstream netback implementation that on the TX
path (from guest to Dom0) it copies the whole packet from guest memory into
Dom0. That simply became a bottleneck with 10Gb NICs, and generally it's a
huge
Hi Hans,
On Tue, Feb 18, 2014 at 09:49:21PM +0100, Hans de Goede wrote:
Hi,
On 02/18/2014 04:37 PM, Maxime Ripard wrote:
snip
+
+ for (i = 0; i data-sg_len; i++) {
+ pdes[i].config = SDXC_IDMAC_DES0_CH | SDXC_IDMAC_DES0_OWN |
+
On Tue, 2014-02-18 at 22:52 +0100, Peter Zijlstra wrote:
4.Some drivers allow user-mode code to mmap() some of their
state. Any changes undertaken by the user-mode code would
be invisible to the compiler.
A good point, but a compiler that doesn't try to (incorrectly)
On Tue, 2014-02-18 at 10:02 +0100, Geert Uytterhoeven wrote:
*** WARNINGS ***
188 regressions:
[...]
+ /scratch/kisskb/src/drivers/target/target_core_alua.c: warning:
'alua_ascq' may be used uninitialized in this function [-Wuninitialized]: =
773:18
This one popped up on my (Fedora
On 02/19/2014 12:06 AM, Andrew Morton wrote:
On Mon, 17 Feb 2014 14:20:47 +0200 Sougata Santra soug...@tuxera.com wrote:
Concurrent access to alloc_blocks in hfsplus_inode_info is
protected by extents_lock mutex. This patch fixes two
instances where alloc_blocks modification was not protected
On Tue, 2014-02-18 at 13:02 -0800, Luis R. Rodriguez wrote:
On Sun, Feb 16, 2014 at 10:57 AM, Stephen Hemminger
step...@networkplumber.org wrote:
On Fri, 14 Feb 2014 18:59:37 -0800
Luis R. Rodriguez mcg...@do-not-panic.com wrote:
From: Luis R. Rodriguez mcg...@suse.com
It doesn't
On Tue, 2014-02-18 at 18:46 +, David Vrabel wrote:
On 18/02/14 17:40, Ian Campbell wrote:
On Mon, 2014-01-20 at 21:24 +, Zoltan Kiss wrote:
@@ -344,8 +346,26 @@ struct xenvif *xenvif_alloc(struct device *parent,
domid_t domid,
vif-pending_prod = MAX_PENDING_REQS;
for
This patch fails to apply to my char-misc-next branch (I've pulled in
3.14-rc3 into this branch now):
checking file drivers/misc/mei/amthif.c
checking file drivers/misc/mei/client.c
Hunk #4 FAILED at 681.
Hunk #5 succeeded at 815 (offset -2 lines).
Hunk #6
On Wed, Feb 19, 2014 at 10:52 AM, Paul Bolle pebo...@tiscali.nl wrote:
- ret = core_alua_state_nonoptimized(cmd, cdb,
- nonop_delay_msecs, alua_ascq);
+ core_alua_state_nonoptimized(cmd, cdb, nonop_delay_msecs);
I suggest making
Hi Jens,
After I posted to pull request, we got a report about a smatch warning,
which was not CCed to you or the lkml.
It is not a bug right now, but a mistake that could easily become a bug
as we move forward. Normally I would keep this in my queue until the next
batch. Just to be prepared in
From: Andreas Gruenbacher agr...@linbit.com
Right now every resource has exactly one connection. But we are preparing
for dynamic connections. I.e. in the future thre can be resources without
connections.
However smatch points this out as 'variable dereferenced before check',
which is correct.
On Sun, Feb 16, 2014 at 04:42:05PM +, Wang YanQing wrote:
Update Documentatin/kmemleak.txt to
reflect the following changes:
Commit b69ec42b1b194cc88f04b3fbcda8d3f93182d6c3
(Kconfig: clean up the long arch list for the DEBUG_KMEMLEAK config option)
make we can't check supported
On Tue, Feb 18, 2014 at 01:48:19PM -0800, Greg Kroah-Hartman wrote:
On Tue, Feb 18, 2014 at 04:34:12PM +0100, Johannes Thumshirn wrote:
The MCB (MEN Chameleon Bus) is a Bus specific to MEN Mikroelektronik
FPGA based devices. It is used to identify MCB based IP-Cores within
an FPGA and
On Tue, 2014-02-18 at 20:36 +, Zoltan Kiss wrote:
On 18/02/14 17:06, Ian Campbell wrote:
On Mon, 2014-01-20 at 21:24 +, Zoltan Kiss wrote:
This patch contains the new definitions necessary for grant mapping.
Is this just adding a bunch of (currently) unused functions? That's a
On Wed, 2014-02-19 at 10:59 +0100, Geert Uytterhoeven wrote:
On Wed, Feb 19, 2014 at 10:52 AM, Paul Bolle pebo...@tiscali.nl wrote:
- ret = core_alua_state_nonoptimized(cmd, cdb,
- nonop_delay_msecs, alua_ascq);
+
On 02/19/2014 03:56 AM, Steven Rostedt wrote:
While debugging the crash with the bad nr_running accounting, I hit
another bug where, after running my sched deadline test, I was getting
failures to take a CPU offline. It was giving me a -EBUSY error.
Adding a bunch of trace_printk()s around,
On Wed, 2014-02-19 at 13:08 +0900, Mark Brown wrote:
On Tue, Feb 18, 2014 at 09:12:09AM +0100, Krzysztof Kozlowski wrote:
On Tue, 2014-02-18 at 09:35 +0900, Mark Brown wrote:
I don't understand the above? Are you saying that suspend mode actually
turns off the regulator or something
op 19-02-14 05:53, Jiang Liu schreef:
On some platforms, ACPI _DSM method (nouveau_op_dsm_muid, function 0)
has special requirements on the fourth parameter, which is different
from ACPI specifications. So revert to the private implementation
to check availability of _DSM functions instead of
On Tue, Feb 18, 2014 at 07:17:04PM +, Jonathan Cameron wrote:
On February 18, 2014 3:34:14 PM GMT+00:00, Johannes Thumshirn
johannes.thumsh...@men.de wrote:
Add support for MEN 16z188 ADC IP Core on MCB FPGAs.
Signed-off-by: Johannes Thumshirn johannes.thumsh...@men.de
Looks pretty
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
This update also cleans up a bit xhci_setup_msi() and
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
The Makefile is designed to use the host toolchain so it may be
unsafe to build the tests if the kernel has been configured and built
for another architecture. This fixes a build problem when the kernel has
been configured and built for the MIPS architecture but the host is
not MIPS
701 - 800 of 1390 matches
Mail list logo
