From: Ralf Baechle <ralf@linux-mips.org>
To: "Steven J. Hill" <sjhill@realitydiluted.com>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS: Fixup ordering of micro assembler instructions.
Date: Tue, 19 Jun 2012 20:04:25 +0100 [thread overview]
Message-ID: <20120619190425.GA11280@linux-mips.org> (raw)
In-Reply-To: <4FD957C4.3000805@realitydiluted.com>
On Wed, Jun 13, 2012 at 10:17:24PM -0500, Steven J. Hill wrote:
> On 06/13/2012 10:08 PM, Steven J. Hill wrote:
> > On 05/30/2012 03:46 PM, linux-mips@linux-mips.org wrote:
> >> Author: Steven J. Hill <sjhill@mips.com> Fri May 11 01:35:47 2012 -0500
> >> Comitter: Ralf Baechle <ralf@linux-mips.org> Wed May 30 21:37:16 2012
> >> +0100 Commit: 6e3f8b69731d6dc03afdd47cfdddb0e479a6d2a9 Gitweb:
> >> http://git.linux-mips.org/g/ralf/linux/6e3f8b69731d Branch: master
> >
> >> A number of new instructions have been added to the micro assembler
> >> causing the list to no longer be in alphabetical order. This patch fixes
> >> up the name ordering.
> >
> >> Signed-off-by: Steven J. Hill <sjhill@mips.com> Cc:
> >> linux-mips@linux-mips.org Patchwork:
> >> https://patchwork.linux-mips.org/patch/3789/ Signed-off-by: Ralf Baechle
> >> <ralf@linux-mips.org>
> >
> > Ralf,
> >
> > This patch is fscked. The lines for _bbit0 and _bbit1 are duplicated.
> > Please commit a patch to remove the duplicate lines. Thanks.
> >
> And the file 'arch/mips/mm/uasm.c' was dropped the completely for no reason.
> This also needs to be fixed in your commit.
Also a victim of the conflicts I had to deal with, primarily because I
don't have the microMIPS stuff not yet applied.
Ralf
next prev parent reply other threads:[~2012-06-19 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1903563Ab2E3UqG/20120530204607Z+6387@eddie.linux-mips.org>
2012-06-14 3:08 ` MIPS: Fixup ordering of micro assembler instructions Steven J. Hill
2012-06-14 3:17 ` Steven J. Hill
2012-06-19 19:04 ` Ralf Baechle [this message]
2012-06-19 18:33 ` Ralf Baechle
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=20120619190425.GA11280@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=sjhill@realitydiluted.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