From: Ralf Baechle <ralf@linux-mips.org>
To: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Cc: linux-mips@linux-mips.org, aaro.koskinen@iki.fi,
david.daney@cavium.com, linux-kernel@vger.kernel.org,
markos.chandras@imgtec.com, dengcheng.zhu@imgtec.com,
chenhc@lemote.com, akpm@linux-foundation.org
Subject: Re: [PATCH] MIPS: Remove a temporary hack for debugging cache flushes in SMTC configuration
Date: Thu, 20 Nov 2014 22:54:18 +0100 [thread overview]
Message-ID: <20141120215417.GA20017@linux-mips.org> (raw)
In-Reply-To: <20141120214557.GA19608@linux-mips.org>
On Thu, Nov 20, 2014 at 10:45:58PM +0100, Ralf Baechle wrote:
> So I'm more thinking of something like below.
And while we're at it, these were unused rsp. only used by other
unused macros.
Ralf
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
arch/mips/include/asm/r4kcache.h | 8 --------
1 file changed, 8 deletions(-)
diff --git a/arch/mips/include/asm/r4kcache.h b/arch/mips/include/asm/r4kcache.h
index cd6e0af..392b159 100644
--- a/arch/mips/include/asm/r4kcache.h
+++ b/arch/mips/include/asm/r4kcache.h
@@ -124,10 +124,6 @@ extern void mt_cflush_release(void);
#define __inv_dflush_prologue __dflush_prologue
#define __inv_dflush_epilogue __dflush_epilogue
-#define __sflush_prologue {
-#define __sflush_epilogue }
-#define __inv_sflush_prologue __sflush_prologue
-#define __inv_sflush_epilogue __sflush_epilogue
#else /* CONFIG_MIPS_MT */
@@ -137,10 +133,6 @@ extern void mt_cflush_release(void);
#define __dflush_epilogue }
#define __inv_dflush_prologue {
#define __inv_dflush_epilogue }
-#define __sflush_prologue {
-#define __sflush_epilogue }
-#define __inv_sflush_prologue {
-#define __inv_sflush_epilogue }
#endif /* CONFIG_MIPS_MT */
prev parent reply other threads:[~2014-11-20 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 2:27 [PATCH] MIPS: Remove a temporary hack for debugging cache flushes in SMTC configuration Leonid Yegoshin
2014-09-06 2:27 ` Leonid Yegoshin
2014-11-20 21:45 ` Ralf Baechle
2014-11-20 21:54 ` Ralf Baechle [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=20141120215417.GA20017@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=aaro.koskinen@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=chenhc@lemote.com \
--cc=david.daney@cavium.com \
--cc=dengcheng.zhu@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.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 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.