[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikP3FHZ0f7umRRzXcT1ytfa9XfE41UHmQ98kO2h@mail.gmail.com>
Date: Sat, 14 Aug 2010 08:36:30 +0200
From: Sedat Dilek <sedat.dilek@...glemail.com>
To: Greg KH <gregkh@...e.de>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Call traces w/ 2.6.35.2 (not w/ 2.6.35.1 plus 2.6.35.2-rc1)
Hope this helps to give an overview what has changed:
$ grep "diff --git" patch-2.6.35.2 | sort > list.patch-2.6.35.2
$ grep "diff --git" new.patch | sort > list.patch-2.6.35.1+patch-2.6.35.2-rc1
$ diff -Naur list.patch-2.6.35.2
list.patch-2.6.35.1+patch-2.6.35.2-rc1 | grep ^+diff
+diff --git a/arch/arm/plat-mxc/include/mach/gpio.h
b/arch/arm/plat-mxc/include/mach/gpio.h
+diff --git a/drivers/net/e1000e/netdev.c b/drivers/net/e1000e/netdev.c
+diff --git a/drivers/net/igb/igb_main.c b/drivers/net/igb/igb_main.c
+diff --git a/fs/block_dev.c b/fs/block_dev.c
+diff --git a/include/linux/notifier.h b/include/linux/notifier.h
+diff --git a/Makefile b/Makefile
$ diff -Naur list.patch-2.6.35.2
list.patch-2.6.35.1+patch-2.6.35.2-rc1 | grep ^-diff
-diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
-diff --git a/mm/memory.c b/mm/memory.c
$ ls -l list.patch-2.6.35.*
-rw-r--r-- 1 sd sd 9004 14. Aug 08:32 list.patch-2.6.35.1+patch-2.6.35.2-rc1
-rw-r--r-- 1 sd sd 8724 14. Aug 08:32 list.patch-2.6.35.2
- Sedat -
On Sat, Aug 14, 2010 at 8:20 AM, Sedat Dilek <sedat.dilek@...glemail.com> wrote:
> Hi Greg,
>
> looks like 2.6.35.2 misses some fixes from 2.6.35.2-rc1?
>
> sd@...x:~/src/linux-2.6/patches/upstream$ cat patch-2.6.35.1
> patch-2.6.35.2-rc1 > new.patch
>
> sd@...x:~/src/linux-2.6/patches/upstream$ grep "diff --git" new.patch | wc -l
> 132
>
> sd@...x:~/src/linux-2.6/patches/upstream$ grep "diff --git"
> patch-2.6.35.2 | wc -l
> 128
>
> Unfortunately, a kernel patched w/ 2.6.35.2 causes Call traces here.
>
> Attached are dmeg outputs for both kernels.
>
>
> Kind Regards,
> - Sedat -
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists