From: Christoph Hellwig <hch@lst.de>
To: Brian Foster <bfoster@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: require 64-bit sector_t
Date: Wed, 18 Jun 2014 17:21:35 +0200 [thread overview]
Message-ID: <20140618152135.GA11821@lst.de> (raw)
In-Reply-To: <20140617141431.GA8905@bfoster.bfoster>
On Tue, Jun 17, 2014 at 10:14:31AM -0400, Brian Foster wrote:
> Given that the existence of the string indicates large block/inode
> numbers, shouldn't we leave it to avoid any confusion? That aside, the
> rest of the patch looks fine to me.
As these have been enabled in any sane configuration I don't really see
a point in printing these.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-18 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 16:44 [PATCH] xfs: require 64-bit sector_t Christoph Hellwig
2014-06-17 14:14 ` Brian Foster
2014-06-18 15:21 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-14 16:46 Christoph Hellwig
2013-12-10 16:20 ` Christoph Hellwig
2014-06-16 14:47 ` Christoph Hellwig
2013-12-13 21:37 ` Ben Myers
2013-12-13 23:01 ` Ben Myers
2013-12-16 22:15 ` Ben Myers
2014-01-09 15:19 ` Ben Myers
2014-01-09 18:48 ` Michael L. Semon
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=20140618152135.GA11821@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--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 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).