From: Omkhar Arasaratnam <iamroot@ca.ibm.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
tgall@us.ibm.com, antonb@au1.ibm.com,
James Bottomley <James.Bottomley@SteelEye.com>,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: [BUG] 2.6.11- sym53c8xx Broken on pp64
Date: Wed, 09 Mar 2005 22:53:42 -0600 [thread overview]
Message-ID: <422FD2D6.9050104@ca.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503091944030.2530@ppc970.osdl.org>
Linus Torvalds wrote:
>
>There are certainly sym changes in there too since 2.6.9, let's see if
>James or Willy have any suggestions. It might not be ppc64-specific.
>
> Linus
>
>
>
I have tried with 2.6.10, this appears to fail as well. Unfortunately I
don't have console access right now so I will have confirm the message
in the am. I'll start bisecting patches once we confirm.
Omkhar
next prev parent reply other threads:[~2005-03-10 4:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 1:51 [BUG] 2.6.11- sym53c8xx Broken on pp64 Omkhar Arasaratnam
2005-03-10 2:10 ` Benjamin Herrenschmidt
2005-03-10 2:25 ` Linus Torvalds
2005-03-10 5:06 ` Ryan Anderson
2005-03-10 5:40 ` Sam Ravnborg
2005-03-13 4:32 ` [PATCH] Auto-append localversion for BK users needs to use CONFIG_SHELL Ryan Anderson
2005-04-03 19:17 ` Sam Ravnborg
2005-03-10 3:11 ` [BUG] 2.6.11- sym53c8xx Broken on pp64 Omkhar Arasaratnam
2005-03-10 3:34 ` Omkhar Arasaratnam
2005-03-10 3:47 ` Linus Torvalds
2005-03-10 4:53 ` Omkhar Arasaratnam [this message]
2005-03-10 5:59 ` Benjamin Herrenschmidt
2005-03-10 12:17 ` Matthew Wilcox
2005-03-10 15:17 ` James Bottomley
2005-03-10 17:05 ` Omkhar Arasaratnam
2005-03-10 22:02 ` Benjamin Herrenschmidt
2005-03-11 14:54 ` Omkhar Arasaratnam
2005-03-13 20:32 ` Omkhar Arasaratnam
2005-03-15 15:54 ` Omkhar Arasaratnam
2005-03-15 23:38 ` Benjamin Herrenschmidt
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=422FD2D6.9050104@ca.ibm.com \
--to=iamroot@ca.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=antonb@au1.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=tgall@us.ibm.com \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.