From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS: Declare uasm bbit0 and bbit1 functions.
Date: Tue, 28 Dec 2010 17:59:33 +0100 [thread overview]
Message-ID: <20101228165933.GB375@linux-mips.org> (raw)
In-Reply-To: <1292889290-12849-2-git-send-email-ddaney@caviumnetworks.com>
On Mon, Dec 20, 2010 at 03:54:49PM -0800, David Daney wrote:
> these are already defined, but declaring them allow them to be used
> outside of uasm.c.
>
> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
> ---
> arch/mips/include/asm/uasm.h | 2 ++
Queued for 2.6.38 - but a few of your patches to uasm.h only apply with
fuzz so I'm wondering if I'm missing a patch or what your patches were
created against.
Thanks,
Ralf
next prev parent reply other threads:[~2010-12-28 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 23:54 [PATCH 0/2] MIPS: Use Octeon BBIT instructions in TLB handlers David Daney
2010-12-20 23:54 ` [PATCH 1/2] MIPS: Declare uasm bbit0 and bbit1 functions David Daney
2010-12-28 16:59 ` Ralf Baechle [this message]
2010-12-20 23:54 ` [PATCH 2/2] MIPS: Use BBIT instructions in TLB handlers David Daney
2010-12-28 17:00 ` 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=20101228165933.GB375@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.