From: Paul E. McKenney paul...@linux.vnet.ibm.com
Although the atomic_long_t functions are quite useful, they are a bit
obscure. This commit therefore adds the common ones alongside their
atomic_t counterparts in Documentation/memory-barriers.txt.
Signed-off-by: Paul E. McKenney
From: Paul E. McKenney paul...@linux.vnet.ibm.com
The Documentation/memory-barriers.txt file was written before the need
for ACCESS_ONCE() was fully appreciated. It therefore contains no
ACCESS_ONCE() calls, which can be a problem when people lift examples
from it. This commit therefore adds
Hi Nicolas,
On Tue, Oct 15, 2013 at 09:54:21AM +0200, Nicolas Ferre wrote:
On 15/10/2013 01:59, Soren Brinkmann :
Adjust the ethernet clock according to the negotiated link speed.
Signed-off-by: Soren Brinkmann soren.brinkm...@xilinx.com
I will need more time to study this one.
set_handle_irq(gic_handle_irq);
+ gic-bypass_flag = (bypass_val 0xf) 4;
Beware, the top 2 bits are reserved on GICv1, and shouldn't be messed with.
The only time those bits are touched are when the dts is modified with the
bypass flag. Otherwise those bits remain untouched as
On Sat, Nov 09, 2013 at 12:28:57PM +0530, Anurag Aggarwal wrote:
Thanks for your input Dave,
I think there is another way to avoid the stack overflow and reduce
the number of checks also,
Stack overflow will cause a problem only when we are backtracking the
last set of registers.
i.e
Em Fri, Nov 22, 2013 at 12:13:52PM -0700, David Ahern escreveu:
On 11/22/13, 11:44 AM, Arnaldo Carvalho de Melo wrote:
Em Mon, Nov 18, 2013 at 01:32:46PM -0700, David Ahern escreveu:
Save vmlinux or kallsyms path loaded using embedded default lookup (ie.,
not a user specified path). Upcoming
On Thu, Nov 21, 2013 at 11:22:42PM +, Al Viro wrote:
On Thu, Nov 21, 2013 at 03:01:07PM -0800, Greg KH wrote:
Al, did this fix end up in Linus's tree yet? I'd like to pull it into
the next 3.12-stable release, but will wait until Linus has it of
course.
Yes - ede4ce.
Thanks, now
From: Martin Schwidefsky schwidef...@de.ibm.com
Since commit 1e75fa8be9f (time: Condense timekeeper.xtime
into xtime_sec - merged in v3.6), there has been an problem
with the error accounting in the timekeeping code, such that
when truncating to nanoseconds, we round up to the next nsec,
but the
On 11/22/2013 05:52 AM, Viresh Kumar wrote:
On 22 November 2013 18:07, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Friday, November 22, 2013 04:59:49 PM Viresh Kumar wrote:
Some platforms might want to change frequency before suspending governors.
Like:
- Some platform which want to set
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
We can kill either task-did_exec or PF_FORKNOEXEC, they are
mutually exclusive. The patch kill -did_exec because it has
a single user.
It's ok.
but,
- * Auch. Had to add the 'did_exec' flag to conform completely to POSIX.
- * LBT 04.03.94
+ *
On Fri, Nov 22, 2013 at 09:19:46AM -0500, Vivek Goyal wrote:
On Fri, Nov 22, 2013 at 05:34:03AM -0800, Eric W. Biederman wrote:
[..]
Why ELF case is so interesting. I have not use kexec to boot ELF
images in years and have not seen others using it too. In fact bzImage
seems to be the
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
next_thread() should be avoided, change check_unsafe_exec()
to use while_each_thread(). This also saves 32 bytes.
Just curious.
Why it should be avoided? Just for cleaner code? Or is there
serious issue?
--
To unsubscribe from this list: send the
Am 20.11.2013 16:22, schrieb Chinmay V S:
Hi Stefan,
thanks for your great and detailed reply. I'm just wondering why an
intel 520 ssd degrades the speed just by 2% in case of O_SYNC. intel 530
the newer model and replacement for the 520 degrades speed by 75% like
the crucial m4.
The Intel DC
On Thu, Nov 21, 2013 at 03:16:13PM -0800, Michael Marineau wrote:
On Thu, Nov 21, 2013 at 3:01 PM, Greg KH gre...@linuxfoundation.org wrote:
On Wed, Nov 13, 2013 at 02:51:59PM -0800, Michael Marineau wrote:
On Wed, Nov 13, 2013 at 4:39 AM, Al Viro v...@zeniv.linux.org.uk wrote:
On Wed, Nov
Am 20.11.2013 16:55, schrieb J. Bruce Fields:
On Wed, Nov 20, 2013 at 10:37:03AM -0500, Theodore Ts'o wrote:
On Wed, Nov 20, 2013 at 08:52:36PM +0530, Chinmay V S wrote:
If you have confirmed the performance numbers, then it indicates that
the Intel 530 controller is more advanced and makes
On Fri, Nov 22, 2013 at 10:42 AM, Joel Fernandes jo...@ti.com wrote:
On 11/22/2013 09:58 AM, Rob Herring wrote:
On Thu, Nov 21, 2013 at 7:56 PM, Joel Fernandes jo...@ti.com wrote:
This work is a migration effort of OMAP system timers to the
clocksource/clockevent framework. Consider this as a
Hi Christoph,
Am 21.11.2013 11:11, schrieb Christoph Hellwig:
2. Some drives may implement CMD_FLUSH to return immediately i.e. no
guarantee the data is actually on disk.
In which case they aren't spec complicant. While I've seen countless
data integrity bugs on lower end ATA SSDs I've not
On 11/22/13, 12:40 PM, Arnaldo Carvalho de Melo wrote:
Em Fri, Nov 22, 2013 at 12:13:52PM -0700, David Ahern escreveu:
On 11/22/13, 11:44 AM, Arnaldo Carvalho de Melo wrote:
Em Mon, Nov 18, 2013 at 01:32:46PM -0700, David Ahern escreveu:
Save vmlinux or kallsyms path loaded using embedded
Commit-ID: 4be77398ac9d948773116b6be4a3c91b3d6ea18c
Gitweb: http://git.kernel.org/tip/4be77398ac9d948773116b6be4a3c91b3d6ea18c
Author: Martin Schwidefsky schwidef...@de.ibm.com
AuthorDate: Fri, 22 Nov 2013 11:44:51 -0800
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Fri, 22
On Fri, Nov 22, 2013 at 11:18 AM, Oleg Nesterov o...@redhat.com wrote:
Change k_getrusage() to use while_each_thread(), no changes in
the compiled code.
Signed-off-by: Oleg Nesterov o...@redhat.com
Reviewed-by: Sameer Nanda sna...@chromium.org
---
kernel/sys.c |3 +--
1 files changed,
On Fri, Nov 22, 2013 at 11:18 AM, Oleg Nesterov o...@redhat.com wrote:
do_task_stat() can use while_each_thread(), no changes in
the compiled code.
Signed-off-by: Oleg Nesterov o...@redhat.com
Reviewed-by: Sameer Nanda sna...@chromium.org
---
fs/proc/array.c |3 +--
1 files changed, 1
On Fri, Nov 22, 2013 at 11:18 AM, Oleg Nesterov o...@redhat.com wrote:
Change do_signal_stop() and do_sigaction() to avoid next_thread()
and use while_each_thread() instead.
Signed-off-by: Oleg Nesterov o...@redhat.com
Reviewed-by: Sameer Nanda sna...@chromium.org
---
kernel/signal.c |
On 11/22, KOSAKI Motohiro wrote:
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
next_thread() should be avoided, change check_unsafe_exec()
to use while_each_thread(). This also saves 32 bytes.
Just curious.
Why it should be avoided? Just for cleaner code?
Nobody except signal-curr_target
Linus Torvalds torva...@linux-foundation.org wrote:
So for future cases: if there are big independent overhauls of core
subsystems, I'd really like to see them kept separate, ok?
Since the trusted and encrypted keys that Mimi and Dmitry deal with are also
more akin to the keyring stuff, should
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
fs_struct-in_exec == T means that this -fs is used by a single
process (thread group), and one of the treads does do_execve().
To avoid the mt-exec races this code has the following complications:
1. check_unsafe_exec() returns -EBUSY if
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
Both success/failure paths cleanup bprm-file, we can move this
code into free_bprm() to simlify and cleanup this logic.
Signed-off-by: Oleg Nesterov o...@redhat.com
Acked-by: KOSAKI Motohiro kosaki.motoh...@jp.fujitsu.com
--
To unsubscribe from
On 11/22, KOSAKI Motohiro wrote:
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
We can kill either task-did_exec or PF_FORKNOEXEC, they are
mutually exclusive. The patch kill -did_exec because it has
a single user.
It's ok.
but,
- * Auch. Had to add the 'did_exec' flag to conform
(11/22/2013 3:24 PM), Oleg Nesterov wrote:
On 11/22, KOSAKI Motohiro wrote:
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
next_thread() should be avoided, change check_unsafe_exec()
to use while_each_thread(). This also saves 32 bytes.
Just curious.
Why it should be avoided? Just for cleaner
(11/22/2013 3:33 PM), Oleg Nesterov wrote:
On 11/22, KOSAKI Motohiro wrote:
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
We can kill either task-did_exec or PF_FORKNOEXEC, they are
mutually exclusive. The patch kill -did_exec because it has
a single user.
It's ok.
but,
- * Auch. Had to
On 11/22/2013 02:14 PM, Linus Torvalds wrote:
On Fri, Nov 22, 2013 at 11:04 AM, Waiman Longwaiman.l...@hp.com wrote:
In term of single-thread performance (no contention), a 256K
lock/unlock loop was run on a 2.4GHz and 2.93Ghz Westmere x86-64
CPUs. The following table shows the average time
On 11/06/2013 10:31 PM, Richard Weinberger wrote:
Can you please ask gdb for the value of offset?
With this diff against latest Linus tree v3.12-11355-g57498f9 :
diff --git a/lib/radix-tree.c b/lib/radix-tree.c
index 7811ed3..54d9802 100644
--- a/lib/radix-tree.c
+++ b/lib/radix-tree.c
@@
So you had an extra week to prepare your pull requests, and if you
were planning on sending it in the last two days thinking I'd close
the merge window on Sunday as usual, I can only laugh derisively in
your general direction, and call you bad names. Because I'm not
interested in your excuses. I
On 11/22/2013 03:01 PM, Stefan Priebe wrote:
Hi Christoph,
Am 21.11.2013 11:11, schrieb Christoph Hellwig:
2. Some drives may implement CMD_FLUSH to return immediately i.e. no
guarantee the data is actually on disk.
In which case they aren't spec complicant. While I've seen countless
data
On Wed, 20 Nov 2013, Vivek Goyal wrote:
This patch implements the in kernel kexec functionality. It implements a
new system call kexec_file_load. I think parameter list of this system
call will change as I have not done the kernel image signature handling
yet. I have been told that I might
On 11/22, KOSAKI Motohiro wrote:
(11/22/2013 12:54 PM), Oleg Nesterov wrote:
fs_struct-in_exec == T means that this -fs is used by a single
process (thread group), and one of the treads does do_execve().
To avoid the mt-exec races this code has the following complications:
1.
On Fri, Nov 22, 2013 at 11:40:32AM -0700, Stephen Warren wrote:
On 11/22/2013 05:14 AM, Mika Westerberg wrote:
From: Heikki Krogerus heikki.kroge...@linux.intel.com
All platforms using this driver are now converted to the new
descriptor-based GPIO interface.
Don't you want to remove
On Mon, Nov 18, 2013 at 3:17 AM, Hugh Dickins hu...@google.com wrote:
Sorry for the delay: I was on the point of reporting success last
night, when I tried a debug kernel: and that didn't work so well
(got spinlock bad magic report in pwd_adjust_max_active(), and
tests wouldn't run at all).
I have found no problem in this patch. However, I have a very basic question.
Why do we need to keep fs-in_exec?
To ensure that a sub-thread can't create a new process with the same
-fs while we are doing exec without LSM_UNSAFE_SHARE, I guess. This
is only for security/ code.
But in
On 11/22/2013 01:56 PM, Heikki Krogerus wrote:
On Fri, Nov 22, 2013 at 11:40:32AM -0700, Stephen Warren wrote:
On 11/22/2013 05:14 AM, Mika Westerberg wrote:
From: Heikki Krogerus heikki.kroge...@linux.intel.com
All platforms using this driver are now converted to the new
descriptor-based
Hi Ric,
Am 22.11.2013 21:37, schrieb Ric Wheeler:
On 11/22/2013 03:01 PM, Stefan Priebe wrote:
Hi Christoph,
Am 21.11.2013 11:11, schrieb Christoph Hellwig:
2. Some drives may implement CMD_FLUSH to return immediately i.e. no
guarantee the data is actually on disk.
In which case they
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk ivan.khoronz...@ti.com wrote:
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Binding shouldn’t normally refer to code.
Just saying something like:
Adding binging for TI Async External Memory Interface (AEMIF) controller.
2013/11/22 Jonas Jensen jonas.jen...@gmail.com:
On 22 November 2013 15:57, Jonas Jensen jonas.jen...@gmail.com wrote:
drivers/net/ethernet/moxa/moxart_ether.c | 179
++-
drivers/net/ethernet/moxa/moxart_ether.h | 1 +
2 files changed, 179 insertions(+), 1
Hi,
On Wed 13-11-13 16:11:47, Dave Jones wrote:
here's another one..
=
[ INFO: possible recursive locking detected ]
3.12.0+ #2 Not tainted
-
trinity-child3/13302 is trying to acquire lock:
Dear RT folks!
I'm pleased to announce the v3.12.1-rt4 patch set.
Changes since v3.12.0-rt2
- rtmutex: the patch with the conversion to raw_spinlock_irq() of the
waiter lock has been replaced by a trylock attempt this keeps the
change a lot smaller. Initially suggested by Matt Cowell.
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk ivan.khoronz...@ti.com wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum value is 1 (0 treated as 1).
+
+- ti,cs-wsetup:write
On Fri, Nov 22, 2013 at 12:35 PM, Waiman Long waiman.l...@hp.com wrote:
Yes, the extra latency of the fair lock in earlier patch is due to the need
to do a second cmpxchg(). That can be avoided by doing a read first, but
that is not good for good cache. So I optimized it for the default
Hello Jonas,
+ if (!priv-phy_dev)
+ return -ENODEV;
This should not be required since you will fail probing the interface
if you cannot connect to the PHY device.
+
+ return phy_ethtool_gset(priv-phy_dev, cmd);
+}
+
+static int moxart_set_settings(struct
From: Rob Herring rob.herr...@calxeda.com
Add missing arm,armv8-pmuv3 compatible property for ARMv8 PMU.
Signed-off-by: Rob Herring rob.herr...@calxeda.com
Cc: Will Deacon will.dea...@arm.com
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Ian Campbell
From: Rob Herring rob.herr...@calxeda.com
Add arm,gic-400 compatible property for ARM GIC-400 IP.
Signed-off-by: Rob Herring rob.herr...@calxeda.com
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Ian Campbell ijc+devicet...@hellion.org.uk
---
Unwind may loop forever if sample is incomplete or bogus. Bound the number of
unw_step() that yield the same IP to prevent infinite loop.
Signed-off-by: Francis Giraldeau francis.girald...@gmail.com
---
tools/perf/util/unwind.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff
H. Peter Anvin h...@zytor.com writes:
If you have a real iotlb, why would you need contiguous memory?
iotlb is often slow.
Another use case is allocating 1GB pages at runtime.
-Andi
--
a...@linux.intel.com -- Speaking for myself only
--
To unsubscribe from this list: send the line
On Wed, Nov 20, 2013 at 04:22:21AM +, Masami Hiramatsu wrote:
Use NOKPROBE_SYMBOL macro to protect functions from kprobes
instead of __kprobes annotation in trap.c.
This also applies __always_inline annotation for some cases,
because NOKPROBE_SYMBOL() will inhibit inlining by referring
If the warning added by that patch does *not* trigger than can you also
test this patch? It removes the barriers which should not be necessary
and takes a reference tot he page before waiting on the lock. The
previous version did not take the reference because otherwise the
WARN_ON could not
On 11/22/2013 01:54 PM, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
Le 22/11/2013 08:43, Francis Moreau a écrit :
Le 21/11/2013 12:17, Jingoo Han a écrit :
[...]
Also I took a look at the changes between v3.11 and v3.12 in this area
and those
On Nov 22, 2013, at 3:17 PM, Rob Herring robherri...@gmail.com wrote:
From: Rob Herring rob.herr...@calxeda.com
Add arm,gic-400 compatible property for ARM GIC-400 IP.
Signed-off-by: Rob Herring rob.herr...@calxeda.com
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland
On Nov 22, 2013, at 3:17 PM, Rob Herring robherri...@gmail.com wrote:
From: Rob Herring rob.herr...@calxeda.com
Add missing arm,armv8-pmuv3 compatible property for ARMv8 PMU.
Signed-off-by: Rob Herring rob.herr...@calxeda.com
Cc: Will Deacon will.dea...@arm.com
Cc: Pawel Moll
On 11/22/2013 03:38 PM, Kumar Gala wrote:
On Nov 22, 2013, at 3:17 PM, Rob Herring robherri...@gmail.com wrote:
From: Rob Herring rob.herr...@calxeda.com
Add missing arm,armv8-pmuv3 compatible property for ARMv8 PMU.
Signed-off-by: Rob Herring rob.herr...@calxeda.com
Cc: Will Deacon
On 11/22/2013 01:03 AM, viresh kumar wrote:
On Thursday 21 November 2013 12:39 PM, Viresh Kumar wrote:
[...]
Copying another mail from Nishant here to get my cc'list back..
On Friday 22 November 2013 05:12 AM, Nishanth Menon wrote:
I gave this a quick run on my 3.12 kernel:
Coverity caught double free possibility (CID 1130962).
I can patch this, but I have to know if is correct to free comp_opts
in the function squashfs_decompressor_create() or it had to be done in
the caller. My bet is the caller.
128void *squashfs_decompressor_setup(struct super_block *sb,
Add binding documentation for the hym8563 rtc chip.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
.../devicetree/bindings/rtc/haoyu,hym8563.txt | 29
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/haoyu,hym8563.txt
diff
This series adds support for the Haoyu Microelectronics HYM8563 rtc. This
chip is often used in designs around the Cortex-A9 SoCs from Rockchip to
provide rtc functionality and the 32kHz suspend clock the SoC needs.
Heiko Stuebner (2):
Documentation: dt: Add dt hym8563 binding
rtc: add
On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
On 11/22/2013 01:54 PM, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
Le 22/11/2013 08:43, Francis Moreau a écrit :
Le 21/11/2013 12:17, Jingoo Han a écrit :
[...]
Also I took a
The Haoyu Microelectronics HYM8563 provides rtc- and alarm functions
as well as a clock output of up to 32kHz.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
drivers/rtc/Kconfig | 11 +
drivers/rtc/Makefile |1 +
drivers/rtc/rtc-hym8563.c | 619
On Fri, Nov 22, 2013 at 10:50 PM, Geyslan Gregório Bem
geys...@gmail.com wrote:
Coverity caught double free possibility (CID 1130962).
Just wondering, where can one find/verify such CIDs?
--
Thanks,
//richard
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On Friday, November 22, 2013 10:54:29 AM Shuah Khan wrote:
Tracing infrastructure routine __assign_str doesn't handle null strings.
As a result when an trace event passes in a null string, kernel panics
when skip_spaces() is invoked on the string. The following oops occurred
when a null wakeup
On 11/20/13 00:50, Nicolas Dichtel wrote:
Since commit 7a6354e241d8 (sched: Move wait.c into kernel/sched/), the path
of this file has changed.
This is a fatal kernel-doc error. Please merge quickly/soon. Thanks.
CC: Peter Zijlstra pet...@infradead.org
CC: Ingo Molnar mi...@kernel.org
Currently, zswap is writeback cache; stored pages are not sent
to swap disk, and when zswap wants to evict old pages it must
first write them back to swap cache/disk manually. This avoids
swap out disk I/O up front, but only moves that disk I/O to
the writeback case (for pages that are evicted),
Currently, zswap_entry_put removes the entry from its tree if
the resulting refcount is 0. Several places in code put an
entry's initial reference, but they also must remove the entry
from its tree first, which makes the tree removal in zswap_entry_put
redundant.
I believe this has the refcount
2013/11/22 Richard Weinberger richard.weinber...@gmail.com:
On Fri, Nov 22, 2013 at 10:50 PM, Geyslan Gregório Bem
geys...@gmail.com wrote:
Coverity caught double free possibility (CID 1130962).
Just wondering, where can one find/verify such CIDs?
--
Thanks,
//richard
Anyone can sign in
Hello, Hugh.
I applied the following patch to cgroup/for-3.13-fixes. For longer
term, I think it'd be better to pull workqueue init before cgroup one
but this one should be easier to backport for now.
Thanks!
- 8 -
From e5fca243abae1445afbfceebda5f08462ef869d3 Mon Sep 17 00:00:00 2001
On Fri, Nov 22, 2013 at 09:59:37PM +0100, William Dauchy wrote:
Hugh, Tejun,
Do we have some news about this patch? I'm also hitting this bug on a 3.10.x
Just applied to cgroup/for-3.13-fixes w/ stable cc'd. Will push to
Linus next week.
Thanks.
--
tejun
--
To unsubscribe from this list:
On Wed, Nov 6, 2013 at 7:49 AM, ethan.zhao ethan.ker...@gmail.com wrote:
Though no specification about NumVFs register initial value after POST, to
void the confusion
lspci output as following before VF was enabled, we should clear the NumVFs
value left by BIOS
to zero:
$lspci -vvv -s
Hi Peter,
On Fri, Nov 22, 2013 at 12:09:54PM -0500, Peter Hurley wrote:
Most line disciplines already handle the undocumented NULL flag
ptr in their .receive_buf method; however, several don't.
Document the NULL flag ptr, and correct handling in the
N_MOUSE, N_GSM0710 and N_R394 line
Based on Richard Weinberger patch https://lkml.org/lkml/2012/3/16/510
Functions like this one are evil:
void foo()
{
...
}
Signed-off-by: Elena Ufimtseva ufimts...@gmail.com
---
Changes since v1:
- added white space in regular expression between (), based
on comments from Joe Perches.
On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
Ok, I've finally managed to find out the bad commit:
ad07277e82dedabacc52c82746633680a3187d25: ACPI / PM: Hold acpi_scan_lock
over system PM transitions
I verified that the
On Fri, 22 Nov 2013 12:01:06 -0500 Luiz Capitulino lcapitul...@redhat.com
wrote:
Signed-off-by: Luiz capitulino lcapitul...@redhat.com
---
include/linux/mmzone.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
On Friday, November 22, 2013 08:43:55 AM Bjorn Helgaas wrote:
[+cc Rafael, James]
On Tue, Nov 19, 2013 at 11:18 PM, Tejun Heo t...@kernel.org wrote:
(cc'ing Bjorn)
Hello,
On Tue, Nov 19, 2013 at 03:09:58PM +0200, Mika Westerberg wrote:
Commit bcdde7e221a8 (sysfs: make
On Mon, 18 Nov 2013, Viresh Kumar wrote:
On Fri, Mar 22, 2013 at 3:23 AM, Thomas Gleixner t...@linutronix.de wrote:
--- linux-2.6.orig/kernel/cpu/idle.c
+++ linux-2.6/kernel/cpu/idle.c
+void cpu_startup_entry(enum cpuhp_state state)
+{
+ current_set_polling();
+
On Thu, 2013-11-21 at 14:17 +0800, dyo...@redhat.com wrote:
Hi,
Here is the V3 for supporting kexec kernel efi runtime.
Per pervious discussion I pass the 1st kernel efi runtime mapping
via setup_data to 2nd kernel. Besides of the runtime mapping
info I also pass the fw_vendor, runtime,
On Mon, 2013-11-04 at 16:52 +, Joseph S. Myers wrote:
From: Joseph Myers jos...@codesourcery.com
The e500 SPE floating-point emulation code clears existing exceptions
(__FPU_FPSCR = ~FP_EX_MASK;) before ORing in the exceptions from the
emulated operation. However, these exception bits
On Fri, 2013-11-22 at 17:17 -0500, Elena Ufimtseva wrote:
Based on Richard Weinberger patch https://lkml.org/lkml/2012/3/16/510
Functions like this one are evil:
void foo()
{
...
}
[]
- added white space in regular expression between (), based
on comments from Joe Perches.
Thanks
On Sat, Mar 16, 2013 at 09:21:40AM -0700, Greg Kroah-Hartman wrote:
On Thu, Mar 14, 2013 at 08:24:45PM -0700, Guenter Roeck wrote:
Provide devres functions for device_create_file, sysfs_create_file,
and sysfs_create_group plus the respective remove functions.
Idea is to be able to drop
On Fri, Nov 22, 2013 at 5:45 PM, Joe Perches j...@perches.com wrote:
On Fri, 2013-11-22 at 17:17 -0500, Elena Ufimtseva wrote:
Based on Richard Weinberger patch https://lkml.org/lkml/2012/3/16/510
Functions like this one are evil:
void foo()
{
...
}
[]
- added white space in
On 11/22/2013 02:24 PM, Chang wrote:
On 11/22/2013 03:27 PM, Vlad Yasevich wrote:
On 11/22/2013 02:49 AM, Chang Xiangzhong wrote:
tsn_gap_acked is an important state flag in chunk, which indicates if
the
chunk has been acked in gap reports before.
Actually, this bit indicates simply that
On Fri, Nov 22, 2013 at 02:47:38PM -0800, Dmitry Torokhov wrote:
On Sat, Mar 16, 2013 at 09:21:40AM -0700, Greg Kroah-Hartman wrote:
On Thu, Mar 14, 2013 at 08:24:45PM -0700, Guenter Roeck wrote:
Provide devres functions for device_create_file, sysfs_create_file,
and sysfs_create_group
Hi Tejun,
On Fri, Nov 22, 2013 at 11:18 PM, Tejun Heo t...@kernel.org wrote:
Just applied to cgroup/for-3.13-fixes w/ stable cc'd. Will push to
Linus next week.
Thank your for your quick reply. Do you also have a backport for
v3.10.x already available?
Best regards,
--
William
--
To
This commit enables the watchdog driver for the BCM281xx family of SoCs.
Signed-off-by: Markus Mayer markus.ma...@linaro.org
Reviewed-by: Matt Porter matt.por...@linaro.org
Acked-by: Guenter Roeck li...@roeck-us.net
---
arch/arm/configs/bcm_defconfig |3 +++
1 file changed, 3 insertions(+)
This is version 5 of the watchdog driver for the BCM281xx family of mobile
SoCs.
Changes since version 4:
- Fixed whitespace issue in Kconfig help section
- Rebased onto 3.13-rc1 (due to merge conflict in Makefile)
Changes since version 3:
- Removed #include linux/miscdevice.h
- Added
This commit adds support for the watchdog timer used on the BCM281xx
family of SoCs.
Signed-off-by: Markus Mayer markus.ma...@linaro.org
Reviewed-by: Matt Porter matt.por...@linaro.org
Reviewed-by: Guenter Roeck li...@roeck-us.net
---
drivers/watchdog/Kconfig| 22 +++
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive 2nd round of updates for the input subsystem. You will get a
new driver for Surface
On Fri, 8 Nov 2013 20:47:38 +0800 Zhi Yong Wu zwu.ker...@gmail.com wrote:
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -611,7 +611,7 @@ static int me_pagecache_clean(struct page *p, unsigned
long pfn)
}
/*
- * Dirty cache page page
+ * Dirty cache page
* Issues: when
Hello,
On Wed, Nov 20, 2013 at 12:51:21AM -0500, Tejun Heo wrote:
The patch is just extremely marginal. Ah well... why not? I'll apply
it once -rc1 drops.
So, I was about to apply this patch but decided against it. It
doesn't really make anything better and the code looks worse
afterwards.
On Thu, Nov 21, 2013 at 11:54 PM, yzhu1 yanjun@windriver.com wrote:
Hi, maintainers
This change is based on a similar change made to e1000e support in
commit bb9e44d0d0f4 (e1000e: prevent oops when adapter is being closed
and reset simultaneously). The same issue has also been observed
On Fri, Nov 22, 2013 at 03:28:07PM -0600, Alex Thorlton wrote:
If the warning added by that patch does *not* trigger than can you also
test this patch? It removes the barriers which should not be necessary
and takes a reference tot he page before waiting on the lock. The
previous version
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Rework acpi_bus_trim() and acpi_bus_device_attach(), which is
renamed as acpi_bus_attach(), to walk the list of each device
object's children directly and call themselves recursively for
each child instead of using acpi_walk_namespace(). This
On Saturday, November 23, 2013 12:22:23 AM Rafael J. Wysocki wrote:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Rework acpi_bus_trim() and acpi_bus_device_attach(), which is
renamed as acpi_bus_attach(), to walk the list of each device
object's children directly and call themselves
On Thu, Nov 14, 2013 at 6:56 AM, Oleg Nesterov o...@redhat.com wrote:
Move the setting of PF_NO_SETAFFINITY up before set_cpus_allowed()
in create_worker(). Otherwise userland can change -cpus_allowed
in between.
Signed-off-by: Oleg Nesterov o...@redhat.com
Applied to wq/for-3.13-fixes.
On Fri, 2013-11-22 at 12:20 +0400, Vladimir Davydov wrote:
The patch fixes the following lockdep warning, which is 100%
reproducible on network restart:
==
[ INFO: possible circular locking dependency detected ]
3.12.0+ #47 Tainted: GF
On Fri, 2013-11-22 at 12:20 +0400, Vladimir Davydov wrote:
On e1000_down(), we should ensure every asynchronous work is canceled
before proceeding. Since the watchdog_task can schedule other works
apart from itself, it should be stopped first, but currently it is
stopped after the reset_task.
On 22/11/13 21:50, Geyslan Gregório Bem wrote:
Coverity caught double free possibility (CID 1130962).
I can patch this, but I have to know if is correct to free comp_opts
in the function squashfs_decompressor_create() or it had to be done in
the caller. My bet is the caller.
128void
901 - 1000 of 1074 matches
Mail list logo
