Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2;
Message-ID: <cfc3aa17-0f1b-4ffc-b848-33baa51b1196@gmail.com>
Date:   Wed, 29 Nov 2023 14:48:02 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Jan Kiszka <jan.kiszka@siemens.com>,
        Kieran Bingham <kbingham@kernel.org>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        Shanker Donthineni <sdonthineni@nvidia.com>,
        Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@collabora.com>
From:   Florian Fainelli <f.fainelli@gmail.com>
Subject: No care given to GDB scripts..
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hello,

It is quite clear that there are zero cares being given to making sure 
that GDB scripts continue to work after making changes to core kernel 
code, and why would you, because you probably did not know those 
existed, but they do and they are used, and useful.

A recent example that was fixed by Kuan-Ying is this:

and now of course, "lx-interupts" also stopped working altogether after 
this change:

https://lore.kernel.org/r/20230519134902.1495562-4-sdonthineni@nvidia.com

and who knows what else I could not test that is also broken.

We really need to find a better way to stop breaking GDB scripts, they 
break way too often to be even remotely usable, and this is really sad.

It is also quite clear that we do not have enough continuous integration 
and regression testing to ensure those breakages are caught ahead of time...

</rant>
-- 
Florian