From: Dan Malek <dmalek@jlc.net>
To: Alexander Larsson <alex@signum.se>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Bug report
Date: Mon, 07 Jun 1999 09:53:06 -0400 [thread overview]
Message-ID: <375BCEC2.FE8B95B1@jlc.net> (raw)
In-Reply-To: Pine.LNX.4.04.9906071049580.26155-100000@tammy.signum.se
Alexander Larsson wrote:
>
> In the embedded 2.2.5 sources i found the following in
> arch/ppc/kernel/ppc-stub.c
>
> static inline void set_msr(int msr)
> {
> asm volatile("mfmsr %0" : : "r" (msr));
> }
>
> Shouldn't that be mtmsr?
Yes....Fortunately, it is only used in the kgbd portion of the
kernel, so normal operations are not affected.
-- Dan
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
prev parent reply other threads:[~1999-06-07 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-07 8:54 Bug report Alexander Larsson
1999-06-07 13:53 ` Dan Malek [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=375BCEC2.FE8B95B1@jlc.net \
--to=dmalek@jlc.net \
--cc=alex@signum.se \
--cc=linuxppc-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;
as well as URLs for NNTP newsgroup(s).