From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f46.google.com ([209.85.220.46]:37757 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751403Ab2IZVEF (ORCPT ); Wed, 26 Sep 2012 17:04:05 -0400 Received: by padhz1 with SMTP id hz1so753183pad.19 for ; Wed, 26 Sep 2012 14:04:05 -0700 (PDT) Message-ID: <50636DC2.5070700@gmail.com> Date: Thu, 27 Sep 2012 05:04:02 +0800 From: ching MIME-Version: 1.0 To: "linux-btrfs@vger.kernel.org" Subject: Re: typo in inode.c References: <5062EB9F.4080507@gmail.com> <20120926152313.GB14582@twin.jikos.cz> In-Reply-To: <20120926152313.GB14582@twin.jikos.cz> Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 09/26/2012 11:23 PM, David Sterba wrote: > On Wed, Sep 26, 2012 at 07:48:47PM +0800, ching wrote: >> There is a typo (?) in inode.c (git) > What's the top commit and what git tree? > > This has been fixed in 3.6-rc4 via > 287082b0bd10060e9c6b32ed9605174ddf2f672a > > david > This mistake is in http://git.kernel.org/?p=linux/kernel/git/mason/linux-btrfs.git;a=summary