From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Eric Sandeen <sandeen@redhat.com>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH for 4.15] libxfs: fix dev_t handling in inode forks
Date: Tue, 28 Nov 2017 06:04:51 -0800 [thread overview]
Message-ID: <20171128140451.GA2293@infradead.org> (raw)
In-Reply-To: <4be5c1a1-d274-11b8-935b-ddf23d5b5e64@sandeen.net>
On Mon, Nov 27, 2017 at 02:16:47PM -0600, Eric Sandeen wrote:
> Maybe what I'm missing is that it's stupid to carry all those conversions
> around if they're not needed. ;)
>
> I'll stuff the xfs format device number into the "linux" i_rdev, with a comment
Yes, that was the idea.
prev parent reply other threads:[~2017-11-28 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 1:15 [PATCH for 4.15] libxfs: fix dev_t handling in inode forks Darrick J. Wong
2017-11-16 19:13 ` Eric Sandeen
2017-11-17 16:57 ` Christoph Hellwig
2017-11-27 19:26 ` Eric Sandeen
2017-11-27 20:16 ` Eric Sandeen
2017-11-28 14:04 ` Christoph Hellwig [this message]
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=20171128140451.GA2293@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--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).