From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AB5811C3C0D for ; Mon, 13 Jan 2025 21:48:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736804899; cv=none; b=lxkPkjYw9esBfBq3h4mfv3mHA1n1wnfw4tiRdwwykPmc8fnkRLlzF84xAOXVZfZ2mORDFkutAX83jRUsZQtA7ZX4LbpFq0+WNp6ATGatmuvmWT2RiBiaWUeJz+HNeJKKGTlfi62ojyJlzCPi34zZ1TyOnOiPkMhUbcABV2dFbHU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736804899; c=relaxed/simple; bh=vsfyc46Z0PnrAXppERmVKpnnK/HWNH6QS4zNaQkHg8I=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=JP6PZvipNn/GTc3IU90dHz/0HN08OaThmhXF3z8dMkB5CjMcBLmxeH3VHlgO3JFHbCb0UdCMKIc80sEWeDzWfJZgxI2aYOaFStIX9Hj+GHYKxAqfzf0QuuPW43RYJCCL2qVqahYrUES8mRWU3Ezb8ZwpkCmuRCs1tsJDXzXFuhA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=fper8PUF; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="fper8PUF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E8B0AC4CED6; Mon, 13 Jan 2025 21:48:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1736804899; bh=vsfyc46Z0PnrAXppERmVKpnnK/HWNH6QS4zNaQkHg8I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fper8PUFVzjqrG3pWSoxFTsemVLwlQB32PFKfTuXo5tA/sLNmyeX8imTrtusYsARk TyyRxiLt8m89jJwaSyikjfNSdMPvCqJShqv76bUHL2MS8MMpyRsuZnYlbr6DYyu0jv LtRpaVC0R4va2IduVCLeYqhOZKTiIKEMmOOU5ZJncyy39HDct/YBjiMO3EcXD++8dJ nsyOSBoLSwjDT+RrGsZjesKw5MOYJL1lawbl3ncR57UH1jXI1zt6nDDNzRzOLFQUaS w39x4pW93tmTSZ4TRhcAfvo19P4HofSFQYOIi6YMBDJekLIMO48ex5gKv3DWbQCz5V MtW+rUE8uMjew== Date: Mon, 13 Jan 2025 16:48:17 -0500 From: Sasha Levin To: Dave Airlie Cc: Greg KH , Umesh Nerlige Ramappa , stable@vger.kernel.org, ashutosh.dixit@intel.com, dri-devel@lists.freedesktop.org Subject: Re: AAARRRGGGHHH!!!! (was Re: [PATCH 6.12.y] xe/oa: Fix query mode of operation for OAR/OAC) Message-ID: References: <2025010650-tuesday-motivate-5cbb@gregkh> <20250110205341.199539-1-umesh.nerlige.ramappa@intel.com> <2025011215-agreeing-bonfire-97ae@gregkh> <2025011247-spoilage-hamster-28b2@gregkh> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: On Mon, Jan 13, 2025 at 10:44:41AM +1000, Dave Airlie wrote: >Pretty sure we've explained how a few times now, not sure we can do much more. > >If you see a commit with a cherry-pick link in it and don't have any >sight on that commit in Linus's tree, ignore the cherry-pick link in >it, assume it's a future placeholder for that commit id. You could if >you wanted to store that info somewhere, but there shouldn't be a >need. > >When the initial commit enters during the next merge window, you look >for that subject or commit id in the stable tree already, if it >exists, dump the latest Linus patch on the floor, it's already in >stable your job is done. We can't rely too heavily on the subject line. Consider the following two very different commits that have the same subject line: 3119668c0e0a ("drm/amd/display: avoid disable otg when dig was disabled") 218784049f4b ("drm/amd/display: avoid disable otg when dig was disabled") Now, if a new commit lands and it has the following "Fixes:" tag: Fixes: abcdef12345 ("drm/amd/display: avoid disable otg when dig was disabled") Does it refer to one of the older commits? Or a new commit that will show up during the merge window? Or... What happens if a new commit with the very same subject line shows up, and it has a cherry-pick link that points to a completely different commit that is not in the tree yet? :) But just in general, there are so many odd combinations of commits where trying to follow the suggestion you've made will just break... Something like these two identical commits which are not tagged for stable: 21afc872fbc2 ("drm/amd/display: Add monitor patch for specific eDP") 3d71a8726e05 ("drm/amd/display: Add monitor patch for specific eDP") And the following two identical ones which are tagged for stable: b7cdccc6a849 ("drm/amd/display: Add monitor patch for specific eDP") 04a59c547575 ("drm/amd/display: Add monitor patch for specific eDP") -- Thanks, Sasha