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;
MIME-Version: 1.0
References: <154308522458.237140.16550557898744466932.stgit@dwillia2-desk3.amr.corp.intel.com>
 <20181125075410.D0EF220865@mail.kernel.org>
In-Reply-To: <20181125075410.D0EF220865@mail.kernel.org>
From:   Dan Williams <dan.j.williams@intel.com>
Date:   Sun, 25 Nov 2018 08:37:52 -0800
Message-ID: <CAPcyv4gQmTSqwLUnD2pR0hgJrmRAGEToHNmPZMYQ4+oUmJapRw@mail.gmail.com>
Subject: Re: [PATCH 2/2] libnvdimm, pfn: Pad pfn namespaces relative to other regions
To:     sashal@kernel.org
Cc:     linux-nvdimm <linux-nvdimm@lists.01.org>,
        stable <stable@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sat, Nov 24, 2018 at 11:54 PM Sasha Levin <sashal@kernel.org> wrote:
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: cfe30b872058 libnvdimm, pmem: adjust for section collisions with 'System RAM'.
>
> The bot has tested the following trees: v4.19.4, v4.14.83, v4.9.140.
>
> v4.19.4: Build OK!
> v4.14.83: Build OK!
> v4.9.140: Failed to apply! Possible dependencies:
>     Unable to calculate
>
>
> How should we proceed with this patch?

4.9-stable will need a manual backport since this code was refactored
in the intervening kernel releases.