From: Greg KH <gregkh@suse.de>
To: sedat.dilek@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Call traces w/ 2.6.35.2 (not w/ 2.6.35.1 plus 2.6.35.2-rc1)
Date: Sat, 14 Aug 2010 06:42:54 -0700 [thread overview]
Message-ID: <20100814134254.GC17430@suse.de> (raw)
In-Reply-To: <AANLkTi=YL_VKKDU8ok=OYotPhyQcGsVB2O-PU29+70YT@mail.gmail.com>
On Sat, Aug 14, 2010 at 08:20:26AM +0200, Sedat Dilek wrote:
> Hi Greg,
>
> looks like 2.6.35.2 misses some fixes from 2.6.35.2-rc1?
Huh? I don't understand what you are trying to show here at all.
> sd@tbox:~/src/linux-2.6/patches/upstream$ cat patch-2.6.35.1
> patch-2.6.35.2-rc1 > new.patch
>
> sd@tbox:~/src/linux-2.6/patches/upstream$ grep "diff --git" new.patch | wc -l
> 132
>
> sd@tbox:~/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.
And these are also showing up on Linus's tree right now as well? Have
you reported them?
thanks,
greg k-h
next prev parent reply other threads:[~2010-08-14 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 6:20 Call traces w/ 2.6.35.2 (not w/ 2.6.35.1 plus 2.6.35.2-rc1) Sedat Dilek
2010-08-14 6:36 ` Sedat Dilek
2010-08-14 13:43 ` Greg KH
2010-08-14 15:28 ` Sedat Dilek
2010-08-14 17:33 ` Greg KH
2010-08-14 13:42 ` Greg KH [this message]
2010-08-14 15:40 ` Sedat Dilek
2010-08-14 15:49 ` wylda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100814134254.GC17430@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox