Hi Jiri,
On Fri, Apr 18, 2014 at 3:52 AM, Jiri Olsa wrote:
> On Thu, Apr 17, 2014 at 10:38:19PM +0900, Namhyung Kim wrote:
>> Hi Jiri,
>>
>> 2014-04-17 (목), 14:00 +0200, Jiri Olsa:
>> > On Thu, Apr 17, 2014 at 04:53:23PM +0900, Namhyung Kim wrote:
>> > > Hi,
>> > >
>> > > This is a small fixes fo
Hi Alexey, Kim,
On 04/18/2014 02:04 PM, Alexey Khoroshilov wrote:
> On 17.04.2014 00:45, Jaegeuk Kim wrote:
>> Hi,
>>
>> 2014-04-16 (수), 18:11 -0700, Alexey Khoroshilov:
>>> Hi,
>>>
>>> But would not ability to trigger BUG_ON by mounting a crafted image
>>> considered as an issue having security i
Thank you for the explanation.
The following patch will resolve the issue.
Thanks,
>From 2048e7458c982f4297da9d3366ab29224ae2e8b0 Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Fri, 18 Apr 2014 15:21:04 +0900
Subject: [PATCH] f2fs: avoid BUG_ON when mouting corrupted image having
garbage block
Hi,
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, April 18, 2014 11:40 AM
>
> On Fri, Apr 18, 2014 at 03:00:21AM +, Zheng, Lv wrote:
> > Hi, Greg
> >
> > > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > > Sent: Friday, April 18, 2014 10:44 AM
> > >
> > > On Fri, A
Hi,
On Thu, Apr 17, 2014 at 12:53:03PM +0200, Thierry Reding wrote:
> On Thu, Apr 17, 2014 at 12:21:44AM -0700, Brian Norris wrote:
> > We are introducing a new SPI-NOR library/framework for MTD, to support
> > various
> > types of SPI-NOR flash controllers which require (or benefit from) intimat
On Thu, Apr 17, 2014 at 5:28 PM, Andi Kleen wrote:
> BTW if you're worried about sysctl races you may also want to resurrect
> https://lkml.org/lkml/2009/12/20/214
Yeah, this had bothered me too while reading the code. The only "good"
news is that the strings are always NULL terminated and only "
On Fri, Apr 18, 2014 at 08:01:22AM +0200, Bastien Armand wrote:
> This patch fixes sparse warnings in panel.c.
What sparse warnings were fixed here?
It looks like you did a lot of different things, can you please break
this out into "one patch per logical change" so it can be reviewed
easier?
th
Hi,
On Thu, 17 Apr 2014 06:33:59 -0700
Antoine Ténart wrote:
> Sebastian,
>
> On Wed, Apr 16, 2014 at 04:26:06PM +0200, Sebastian Hesselbarth wrote:
> > On 04/16/2014 02:40 PM, Antoine Ténart wrote:
> > >Add a Driver to support the SDHCI controller of the Marvell Berlin SoCs.
> > >This controll
On 17.04.2014 00:45, Jaegeuk Kim wrote:
> Hi,
>
> 2014-04-16 (수), 18:11 -0700, Alexey Khoroshilov:
>> Hi,
>>
>> But would not ability to trigger BUG_ON by mounting a crafted image
>> considered as an issue having security implications?
> Sorry, I can't come up with you.
> Could you please explain w
Got it.
The patch is like this.
Thanks,
>From 5f7a3bcf0df10bbb47a6e4409cc92ba8e6090674 Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Fri, 18 Apr 2014 11:14:37 +0900
Subject: [PATCH] f2fs: add available_nids to fix handling max_nid
correctly
This patch introduces available_nids for alloc_nids(
This patch fixes sparse warnings in panel.c.
Signed-off-by: Bastien Armand
---
drivers/staging/panel/panel.c | 209 ++---
1 file changed, 111 insertions(+), 98 deletions(-)
diff --git a/drivers/staging/panel/panel.c b/drivers/staging/panel/panel.c
index 08f
(2014/04/17 19:05), Peter Zijlstra wrote:
> Anyway, if you want to preserve the same broken ass crap we had pre
> NOHZ, something like the below should do that.
>
> I'm not really thrilled with iowait_{start,stop}() but I think they
> should have the same general cost as the atomic ops we already
Helpdesk Service Center requires your immediate re-activation of your Email
account. This is to improve and to Upgrade your Email Account and to keep your
Account Updated. Inability to complete this procedure will render your account
inactivate. Activate your Account by completing the survey pro
Hello Davidlohr,
On Fri, Apr 18, 2014 at 12:31 AM, Davidlohr Bueso wrote:
> On Thu, 2014-04-17 at 22:23 +0200, Michael Kerrisk (man-pages) wrote:
>> Hi Manfred!
>>
>> On Thu, Apr 17, 2014 at 6:22 PM, Manfred Spraul
>> wrote:
>> > Hi Michael,
>> >
>> >
>> > On 04/17/2014 12:53 PM, Michael Kerrisk
On 04/17/2014 09:58 PM, Herbert Xu wrote:
>>
>> It doesn't make sense, sorry. The right thing to drop here is not
>> "asmlinkage", it is "static": this is an external declaration.
>
> It's a function pointer that's static, not the function that
> it's pointing to.
>
{facepalm} Right, function *
On Thu, Apr 17, 2014 at 09:49:56PM -0700, H. Peter Anvin wrote:
> On 04/17/2014 08:28 AM, Marek Vasut wrote:
> > On Wednesday, April 16, 2014 at 06:19:50 PM, Jianyu Zhan wrote:
> >> Commit 128ea04a9885("lto: Make asmlinkage __visible") restricts
> >> asmlinkage to externally_visible, this causes co
On 04/17/2014 08:28 AM, Marek Vasut wrote:
> On Wednesday, April 16, 2014 at 06:19:50 PM, Jianyu Zhan wrote:
>> Commit 128ea04a9885("lto: Make asmlinkage __visible") restricts
>> asmlinkage to externally_visible, this causes compilation warnings:
>>
>> arch/x86/crypto/sha256_ssse3_glue.c:56:1:
On Fri, Apr 18, 2014 at 06:35:56AM +0200, Andi Kleen wrote:
> From: Andi Kleen
>
> Apparently someone's C library declares strtoul with warn_unused_result.
> Cast to void to avoid the warning. Error handling is not useful here.
Umm... Since we don't give a fsck for the value, isn't that simply
From: Andi Kleen
Apparently someone's C library declares strtoul with warn_unused_result.
Cast to void to avoid the warning. Error handling is not useful here.
Cc: Viresh Kumar
Signed-off-by: Andi Kleen
---
scripts/mod/modpost.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
Il 16/04/2014 18:52, Marcelo Tosatti ha scritto:
How about handling VM-entry error due to invalid state with
vmx->emulation_required = true;
continue to main vcpu loop;
What would reset it to false though? None of the places that call
emulation_required() is a hot path right now, and this pa
On Thu, Apr 17, 2014 at 11:28 PM, Lennart Sorensen
wrote:
> On Thu, Apr 17, 2014 at 11:00:37PM +0200, Jos Huisken wrote:
>> I was trying to maintain a local and remote directory in sync with
>> lsync, using inotify.
>> I happen to have >4M files and >400k directories... running over
>> /proc/sys/f
If EFER.LMA is off, cs.l does not determine execution mode.
Currently, the emulation engine assumes differently.
Signed-off-by: Nadav Amit
---
:100644 100644 f4d9839... c99f7eb... M arch/x86/kvm/x86.c
arch/x86/kvm/x86.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch
When using address-size override prefix with string instructions in long-mode,
ESI/EDI/ECX are zero extended if they are affected by the instruction
(incremented/decremented). Currently, the KVM emulator does not do so.
In addition, although it is not well-documented, when address override prefix
On 04/14/2014 09:40 PM, Andy Shevchenko wrote:
On Fri, 2014-04-11 at 16:14 +0800, Hongbo Zhang wrote:
On 04/10/2014 07:29 PM, Andy Shevchenko wrote:
On Thu, 2014-04-10 at 15:10 +0800, hongbo.zh...@freescale.com wrote:
[]
@@ -819,8 +826,7 @@ static void fsldma_cleanup_descriptor(struct fsldm
On Tue, Feb 4, 2014 at 12:20 PM, Hugh Dickins wrote:
> On Mon, 3 Feb 2014, Andrew Morton wrote:
>> On Mon, 27 Jan 2014 18:03:04 +0800 Weijie Yang
>> wrote:
>>
>> > When swapon the same S_ISBLK blockdev concurrent, the allocated two
>> > swap_info could hold the same block_device, because claim_s
> > + freq = clk_get_rate(ftm_clk);
> > +
> > + calc_closest_cound_cyc(freq);
> > +
> > + BUG_ON(ftm_clocksource_init(freq));
> > +
> > + BUG_ON(ftm_clockevent_init(freq, irq));
> > +}
> > +CLOCKSOURCE_OF_DECLARE(vf610, "fsl,vf610-ftm-timer", ftm_timer_init);
>
>
> I am not a big fan of t
> > Here using the FTM0 as clock event device and the FTM1 as clock
> > source device.
>
> As it is a new driver, please add a more elaborated description of the
> timer.
>
Please see the next version.
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
>
On 04/17/2014 08:40 PM, Masami Hiramatsu wrote:
> (2014/04/18 2:31), Sasha Levin wrote:
>>> I also have seen several attempts at using the generic instruction
>>> decoder which has resulted in more complexity, not less, because of
>>> excess generality, so it is not an obvious thing.
>>
>> Let's sp
On Thursday, April 17, 2014 9:13 PM, Marc Zyngier wrote:
> On Wed, Apr 16 2014 at 5:33:31 am BST, Jungseok Lee
> wrote:
> > This patch adds 4 levels of translation tables implementation for both
> > HYP and stage2. A combination of 4KB + 4 levels host and 4KB + 4
> > levels guest can run on ARMv
(2014/04/18 2:31), Sasha Levin wrote:
>> I also have seen several attempts at using the generic instruction
>> decoder which has resulted in more complexity, not less, because of
>> excess generality, so it is not an obvious thing.
>
> Let's split this patchset into two:
>
> We have one part whic
On Fri, Apr 18, 2014 at 03:00:21AM +, Zheng, Lv wrote:
> Hi, Greg
>
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Friday, April 18, 2014 10:44 AM
> >
> > On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> > > Note that this patch is only used for stable kernels, ups
(2014/04/18 0:33), Sasha Levin wrote:
> On 04/16/2014 01:44 AM, Masami Hiramatsu wrote:
>> Same thing can be done in awk part and insn.c, and we can encode it by
>>
>> #define INAT_MAKE_MEMSZ(size) (size << INAT_MEMSZ_OFFS)
>>
>> And decode it by
>>
>> insn->memsz_bytes = 1 << ((attr & INAT_MEMSZ_M
Hi,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Friday, April 18, 2014 10:16 AM
> To: Chao Yu
> Cc: linux-f2fs-de...@lists.sourceforge.net; linux-fsde...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to ena
From: Alan Cox
Not all systems enumerate the PWM devices via ACPI. They can also be exposed
via the PCI interface.
Signed-off-by: Alan Cox
Signed-off-by: Chew, Chiau Ee
---
drivers/pwm/pwm-lpss.c | 161 ++-
1 files changed, 130 insertions(+), 31 de
Hi,
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, April 18, 2014 10:44 AM
>
> On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> > Note that this patch is only used for stable kernels, upstream kernels
> > will have this problem fixed in ACPICA 201303-04 release. S
(2014/04/17 22:43), Vivek Goyal wrote:
> On Thu, Apr 17, 2014 at 10:59:14AM +0900, Masami Hiramatsu wrote:
>
> [..]
@@ -112,9 +113,14 @@ void panic(const char *fmt, ...)
/*
* If we have crashed and we have a crash kernel loaded let it handle
* everything else.
-
Hi, Greg
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Friday, April 18, 2014 10:44 AM
>
> On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> > Note that this patch is only used for stable kernels, upstream kernels
> > will have this problem fixed in ACPICA 201303-04 releas
On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> Note that this patch is only used for stable kernels, upstream kernels
> will have this problem fixed in ACPICA 201303-04 release. So upstream
> kernels shouldn't merge this commit.
What kernel commit fixed this issue in "upstream"?
> I
This patch adds official maintainer for low power Intel MID SoC
platforms.
Signed-off-by: David Cohen
Cc: Mark Gross
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6dc67b1fdb50..b6056f33cb4d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
Several conditions in bcm_kona_smc_init() are handled with BUG_ON().
That function is capable of returning an error, so do that instead.
Also, don't assume of_get_address() returns a valid pointer.
Signed-off-by: Alex Elder
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
Reviewed-by: Matt Po
There's logic in bcm_kona_smc() to ensure __bcm_kona_smc() gets
called on CPU 0; if already executing on CPU 0, that function is
called directly. The direct call is not protected from interrupts,
however, which is not safe.
Note that smp_call_function_single() is designed to handle the case
where
This patch just does some simple cleanup in "bcm_kona_smc.c":
- Get rid of the secure_bridge_data structure. Instead, just
define two globals that record the physical and virtual
addresses of the SMC arguments buffer. Use "buffer" instead
of "bounce" in their names. Drop of
The pointer used to pass parameters to an "smc" call is produced
through a call to ioremap(). As such, we should be using functions
like writel() to access it.
Signed-off-by: Alex Elder
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
Reviewed-by: Matt Porter
---
arch/arm/mach-bcm/bcm_kona_
Move the code that implements the "smc" call into a C function that
uses inline assembly. This allows us to make that function private,
and enables us to get rid of "arch/arm/mach-bcm/bcm_kona_smc_asm.S".
Rename what had been the "buffer_addr" argument to be "buffer_phys"
so it's consistent with o
Currently it is assumed that SEC_ROM_RET_OK is the only valid "good"
result of a secure monitor request. However the values that can be
returned by a secure monitor request are dependent on which service
id was provided.
We therefore should handle the result in a request-dependent way.
The most n
The block of comments in bcm_kona_do_smc() are somewhat confusing.
This patch attempts to clarify what's going on.
Signed-off-by: Alex Elder
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
Reviewed-by: Matt Porter
---
arch/arm/mach-bcm/bcm_kona_smc.c | 38 -
Clean up a few header file includes, eliminating a few that are not
really needed and putting in their place some that are.
Signed-off-by: Alex Elder
Reviewed-by: Matt Porter
---
arch/arm/mach-bcm/board_bcm21664.c |3 +--
arch/arm/mach-bcm/kona.c |5 +++--
arch/arm/mach-bcm/ko
Add a new config option ARCH_BCM_MOBILE_L2_CACHE that allows support
for level-2 cache to be enabled or disabled at build time for
BCM218XX and BCM21664 family SoCs.
Build support for SMC only if it's required (currently it's only
required for to support level 2 cache control).
If arch/arm/mach-b
This series cleans up a number of things in the code that issues
secure monitor ("smc") requests for the bcm281xx and bcm21664 SoC
families. This code is currently used only for enabling the level-2
cache.
There are some bug fixes and other improvements. An assembly
language file containing a si
These source files contain only level-2 cache initialization code,
so rename them to make that fact more obvious.
Signed-off-by: Alex Elder
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
Reviewed-by: Matt Porter
---
arch/arm/mach-bcm/Makefile|2 +-
arch/arm/mach-bcm
This patch uses dev_err/info function to show accurate log message with device
name
instead of pr_err/info function.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
drivers/cpufreq/exynos-cpufreq.c | 21 -
drivers/cpufreq/exynos-cpufreq.h | 1 +
2 files changed, 13
This patch add new Exynos3250 cpufreq driver to support DVFS (Dynamic Voltage
Frequency Scaling). Exynos3250 uses the Cortex-A7 dual cores and has a target
speed of 1.0 GHz. Exynos3250 cpufreq driver has range from 100MHz to 1000MHz.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
drive
This patchset support cpufreq driver for Exynos3250 which uses the Cortex-A7
dual cores and has a target speed of 1.0 GHz and code clean using dev_err/info
instead of pr_err/info function.
This patchset has a dependency on following patchset[1] to support Exynos3250:
[1] https://lkml.org/lkml/2014
Hi Chao,
How about this?
---
fs/f2fs/f2fs.h | 1 +
fs/f2fs/node.c | 6 --
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 55152de..556d06b 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@ -244,6 +244,7 @@ static inline void set_raw_exte
Linux backports [0] backports-v3.15-rc1 is out [1]. Please
go test and see if you can and break things or if see if
we've broken anything so far before a final release in
sync with Linus' releases. As usual development only happens
on the master branch, we'll then carry fixes onto the stable
branch
Linux backports [0] backports-v3.14-1 is out [1]. Thanks for Hauke
for taking the torch while I was in limbo. The release obviously
has all the things that upstream has so there's no point in mentioning
any of that, but new drivers are igb, added by Stefan. This release
also has a new backports-upd
Hi,
This was already resolved by Jingoo Han.
Thanks,
2014-04-17 (목), 18:01 +0200, Fabian Frederick:
> recover_inline_xattr is only used in node.c
>
> Cc: Jaegeuk Kim
> Cc: Andrew Morton
> Signed-off-by: Fabian Frederick
> ---
> fs/f2fs/node.c | 2 +-
> 1 file changed, 1 insertion(+), 1 delet
Hi, Stable reviewers
This patch is not included in any upstream kernel, so it might not follow the
stable rule.
If you think you need more information, please ignore this message.
This urgent fix is sent here for people who are monitoring stable and seeking
for this fix.
Thanks and best regards
Note that this patch is only used for stable kernels, upstream kernels
will have this problem fixed in ACPICA 201303-04 release. So upstream
kernels shouldn't merge this commit.
It is reported that there are buggy BIOSes in the world: AMI uses a XSDt
compiler for early BIOSes, this compiler will
3 new linux backports release are now available based on linux-next
tags next-20140320 [0] next-20140411 [1] and next-20140417 [2]. This
should mean that we can keep things in synch now almost daily, and
drivers can be tested with the latest code as-is on linux-next. We've
shaved off k
On 04/17/2014 01:40 PM, Raghavendra K T wrote:
On 04/17/2014 10:53 PM, Konrad Rzeszutek Wilk wrote:
On Thu, Apr 17, 2014 at 11:03:52AM -0400, Waiman Long wrote:
v8->v9:
- Integrate PeterZ's version of the queue spinlock patch with some
modification:
http://lkml.kernel.org/r/2014031
On 04/17/2014 01:23 PM, Konrad Rzeszutek Wilk wrote:
On Thu, Apr 17, 2014 at 11:03:52AM -0400, Waiman Long wrote:
v8->v9:
- Integrate PeterZ's version of the queue spinlock patch with some
modification:
http://lkml.kernel.org/r/20140310154236.038181...@infradead.org
- Break the m
On 04/17/2014 12:36 PM, Peter Zijlstra wrote:
On Thu, Apr 17, 2014 at 11:03:58AM -0400, Waiman Long wrote:
There is a problem in the current trylock_pending() function. When the
lock is free, but the pending bit holder hasn't grabbed the lock&
cleared the pending bit yet, the trylock_pending()
From: "Luis R. Rodriguez"
This is a wrapper for folks which by work on git trees, specifically
the linux kernel with lots of files and with random task Cocci files.
The assumption is all you need is multithreaded support and currently only
a shell script is lying around, but that isn't easily ext
The default size for shmmax is, and always has been, 32Mb.
Today, this value is rather small, making users have to
increase it via sysctl, which can cause unnecessary work and
userspace application workarounds. Ie:
http://rhaas.blogspot.com/2012/06/absurd-shared-memory-limits.html
Unix has histor
From: "Luis R. Rodriguez"
Don't rely on driver files or other headers having this file included.
CC: Alexander Smirnov
Cc: Dmitry Eremin-Solenikov
Cc: linux-zigbee-de...@lists.sourceforge.net
Signed-off-by: Luis R. Rodriguez
---
include/net/6lowpan.h | 1 +
1 file changed, 1 insertion(+)
di
From: "Luis R. Rodriguez"
CC: Alexander Smirnov
Cc: Dmitry Eremin-Solenikov
Cc: linux-zigbee-de...@lists.sourceforge.net
Signed-off-by: Luis R. Rodriguez
---
net/ieee802154/reassembly.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/ieee802154/reassembly.c b/net/ieee8
From: "Luis R. Rodriguez"
This will simplify the new reassembly backport
with no code changes being required.
CC: Alexander Smirnov
Cc: Dmitry Eremin-Solenikov
Cc: linux-zigbee-de...@lists.sourceforge.net
Cc: David S. Miller"
Cc: net...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-
Here's a few changes that can help automate the backport of 6lowpan.
I've been carrying them around for a while, I think its best to just
merge these upstream as its nothing controversial.
Luis R. Rodriguez (3):
6lowpan: add helper to get 6lowpan namespace
6lowpan: make lowpan_cb static
6low
This patch fix the offset of CPU boot address and don't need to send smc call
of SMC_CMD_CPU1BOOT command for secondary CPU boot because Exynos3250 removes
WFE in secure mode.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
arch/arm/mach-exynos/firmware.c | 10 --
1 file changed
This patch decide proper lowpower mode of either a15 or a9 according to own ID
from Main ID register.
Cc: Arnd Bergmann
Cc: Marc Zynigier
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
arch/arm/mach-exynos/hotplug.c | 19 ---
1 file changed, 12 insertions(+), 7 deleti
The Exynos3250 clocks are statically listed and registered using the
Samsung specific common clock helper functions. Both device tree based
clock lookup and clkdev based clock lookups are supported.
Cc: Mike Turquette
Cc: Kukjin Kim
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Camp
From: Kyungmin Park
This patch fix the offset of CPU boot address and change parameter of smc call
of SMC_CMD_CPU1BOOT command for Exynos4212.
Signed-off-by: Kyungmin Park
Signed-off-by: Chanwoo Choi
---
arch/arm/mach-exynos/firmware.c | 15 ++-
1 file changed, 14 insertions(+), 1
Hey again,
> [ninez@localhost ~]$ (cat /proc/meminfo ; cat /proc/meminfo) | grep
> KernelStack
> KernelStack:3728 kB
> KernelStack:3728 kB
> [ninez@localhost ~]$ (cat /proc/meminfo ; cat /proc/meminfo) | grep
> KernelStack
> KernelStack:3696 kB
> KernelStack:369
From: Tomasz Figa
This patch add new the clock drvier of Exynos3250 SoC based on Cortex-A7
using common clock framework. The CMU (Clock Management Unit) of Exynos3250
control PLLs(Phase Locked Loops) and generate system clocks for CPU, buses,
and function clocks for individual IPs.
The CMU of Ex
From: Tomasz Figa
This patch add new exynos3250.dtsi to support Exynos3250 SoC based on Cortex-A7
dual core and includes following dt nodes:
- GIC interrupt controller
- Pinctrl to control GPIOs
- Clock controller
- CPU information (Cortex-A7 dual core)
- UART to support serial port
- MCT (Multi
This patch add Exynos3250's SoC ID. Exynos 3250 is System-On-Chip(SoC) that
is based on the 32-bit RISC processor for Smartphone. Exynos3250 uses Cortex-A7
dual cores and has a target speed of 1.0GHz.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
---
arch/arm/mach-exynos/Kconfig
This patchset support new Exynos3250 Samsung SoC based on Cortex-A7 dual core.
Exynos3250 is a System-On-Chip (SoC) that is based on 32-bit RISC processor
for Smartphone. It is desigend with the 28nm low-power high-K metal gate process
and provides the best performance features.
This patchset incl
On 04/17 21:31, Tejun Heo wrote:
> On Thu, Apr 17, 2014 at 09:48:03AM +0200, Hans de Goede wrote:
>>> Hmmm this should work but looks a bit tedious and it could be
>>> better to have a better mechanism to match devices to their
>>> port_infos. Hans, can you please comment? If getting somethin
On Fri, Apr 18, 2014 at 01:37:26AM +0100, Al Viro wrote:
> IOW, workqueue is not the right tool here. OTOH, it looks like we do have
> a problem with kernel/acct.c vs. umount; it just requires a race between
> auto-closing and acct_process_in_ns(). It's narrow, so it doesn't bite
> us all the tim
Free the vd (virt descriptor) after the callback is called. In EDMA driver
atleast which uses virt-dma, we make use of the desc during the callback and if
its dangerously freed before the callback is called. I also noticed this in
omap-dma dmaengine driver.
Cc: Vinod Koul
Cc: Dan Williams
Cc: R
Attn;
We have concluded to effect your payment- through-Money Gram $5,000 daily
until the$1.5million US is completely transferred to you accordingly. Though,
Director Dr. Richard chris has sent $5,000 in your name today so contact Money
Gram Agent:below with your full Name,phone contact and addres
Switch the common SDHCI code over to use mmc_host's regulator pointers
and remove the ones in the sdhci_host structure.
Signed-off-by: Tim Kryger
---
drivers/mmc/host/sdhci.c | 71 -
include/linux/mmc/sdhci.h |3 --
2 files changed, 38 insertion
This series updates SDHCI to use the common regulator infrastructure that mmc
core provides.
Tim Kryger (2):
mmc: sdhci: Use supplies in common mmc_host struct
mmc: sdhci: Use common mmc_regulator_get_supply
drivers/mmc/host/sdhci.c | 96 +
incl
Replace some buggy code with a call to mmc_regulator_get_supply.
When external regulator provides VDD, ocr_avail is set directly based on
the supported voltage range. This allows for the use of regulators that
can't provide exactly 1.8v, 3.0v, or 3.3v. Commit cec2e21 had attempted
to address thi
On Thu, Apr 17, 2014 at 12:41 PM, Leif Lindholm
wrote:
> drivers/of/fdt.c contains a workaround for a missing memory type
> entry on longtrail firmware. Make that quirk PPC32 only, and while
> at it - fix up the .dts files in the tree currently working only
> because of that quirk.
But why do you
On 03/22/14 23:55, beh...@converseincode.com wrote:
From: Mark Charlebois
Replaced non-standard C use of Variable Length Arrays In Structs (VLAIS) in
xt_repldata.h with a C99 compliant flexible array member and then calculated
offsets to the other struct members. These other members aren't refe
According to Intel specifications, PAE and non-PAE does not have any reserved
bits. In long-mode, regardless to PCIDE, only the high bits (above the
physical address) are reserved.
Signed-off-by: Nadav Amit
---
:100644 100644 7de069af.. e21aee9... M arch/x86/include/asm/kvm_host.h
:100644 10064
The IN instruction is not be affected by REP-prefix as INS is. Therefore, the
emulation should ignore the REP prefix as well. The current emulator
implementation tries to perform writeback when IN instruction with REP-prefix
is emulated. This causes it to perform wrong memory write or spurious #G
On Thu, Apr 17, 2014 at 11:12:03PM +0100, Al Viro wrote:
> That's all. And yes, I believe that such series would make sense on its
> own and once it survives beating (see above about docker - that bastard has
> surprised me quite a bit re stressing namespace-related codepaths), I would
> be quite
If a guest enables a performance counter but does not enable PMI, the
hypervisor currently does not reprogram the performance counter once it
overflows. As a result the host performance counter is kept with the original
sampling period which was configured according to the value of the guest's
cou
Use the resource-managed extcon device register function (i.e.
devm_extcon_dev_register()) instead of extcon_dev_register(). If extcon device
is attached with this function, that extcon device is automatically unregistered
on driver detach. That reduces tiresome managing code.
Signed-off-by: Sangj
Use the resource-managed extcon device register function (i.e.
devm_extcon_dev_register()) instead of extcon_dev_register(). If extcon device
is attached with this function, that extcon device is automatically unregistered
on driver detach. That reduces tiresome managing code.
Signed-off-by: Sangj
Use the resource-managed extcon device register function (i.e.
devm_extcon_dev_register()) instead of extcon_dev_register(). If extcon device
is attached with this function, that extcon device is automatically unregistered
on driver detach. That reduces tiresome managing code.
Signed-off-by: Sangj
Use the resource-managed extcon device register function (i.e.
devm_extcon_dev_register()) instead of extcon_dev_register(). If extcon device
is attached with this function, that extcon device is automatically unregistered
on driver detach. That reduces tiresome managing code.
Signed-off-by: Sangj
These patches add resource-managed extcon device register functions for
developers' convenience and apply them to related device driver files.
This work can make the code more tidy since extcon device is automatically
unregistered on driver detach so tiresome managing codes could be removed.
Chan
Add resource-managed extcon device register function for convenience.
For example, if a extcon device is attached with new
devm_extcon_dev_register(), that extcon device is automatically
unregistered on driver detach.
Signed-off-by: Sangjung Woo
---
drivers/extcon/extcon-class.c | 72 +
Use the resource-managed extcon device register function (i.e.
devm_extcon_dev_register()) instead of extcon_dev_register(). If extcon device
is attached with this function, that extcon device is automatically unregistered
on driver detach. That reduces tiresome managing code.
Signed-off-by: Sangj
Use the resource-managed extcon device register function (i.e.
devm_extcon_dev_register()) instead of extcon_dev_register(). If extcon device
is attached with this function, that extcon device is automatically unregistered
on driver detach. That reduces tiresome managing code.
Signed-off-by: Sangj
Use the resource-managed extcon device register function (i.e.
devm_extcon_dev_register()) instead of extcon_dev_register(). If extcon device
is attached with this function, that extcon device is automatically unregistered
on driver detach. That reduces tiresome managing code.
Signed-off-by: Sangj
1 - 100 of 715 matches
Mail list logo
