From: "Frank Ch. Eigler" <fche@redhat.com>
To: DJ Delorie <dj@redhat.com>
Cc: cgen@sources.redhat.com, sid@sources.redhat.com
Subject: Re: [patch] xstormy16 psw semantics
Date: Fri, 14 Feb 2003 11:53:00 -0000 [thread overview]
Message-ID: <20030214115339.GE22855@redhat.com> (raw)
In-Reply-To: <200302132025.h1DKPqB31613@greed.delorie.com>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Hi -
dj wrote:
> Sanyo noted that the PSW wasn't getting set right. It is always set
> after the move operation. [...]
> Also, I'm still waiting for approval for my previous patches:
> http://sources.redhat.com/ml/sid/2003-q1/msg00012.html
> http://sources.redhat.com/ml/sid/2003-q1/msg00011.html
Please consider yourself as an xstormy16 port expert, and commit
such things at will. (Please still post diffs though.)
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-14 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 20:25 DJ Delorie
2003-02-14 11:53 ` Frank Ch. Eigler [this message]
2003-02-18 22:58 ` DJ Delorie
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=20030214115339.GE22855@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dj@redhat.com \
--cc=sid@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).