From: Paul Mackerras <paulus@samba.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc64-dev@lists.linuxppc.org,
Anton Blanchard <anton@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PPC64] xmon sparse cleanups
Date: Tue, 5 Oct 2004 20:38:52 +1000 [thread overview]
Message-ID: <16738.31164.464250.638432@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20041005064255.GF3695@zax>
David Gibson writes:
> Andrew, please apply:
>
> This patch removes many sparse warnings from the xmon code. Mostly
> K&R function declarations and 0-instead-of-NULLs.
The trouble with this patch is that it makes ppc-opc.c diverge from
the version in binutils, which is where it came from. I'd rather keep
it as close as possible to that version. I have no problem with the
changes to the other files.
Paul.
next prev parent reply other threads:[~2004-10-05 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 6:42 David Gibson
2004-10-05 10:38 ` Paul Mackerras [this message]
2004-10-11 2:11 ` David Gibson
2004-10-21 3:36 David Gibson
2004-10-23 8:20 ` Paul Mackerras
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=16738.31164.464250.638432@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®