[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+55aFwe58WRAYC_+rhkGRPmS5FjdckxHa1KS0kpqv8RYbb9eg@mail.gmail.com>
Date: Mon, 21 Mar 2016 19:38:33 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Chris Mason <clm@...com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-btrfs <linux-btrfs@...r.kernel.org>
Subject: Re: [GIT PULL] Btrfs
On Mon, Mar 21, 2016 at 7:24 PM, Chris Mason <clm@...com> wrote:
>
> Hmmm, rereading my answer I realized I didn't actually answer. I really
> think this is fixed. I left the warning only because I originally
> expected something much more exotic.
Ok. It's more that you said the top commit fixes a problem, and the
only case where the top commit makes a difference it will also do that
WARN_ON_ONCE.
But it's pulled, test-built, and pushed out now.
Linus
Powered by blists - more mailing lists