Legacy PCI suspend-resume handlers are called with interrupts enabled.
But cx8800_suspend/cx8800_resume and cx8802_suspend_common/cx8802_resume_common
use spin_lock/spin_unlock functions to acquire dev-slock, while the same lock
is acquired in
the corresponding irq-handlers: cx8800_irq and
On Sat, Apr 13, 2013 at 12:53:36PM -0700, Josh Triplett wrote:
On Sat, Apr 13, 2013 at 12:34:25PM -0700, Paul E. McKenney wrote:
On Sat, Apr 13, 2013 at 11:18:00AM -0700, Josh Triplett wrote:
On Fri, Apr 12, 2013 at 11:38:04PM -0700, Paul E. McKenney wrote:
On Fri, Apr 12, 2013 at
From: Suleiman Souhlal sulei...@google.com
Revert v3.2's 62a3dde (vfs: fix spinning prevention in prune_icache_sb).
This commit doesn't look right:
Since we are looking at the tail of the list (sb-s_inode_lru.prev)
if we want to skip an inode, we should put it back at the head of
the list
On Sat, Apr 13, 2013 at 9:26 AM, Joerg Roedel j...@8bytes.org wrote:
On Sat, Apr 13, 2013 at 11:06:22PM +0800, Andrew Cooks wrote:
On Fri, Apr 12, 2013 at 4:06 PM, Joerg Roedel j...@8bytes.org wrote:
Oh, that's sad. You were the only one having a machine wich actually has
unity-mapped
On Sun, Apr 14, 2013 at 12:44:00AM +0300, Ville Syrjälä wrote:
On Sat, Apr 13, 2013 at 10:02:21AM -0600, Jake Edge wrote:
Hi Zhang Rui,
The problem reported in https://lkml.org/lkml/2012/12/4/428 (and
incorrectly attributed to a suspend patch by me here:
On Sat, Apr 13, 2013 at 12:30 AM, Rakib Mullick rakib.mull...@gmail.com wrote:
On Sat, Apr 13, 2013 at 6:04 AM, Paul Gortmaker
paul.gortma...@windriver.com wrote:
Recent activity has had a focus on moving functionally related blocks of
stuff
out of sched/core.c into stand-alone files. The
On Fri, Apr 12, 2013 at 1:13 PM, Kees Cook keesc...@chromium.org wrote:
This provides routines for selecting a randomized kernel base offset,
bounded by the e820 entries. It tries to use RDRAND and falls back to
RDTSC. If noaslr is on the kernel command line, no offset will be used.
Heavily
(4/13/13 5:14 AM), Marco Stornelli wrote:
Hi,
I was seeing the code of __mm_populate (in -next) and I've got a doubt
about the return value. The function __mlock_posix_error_return should
return a proper error for mlock, converting the return value from
__get_user_pages. It checks for
On Fri, Apr 12, 2013 at 1:13 PM, Kees Cook keesc...@chromium.org wrote:
[...]
diff --git a/arch/x86/boot/compressed/head_64.S
b/arch/x86/boot/compressed/head_64.S
index c1d383d..fc37910 100644
--- a/arch/x86/boot/compressed/head_64.S
+++ b/arch/x86/boot/compressed/head_64.S
@@ -59,7 +59,7
On Mon, Apr 8, 2013 at 1:12 PM, tip-bot for Thomas Gleixner
tip...@zytor.com wrote:
Commit-ID: a1a04ec3c7c27a682473fd9beb2c996316a64649
Gitweb: http://git.kernel.org/tip/a1a04ec3c7c27a682473fd9beb2c996316a64649
Author: Thomas Gleixner t...@linutronix.de
AuthorDate: Thu, 21 Mar 2013
I no longer remember any of the previous z* discussions, including my
own review and I was not online as I wrote this. I may repeat myself,
contradict myself or rehash topics that were visited already and have
been concluded. If I do any of that then sorry.
On Wed, Apr 10, 2013 at 01:18:53PM
On Wed, Apr 10, 2013 at 01:18:55PM -0500, Seth Jennings wrote:
debugfs currently lack the ability to create attributes
that set/get atomic_t values.
This patch adds support for this through a new
debugfs_create_atomic_t() function.
Acked-by: Greg Kroah-Hartman gre...@linuxfoundation.org
On Wed, Apr 10, 2013 at 01:18:56PM -0500, Seth Jennings wrote:
zswap is a thin compression backend for frontswap. It receives
pages from frontswap and attempts to store them in a compressed
memory pool, resulting in an effective partial memory reclaim and
dramatically reduced swap device I/O.
On Wed, Apr 10, 2013 at 01:18:59PM -0500, Seth Jennings wrote:
This patch adds support for evicting swap pages that are currently
compressed in zswap to the swap device. This functionality is very
important and make zswap a true cache in that, once the cache is full
or can't grow due to
Just tried to build from the linux-3.0.73 source tarball and got the following
error:
arch/x86/mm/numa_32.c:107: error: redefinition of 'alloc_remap'
include/linux/bootmem.h:144: note: previous definition of 'alloc_remap' was here
make[2]: *** [arch/x86/mm/numa_32.o] Error 1
make[1]: ***
On 04/13/2013 12:23 AM, Borislav Petkov wrote:
On Fri, Apr 12, 2013 at 04:46:50PM +0800, Alex Shi wrote:
Thanks a lot for comments, Len!
AFAICT, you kinda forgot to answer his most important question:
These numbers suggest that this patch series simultaneously
has a negative impact on
On 04/13/2013 01:12 AM, Borislav Petkov wrote:
On Fri, Apr 12, 2013 at 06:48:31PM +0200, Mike Galbraith wrote:
(just saying there are other aspects besides joules in there)
Yeah, but we don't allow any regressions in sched*, do we? Can we pick
only the good cherries? :-)
Thanks for all of
Oleg Nesterov o...@redhat.com writes:
exit_notify() does exit_task_namespaces() after
forget_original_parent(). This was needed to ensure that -nsproxy
can't be cleared prematurely, an exiting child we are going to
reparent can do do_notify_parent() and use the parent's (ours) pid_ns.
On 04/13/2013 05:37 PM, Yinghai Lu wrote:
so decompress code position is changed?
You may push out bss and other data area of run-time kernel of limit
that boot loader
chose according to setup_header.init_size.
aka that make those area overlap with ram hole or other area like
boot
On Fri, Apr 12, 2013 at 04:47:50PM -0700, Linus Torvalds wrote:
This is a much more generic bug in kobjects, and I would hate to add
some random workaround for just one case of this bug like you do. The
more fundamental bug needs to be fixed too.
I think the more fundamental bugfix is to
From: Namjae Jeon namjae.j...@samsung.com
Implement preallocation via the fallocate syscall on VFAT partitions.
Change Log:
v4: Rework based on review comments.
Add check in fat_setattr to release fallocated blocks on a truncate
v3: Release preallocated blocks at file release.
With
I notice that where a commit is cherry-picked cleanly on a stable
branch, like 6b90466cfec2a2fe027187d675d8d14217c12d82, your script finds
the corresponding commit on the stable branch. This is useful.
But where some backporting changes are needed, such as for
On Sat, Apr 13, 2013 at 5:45 PM, Thierry Reding
thierry.red...@avionic-design.de wrote:
On Sat, Apr 13, 2013 at 08:54:22AM -0400, Rob Clark wrote:
On Mon, Mar 4, 2013 at 1:46 PM, Tony Lindgren t...@atomide.com wrote:
drivers/gpu/drm/tilcdc/tilcdc_slave.o:(.data+0x54): multiple definition
Hi
On Sat, Apr 13, 2013 at 8:35 PM, Al Viro v...@zeniv.linux.org.uk wrote:
On Fri, Apr 12, 2013 at 04:47:50PM -0700, Linus Torvalds wrote:
This is a much more generic bug in kobjects, and I would hate to add
some random workaround for just one case of this bug like you do. The
more
On Sat, Apr 13, 2013 at 09:42:06PM -0700, Anatol Pomozov wrote:
in kobject_cleanup(). Why don't we require kobject_del() before the final
kobject_put(), if the sucker had been added? FWIW, I thought it *was*
required all along...
But kobject_release/kobject_cleanup function is called
--
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.org/lkml/
Convert various printk logging styles to current styles.
Uncompiled, untested.
Joe Perches (3):
fec: Convert printks to netdev_level
gianfar: Use netdev_level when possible
ucc_geth: Convert ugeth_level to pr_level
drivers/net/ethernet/freescale/fec_main.c | 26 +-
Use a more current logging message style.
Convert the printks where a struct net_device is available to
netdev_level. Convert the other printks to pr_level and
add pr_fmt where appropriate.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/net/ethernet/freescale/fec_main.c| 26
Use a more current logging style.
Convert pr_level to netdev_level when a struct net_device is
available. Add pr_fmt and neaten other formats too.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/net/ethernet/freescale/gianfar_ethtool.c | 24 +---
On 04/14/2013 09:28 AM, Alex Shi wrote:
These numbers suggest that this patch series simultaneously
has a negative impact on performance and energy required
to retire the workload. Why do it?
Even some scenario the total energy cost more, at least the avg watts
dropped in that
The case of PLL_TYPE_WM8750 in both these functions is missing a break
statement causing a fall-through to the default: case.
Insert the missing break statements.
Signed-off-by: Tony Prisk li...@prisktech.co.nz
---
Mike,
Any chance this can still go in as a fix for 3.9
The fault makes it
commit 3401d54696f (KVM: ARM: Introduce KVM_ARM_SET_DEVICE_ADDR ioctl)
added the case, but omitted adding break;
Add it.
Found with grep version 2.54 pattern:
$ grep -rP --include=*.[ch]
\b(\w+)\s*=[^;]+;\s*(?:case\s+\w+:|default:)\s*\1\s*=
Signed-off-by: Joe Perches j...@perches.com
---
diff
301 - 332 of 332 matches
Mail list logo
