From: Christoph Hellwig <hch@lst.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
Amir Goldstein <amir73il@gmail.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 2/3] xfs: use uuid_be to implement the uuid_t type
Date: Wed, 10 May 2017 16:15:46 +0200 [thread overview]
Message-ID: <20170510141546.GA23916@lst.de> (raw)
In-Reply-To: <1494420895.16411.4.camel@linux.intel.com>
On Wed, May 10, 2017 at 03:54:55PM +0300, Andy Shevchenko wrote:
> I'm fine with above and it looks like I could rebase my current work
> whenever (1) has been done.
>
> Looking forward to repository with changes I can rebase on top of.
Here is what I currently have:
http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/uuid-types
It hasn't survived the buildbot yet, so take it with a grain of salt.
next prev parent reply other threads:[~2017-05-10 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 7:57 XFS UUID cleanups Christoph Hellwig
2017-05-05 7:57 ` [PATCH 1/3] xfs: use uuid_copy() helper to abstract uuid_t Christoph Hellwig
2017-05-05 7:57 ` [PATCH 2/3] xfs: use uuid_be to implement the uuid_t type Christoph Hellwig
2017-05-05 8:44 ` Amir Goldstein
2017-05-05 8:48 ` Christoph Hellwig
2017-05-05 9:42 ` Andy Shevchenko
2017-05-05 9:56 ` Christoph Hellwig
2017-05-05 10:06 ` Andy Shevchenko
2017-05-05 10:10 ` Christoph Hellwig
2017-05-10 8:39 ` Amir Goldstein
2017-05-10 12:01 ` Christoph Hellwig
2017-05-10 12:54 ` Andy Shevchenko
2017-05-10 14:15 ` Christoph Hellwig [this message]
2017-05-05 7:57 ` [PATCH 3/3] xfs: remove uuid_getnodeuniq and xfs_uu_t Christoph Hellwig
2017-05-05 8:27 ` Amir Goldstein
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=20170510141546.GA23916@lst.de \
--to=hch@lst.de \
--cc=amir73il@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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 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.