Kernel

[PATCH 01/10] trivial: fix typos concerning "first"
Signed-off-by: Uwe Kleine-König <u.kleine-koenig(a)pengutronix.de> --- drivers/net/gianfar.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/net/gianfar.c b/drivers/net/gianfar.c index 1830f31..abfdf93 100644 --- a/drivers/net/gianfar.c +++ b/drivers/net/gianfar.c @@ -904,7 +90... 11 Jun 2010 07:02

ASoC: Remove unused header
On Thu, 2010-06-10 at 17:54 -0600, Grant Likely wrote: The header contains an extern that isn't used by anything. Remove. Signed-off-by: Grant Likely <grant.likely(a)secretlab.ca> Cc: Liam Girdwood <lrg(a)slimlogic.co.uk> Cc: Mark Brown <broonie(a)opensource.wolfsonmicro.com> Cc: Jon Smirl <jonsmirl(a)gmail... 11 Jun 2010 07:02

[PATCH 3/4] x86: ioremap: remove physical address warning message
Current ioremap() code for x86 displays warning message if too high address to handle is passed. But this can happen as usual cases. For example, if 64-bit BAR is assigned to a PCI device and its device driver calls pci_iomap(). So this patch changes the warning messages as follows. - Change printk message from ... 11 Jun 2010 05:57

[PATCH 2/4] x86: ioremap: fix physical address check
If the physical address is too high to be handled by ioremap() in x86_32 PAE (e.g. more than 36-bit physical address), ioremap() must return error (NULL). However, current x86 ioremap try to map this too high physical address, and it causes unexpected behavior. The ioremap() seems to check the specified physical ... 11 Jun 2010 05:57

[PATCH 4/4] x86: ioremap: fix normal ram range check
Check for norma RAM in x86 ioremap() code seems to not work for the last page frame in the specified physical address range. Signed-off-by: Kenji Kaneshige <kaneshige.kenji(a)jp.fujitsu.com> --- arch/x86/mm/ioremap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: linux-2.6.34/arch/x86/mm/ior... 11 Jun 2010 05:57

[RFC][PATCH 0/4] x86: ioremap() problem in X86_32 PAE
Hi, I encountered the problem that loading ioatdma driver causes kernel hangup or kernel panic in X86_32 PAE environment. I found that this was caused by NOT ioatdma driver but x86's ioremap() behavior in X86_32 PAE environment. On my environment, 64-bit MMIO region is assigned to ioatdma PCI devices, and those ... 11 Jun 2010 05:57

[PATCH 1/4] x86: ioremap: fix wrong address masking
Current x86 ioremap() doesn't handle physical address higher than 32-bit properly in X86_32 PAE mode. When physical address higher than 32-bit is passed to ioremap(), higher 32-bits in physical address is cleared wrongly. Due to this bug, ioremap() can map wrong address to linear address space. In my case, 64-bi... 11 Jun 2010 05:57

[BUG ?] Nouveau driver on 330M GT
Hi, I tested Nouveau with 2.6.34, and now with 2.6.35-rc2 and It does not work with my laptop (chip NVIDIA GeForce 330M GT). (I give more information of the nvidia chip below). I've seen an error message related to my nvidia chip that may also be related to my problem : pci 0000:01:00.0: no compatible bridg... 15 Jun 2010 17:38

blkiocg_update_io_add_stats(): INFO: trying to register non-static key
On 2010-06-11 09:15, Peter Zijlstra wrote: On Wed, 2010-06-02 at 15:04 +0200, Jens Axboe wrote: On Wed, Jun 02 2010, Ingo Molnar wrote: btw., there's another warning triggered by the new blk-cgroups stats code: sda:INFO: trying to register non-static key. the code is fine but needs lockd... 11 Jun 2010 04:52

perf/tracing: Fix regression of perf losing kprobe events
Steven Rostedt wrote: Ingo, Please pull the latest tip/perf/urgent tree, which can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git tip/perf/urgent Steven Rostedt (1): perf/tracing: Fix regression of perf losing kprobe events ---- ... 11 Jun 2010 04:52