Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 14 Oct 2020 08:55:22 +0200
From:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To:     Roland Scheidegger <sroland@vmware.com>
Cc:     linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        Zack Rusin <zackr@vmware.com>,
        Martin Krastev <krastevm@vmware.com>,
        Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.8 050/124] drm/vmwgfx: Fix error handling in get_node
Message-ID: <20201014065522.GA2762376@kroah.com>
References: <20201012133146.834528783@linuxfoundation.org>
 <20201012133149.276124624@linuxfoundation.org>
 <703ec8e7-f036-948d-f155-73f0c946aeba@vmware.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <703ec8e7-f036-948d-f155-73f0c946aeba@vmware.com>
Precedence: bulk

On Tue, Oct 13, 2020 at 05:55:31PM +0200, Roland Scheidegger wrote:
> Hi,
> 
> this commit should NOT be applied to 5.8.
> It fixes a regression introduced by
> 58e4d686d456c3e356439ae160ff4a0728940b8e (drm/ttm: cleanup
> ttm_mem_type_manager_func.get_node interface v3) which is part of 5.9
> but not 5.8.
> Applying this to 5.8 will very likely break things. I don't know why it
> ended up as a candidate for 5.8.

Now dropped, thanks.  And it was probably picked up due to the wording
in the changelog text, along with a lack of a "Fixes:" tag that pointed
at the exact change it fixed up, which would have shown that this is a
5.9-only thing.

thanks,

greg k-h