Implement the new barriers; as per the old versions the metag atomic
imply a full barrier.
Signed-off-by: Peter Zijlstra
---
arch/metag/include/asm/atomic.h |6 +-
arch/metag/include/asm/barrier.h |3 +++
arch/metag/include/asm/bitops.h |6 --
3 files changed, 4 insertions(
Implement the new smp_mb__* ops as per the old ones.
Signed-off-by: Peter Zijlstra
---
arch/tile/include/asm/atomic_32.h | 10 --
arch/tile/include/asm/atomic_64.h |6 --
arch/tile/include/asm/barrier.h | 14 ++
arch/tile/include/asm/bitops.h|1 +
arch/t
MIPS is interesting and has hardware variants that reorder over ll/sc
as well as those that do not.
Implement the 2 new barrier functions as per the old barriers.
Signed-off-by: Peter Zijlstra
---
arch/mips/include/asm/atomic.h |9 -
arch/mips/include/asm/barrier.h |3 +++
arch
mn10300 fully relies on asm-generic/barrier.h and therefore its
smp_mb() is barrier(). We can use the default implementation.
Signed-off-by: Peter Zijlstra
---
arch/mn10300/include/asm/atomic.h |7 +--
arch/mn10300/include/asm/bitops.h |4 +---
arch/mn10300/mm/tlb-smp.c |
As per the existing implementation; implement the new one using
smp_mb().
AFAICT the s390 compare-and-swap does imply a barrier, however there
are some immediate ops that seem to be singly-copy atomic and do not
imply a barrier. One such is the "ni" op (which would be
and-immediate) which is used
Update the documentation to reflect the change of barrier primitives.
Signed-off-by: Peter Zijlstra
---
Documentation/atomic_ops.txt | 31 ++
Documentation/memory-barriers.txt | 44 ++
2 files changed, 24 insertions(+), 51 dele
m68k uses asm-generic/barrier.h and its smp_mb() is barrier(),
therefore we can use the generic versions that use smp_mb().
Signed-off-by: Peter Zijlstra
---
arch/m68k/include/asm/atomic.h |8 +---
arch/m68k/include/asm/bitops.h |7 +--
2 files changed, 2 insertions(+), 13 deleti
The arc mb() implementation is a compiler barrier(), therefore it all
doesn't matter one way or the other. Simply remove the existing
definitions and use whatever is generated by the defaults.
Signed-off-by: Peter Zijlstra
---
arch/arc/include/asm/atomic.h |5 -
arch/arc/include/asm/bito
M32r uses asm-generic/barrier.h and its smp_mb() is barrier();
therefore we can use the generic versions which default to smp_mb().
Signed-off-by: Peter Zijlstra
---
arch/m32r/include/asm/atomic.h |7 +--
arch/m32r/include/asm/bitops.h |6 ++
2 files changed, 3 insertions(+), 10
sparc32: fully relies on asm-generic/barrier.h and thus can use its
implementation.
sparc64: is strongly ordered and its atomic ops imply a full barrier,
implement the new primitives using barrier().
Signed-off-by: Peter Zijlstra
---
arch/sparc/include/asm/atomic_32.h |7
Xtensa SMP has ll/sc which is fully serializing, therefore its exising
smp_mb__{before,after}_clear_bit() appear unduly heavy.
Implement the new barriers are barrier().
Signed-off-by: Peter Zijlstra
---
arch/xtensa/include/asm/atomic.h |7 +--
arch/xtensa/include/asm/barrier.h |3 +
Since the smp_mb__{before,after}*() ops are fundamentally dependent on
how an arch can implement atomics it doesn't make sense to have 3
variants of them. They must all be the same.
Furthermore, the 3 variants suggest they're only valid for those 3
atomic ops, while we have many more where they co
Powerpc allows reordering over its ll/sc implementation. Implement the
two new barriers as appropriate.
Signed-off-by: Peter Zijlstra
---
arch/powerpc/include/asm/atomic.h |6 +-
arch/powerpc/include/asm/barrier.h |3 +++
arch/powerpc/include/asm/bitops.h |6 +-
arch/powerp
parisc fully relies on asm-generic/barrier.h, therefore its smp_mb()
is barrier and the default implementation suffices.
Signed-off-by: Peter Zijlstra
---
arch/parisc/include/asm/atomic.h |6 +-
arch/parisc/include/asm/bitops.h |4 +---
2 files changed, 2 insertions(+), 8 deletions(-
score fully relies on asm-generic/barrier.h, so it can use its default
implementation.
Signed-off-by: Peter Zijlstra
---
arch/score/include/asm/bitops.h |7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
--- a/arch/score/include/asm/bitops.h
+++ b/arch/score/include/asm/bitops.h
@@
x86 is strongly ordered and all its atomic ops imply a full barrier.
Implement the two new primitives as the old ones were.
Signed-off-by: Peter Zijlstra
---
arch/x86/include/asm/atomic.h |7 +--
arch/x86/include/asm/barrier.h |4
arch/x86/include/asm/bitops.h |
AARGH64 uses ll/sc primitives that do not imply any barriers for the
normal atomics, therefore smp_mb__{before,after} should be a full
barrier.
Since AARGH64 doesn't use asm-generic/barrier.h, add the required
definitions to its asm/barrier.h.
Signed-off-by: Peter Zijlstra
---
arch/arm64/includ
c6x doesn't have a barrier.h and completely relies on
asm-generic/barrier.h. Therefore its smp_mb() is barrier() and we can
use the default versions that are smp_mb().
Signed-off-by: Peter Zijlstra
---
arch/c6x/include/asm/bitops.h |8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
ia64 atomic ops are full barriers; implement the new
smp_mb__{before,after}_atomic().
Signed-off-by: Peter Zijlstra
---
arch/ia64/include/asm/atomic.h |7 +--
arch/ia64/include/asm/barrier.h |3 +++
arch/ia64/include/asm/bitops.h |6 ++
3 files changed, 6 insertions(+), 10
Blackfin's atomic primitives do not imply a full barrier as whitnessed
from its SMP smp_mb__{before,after}_clear_bit() implementations.
However since !SMP smp_mb() reduces to barrier() remove everything and
rely on the asm-generic/barrier.h implentation.
Signed-off-by: Peter Zijlstra
---
arch/b
SH can use the asm-generic/barrier.h implementation since that uses
smp_mb().
Signed-off-by: Peter Zijlstra
---
arch/sh/include/asm/atomic.h |6 +-
arch/sh/include/asm/bitops.h |7 +--
2 files changed, 2 insertions(+), 11 deletions(-)
--- a/arch/sh/include/asm/atomic.h
+++ b/arc
ARM uses ll/sc primitives that do not imply barriers for all regular
atomic ops, therefore smp_mb__{before,after} need be a full barrier.
Since ARM doesn't use asm-generic/barrier.h include the required
definitions in its asm/barrier.h
Signed-off-by: Peter Zijlstra
---
arch/arm/include/asm/atom
Cris fully relies on asm-generic/barrier.h, therefore its smp_mb() is
barrier(), thus we can use the default implementation that uses
smp_mb().
Signed-off-by: Peter Zijlstra
---
arch/cris/include/asm/atomic.h |7 +--
arch/cris/include/asm/bitops.h |9 ++---
2 files changed, 3 ins
Openrisc fully relies on asm-generic/barrier.h and therefore its
smp_mb() is barrier().
Signed-off-by: Peter Zijlstra
---
arch/openrisc/include/asm/bitops.h |9 +
1 file changed, 1 insertion(+), 8 deletions(-)
--- a/arch/openrisc/include/asm/bitops.h
+++ b/arch/openrisc/include/asm/
Both already use asm-generic/barrier.h as per their
include/asm/Kbuild. Remove the stale files.
Signed-off-by: Peter Zijlstra
---
arch/arc/include/asm/barrier.h | 37 -
arch/hexagon/include/asm/barrier.h | 37 -
2 fi
* Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 0afd2d51029961281572d02545c7bde1b3f4292c:
>
> Merge tag 'perf-core-for-mingo' of
> git://git.kernel.org/pub/scm/linux/k
Hi all,
Here's a respin (and per arch breakout) of the first 3 patches that spawned
this large C11 atomics thread.
These patches deprecate smp_mb__{before,after}_{atomic_{inc,dec},clear_bit}()
and replace it by just the two smp_mb__{before,after}_atomic().
Assuming people like this; how would we
AVR32's mb() implementation is a compiler barrier(), therefore it all
doesn't matter, fully rely on whatever asm-generic/barrier.h
generates.
Signed-off-by: Peter Zijlstra
---
arch/avr32/include/asm/atomic.h |5 -
arch/avr32/include/asm/bitops.h |9 ++---
2 files changed, 2 inser
On 18.03.2014 23:25, Arnaldo Carvalho de Melo wrote:
> From: Don Zickus
>
> Now that we can properly synthesize threads system-wide, make sure the
> mmap and mmap2 events use tids instead of pids to locate their maps.
This is a good change but it cannot go yet because it is dependent on Jiri's
"
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140318:
The powerpc tree still had its build failure.
The net-next tree lost 2 of its another build failures.
The wireless-next tree lost its build failure but gained another for
which I reverted 2
On Wed, Mar 19, 2014 at 2:54 AM, Ben Widawsky wrote:
> On Tue, Mar 18, 2014 at 09:18:42PM -0400, Steven Rostedt wrote:
>> On Wed, 19 Mar 2014 11:53:50 +1100
>> Stephen Rothwell wrote:
>>
>>
>> > Caused by commit a25ca17c1eac ("drm/i915: Do not dereference pointers
>> > from ring buffer in evict e
On Wed, Mar 5, 2014 at 8:25 PM, Markus Mayer wrote:
> Since sdhci_bcm_kona_sd_card_emulate() can be called from interrupt
> context, we must use a spinlock instead of a mutex. This change
> essentially restores the way things worked before the change to
> mutexes in http://www.spinics.net/lists/li
Correct passing parameter sequence, which will avoid the id of
fix screen info is overwritten.
Signed-off-by: Bo Shen
---
drivers/video/atmel_lcdfb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/atmel_lcdfb.c b/drivers/video/atmel_lcdfb.c
index cd96162..695f2
On Tue, 2014-03-18 at 17:16 -0700, Mike Turquette wrote:
> Quoting Krzysztof Kozlowski (2014-03-17 02:19:16)
> > This patch adds support for S2MPS14 PMIC clocks (BT and AP) to the
> > s2mps11 clock driver.
> >
> > Signed-off-by: Krzysztof Kozlowski
> > Reviewed-by: Yadwinder Singh Brar
> > Revie
Am Montag, 17. März 2014, 08:34:06 schrieb Stephan Mueller:
> +static int drbg_seed(struct drbg_state *drbg, struct drbg_string *pers,
> + bool reseed)
> +{
> + int ret = 0;
> + unsigned char *entropy = NULL;
> + size_t entropylen = 0;
> + struct drbg_string data1;
Dear Greg,
This is extcon-next full request for v3.15. I add detailed description of this
pull request on below. Please pull extcon with following updates.
This patchset is rebased on 'Linux 3-14-rc5' because char-misc-next is based on
'Linux 3-14-rc5'.
Best Regards,
Chanwoo Choi
The following
On Wed, Mar 19, 2014 at 11:08:20AM +0800, Ming Lei wrote:
> > + blk_rq_init(q, q->flush_rq);
> > + if (reg->cmd_size)
> > + q->flush_rq->special =
> > + blk_mq_rq_to_pdu(q->flush_rq);
> > +
> > + if (reg->
On Wed, Mar 19, 2014 at 01:22:07PM +0800, Ming Lei wrote:
> exit_request definition is missed.
oops that accidentally went into another commit.
New version below:
---
From: Christoph Hellwig
Subject: blk-mq: add a exit_request method
This gives drivers an easy way to free any ressources alloca
It doesn't need to trace status of buffer when buffers are
allocated/deallocated. So stuff of tracing memory status
are removed. And also UISMALLOC/UISFREE macro are removed
completetly. just use kzalloc/kfree.
Signed-off-by: Daeseok Youn
---
drivers/staging/unisys/include/uisutils.h |6 --
The NM_WOUT_THRESHOLD is now obsolete since f2fs starts to control on a basis
of the memory footprint.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/debug.c | 8
fs/f2fs/node.c | 5 +
fs/f2fs/node.h | 3 ---
3 files changed, 5 insertions(+), 11 deletions(-)
diff --git a/fs/f2fs/debug.c
The try_to_free_nats should not receive the negative nr_shrink.
Otherwise, it can drop all the nat entries by the while loop.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/node.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index 707fd20..04450a5 1
This patch adds missing dir_level documentation.
Signed-off-by: Jaegeuk Kim
---
Documentation/ABI/testing/sysfs-fs-f2fs | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-fs-f2fs
b/Documentation/ABI/testing/sysfs-fs-f2fs
index 4ac2c25..62dd725 100644
--- a
It is more reasonable to determine the reclaiming rate of prefree segments
according to the volume size, which is set to 5% by default.
For example, if the volume is 128GB, the prefree segments are reclaimed
when the number reaches to 6.4GB.
Signed-off-by: Jaegeuk Kim
---
Documentation/filesyste
This patch introduces ram_thresh, a sysfs entry, which controls the memory
footprint used by the free nid list and the nat cache.
Previously, the free nid list was controlled by MAX_FREE_NIDS, while the nat
cache was managed by NM_WOUT_THRESHOLD.
However, this approach cannot be applied dynamicall
On 18 March 2014 18:09, Mark Brown wrote:
> On Tue, Mar 18, 2014 at 03:53:02PM +0530, Sachin Kamat wrote:
>> Silences the following type of error/warnings:
>> ERROR: that open brace { should be on the previous line
>> WARNING: Missing a blank line after declarations
>
> Applied, but...
>
>> -
Remove unused code under C99 comment style
Signed-off-by: Mathieu Maret
---
drivers/staging/wlags49_h2/wl_netdev.c | 38 --
1 file changed, 38 deletions(-)
diff --git a/drivers/staging/wlags49_h2/wl_netdev.c
b/drivers/staging/wlags49_h2/wl_netdev.c
index ae42c8e
Remove space between parenthesis.
Test with simple statement does not need brackets.
Simplify test condition
Signed-off-by: Mathieu Maret
---
drivers/staging/wlags49_h2/wl_netdev.c | 29 +++--
1 file changed, 11 insertions(+), 18 deletions(-)
diff --git a/drivers/staging
Code is using C99 code style, so change them to kernel style
Signed-off-by: Mathieu Maret
---
drivers/staging/wlags49_h2/wl_netdev.c | 158 +++--
1 file changed, 89 insertions(+), 69 deletions(-)
diff --git a/drivers/staging/wlags49_h2/wl_netdev.c
b/drivers/staging/
Multi statement macro should use do{}while(0)
Signed-off-by: Mathieu Maret
---
drivers/staging/wlags49_h2/wl_netdev.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/wlags49_h2/wl_netdev.c
b/drivers/staging/wlags49_h2/wl_netdev.c
index 255d291..645595
On Tue, Mar 11, 2014 at 06:09:16PM +0800, Dongsheng Yang wrote:
> As the task nice value is in [-20, 19] and the io priority is in [0, 7],
> and the convert method from niceval to ioprio is implemented with an
> opened code in task_nice_ioprio().
>
> This patch move the implementation to a macro N
On 18 March 2014 18:41, Krzysztof Kozlowski wrote:
> Initialize the 'regmap_rtc' on S2MPA01 to some sane value. Sane at least
> for S5M87X chipsets, not S2MPS/S2MPA but it won't be used because
> rtc-s5m driver does not support S2MPA01.
>
> This fixes following error:
> drivers/mfd/sec-core.c:342:
On 19/03/14 02:48, Alexandre Courbot wrote:
On Tue, Mar 18, 2014 at 7:41 PM, Ben Dooks wrote:
Some of the gpiod_ calls take a pointer to a gpio_desc as their
argument but only check to see if it is NULL to validate the
input.
Calls such as devm_gpiod_get() return an error-pointer if they
fail,
I picked up all except:
2 - whcih I don't think should go through a scheduler tree
6 - its tools/ bits, the changelog wasn't clear if the MIN/MAX_NICE
macros were uapi visible and I couldn't be bothered to figure it out.
8 - I don't like the pointless macro
--
To unsubscribe from this l
> On 18 March 2014 18:27, Krzysztof Kozlowski wrote:
> > Dummy I2C device allocated in sec_pmic_probe() leaked if
> > devm_regmap_init_i2c() failed. Unregister it before returning from
> > probe.
> >
> > Signed-off-by: Krzysztof Kozlowski
>
> Looks good.
> Reviewed-by: Sachin Kamat
Applied wit
On Wed, Mar 19, 2014 at 5:33 PM, Ben Dooks wrote:
> On 19/03/14 02:48, Alexandre Courbot wrote:
>>
>> On Tue, Mar 18, 2014 at 7:41 PM, Ben Dooks
>> wrote:
>>>
>>> Some of the gpiod_ calls take a pointer to a gpio_desc as their
>>> argument but only check to see if it is NULL to validate the
>>> i
Hi Boris,
2014-03-18 21:18 GMT+01:00 Boris BREZILLON :
>
> Hello,
>
> This series introduce the real clock model (as described in atmel datasheets)
> for slow and main clocks.
>
> The modifications introduced by this series break the DT compat, but, as the
> at91 CCF based implementation is prett
On Wed, 2014-03-19 at 13:57 +0530, Sachin Kamat wrote:
> On 18 March 2014 18:41, Krzysztof Kozlowski wrote:
> > Initialize the 'regmap_rtc' on S2MPA01 to some sane value. Sane at least
> > for S5M87X chipsets, not S2MPS/S2MPA but it won't be used because
> > rtc-s5m driver does not support S2MPA01
On Tue, 18 Mar 2014 16:46:24 +0530, Sachin Kamat wrote:
> On 18 March 2014 16:44, Cho KyongHo wrote:
> > On Fri, 14 Mar 2014 20:57:42 +0530, Sachin Kamat wrote:
> >> Hi KyongHo,
> >>
> >> On 14 March 2014 10:39, Cho KyongHo wrote:
> >> >
> >> > -static struct platform_driver exynos_sysmmu_driver
On Tue, Mar 18, 2014 at 04:56:42PM +0800, Yan, Zheng wrote:
> export __hrtimer_start_range_ns() to allow building perf Intel uncore
> driver as module
Bah; you didn't cc the hrtimer maintainer.
Thomas, ack on this?
> Signed-off-by: Yan, Zheng
> ---
> kernel/hrtimer.c | 1 +
> 1 file changed, 1
On Tue, Mar 18, 2014 at 04:56:44PM +0800, Yan, Zheng wrote:
> This patch adds support for building Intel uncore driver as module.
> It adds clean-up code and config option for the Intel uncore driver
>
> Signed-off-by: Yan, Zheng
> ---
> arch/x86/Kconfig | 7
>
On Wed, Mar 19, 2014 at 3:54 PM, Christoph Hellwig wrote:
> On Wed, Mar 19, 2014 at 11:08:20AM +0800, Ming Lei wrote:
>> > + blk_rq_init(q, q->flush_rq);
>> > + if (reg->cmd_size)
>> > + q->flush_rq->special =
>> > + b
On Tue, 18 Mar 2014, Bryan Wu wrote:
> On Tue, Mar 18, 2014 at 2:40 AM, Lee Jones wrote:
> >> > > > > Signed-off-by: Alexander Shiyan
> >> > > > > ---
> >> > > > > include/linux/mfd/mc13xxx.h | 22 --
> >> > > > > 1 file changed, 12 insertions(+), 10 deletions(-)
> >> > > >
On Wed, 19 Mar 2014 08:59:09 +0900, Jingoo Han wrote:
> On Wednesday, March 19, 2014 12:12 AM, Tomasz Figa wrote:
> > On 18.03.2014 11:38, Cho KyongHo wrote:
> > > On Fri, 14 Mar 2014 14:28:36 +0100, Tomasz Figa wrote:
> > >> On 14.03.2014 06:05, Cho KyongHo wrote:
> > >>> This patch uses managed d
On Tue, 18 Mar 2014 16:14:53 +0100, Tomasz Figa wrote:
> On 18.03.2014 12:09, Cho KyongHo wrote:
> > On Fri, 14 Mar 2014 20:52:43 +0530, Sachin Kamat wrote:
> >> Hi KyongHo,
> >>
> >> On 14 March 2014 10:35, Cho KyongHo wrote:
> >>> This patch uses managed device helper functions in the probe().
>
On 19 March 2014 14:29, Cho KyongHo wrote:
> On Tue, 18 Mar 2014 16:14:53 +0100, Tomasz Figa wrote:
>> On 18.03.2014 12:09, Cho KyongHo wrote:
>> > On Fri, 14 Mar 2014 20:52:43 +0530, Sachin Kamat wrote:
>> >> Hi KyongHo,
>> >>
>> >> On 14 March 2014 10:35, Cho KyongHo wrote:
>> >>> This patch us
This patch adds device tree binding documentation for the Dialog Semiconductors
DA9063 PMIC and its regulator nodes.
Signed-off-by: Philipp Zabel
---
.../devicetree/bindings/mfd/da9063-i2c.txt | 68 ++
1 file changed, 68 insertions(+)
create mode 100644 Documentation
Wed, 19 Mar 2014 08:51:44 + от Lee Jones :
> On Tue, 18 Mar 2014, Bryan Wu wrote:
>
> > On Tue, Mar 18, 2014 at 2:40 AM, Lee Jones wrote:
> > >> > > > > Signed-off-by: Alexander Shiyan
> > >> > > > > ---
> > >> > > > > include/linux/mfd/mc13xxx.h | 22 --
> > >> > > > >
On Tue, 18 Mar 2014 16:25:11 +0100, Tomasz Figa wrote:
> On 18.03.2014 11:52, Cho KyongHo wrote:
> > On Fri, 14 Mar 2014 14:39:33 +0100, Tomasz Figa wrote:
> >>> @@ -557,11 +558,23 @@ static int exynos_sysmmu_probe(struct
> >>> platform_device *pdev)
> >>> return 0;
> >>>}
> >>>
> >>
> tps65910_irq_init() sets the 'tps65910->chip_irq' before calling
> regmap_add_irq_chip(). If this regmap_add_irq_chip() call fails in
> memory allocation of regmap_irq_chip_data members then:
> 1. The 'tps65910->chip_irq' will still hold some value;
> 2. 'tps65910->irq_data' will be pointing to a
> The tps65910_i2c_probe() allocates regmap_irq_chip in
> tps65910_irq_init() but it does not clean this up in case of
> mfd_add_devices() failure.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/mfd/tps65910.c |1 +
> 1 file changed, 1 insertion(+)
Applied, thanks.
--
Lee Jones
Li
On Tue, 18 Mar 2014 16:33:04 +0100, Tomasz Figa wrote:
> On 18.03.2014 12:23, Cho KyongHo wrote:
> > On Fri, 14 Mar 2014 17:07:53 +0100, Tomasz Figa wrote:
> >> Hi KyongHo,
> >>
> >> On 14.03.2014 06:10, Cho KyongHo wrote:
>
> [snip]
>
> >>> @@ -677,11 +679,40 @@ static int __init exynos_sysmmu_p
On Tue, Mar 18, 2014 at 05:44:30PM +, Mark Brown wrote:
> On Tue, Mar 18, 2014 at 05:22:31PM +, Charles Keepax wrote:
>
> > - /*
> > -* LDO1 can only be used to supply DCVDD so if it has no
> > -* consumers then DCVDD is supplied externally.
> > -*/
> > - if (arizona->pdata
Hi Neil,
On 03/18/2014 11:24 PM, NeilBrown wrote:
> On Tue, 18 Mar 2014 13:37:15 +0100 "Michael Kerrisk (man-pages)"
> wrote:
>
>> On 03/18/2014 10:43 AM, Christoph Hellwig wrote:
>>> On Tue, Mar 18, 2014 at 09:00:07AM +1100, NeilBrown wrote:
ESTALE is also returned if the filesystem does n
[CC =+ Al Viro]
Hi Neil,
On 03/19/2014 05:13 AM, NeilBrown wrote:
> On Tue, 18 Mar 2014 13:55:15 +0100 "Michael Kerrisk (man-pages)"
> wrote:
>
>> Hi Aneesh, (and others)
>>
>> After integrating review comments from NeilBown and Christoph Hellwig,
>> here is draft 2 of a man page I've written f
> Initialize the 'regmap_rtc' on S2MPA01 to some sane value. Sane at least
> for S5M87X chipsets, not S2MPS/S2MPA but it won't be used because
> rtc-s5m driver does not support S2MPA01.
>
> This fixes following error:
> drivers/mfd/sec-core.c:342:45: warning: ‘regmap_rtc’ may be used
> uninitiali
On 03/19/2014 11:38 AM, Viresh Kumar wrote:
> On 18 March 2014 18:20, Srivatsa S. Bhat
> wrote:
>> On 03/14/2014 01:13 PM, Viresh Kumar wrote:
>>> + if ((state != CPUFREQ_PRECHANGE) && (state != CPUFREQ_POSTCHANGE))
>>
>> Wait a min, when is this condition ever true? I mean, what else can
>> '
Hi, Sylwester
Thanks for your review.
On 3/15/2014 5:17 AM, Sylwester Nawrocki wrote:
Hi Josh,
On 03/14/2014 11:12 AM, Josh Wu wrote:
+clk = v4l2_clk_get(&client->dev, "mclk");
+if (IS_ERR(clk))
+return -EPROBE_DEFER;
You should instead make it:
return PTR_ERR(clk);
On 19 March 2014 14:47, Srivatsa S. Bhat
wrote:
> Wait, I think I remember. The problem was about dealing with drivers that
> do asynchronous notification (those that have the ASYNC_NOTIFICATION flag
> set). In particular, exynos-5440 driver sends out the POSTCHANGE notification
> from a workqueue
On Wed, 19 Mar 2014, Oliver Hartkopp wrote:
> On 18.03.2014 23:15, Thomas Gleixner wrote:
> > On Tue, 18 Mar 2014, Marc Kleine-Budde wrote:
> >> On 03/18/2014 06:19 PM, Thomas Gleixner wrote:
> >>> +static void c_can_hw_raminit_wait(const struct c_can_priv *priv, u32
> >>> mask,
> >>> +
Hi Peter,
On 03/19/2014 04:36 PM, Peter Zijlstra wrote:
I picked up all except:
2 - whcih I don't think should go through a scheduler tree
I will send it to sys maintainers.
6 - its tools/ bits, the changelog wasn't clear if the MIN/MAX_NICE
macros were uapi visible and I couldn't b
Dear Alessandro Zummo,
I'm humbly reminding myself :). If these patches are OK can I have an
Ack from you so Lee Jones could apply them to MFD tree?
Best regards,
Krzysztof Kozlowski
On Fri, 2014-02-28 at 14:00 +0100, Krzysztof Kozlowski wrote:
> Hi,
>
>
> Few days ago I sent patches adding
On 03/04/2014 01:23 AM, Joonsoo Kim wrote:
> On Mon, Mar 03, 2014 at 12:02:00PM +0100, Vlastimil Babka wrote:
>> On 02/14/2014 07:53 AM, Joonsoo Kim wrote:
>>> changes for v2
>>> o include more experiment data in cover letter
>>> o deal with vlastimil's comments mostly about commit description on 4
2014-03-18 23:59 GMT+09:00, OGAWA Hirofumi :
> Namjae Jeon writes:
>
>> +static void check_fallocated_region(struct inode *inode, sector_t
>> iblock,
>> +unsigned long *max_blocks, struct buffer_head *bh_result)
>> +{
>> +struct super_block *sb = inode->i_sb;
>> +sector_t last_
In consolidated environments, when there are multiple virtual machines (VMs)
running on one CPU core, timekeeping will be a problem to the guest OS.
Here, I report my findings about Linux process scheduler.
Description
Linux CFS relies on rq->clock_task to charge each task, determin
Adding libdw DWARF post unwind support, which is part
of elfutils-devel/libdw-dev package from version 0.158.
Also includes the test suite for dwarf unwinding, by adding the
arch specific test code and the perf_regs_load function.
This series depends on the following kernel patches series:
- AARC
Introducing perf_regs_load function, which is going
to be used for dwarf unwind test in following patches.
It takes single argument as a pointer to the regs dump
buffer and populates it with current registers values, as
expected by the perf built-in unwinding test.
Signed-off-by: Jean Pihet
Cc:
Adding libdw DWARF post unwind support, which is part
of elfutils-devel/libdw-dev package from version 0.158.
Note: the libdw code needs some support for dwarf unwinding
on ARM64, this code is submitted seperately on the elfutils
ML.
The new code is contained in unwin-libdw.c object, and
implemen
Adding dwarf unwind test, that setups live machine data over
the perf test thread and does the remote unwind.
Need to use -fno-optimize-sibling-calls for test compilation,
otherwise 'krava_*' function calls are optimized into jumps
and ommited from the stack unwind.
Cc: Jiri Olsa
Cc: Corey Ashfo
Hello,
this is a small fixup for the patch 5/8 (printk: Hand over printing to
console if printing too long) in my printk series. It fixes a bogus warning
on non-preemptible kernels. Please just fold it into that patch (I can
resend the patch or the series but I don't think that's necessary for
Hi Tomasz,
On 03/19/2014 12:46 AM, Tomasz Figa wrote:
> On 17.03.2014 06:19, Chanwoo Choi wrote:
>> Hi Tomasz,
>>
>> On 03/15/2014 02:35 AM, Tomasz Figa wrote:
>>> Hi Chanwoo, Mark,
>>>
>>> On 14.03.2014 11:56, Chanwoo Choi wrote:
Hi Mark,
On 03/14/2014 07:35 PM, Mark Rutland wrote:
Hello Jean-Christophe,
Le 19/03/2014 07:06, Jean-Christophe PLAGNIOL-VILLARD a écrit :
You must keep me in Cc
I always did, this is an oversight.
first and last warning
Now, this is my turn.
I don't like to be threatened, especially when this message is only sent
to me.
BTW, last warni
On 19/03/2014 08:47, Bo Shen :
> Correct passing parameter sequence, which will avoid the id of
> fix screen info is overwritten.
>
> Signed-off-by: Bo Shen
Acked-by: Nicolas Ferre
Thanks.
> ---
> drivers/video/atmel_lcdfb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -
On 03/19/2014 11:38 AM, Viresh Kumar wrote:
> On 18 March 2014 18:20, Srivatsa S. Bhat
> wrote:
>> On 03/14/2014 01:13 PM, Viresh Kumar wrote:
>>> + if ((state != CPUFREQ_PRECHANGE) && (state != CPUFREQ_POSTCHANGE))
>>
>> Wait a min, when is this condition ever true? I mean, what else can
>> '
On 03/19/2014 02:50 PM, Viresh Kumar wrote:
> On 19 March 2014 14:47, Srivatsa S. Bhat
> wrote:
>> Wait, I think I remember. The problem was about dealing with drivers that
>> do asynchronous notification (those that have the ASYNC_NOTIFICATION flag
>> set). In particular, exynos-5440 driver sends
On 19 March 2014 07:21, Preeti U Murthy wrote:
> Hi Vincent,
>
> On 03/18/2014 11:26 PM, Vincent Guittot wrote:
>> A new flag SD_SHARE_POWERDOMAIN is created to reflect whether groups of CPUs
>> in a sched_domain level can or not reach different power state. As an
>> example,
>> the flag should b
On Wed, 19 Mar 2014, Peter Zijlstra wrote:
> On Tue, Mar 18, 2014 at 04:56:42PM +0800, Yan, Zheng wrote:
> > export __hrtimer_start_range_ns() to allow building perf Intel uncore
> > driver as module
>
> Bah; you didn't cc the hrtimer maintainer.
>
> Thomas, ack on this?
Yup.
> > Signed-off-b
> - val = simple_strtoul(buf, &endp, 0);
> - if (endp == buf || val > 0x3f)
> - return -EINVAL;
> + ret = kstrtoul(buf, 0, &val);
> + if (ret)
> + return ret;
> val = (val << 12) | (sysreg_read(PCCR) & 0xfffc0fff);
you removed 0x3f check
this conversion is not trivial as it seems
--
To unsubscr
From: beh...@converseincode.com
> 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 referenced by
>
Shouldn't the mass-conversion patch (patch 31) go first?
David
--
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
Please read the FAQ at http://www.tux
Hi
Maybe this is a noob question...
Where in the linux kernel source (2.6), the
thread scheduler has been implemented? Searching
the web shows that there should sched_fair.c but
I can not find that in the source directory (the
kernel source has been installed).
Basically, I want to know
1 - 100 of 745 matches
Mail list logo
