From: Christoph Hellwig <hch@infradead.org>
To: torvalds@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] freevxfs updates for 4.8
Date: Thu, 28 Jul 2016 15:33:16 +0200 [thread overview]
Message-ID: <20160728133316.GA12123@infradead.org> (raw)
Hi Linus,
after many years I finally have some major freevxfs updated, thanks to
Krzysztof Błaszkowski:
The following changes since commit bf1bb4b460c8dc3a33793bff21464a9d816697ad:
freevxfs: update Kconfig information (2016-06-13 10:20:39 +0200)
are available in the git repository at:
git://git.infradead.org/users/hch/freevxfs.git tags/freevxfs-for-4.8
for you to fetch changes up to bf1bb4b460c8dc3a33793bff21464a9d816697ad:
freevxfs: update Kconfig information (2016-06-13 10:20:39 +0200)
----------------------------------------------------------------
freevxfs updates for 4.7:
- support for foreign endianess and HP-UP superblocks from
Krzysztof Błaszkowski
----------------------------------------------------------------
next reply other threads:[~2016-07-28 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 13:33 Christoph Hellwig [this message]
2016-07-28 20:03 ` [GIT PULL] freevxfs updates for 4.8 Linus Torvalds
2016-07-29 7:57 ` Christoph Hellwig
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=20160728133316.GA12123@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).