Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932684AbcCVCig (ORCPT ); Mon, 21 Mar 2016 22:38:36 -0400 Received: from mail-io0-f174.google.com ([209.85.223.174]:33740 "EHLO mail-io0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932238AbcCVCie (ORCPT ); Mon, 21 Mar 2016 22:38:34 -0400 MIME-Version: 1.0 In-Reply-To: <20160322022412.zpsdrxiocoivcnwg@floor.thefacebook.com> References: <20160322002436.angclbg3eg6c65ik@floor.thefacebook.com> <20160322021533.xqalzzk5itglqu3x@floor.thefacebook.com> <20160322022412.zpsdrxiocoivcnwg@floor.thefacebook.com> Date: Mon, 21 Mar 2016 19:38:33 -0700 X-Google-Sender-Auth: n396zuTviWgHuUPQGYvKcLGTe00 Message-ID: Subject: Re: [GIT PULL] Btrfs From: Linus Torvalds To: Chris Mason , Linus Torvalds , LKML , linux-btrfs Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 475 Lines: 13 On Mon, Mar 21, 2016 at 7:24 PM, Chris Mason 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