From: David Miller <davem@davemloft.net>
To: sandeen@sandeen.net
Cc: matorola@gmail.com, sparclinux@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [sparc64] crc32c misbehave
Date: Tue, 06 Jun 2017 15:05:55 -0400 (EDT) [thread overview]
Message-ID: <20170606.150555.855421580901340490.davem@davemloft.net> (raw)
In-Reply-To: <20170531.124916.1406665885250072302.davem@davemloft.net>
Just FYI, I've meanwhile pushed a fix for the GCC bug that created
this mess to all active branches.
next prev parent reply other threads:[~2017-06-06 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADxRZqzgaL4ew6PVek3WBsdwo6GcT0ORx=7h+6p0V3NAr8qF+w@mail.gmail.com>
[not found] ` <CADxRZqzNTB1n0g1r_2rLsjifHpJ+_x1WPxNOSqEcHbi74jHi5w@mail.gmail.com>
[not found] ` <20170531.115335.213691069712156732.davem@davemloft.net>
2017-05-31 16:19 ` [sparc64] crc32c misbehave Eric Sandeen
2017-05-31 16:31 ` Eric Sandeen
2017-05-31 16:49 ` David Miller
2017-06-01 21:44 ` David Miller
2017-06-02 1:57 ` David Miller
2017-06-02 2:10 ` Eric Sandeen
2017-06-02 3:33 ` David Miller
2017-06-02 3:34 ` Eric Sandeen
2017-06-06 19:05 ` David Miller [this message]
2017-06-06 19:09 ` Eric Sandeen
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=20170606.150555.855421580901340490.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-xfs@vger.kernel.org \
--cc=matorola@gmail.com \
--cc=sandeen@sandeen.net \
--cc=sparclinux@vger.kernel.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 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 NNTP newsgroup(s).