Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 5 Nov 2018 17:51:37 +0100
From:   David Sterba <dsterba@suse.cz>
To:     Arnd Bergmann <arnd@arndb.de>
Cc:     Qu Wenruo <wqu@suse.de>, Chris Mason <clm@fb.com>,
        David Sterba <DSterba@suse.com>,
        Josef Bacik <josef@toxicpanda.com>,
        Gu Jinxiang <gujx@cn.fujitsu.com>,
        Changbin Du <changbin.du@gmail.com>,
        Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>,
        Anand Jain <anand.jain@oracle.com>,
        Nikolay Borisov <nborisov@suse.com>,
        linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: avoid link error with CONFIG_NO_AUTO_INLINE
Message-ID: <20181105165137.GD9136@twin.jikos.cz>
Reply-To: dsterba@suse.cz
Mail-Followup-To: dsterba@suse.cz, Arnd Bergmann <arnd@arndb.de>,
        Qu Wenruo <wqu@suse.de>, Chris Mason <clm@fb.com>,
        David Sterba <DSterba@suse.com>, Josef Bacik <josef@toxicpanda.com>,
        Gu Jinxiang <gujx@cn.fujitsu.com>,
        Changbin Du <changbin.du@gmail.com>,
        Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>,
        Anand Jain <anand.jain@oracle.com>,
        Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org,
        linux-kernel@vger.kernel.org
References: <20181103153941.1881966-1-arnd@arndb.de>
 <87d4e8ce-2142-9d6e-498a-c7e5b83964eb@suse.de>
 <CAK8P3a27sNTiKV--smXd1wUzkGY70uUhS1rif6tgUobE+YYcbw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAK8P3a27sNTiKV--smXd1wUzkGY70uUhS1rif6tgUobE+YYcbw@mail.gmail.com>
User-Agent: Mutt/1.5.23.1 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sun, Nov 04, 2018 at 11:32:03PM +0100, Arnd Bergmann wrote:
> >> Cc: Changbin Du <changbin.du@gmail.com>
> >> Fixes: 943b8435c3bd ("kernel hacking: add a config option to disable
> >> compiler auto-inlining")
> >
> > I can't find it in the mainline kernel, is the commit hash correct?
> > If not merged, we should still has a chance to further polish that patch.
> 
> It's in linux-next.

I can't find it in current linux-next either, the final reference in
Fixes: must refer to a commit in Linus' tree.

You can take this fix with the patch that introduces the config option
(ack for that) in case merging through the btrfs tree would be too late
for it (ie. no common base for the git trees containg the new code and fix).

Or I can take it through btrfs tree in 4.20-rc cycle. In both cases the
Fixes: does not need to be there.