From: Anton Blanchard <anton@samba.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: paulus@samba.org, jdike@karaya.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sigcontext_struct -> sigcontext
Date: Wed, 25 Sep 2002 23:59:53 +1000 [thread overview]
Message-ID: <20020925135953.GE2858@krispykreme> (raw)
In-Reply-To: <20020925170742.410f3887.sfr@canb.auug.org.au>
> PPC and PPC64 are the only two architectures that define a struct
> sigcontext_struct - all the others use struct sigcontext (UML seems to
> have been infected :-)). This patch just renames sigcontext_struct to
> sigcontext. It also renames sigcontext32_struct to sigcontext.
Thanks Stephen,
I have merged the ppc64 bits.
Anton
next prev parent reply other threads:[~2002-09-25 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 7:07 [PATCH] sigcontext_struct -> sigcontext Stephen Rothwell
2002-09-25 13:59 ` Anton Blanchard [this message]
2002-10-01 2:43 ` Jeff Dike
2002-10-01 15:33 ` Peter Bergner
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=20020925135953.GE2858@krispykreme \
--to=anton@samba.org \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).