From: Andreas Schwab <schwab@linux-m68k.org>
To: Lanttor <lanttor.guo@freescale.com>
Cc: linux-m68k@vger.kernel.org,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: Interrupt issue on m68k platform and some fix
Date: Thu, 02 Jul 2009 11:05:59 +0200 [thread overview]
Message-ID: <m38wj7tpxk.fsf@hase.home> (raw)
In-Reply-To: <4A4C76CB.4000208@freescale.com> (Lanttor's message of "Thu, 02 Jul 2009 16:58:51 +0800")
Lanttor <lanttor.guo@freescale.com> writes:
> So this code sets value 1 to the second byte of preempt_count field.
No. Byte would be addqb.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-07-02 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 4:07 Interrupt issue on m68k platform and some fix Lanttor
2009-07-02 8:24 ` Andreas Schwab
2009-07-02 8:58 ` Lanttor
2009-07-02 9:05 ` Andreas Schwab [this message]
2009-07-02 10:06 ` Lanttor
2009-07-02 20:25 ` Roman Hodek
2009-07-03 3:18 ` Lanttor
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=m38wj7tpxk.fsf@hase.home \
--to=schwab@linux-m68k.org \
--cc=lanttor.guo@freescale.com \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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