From: Ralf Baechle <ralf@linux-mips.org>
To: Zhang Le <r0bertz@gentoo.org>
Cc: linux-mips@linux-mips.org, yanh@lemote.com, zhangfx@lemote.com,
penglj@lemote.com
Subject: Re: [PATCH] Loongson 2 requires no NOP insns to work around hazards
Date: Sat, 18 Apr 2009 14:22:34 +0200 [thread overview]
Message-ID: <20090418122234.GH11339@linux-mips.org> (raw)
In-Reply-To: <1239786112-22120-1-git-send-email-r0bertz@gentoo.org>
On Wed, Apr 15, 2009 at 05:01:52PM +0800, Zhang Le wrote:
> Quoting from Loongson2FUserGuide.pdf:
>
> 5.22.1 Hazards
> The processor detects most of the pipeline hazards in hardware, including CP0 hazards and
> load hazards. No NOP instructions are required to correct instruction sequences.
Patch looks ok - but *please* generate patches against a new source tree.
Your patch rejects because of another patches that was applied over two
week before you sent this one.
Applied,
Ralf
next prev parent reply other threads:[~2009-04-18 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 9:01 [PATCH] Loongson 2 requires no NOP insns to work around hazards Zhang Le
2009-04-18 12:22 ` Ralf Baechle [this message]
2009-04-18 13:30 ` Zhang Le
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=20090418122234.GH11339@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=penglj@lemote.com \
--cc=r0bertz@gentoo.org \
--cc=yanh@lemote.com \
--cc=zhangfx@lemote.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