From: Chris Mason <clm@fb.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Josef Bacik <jbacik@fb.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: new stuff in the btrfs tree
Date: Wed, 13 Aug 2014 20:44:05 -0400 [thread overview]
Message-ID: <53EC0655.8030600@fb.com> (raw)
In-Reply-To: <20140814100750.5c6368f1@canb.auug.org.au>
On 08/13/2014 08:07 PM, Stephen Rothwell wrote:
> Hi all,
>
> Are all the commits just added to the btrfs tree really intended for
> v3.17? If not then please remove them until after v3.17-rc1 is
> released. If so, then they are very late :-(
>
> I suspect the latter because some of them seem to date from June (and a
> few even from February).
>
Hi Stephen,
Yes, these are for 3.17-rc1. My push to my -next tree was late due to
vacations and because we've been hunting a deadlock in our workqueue
code, but I've had these in testing for some time.
-chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <clm@fb.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Josef Bacik <jbacik@fb.com>
Cc: <linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: new stuff in the btrfs tree
Date: Wed, 13 Aug 2014 20:44:05 -0400 [thread overview]
Message-ID: <53EC0655.8030600@fb.com> (raw)
In-Reply-To: <20140814100750.5c6368f1@canb.auug.org.au>
On 08/13/2014 08:07 PM, Stephen Rothwell wrote:
> Hi all,
>
> Are all the commits just added to the btrfs tree really intended for
> v3.17? If not then please remove them until after v3.17-rc1 is
> released. If so, then they are very late :-(
>
> I suspect the latter because some of them seem to date from June (and a
> few even from February).
>
Hi Stephen,
Yes, these are for 3.17-rc1. My push to my -next tree was late due to
vacations and because we've been hunting a deadlock in our workqueue
code, but I've had these in testing for some time.
-chris
next prev parent reply other threads:[~2014-08-14 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 0:07 linux-next: new stuff in the btrfs tree Stephen Rothwell
2014-08-14 0:44 ` Chris Mason [this message]
2014-08-14 0:44 ` Chris Mason
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=53EC0655.8030600@fb.com \
--to=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.