From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: new 64 bit math link fail in xfs in linux-next today
Date: Wed, 16 Apr 2014 12:09:37 -0400 [thread overview]
Message-ID: <534EAB41.60901@windriver.com> (raw)
Hi Dave,
Not sure if this has been reported yet, but this new failure showed
up in the xtensa link of today's linux-next builds.
http://kisskb.ellerman.id.au/kisskb/buildresult/10938384/
Paul.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
xfs@oss.sgi.com
Subject: new 64 bit math link fail in xfs in linux-next today
Date: Wed, 16 Apr 2014 12:09:37 -0400 [thread overview]
Message-ID: <534EAB41.60901@windriver.com> (raw)
Hi Dave,
Not sure if this has been reported yet, but this new failure showed
up in the xtensa link of today's linux-next builds.
http://kisskb.ellerman.id.au/kisskb/buildresult/10938384/
Paul.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-04-16 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 16:09 Paul Gortmaker [this message]
2014-04-16 16:09 ` new 64 bit math link fail in xfs in linux-next today Paul Gortmaker
2014-04-16 20:59 ` Mark Tinguely
2014-04-16 21:45 ` Paul Gortmaker
2014-04-16 21:45 ` Paul Gortmaker
2014-04-16 21:51 ` [PATCH] xfs: fix 32bit __divdi3 undefined Mark Tinguely
2014-04-16 21:57 ` Eric Sandeen
2014-04-16 22:10 ` Dave Chinner
2014-04-16 22:30 ` Mark Tinguely
2014-04-16 21:57 ` new 64 bit math link fail in xfs in linux-next today Dave Chinner
2014-04-16 21:57 ` Dave Chinner
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=534EAB41.60901@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=david@fromorbit.com \
--cc=linux-next@vger.kernel.org \
--cc=xfs@oss.sgi.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.