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:   Sun, 2 Oct 2022 17:37:15 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     wangyong <yongw.pur@gmail.com>
Cc:     jaewon31.kim@samsung.com, linux-kernel@vger.kernel.org,
        mhocko@kernel.org, stable@vger.kernel.org, wang.yong12@zte.com.cn
Subject: Re: [PATCH v2 stable-4.19 0/3] page_alloc: consider highatomic
 reserve in watermark fast backports to 4.19
Message-ID: <YzmwKxYVDSWsaPCU@kroah.com>
References: <Yyn7MoSmV43Gxog4@kroah.com>
 <20220925103529.13716-1-yongw.pur@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220925103529.13716-1-yongw.pur@gmail.com>
Precedence: bulk

On Sun, Sep 25, 2022 at 03:35:26AM -0700, wangyong wrote:
> Here are the corresponding backports to 4.19.
> And fix classzone_idx context differences causing patch merge conflicts.
> 
> Original commit IDS:
> 	3334a45 mm/page_alloc: use ac->high_zoneidx for classzone_idx
> 	f27ce0e page_alloc: consider highatomic reserve in watermark fast
> 	9282012 page_alloc: fix invalid watermark check on a negative value
> 
> Changes from v1:
> - Add commit information of the original patches.

None of these have your signed-off-by on them showing that the backport
came from you and that you are responsible for them.

So even if we did think they were valid to backport, I can't take them
as-is :(

thanks,

greg k-h