From: Tom Rini <trini@kernel.crashing.org>
To: Greg Weeks <greg.weeks@timesys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH} PPC 32 multithreaded core dumps
Date: Thu, 4 Mar 2004 08:31:49 -0700 [thread overview]
Message-ID: <20040304153149.GD26065@smtp.west.cox.net> (raw)
In-Reply-To: <404729AC.8010405@timesys.com>
On Thu, Mar 04, 2004 at 08:05:48AM -0500, Greg Weeks wrote:
> Tom Rini wrote:
>
> >On Wed, Feb 25, 2004 at 03:25:56PM -0500, Greg Weeks wrote:
> >
> >>This code fixes the register dumps for 32 bit ppc multi threaded core
> >>dumps. It's largely based on the ppc64 code. It was tested on an 8260
> >
> >This looks right, and I'll think about it a bit more and apply.
> >
> >>processor with the TimeSys modified 2.6.1 kernel. The patch is for
> >>2.6.3. Let me know if there are any problems with it. If anyone can tell
> >>me why arch/ppc/boot/simple/misc.c was including elf.h in the first
> >>place I'd appreciate it. It doesn't appear to need it and it doesn't
> >>like task_struct now.
> >
> >Long ago it used to care more about the file it was dealing with. I'll
> >remove it from the other files in boot/ that include it as well.
>
> How does this still look?
I removed the #include as part of a greater fixing up of arch/ppc/boot,
that I'll hopefully get to Linus for the next release. I'll throw the
multithreaded coredump patch in as well then.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2004-03-04 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 20:25 [PATCH} PPC 32 multithreaded core dumps Greg Weeks
2004-02-25 21:13 ` Tom Rini
2004-03-04 13:05 ` Greg Weeks
2004-03-04 15:31 ` Tom Rini [this message]
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=20040304153149.GD26065@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=greg.weeks@timesys.com \
--cc=linux-kernel@vger.kernel.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.