From: Eric Botcazou <ebotcazou@adacore.com>
To: David Miller <davem@davemloft.net>
Cc: gcc-patches@gcc.gnu.org, cederman@gaisler.com,
sebastian.huber@embedded-brains.de, daniel@gaisler.com
Subject: Re: [PATCH] [SPARC] Add a workaround for the LEON3FT store-store errata
Date: Mon, 26 Jun 2017 07:22:00 -0000 [thread overview]
Message-ID: <3595556.1cW9hBQDSO@polaris> (raw)
In-Reply-To: <20170622.100610.731957483034969313.davem@davemloft.net>
> Eric, does Daniel's patch meet your requirements now?
Yes, modulo the config/sparc/sparc-c.c hunk, what is it used for?
But the implementation looks a bit strange, can't we merge the essentially
identical blocks of code into a single block, as for the other fixes?
--
Eric Botcazo
next prev parent reply other threads:[~2017-06-26 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 13:28 Daniel Cederman
2017-06-22 14:06 ` David Miller
2017-06-26 7:22 ` Eric Botcazou [this message]
2017-06-27 8:52 ` Daniel Cederman
-- strict thread matches above, loose matches on Subject: below --
2017-06-14 8:26 Daniel Cederman
2017-06-20 5:55 ` Sebastian Huber
2017-06-20 15:44 ` David Miller
2017-06-20 19:19 ` Eric Botcazou
2017-06-20 19:54 ` David Miller
2017-06-21 6:35 ` Eric Botcazou
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=3595556.1cW9hBQDSO@polaris \
--to=ebotcazou@adacore.com \
--cc=cederman@gaisler.com \
--cc=daniel@gaisler.com \
--cc=davem@davemloft.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=sebastian.huber@embedded-brains.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).