From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: New zonefs file system
Date: Wed, 15 Jan 2020 23:21:49 +0000 [thread overview]
Message-ID: <BYAPR04MB5816E1F6B9479874B6B78A37E7370@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
Hi Stephen,
Would it be possible to have zonefs being picked-up for inclusion with
linux-next ? This is per Linus instructions as a condition for getting
zonefs initial pull request accepted. The code is now in good shape and
reviewed by several people.
The tree is here:
git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs.git
I prepared a for-next branch based off rc5.
Please let me know if there are additional things I need to do for
getting zonefs into linux-next, e.g. tags ?
Best regards.
--
Damien Le Moal
Western Digital Research
next reply other threads:[~2020-01-15 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 23:21 Damien Le Moal [this message]
2020-01-16 0:44 ` New zonefs file system Stephen Rothwell
2020-01-16 0:50 ` Damien Le Moal
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=BYAPR04MB5816E1F6B9479874B6B78A37E7370@BYAPR04MB5816.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).