From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Biggers <ebiggers3@gmail.com>,
linux-xfs@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
Eric Sandeen <sandeen@redhat.com>,
Eric Biggers <ebiggers@google.com>,
Felix Janda <felix.janda@posteo.de>
Subject: Re: [PATCH v3] Fix building xfsprogs on 32-bit platforms
Date: Thu, 22 Dec 2016 00:58:04 -0800 [thread overview]
Message-ID: <20161222085804.GB23054@infradead.org> (raw)
In-Reply-To: <1a75e88c-014c-b245-2271-f7d201da1285@sandeen.net>
On Wed, Dec 21, 2016 at 03:33:11PM -0600, Eric Sandeen wrote:
> TBH I haven't really tested this on a 32-bit system yet,
> I'm sorry. Right now, I plan to get it into the tree right
> after we cut the next release this week.
It would be useful to have it in the release to avoid a regression.
next prev parent reply other threads:[~2016-12-22 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 0:42 [PATCH v3] Fix building xfsprogs on 32-bit platforms Eric Biggers
2016-12-02 13:13 ` Christoph Hellwig
2016-12-03 15:21 ` Felix Janda
2016-12-21 19:04 ` Eric Biggers
2016-12-21 21:33 ` Eric Sandeen
2016-12-22 8:58 ` Christoph Hellwig [this message]
2016-12-22 15: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=20161222085804.GB23054@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=felix.janda@posteo.de \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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).