From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.9]) (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 EE1BD3921E6 for ; Wed, 25 Feb 2026 10:09:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.9 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772014162; cv=none; b=GYXomKnhrQc8LAm2Wwx1jkQaUH24zDh1I12yAdhY3rBrgwqFaZpaN2JKrjpw/WBGTaZG4zjTHenHWKSOIztRhwZ223BE+mZ0tschDz4ogXPeQhylOKXZNjK2RXpc2ivRIySX8oCU6D/6kh2Tc0WFG7+pwLCPQ/Yiy2/nu/N8ptg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772014162; c=relaxed/simple; bh=wepSaOm0t+IvhtpYH3OBVq6rQXHK0TLue5fO2Q9N3pY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=kWK5wjsHcu7kuKH1+B5Niijmc6kH/7FA9EKVVuo+xYD381ufrVl2FJo0qjyZ0p2+/FqbyFH5nVYsBRjfFXQeAOcaYRkjhHLReT8hoQBg8poUWfyFZKHIejYPhI3Xg3UYJ0aVOKbXfWdDrHAw2ROHjQJ9/KE248+mxfbK7kEjoLA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=Yj1bgqU5; arc=none smtp.client-ip=198.175.65.9 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="Yj1bgqU5" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1772014159; x=1803550159; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=wepSaOm0t+IvhtpYH3OBVq6rQXHK0TLue5fO2Q9N3pY=; b=Yj1bgqU55YmAxk9n9dIM6aB4nT9ptEt0FsdkDG2ytYEBw7IhkZTcd2rr n5GKX4VwWeTgt1/Oo/ltWMtl02nxnCiQanilr/zRMknnb3K71lM2OGBYT kVDbr8nSNCVoVit+wUEbKyu0Dj4IyU5o5AE8VxaO0P2CfXRspkNHNFI9b r7x6QKxlyIHQxZUaqGZEc9tjIDbAPJoUsHnXIVGhXQDzgmxihmXKtZijP /sry4nJFVDJYW6EV9r03mIQsPjYx+XK7d9jxtORJkgLps/cZfIJ5+X30H zIs3U+LUpSUP954rmk6/v44Hy7xbCYKdKu7rTUk9sXhE6pFKYw+CTbAaN A==; X-CSE-ConnectionGUID: Ts5PCfGtQ9iFHqoDvdtX8w== X-CSE-MsgGUID: a1eFWWVZQMmR7W54LHax8g== X-IronPort-AV: E=McAfee;i="6800,10657,11711"; a="95664706" X-IronPort-AV: E=Sophos;i="6.21,310,1763452800"; d="scan'208";a="95664706" Received: from fmviesa003.fm.intel.com ([10.60.135.143]) by orvoesa101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Feb 2026 02:09:18 -0800 X-CSE-ConnectionGUID: J9MRCx5LRxG7t83eIMl+AQ== X-CSE-MsgGUID: 3NgeExdmSjSJDEmoYQe7PA== X-ExtLoop1: 1 Received: from vpanait-mobl.ger.corp.intel.com (HELO localhost) ([10.245.244.71]) by fmviesa003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Feb 2026 02:09:17 -0800 Date: Wed, 25 Feb 2026 12:09:15 +0200 From: Andy Shevchenko To: Krzysztof Kozlowski Cc: linux-kernel@vger.kernel.org, Randy Dunlap Subject: Re: [PATCH v2 1/1] memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal SoC Message-ID: References: <20260224150616.3585591-1-andriy.shevchenko@linux.intel.com> <0eceef2b-4d33-4a09-af92-6b4131a1d8c2@kernel.org> <22092b19-a274-4b68-a1e3-4618c9e225ff@kernel.org> <849296b9-99a9-4c60-8054-c59826abcd2d@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Wed, Feb 25, 2026 at 10:45:22AM +0100, Krzysztof Kozlowski wrote: > On 25/02/2026 10:39, Andy Shevchenko wrote: > >>>> Separate patch in these patch series! The ABI documentation ALWAYS goes > >>>> with the implementation. Every patch on LKML follows that rule and also > >>>> it is explicitly documented in DT submitting patches. > >>> > >>> I see, it seems too hard to do this right from the start. > >> > >> Just like reverts of multiple commits are going in reversed order of > >> commits, then this is done in exact reverse order, so you can simply > >> look at any other patchset and do the reverse. Just took the latets from: > >> https://lore.kernel.org/linux-devicetree/ > >> > >> So this is adding: > >> https://lore.kernel.org/linux-devicetree/20260225-ina4230-v1-0-92b1de981d46@flipper.net/T/#m7817a527e6819c9383456aeaa0fe22f86e470d6f > >> > >> and removing would be exact revert, reverse order, with of course > >> appropriate subjects and commit msgs. > > > > These can't be done as pure set of reverts. This needs a manual work. > > I understand, I wanted to explain how to deduce the proper flow. Got it, thank you! -- With Best Regards, Andy Shevchenko