On 02/07/2014 07:10 AM, Daniel Lezcano wrote:
> The idle_balance modifies the idle_stamp field of the rq, making this
> information to be shared across core.c and fair.c. As we can know if the
> cpu is going to idle or not with the previous patch, let's encapsulate the
> idle_stamp information in
On Wed, Feb 12, 2014 at 08:11:49PM -0800, Linus Torvalds wrote:
> Jakub, any suggestions to how Steven might be able to pinpoint where
> the code generation problem lies?
For a suspected wrong-code where you have no idea where the problem is from
debugging or oops etc., usually the best way is to
On Thu, Feb 13, 2014 at 2:15 AM, Kui Zhang wrote:
> Hello,
>
> When CONFIG_DRM_NOUVEAU=y, I get following error. Blank screen after initrd.
>
> This was in the dmesg.
>
> [0.282559] [drm] hdmi device not found 1 0 1
> [0.282688] nouveau [ DEVICE][:01:00.0] BOOT0 : 0x046800a3
> [
On 02/07/2014 07:10 AM, Daniel Lezcano wrote:
> The scheduler main function 'schedule()' checks if there are no more tasks
> on the runqueue. Then it checks if a task should be pulled in the current
> runqueue in idle_balance() assuming it will go to idle otherwise.
>
> But the idle_balance()
On 02/11/2014 07:11 PM, Daniel Lezcano wrote:
> On 02/10/2014 10:24 AM, Preeti Murthy wrote:
>> HI Daniel,
>>
>> Isn't the only scenario where another cpu can put an idle task on
>> our runqueue,
>
> Well, I am not sure to understand what you meant, but I assume you are
> asking if it is possible
On Tue, Feb 11, 2014 at 3:17 AM, Arend van Spriel wrote:
> The Broadcom bcm43xx sdio devices are fullmac devices that may be
> integrated in ARM platforms. Currently, the brcmfmac driver for
> these devices support use of platform data. This patch specifies
> the bindings that allow this platform
> > The current internal API for TDM is very poor, I don't think we want
> > to expose that 1 to 1 to the devicetree. Since this means we'd have
> > to support that forever. The first thing is that the semantics of
> > snd_soc_dai_set_tdm_slot() are very unclear. E.g. some drivers use a
> > zero
From: zhang jun
>From the following oops log, we find firmware buffer is null, which caused by
>memory alloc failed.
so, we need give a protection and return a error value.
[ 7341.474236] [drm:do_intel_finish_page_flip] *ERROR* invalid or inactive
unpin_work!
[ 7341.494464]
Hi,
On Wed, Feb 12, 2014 at 3:33 AM, David Lanzendörfer
wrote:
> This is based on the driver Allwinner ships in their Android kernel sources.
>
> Initial porting to upstream kernels done by David Lanzendörfer, additional
> fixes and cleanups by Hans de Goede.
>
> It uses dma in bus-master mode
Hi Joe,
On 02/13/2014 01:31 AM, Joe Perches wrote:
> On Wed, 2014-02-12 at 16:55 +0100, Michal Simek wrote:
>> From: Srikanth Thokala
>
> trivia:
>
>> diff --git a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
>> b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
>
>> +
Hello,
When CONFIG_DRM_NOUVEAU=y, I get following error. Blank screen after initrd.
This was in the dmesg.
[0.282559] [drm] hdmi device not found 1 0 1
[0.282688] nouveau [ DEVICE][:01:00.0] BOOT0 : 0x046800a3
[0.282693] nouveau [ DEVICE][:01:00.0] Chipset: G72 (NV46)
On 02/07/2014 07:10 AM, Daniel Lezcano wrote:
> The cpu parameter passed to idle_balance is not needed as it could
> be retrieved from the struct rq.
>
> Cc: alex@linaro.org
> Cc: pet...@infradead.org
> Cc: mi...@kernel.org
> Signed-off-by: Daniel Lezcano
> Signed-off-by: Peter Zijlstra
Set TIF_MEMDIE tsk_thread flag before send kill signal to the
selected thread. This is to fit a usual code sequence and avoid
potential race issue.
Signed-off-by: Weijie Yang
---
drivers/staging/android/lowmemorykiller.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
mode change
Add missing header to fix compilation error.
drivers/net/ethernet/xilinx/xilinx_axienet_main.c:1575:22:
error: undefined identifier 'irq_of_parse_and_map'
drivers/net/ethernet/xilinx/xilinx_axienet_main.c:1576:22:
error: undefined identifier 'irq_of_parse_and_map'
Signed-off-by: Michal Simek
Warning log:
xilinx_axienet_main.c: In function 'axienet_start_xmit_done':
xilinx_axienet_main.c:617:16: warning: operation on 'lp->tx_bd_ci' may be
undefined [-Wsequence-point]
xilinx_axienet_main.c: In function 'axienet_start_xmit':
xilinx_axienet_main.c:703:18: warning: operation on
Hi,
Based on our discussion I am sending 2 bug fixes for axi ethernet
driver against your net tree.
Thanks,
Michal
Changes in v2:
- Separate bug fixes from features and cleanups
Michal Simek (2):
net: axienet: Fix compilation error
net: axienet: Fix compilation warnings
On Sat, Feb 08, 2014 at 08:57:01AM +0100, Andi Kleen wrote:
> const __read_mostly does not make any sense, because const
> data is already read-only. Remove the __read_mostly
> for the ipvs genl_ops. This avoids a LTO
> section conflict compile problem.
Thanks Andi, applied to ipvs-next.
> Cc:
On Fri, Feb 7, 2014 at 2:41 PM, wrote:
> From: zhang jun
>
> From the following oops log, we find firmware buffer is null, which caused by
> memory alloc failed.
> so, we need give a protection and return a error value.
> [ 7341.474236] [drm:do_intel_finish_page_flip] *ERROR* invalid or
On 02/11/2014 03:05 AM, David Rientjes wrote:
On Mon, 10 Feb 2014, Raghavendra K T wrote:
So I understood that you are suggesting implementations like below
1) I do not have problem with the below approach, I could post this in
next version.
( But this did not include 4k limit Linus mentioned
I started noticing problems with KVM guest destruction on Linux 3.12+, where
guest memory wasn't being cleaned up. I bisected it down to the commit
introducing the new 'asm goto'-based atomics, and found this quirk was later
applied to those.
Unfortunately, even with GCC 4.8.2 (which ostensibly
On 02/13/2014 01:18 AM, David Miller wrote:
> From: Michal Simek
> Date: Wed, 12 Feb 2014 16:55:34 +0100
>
>> I have exctracted patches which I have in our
>> xilinx git tree which are missing in the mainline.
>>
>> The first two patches fix compilation error and
>> warnings. Then 5 feature
Hi,
On Wednesday 12 February 2014 09:33 PM, Lee Jones wrote:
> The MiPHY365x is a Generic PHY which can serve various SATA or PCIe
> devices. It has 2 ports which it can use for either; both SATA, both
various SATA or PCIe devices in STMicroelectronics STiH41x SoC series?
> PCIe or one of each
Multiple platforms need to set CPU to a particular frequency before suspending
system. And so they need a common infrastructure which is provided by this
patch. Those platforms just need to initialize their ->suspend() pointers with
the generic routine.
Tested-by: Stephen Warren
Signed-off-by:
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/s5pv210-cpufreq.c | 49 +++
1 file
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/exynos-cpufreq.c | 96 +++-
1 file
Previous patch added support for suspending governors, with callbacks being
called from dpm_{suspend|resume}_noirq(). The problem here is that most of the
devices (i.e. devices with ->suspend() callbacks) have already been suspended by
now and so if drivers want to change frequency before
Earlier cpufreq suspend/resume callbacks into drivers were getting called only
for the boot CPU, as by the time callbacks were called non-boot CPUs were
already removed. Because we might still need driver specific actions on
suspend/resume, its better to use earlier infrastructure from the early
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Tested-by: Stephen Warren
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/tegra-cpufreq.c | 46
This patch adds cpufreq suspend/resume calls to dpm_{suspend|resume}_noirq() for
handling suspend/resume of cpufreq governors.
Lan Tianyu (Intel) & Jinhyuk Choi (Broadcom) found an issue where tunables
configuration for clusters/sockets with non-boot CPUs was getting lost after
suspend/resume, as
This patchset creates/calls cpufreq suspend/resume callbacks from
dpm_{suspend|resume}()
for handling suspend/resume of cpufreq governors and core.
There are multiple problems that are fixed by this patch:
- Nishanth Menon (TI) found an interesting problem on his platform, OMAP. His
board
On Wed, 2014-02-12 at 20:53 -0800, Steven Noonan wrote:
> I started noticing problems with KVM guest destruction on Linux 3.12+, where
> guest memory wasn't being cleaned up. I bisected it down to the commit
> introducing the new 'asm goto'-based atomics, and found this quirk was later
> applied
Add support for S2MPA01 voltage and current regulator.
Signed-off-by: Sachin Kamat
Acked-by: Mark Brown
---
Changes since v2:
* Added missing of_node_put
* Used of_get_child_by_name
---
drivers/regulator/Kconfig |7 +
drivers/regulator/Makefile |1 +
drivers/regulator/s2mpa01.c |
Add the necessary entries required for S2MPA01 multi-function
device. While at it also convert whitespaces to tabs in core.h.
Signed-off-by: Sachin Kamat
Acked-by: Lee Jones
---
No change in v3 since v2.
---
drivers/mfd/sec-core.c | 45 +++-
include/linux/mfd/samsung/core.h
Added initial binding documentation for S2MPA01 MFD.
Signed-off-by: Sachin Kamat
---
Changes since v2:
* Re-worded as suggested by Mark Rutland
---
Documentation/devicetree/bindings/mfd/s2mpa01.txt | 90 +
1 file changed, 90 insertions(+)
create mode 100644
On 22 January 2014 11:34, Viresh Kumar wrote:
> Double ! or !! are normally required to get 0 or 1 out of a expression. A
> comparision always returns 0 or 1 and hence there is no need to apply double !
> over it again.
>
> Signed-off-by: Viresh Kumar
> ---
> kernel/power/suspend.c | 2 +-
> 1
Am Mittwoch, den 12.02.2014, 12:57 -0800 schrieb Andy Lutomirski:
> On Wed, Feb 12, 2014 at 12:40 PM, wrote:
> > From: Stefani Seibold
> >
> > This patch adds conditional fixmap of the VVAR and HPET pages for a 32
> > bit kernel
> >
> > Signed-off-by: Stefani Seibold
>
> Looks good to me.
>
OK. If I send a patch like this again, ChangeLog is written as you comment.
Thanks.
Daeseok Youn.
2014-02-13 11:28 GMT+09:00 David Rientjes :
> On Thu, 13 Feb 2014, Daeseok Youn wrote:
>
>> From f8e0752ac80e56bcbfe197a5820692d199822b52 Mon Sep 17 00:00:00 2001
>> From: Daeseok Youn
>> Date:
Hi Mark,
On 12 February 2014 23:40, Mark Rutland wrote:
> Hi Sachin,
>
> Apologies for the delay on this.
No problem :). Thank you for your review. Please see my comments inline.
>
> On Thu, Jan 09, 2014 at 11:22:34AM +, Sachin Kamat wrote:
>> Added initial binding documentation for
2014-02-12 22:04 GMT+01:00 Alexandre Belloni
:
> Sorry, one more comment on that patch:
>
> On 12/02/2014 at 11:06:42 +0100, Jean-Jacques Hiblot wrote :
>> + pinctrl@f400 {
>> + #address-cells = <1>;
>> + #size-cells =
Hi, all,
While looking at x86 boot code (arch/x86/kernel/setup.c), I got confused due to
bootloader_type and bootloader_version conversion.
I've only checked GRUB and U-Boot bootloader code.
1. GRUB 2
type_of_loader setting = 0x72
-> bootloader_type = 0x72, bootloader_version = 0x2
2.
On Mon, Feb 10, 2014 at 02:42:19PM +0100, Geert Uytterhoeven wrote:
> "ARM: shmobile: r8a7778: add I2C support on DTSI" was applied twice:
>
> commit ae4273ec7b25c8b9c895a4aae31f2fced980b7bf
> commit 3acb51b9215bd99da403ecf8200f8425176b1926
>
> Signed-off-by: Geert Uytterhoeven
Thanks,
On 02/13/2014 01:15 PM, Michael S. Tsirkin wrote:
> On Thu, Feb 13, 2014 at 11:02:13AM +0800, Jason Wang wrote:
>> On 02/12/2014 07:59 PM, Michael S. Tsirkin wrote:
>>> On Wed, Feb 12, 2014 at 01:43:28PM +0800, Jason Wang wrote:
> We should alloc big buffers also when guest can receive UFO
Device core provides way of accessing driver-private data, we should
use it.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_bus.h | 1 -
drivers/input/rmi4/rmi_f01.c | 14 +--
drivers/input/rmi4/rmi_f11.c | 57
3 files changed, 32
(more than usual) the powerpc allyesconfig build.
Changes since 20140212:
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The wireless-next tree gained a build failure for which I applied a patch.
The tip tre
On 02/11, Lee Jones wrote:
>
> > +- interrupts:
> > + Usage: required
> > + Value type:
>
> Either provide an example or a comment to see the description of
> #interrupt-cells
It is part of the example. We also state that the format is
defined by the interrupt parent binding.
>
> > +
On Wed, Feb 12, 2014 at 02:01:01PM +0900, Magnus Damm wrote:
> Hi Geert, Simon,
>
> On Mon, Feb 10, 2014 at 7:47 PM, Geert Uytterhoeven
> wrote:
> > Hi Simon, Magnus,
> >
> > The following patch series completes r8a7790 SoC and Lager board
> > integration for the Renesas Quad Serial
It is an empty stub and is not needed.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/input/rmi4/rmi_f01.c b/drivers/input/rmi4/rmi_f01.c
index 92b90d1..897d8ac 100644
--- a/drivers/input/rmi4/rmi_f01.c
+++
Data that is allocated with devm_kzalloc() should not be freed with
kfree(). In fact, we should rely on the fact that memory is managed and let
devres core free it for us.
Reported-by: Courtney Cavin
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 23 +--
Do not write configuration data in probe(), we have config() for that.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/drivers/input/rmi4/rmi_f01.c b/drivers/input/rmi4/rmi_f01.c
index 897d8ac..976aba3 100644
We do not need to persist it - we read it when signalled.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/drivers/input/rmi4/rmi_f01.c b/drivers/input/rmi4/rmi_f01.c
index 6f90a6c..1e49ab4 100644
We have too many "data"s: f01_data, driver_data, pdata, etc. Let's
untangle it a bit.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 135 ++-
1 file changed, 68 insertions(+), 67 deletions(-)
diff --git a/drivers/input/rmi4/rmi_f01.c
From: Christopher Heiny
Both F01_RMI_Ctrl2 and F01_RMI_Ctrl3 (doze_interval and wakeup_threshold)
are controlled by the has_adjustable_doze bit.
Signed-off-by: Christopher Heiny
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 7 ---
1 file changed, 4 insertions(+), 3
It is not used by anyone.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/input/rmi4/rmi_f01.c b/drivers/input/rmi4/rmi_f01.c
index 30e0b50..6f90a6c 100644
--- a/drivers/input/rmi4/rmi_f01.c
+++
Use rmi_read()/rmi_write() for reading/writing single-byte data. Also print
error code when IO fails.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 170 ++-
1 file changed, 88 insertions(+), 82 deletions(-)
diff --git
When accessing platform data of RMI device let's make sure we do not
accidentally change data that may be shared by returning const pointer.
Also switch to an inline function instead of macro to ensure type safety.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_bus.h| 7 ++-
Let's allocate interrupt mask together with the main structure and combine
rmi_f01_alloc_memory, rmi_f01_initialize and rmi_f01_probe into single
function.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f01.c | 86
1 file changed, 30
On 12 February 2014 23:32, Mark Rutland wrote:
> On Thu, Jan 09, 2014 at 11:22:33AM +, Sachin Kamat wrote:
>> Add support for S2MPA01 voltage and current regulator.
>>
>> Signed-off-by: Sachin Kamat
>> ---
>> * Addressed comments from Mark Brown
>> - Used module_platform_driver instead of
On 12 February 2014 20:36, Frederic Weisbecker wrote:
> The change I'm applying is strongly inspired from the above. Can I use your
> Signed-off-by?
Sure :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Thu, Feb 13, 2014 at 11:02:13AM +0800, Jason Wang wrote:
> On 02/12/2014 07:59 PM, Michael S. Tsirkin wrote:
> > On Wed, Feb 12, 2014 at 01:43:28PM +0800, Jason Wang wrote:
> >> > We should alloc big buffers also when guest can receive UFO
> >> > pakcets. Otherwise the big packets will be
On Wed, Feb 12, 2014 at 10:39:36PM +0300, Sergey Senozhatsky wrote:
> Add max_comp_streams device attribute documentation.
>
> Signed-off-by: Sergey Senozhatsky
> ---
> Documentation/ABI/testing/sysfs-block-zram | 9 -
> Documentation/blockdev/zram.txt| 20
On Wed, Feb 12, 2014 at 10:39:34PM +0300, Sergey Senozhatsky wrote:
> Do not perform direct LZO compress/decompress calls,
> initialise and use zcomp LZO backend instead.
>
> Signed-off-by: Sergey Senozhatsky
> ---
> drivers/block/zram/Makefile | 2 +-
> drivers/block/zram/zram_drv.c | 62
>
Hello Sergey,
On Wed, Feb 12, 2014 at 10:39:33PM +0300, Sergey Senozhatsky wrote:
> ZRAM performs direct LZO compression algorithm calls, making it the one and
> only option. Introduce compressing backend abstraction zcomp in order to
> support multiple compression algorithms with the following
I started noticing problems with KVM guest destruction on Linux 3.12+, where
guest memory wasn't being cleaned up. I bisected it down to the commit
introducing the new 'asm goto'-based atomics, and found this quirk was later
applied to those.
Unfortunately, even with GCC 4.8.2 (which ostensibly
Sorry, I miss the message .Thanks Shawn's reminding and thanks Sascha's
comments and I will talk with Frank.
-Original Message-
From: Shawn Guo [mailto:shawn@linaro.org]
Sent: Thursday, February 13, 2014 9:56 AM
To: Gong Yibin-B38343
Cc: broo...@kernel.org; s.ha...@pengutronix.de;
Steven Rostedt writes:
> On Tue, 11 Feb 2014 08:27:38 +0100
> Ingo Molnar wrote:
>
>>
>> * Mathieu Desnoyers wrote:
>>
>> > Users have reported being unable to trace non-signed modules loaded
>> > within a kernel supporting module signature.
>>
>> External modules should strive to get out
On Thu, Feb 13, 2014 at 12:03:02PM +0900, Magnus Damm wrote:
> PCI: rcar: Recent driver patches from Ben Dooks and me
>
> [PATCH 01/08] PCI: rcar: check platform_get_irq() return code
> [PATCH v2 02/08] PCI: rcar: add error interrupt handling
> [PATCH 03/08] PCI: rcar: fix bridge logic
On Wed, Feb 12, 2014 at 01:59:11PM -0700, Bjorn Helgaas wrote:
> On Wed, Feb 05, 2014 at 03:52:43PM +0900, Magnus Damm wrote:
> > PCI: rcar: Driver model and physical address space update
> >
> > [PATCH 01/04] PCI: rcar: Register each instance independently
> > [PATCH 02/04] PCI: rcar: Break out
is commit in next-tree:
[5.251993] [ cut here ]
[5.252019] WARNING: CPU: 0 PID: 221 at kernel/locking/lockdep.c:710
__lock_acquire+0x1761/0x1f60()
[5.252019] Modules linked in: e1000
[5.252019] CPU: 0 PID: 221 Comm: lvm Not tainted 3.14.0-rc2-next-20140212 #
On Wed, Feb 12, 2014 at 8:27 PM, Luis R. Rodriguez
wrote:
> I have a test patch that now works that restricts xen-netback from
> getting any IPv4 and IPv6 addresses, and disables multicast. With this
> set in place the xen-frontend still gets IPv4 and IPv6 addresses and
> Multicast still works.
On Wed, Feb 12, 2014 at 2:05 PM, Luis R. Rodriguez
wrote:
> We have to be careful for sure, I'll try to test all cases including
> kvm, but architecturally as I see it so far these things are simply
> exchanging over data through their respective backend channels, I know
> ipv6 interfaces are
From: Liu Junliang
Signed-off-by: Liu Junliang
---
drivers/net/usb/Kconfig |1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/usb/Kconfig b/drivers/net/usb/Kconfig
index 2551bf6..82df7c3 100644
--- a/drivers/net/usb/Kconfig
+++ b/drivers/net/usb/Kconfig
@@ -295,7 +295,6 @@
Dear Thierry :
For this driver, we can set it as 'n', and There is no
rule of thumb as to which should default to y.
Thanks for your advice.
Thanks again.
2014-02-13
liujunliang_ljl
When !defined(CONFIG_EXT4_DEBUG), mb_debug() should be defined as a
no_printk() statement instead of an empty statement in order to suppress
the following compiler warning:
fs/ext4/mballoc.c: In function ‘ext4_mb_cleanup_pa’:
fs/ext4/mballoc.c:2659:47: warning: suggest braces around empty body in
On Wed, Feb 12, 2014 at 7:09 PM, Steven Noonan wrote:
>
> If I change the GCC_VERSION check for the asm_volatile_goto quirk to
> include 4.8.2, then KVM guests are properly cleaned up.
Ok, I guess that means we should just make the quirk unconditional.
Ingo, do you want to do that or should I?
From: David Miller
Date: Wed, 12 Feb 2014 23:05:06 -0500 (EST)
> From: Greg KH
> Date: Wed, 12 Feb 2014 17:39:02 -0800
>
>> Yes, that's horrible as well, but as was already pointed out in this
>> thread, you can't rely on that value to really be "1" after reading it
>> due to the way krefs
From: Greg KH
Date: Wed, 12 Feb 2014 17:39:02 -0800
> Yes, that's horrible as well, but as was already pointed out in this
> thread, you can't rely on that value to really be "1" after reading it
> due to the way krefs work, what happened if someone else just grabbed
> it?
>
> If all they want
On Wed, Feb 12, 2014 at 9:59 PM, Joe Perches wrote:
> On Wed, 2014-02-12 at 21:13 -0500, Patrick Palka wrote:
>> When !defined(CONFIG_EXT4_DEBUG), mb_debug() should be defined as an
>> empty do-while statement so as to suppress the following compiler
>> warning:
>
> Hello Patrick.
>
>>
On 02/13/2014 08:54 AM, Haiyang Zhang wrote:
> Without this patch, the "cat /sys/class/net/ethN/operstate" shows
> "unknown", and "ethtool ethN" shows "Link detected: yes", when VM
> boots up with or without vNIC connected.
>
> This patch fixed the problem.
>
> Signed-off-by: Haiyang Zhang
>
Commit 6ae668cc19e8b18df28cd67b3448d9abd79284a4 introduced a memory leak
in the error path of tda998x_encoder_init
Picked up by the nightly Coverity scan. CID 1174076
Signed-off-by: Dave Jones
diff --git a/drivers/gpu/drm/i2c/tda998x_drv.c
b/drivers/gpu/drm/i2c/tda998x_drv.c
index
On 02/12/2014 06:32 PM, Jiang Liu wrote:
> Ping...
Sorry, will look at it tomorrow.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Kuninori Morimoto
934624d6e9f0b3d41557c4105c286e8daeaadb4e
(regulator: gpio-regulator: do not open-code counting and access of dt array
elements)
removed struct property *prop from of_get_gpio_regulator_config()
but, it is still used on
0094050d783bbadffe83effef11a0bda901153ce
(regulator:
On 02/12/2014 11:18 PM, Jason J. Herne wrote:
> On 02/10/2014 06:17 PM, Tejun Heo wrote:
>> Hello,
>>
>> On Mon, Feb 10, 2014 at 10:32:11AM -0500, Jason J. Herne wrote:
>>> [ 950.778485] XXX: worker->flags=0x1 pool->flags=0x0 cpu=6
>>> pool->cpu=2 rescue_wq= (null)
>>> [ 950.778488]
On 02/12/2014 06:22 PM, Peter Zijlstra wrote:
[snip]
>
> Yes I think there might be a problem here because of how we re-arranged
> things. Let me brew of pot of tea and try to actually wake up.
>
> I suspect we might be good if we clear the need_resched flags before
> calling pick_next_task.
In this if-else conditional statement, if (chan < 16), but
(data[0] == INSN_CONFIG_DIO_QUERY), the function does not return early,
but the else-branch does not get executed either. As a result, mask
would be used uninitialized in the next line. What we want here is if
(chan < 16) and (data[0] !=
battery driver defines acpi_battery_resume() when CONFIG_PM_SLEEP is defined.
This results in the following compile error when CONFIG_PM_SLEEP is undefined.
drivers/acpi/battery.c:847:8: error: ‘acpi_battery_resume’ undeclared here (not
in a function)
Signed-off-by: Shuah Khan
---
sbs driver defines acpi_sbs_resume() when CONFIG_PM_SLEEP is defined. This
results in the following compile error when CONFIG_PM_SLEEP is undefined.
CC [M] drivers/acpi/sbs.o
drivers/acpi/sbs.c:674:8: error: ‘acpi_sbs_resume’ undeclared here (not in a
function)
Signed-off-by: Shuah Khan
---
ac driver defines acpi_ac_resume() when CONFIG_PM_SLEEP is defined. This
results in the following compile error when CONFIG_PM_SLEEP is undefined.
drivers/acpi/ac.c:248:8: error: ‘acpi_ac_resume’ undeclared here (not in a
function)
Signed-off-by: Shuah Khan
---
drivers/acpi/ac.c |2 ++
1
Hello.
I got a lockdep warning shown below, and the bad commit seems to be de055616
\"mm: keep page cache radix tree nodes in check\" as of next-20140212
on linux-next.git.
Regards.
=
[ INFO: possible irq lock inversion dependenc
fan driver defines acpi_fan_suspend() and acpi_fan_resume() when
CONFIG_PM_SLEEP is defined. This results in the following compile error when
CONFIG_PM_SLEEP is undefined.
drivers/acpi/fan.c:60:8: error: ‘acpi_fan_suspend’ undeclared here (not in a
function)
drivers/acpi/fan.c:60:8: error:
thermal driver defines acpi_thermal_resume() when CONFIG_PM_SLEEP is defined.
This results in the following compile error when CONFIG_PM_SLEEP is undefined.
CC drivers/acpi/thermal.o
drivers/acpi/thermal.c:107:8: error: ‘acpi_thermal_resume’ undeclared here (not
in a function)
make[2]:
button driver defines acpi_button_resume() when CONFIG_PM_SLEEP is defined.
This results in the following compile error when CONFIG_PM_SLEEP is undefined.
drivers/acpi/button.c:85:8: error: ‘acpi_button_resume’ undeclared here (not in
a function)
Signed-off-by: Shuah Khan
---
The following acpi drivers fail with compile errors when CONFIG_PM_SLEEP
is undefined.
Shuah Khan (6):
drivers/acpi: fix ac driver compile error when CONFIG_PM_SLEEP is
undefined
drivers/acpi: fix battery driver compile error when CONFIG_PM_SLEEP is
undefined
drivers/acpi: fix
exynos4_local_timer_setup called on the secondary cpu before
irqs are enabled. request_irq can sleep, which produces next warning:
on boot:
[0.37] CPU0: thread -1, cpu 0, socket 0, mpidr 8000
[0.37] Setting up static identity map for 0x403b5700 - 0x403b5758
[0.395000]
mct_init not used anywhere, remove this non-dt stuff.
also remove declaration of mct_init
in arch/arm/mach-exynos/common.h
Signed-off-by: Tarek Dakhran
---
arch/arm/mach-exynos/common.h|2 --
drivers/clocksource/exynos_mct.c | 17 +
2 files changed, 1 insertion(+), 18
exynos4_local_timer_setup called on the secondary cpu before
irqs are enabled. request_irq can sleep, which produces next warning:
BUG: sleeping function called from invalid context at mm/slub.c:965
in_atomic(): 1, irqs_disabled(): 128, pid: 0, name: swapper/3
Call setup_irq for
Resurrecting this thread, as I'm running with GCC 4.8.2 and am
encountering miscompiles without this quirk being enabled for my
compiler version. I'm having trouble pinning down the miscompilation
itself, but I have a problem that seems reliably reproducible in my
environment.
I noticed that when
From: Magnus Damm
Convert the code to allow per-device probe() like other device
drivers. This also delays driver registration due to change from
subsys_initcall() to regular module_platform_driver().
Signed-off-by: Magnus Damm
---
Changes since V1:
- Updated to fit on top of patches from
From: Magnus Damm
Update the R-Car Generation 2 PCI driver Kconfig dependencies
to follow same style as other drivers - no SoC dependencies.
Also, update the COMPILE_TEST bits to depend on ARM. This since
the DMA bounce buffer and dma_ops handling code is ARM specific.
Signed-off-by: Magnus
From: Magnus Damm
Select BOUNCE in case of HIGHMEM to enable bounce buffers in
the block layer. Without this patch the DMABOUNCE code will
error out due to lack of HIGHMEM support, and without DMABOUNCE
there will be silent errors.
Signed-off-by: Magnus Damm
---
drivers/pci/host/Kconfig |
From: Magnus Damm
Add DMABOUNCE support together with a local memory area for
all PCI devices hanging off this bridge. 4MiB of memory is
set aside for coherent allocations which is shared between
the on-chip OHCI and EHCI devices that are hanging off the
PCI bridge. With this patch the driver
1 - 100 of 1754 matches
Mail list logo
