From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yufen Yu <yuyufen@huawei.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [GIT PULL] f2fs update for 4.16-rc1
Date: Thu, 3 May 2018 11:49:00 +0200 [thread overview]
Message-ID: <20180503094900.GA21272@suse.cz> (raw)
In-Reply-To: <20180503084259.4a3b68d6@canb.auug.org.au>
On Thu, May 03, 2018 at 08:42:59AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 3 Apr 2018 12:29:19 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Ping?
>
> Ping again ...
>
> So has Chris gone missing? Or should I just remove the btrfs tree from linux-next?
As far as btrfs code changes are concerned, they go through my tree. The
other conflicting changes are some cgroup tweaks that have impact on
btrfs but do not affect the development.
next prev parent reply other threads:[~2018-05-03 9:51 UTC|newest]
Thread overview: 17+ 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:32 ` Jaegeuk Kim
2018-01-30 22:54 ` Stephen Rothwell
2018-01-31 0:25 ` Jaegeuk Kim
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:20 ` Tejun Heo
2018-04-03 14:45 ` Stephen Rothwell
2018-05-02 22:42 ` Stephen Rothwell
2018-05-03 9:49 ` David Sterba [this message]
2018-06-18 3:38 ` Stephen Rothwell
2018-06-18 18:05 ` Chris Mason
2018-06-18 18:05 ` Chris Mason
2018-06-20 23:26 ` Stephen Rothwell
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=20180503094900.GA21272@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=jaegeuk@kernel.org \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.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 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.