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 6D84F137923 for ; Sun, 22 Feb 2026 20:59:09 +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=1771793949; cv=none; b=bvxBuSfxkMZ3rcdsxHQds/IDvoTU7ua5R4yK0e1dB2sUoAAXjORhTptcA8wWcyBEvWEtMJVV0nVRLW+z/sMSdt/0ejewr+EaxjC6I57rgFu10aka2ViasUjDT3wR3BhzMiKGdISjxBQfzDW3ta9VWAlWHhZ0XGXRJLHaxMt9FUc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771793949; c=relaxed/simple; bh=0fJYGSZ0MJdiJxqAddB3a87X+REtS6w710UDRBNXdMA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=PIjtRqrfSnIR4MsoKqHt8h1DP5SCka9icl4s6mbLDdLk+rs4/kRM9HLtV5gDOBPpRNIMkBtbWwmkfKqSOgO8m6zjgSc60O6PIBQ3lydK8T4x/S0nOiuxF2WnqQsi4Ech+2ZS9ct8FWUsuahRp9qYUSiBRi83qSXEdpQU0S2ZHZw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ehYNJvB7; 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="ehYNJvB7" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 71173C116D0; Sun, 22 Feb 2026 20:59:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771793949; bh=0fJYGSZ0MJdiJxqAddB3a87X+REtS6w710UDRBNXdMA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ehYNJvB7t89L0LsNjLDYU+xshD4UlldaF6Enmy8MxXwOG6NIRyxOA2/X8NlxvN7GX IhdrpHBErpgSQWcpglpWwj4pvkdVBhSRxgpas7HWxf9hXMYie+2xd9X5VYoiV01SI3 20I1YMQNGlXGUN6uIkaxPijYlIpCwJbu3L+rbE74nrw381ieY1i7FmCX2+DtDYiaZo Fosg34HEAZpUW5h4j1awJwdVzNpAPYtBeR3MbKb8WODMpuHgR3SA8FCcl7aWOJxiyl pIDEoZcARoBseiSa9oRXiixXIXl51n3XssDYgIPRnJ/hMXZYKfd368KYztg6JL12Gk VygKO4Pl4Xb7Q== From: Thomas Gleixner To: Meghana Malladi , Marc Zyngier Cc: MD Danish Anwar , Grzegorz Jaszczyk , Suman Anna , David Lechner , Roger Quadros , "Andrew F. Davis" , linux-kernel@vger.kernel.org, srk@ti.com, r-gunasekaran@ti.com, vigneshr@ti.com Subject: Re: [PATCH 3/3] irqchip/irq-pruss-intc: Fix processing of IEP interrupts In-Reply-To: <3486f2bb-439d-4f7e-aad5-8345fba0283b@ti.com> References: <20230919061900.369300-1-danishanwar@ti.com> <20230919061900.369300-4-danishanwar@ti.com> <87ediu4nzs.wl-maz@kernel.org> <0968172c-4c41-4157-a13f-bad3dec677a9@ti.com> <86zf569utc.wl-maz@kernel.org> <3486f2bb-439d-4f7e-aad5-8345fba0283b@ti.com> Date: Sun, 22 Feb 2026 21:59:05 +0100 Message-ID: <87ldgkwl46.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Wed, Feb 18 2026 at 16:56, Meghana Malladi wrote: > On 2/18/26 16:34, Marc Zyngier wrote: >> I'm sorry, but this comes almost 3 years late, and I've long forgotten >> about all of this. I can only conclude that if you (TI, not you >> personally) waited for this long to address my comments, then this is >> probably not something we really need to care about. >> > > Thanks for your reply. I understand the concern about the delay and the > difficulty in revisiting something after such a long gap. > > This work resurfaced now because we are in the process of migrating to > the 6.18 LTS kernel, and while validating the migration we encountered > these issues again. For our platforms, these fixes are required to get > PPS and timestamp functionality working correctly, and for ensuring > long-term stability. For ensuring long-term stability you should work with the upstream community when changes happen and not wait until you finally catch up with reality in production. That's not the way it works. If you ignore feedback for 3 years then you can't expect that everything is dropped to please you now. > I realize this comes a long time after the original discussion, but I > would like to get the patches into the proper shape and aligned with > your feedback. Thanks again for your time and guidance. Marc told you what he's concerned about and that should be sufficient to resubmit the patches with proper change logs and comments in the source code explaining the issue and the solution properly, no? While at it please fix up the broken S-O-B chain in your submission. Documentation/process/ explains it neatly. While at it read the rest of it too and act accordingly. Thanks, tglx