Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 18 Oct 2022 13:55:08 -0700
From:   Andrew Morton <akpm@linux-foundation.org>
To:     Dan Williams <dan.j.williams@intel.com>
Cc:     Nathan Chancellor <nathan@kernel.org>,
        Nick Desaulniers <ndesaulniers@google.com>,
        Tom Rix <trix@redhat.com>, <linux-mm@kvack.org>,
        <linux-kernel@vger.kernel.org>, <llvm@lists.linux.dev>,
        <patches@lists.linux.dev>
Subject: Re: [PATCH] mm/memremap: Mark folio_span_valid() as __maybe_unused
Message-Id: <20221018135508.d1844e583974b03eaa9aa354@linux-foundation.org>
In-Reply-To: <634ee87229a37_6be129430@dwillia2-xfh.jf.intel.com.notmuch>
References: <20221018152645.3195108-1-nathan@kernel.org>
        <634ee87229a37_6be129430@dwillia2-xfh.jf.intel.com.notmuch>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 18 Oct 2022 10:54:58 -0700 Dan Williams <dan.j.williams@intel.com> wrote:

> > ---
> > 
> > I am aware the Fixes SHA is probably not stable but I figured I would
> > include it anyways.
> 
> This fix looks good to me, but I assume commit-ids are not stable until
> the patch moves from mm-unstable to mm-stable. Andrew, do I have that
> right?

Yes, mm-unstable hashes change daily.  But knowing the title of the
patch which needs the fix is quite helpful.