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:   Fri, 4 Nov 2022 16:32:43 -0700
From:   Andrew Morton <akpm@linux-foundation.org>
To:     "Gupta, Pankaj" <pankaj.gupta@amd.com>
Cc:     linux-mm@kvack.org, linux-kernel@vger.kernel.org,
        dan.j.williams@intel.com, thomas.lendacky@amd.com
Subject: Re: [PATCH] mm/memremap.c: map FS_DAX device memory as decrypted
Message-Id: <20221104163243.a4c69e538bbfe3ee620e49f5@linux-foundation.org>
In-Reply-To: <0cbbe205-4573-2dce-14bf-f07c117ac7af@amd.com>
References: <20221102160728.3184016-1-pankaj.gupta@amd.com>
        <20221102130536.96c487d341544b7482eed038@linux-foundation.org>
        <0cbbe205-4573-2dce-14bf-f07c117ac7af@amd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Thu, 3 Nov 2022 08:55:40 +0100 "Gupta, Pankaj" <pankaj.gupta@amd.com> wrote:

> > Should this be backported into earlier kernels?
> 
> Yes, kernel >= 5.10 for clean back-port as it contains the below commit.
> 
> > 
> > Is b7b3c01b19159 a suitable Fixes: target?
> 
> Not very sure. But seems like the right commit for fixes tag as the 
> target code is moved in this commit with multiple range support addition.
> 
> Should I send a v2 with fixes & stable kernel fixes tag?

That's OK thanks - I made those changes to my copy.