From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@freescale.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] ppc32: emulate load/store string instructions
Date: Sat, 19 Mar 2005 15:36:00 +0100 [thread overview]
Message-ID: <43b769d454b49bc3f33414912c7fa3ab@kernel.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0503111609001.9384@blarg.somerset.sps.mot.com>
> + /* Early out if we are an invalid form of lswi */
> + if ((instword & INST_STRING_MASK) == INST_LSWX)
Typo --------------------------------------------^
Segher
next prev parent reply other threads:[~2005-03-21 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 22:12 [PATCH] ppc32: emulate load/store string instructions Kumar Gala
2005-03-19 14:36 ` Segher Boessenkool [this message]
2005-03-21 15:29 ` Kumar Gala
2005-03-21 15:39 ` [PATCH] ppc32: typo fix in load/store string emulation Kumar Gala
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=43b769d454b49bc3f33414912c7fa3ab@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=galak@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).