From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chris Mason <clm@fb.com>
Cc: Josef Bacik <jbacik@fb.com>, Jaegeuk Kim <jaegeuk@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yufen Yu <yuyufen@huawei.com>, Tejun Heo <tj@kernel.org>,
David Sterba <dsterba@suse.cz>
Subject: Re: [GIT PULL] f2fs update for 4.16-rc1
Date: Thu, 21 Jun 2018 09:26:07 +1000 [thread overview]
Message-ID: <20180621092607.3e13e43f@canb.auug.org.au> (raw)
In-Reply-To: <0CA8215A-6529-40B1-90FB-A5902EA47549@fb.com>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
Hi Chris,
On Mon, 18 Jun 2018 14:05:32 -0400 Chris Mason <clm@fb.com> wrote:
>
> Really sorry for the hassle, the f2fs subject line got this filtered
> into a different inbox. Tejun and Josef are working out these btrfs
Ah, that explains it.
> cgroup fixes, so I've pushed v4.17 to my -next tree for now.
Thanks.
> Dave has been doing the Btrfs merge window for some time, so focusing
> linux-next on his tree is a better fit. But either way, I've fixed my
> my email filters so you're back at the top where you belong.
I'll just leave things as they are for now.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-06-20 23:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 22:32 [GIT PULL] f2fs update for 4.16-rc1 Jaegeuk Kim
2018-01-30 22:54 ` Stephen Rothwell
2018-01-31 0:25 ` Jaegeuk Kim
2018-01-31 22:25 ` Stephen Rothwell
2018-03-13 23:17 ` Stephen Rothwell
2018-04-03 2:29 ` Stephen Rothwell
2018-04-03 14:20 ` Tejun Heo
2018-04-03 14:45 ` Stephen Rothwell
2018-06-18 3:38 ` Stephen Rothwell
2018-06-18 18:05 ` Chris Mason
2018-06-20 23:26 ` Stephen Rothwell [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=20180621092607.3e13e43f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=jbacik@fb.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yuyufen@huawei.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).