All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: Frank Li <Frank.Li@kernel.org>,
	dmaengine@vger.kernel.org, phone-devel@vger.kernel.org,
	sashiko-bot@kernel.org
Subject: Re: [PATCH v2 00/13] dmaengine: ste_dma40: Fix probe and allocation bugs
Date: Wed, 9 Sep 2026 17:58:29 +0530	[thread overview]
Message-ID: <aqFQ7Z-4Vcsu8z8w@parshuram> (raw)
In-Reply-To: <CAD++jLnPDc-v5iuy-zaTrmuxFKU2ehr0ZS65BJyR0x8zW5BWNw@mail.gmail.com>

On 24-08-26, 11:14, Linus Walleij wrote:
> Regarding this patch set,
> 
> On Thu, Aug 20, 2026 at 3:15 PM Linus Walleij <linusw@kernel.org> wrote:
> 
> > This series fixes thirteen pre-existing DMA40 bugs found while reviewing the
> > Ux500 LCLA SRAM power-domain conversion.
> 
> This whole exercise which is admittedly a bit of an experient
> remind me of an EMACS macro named "psychoanalyze-pinhead"
> where a dumb random quote generator is fed to an as dumb
> Eliza-type psychologist parrot "AI" program.
> 
> I am basically pitting Gemini against Codex here, where Gemini
> finding more and more fringe issues and Codex fixing them
> and then introducing new bugs and Gemini discovering more
> bugs ad nauseam, bugs being more and more fringe and
> weird as time passes.
> 
> I wonder what to do with this, the driver was *already* working
> fine, all I did was introduce power domains...
> 
> Possibly I will take a final sweep over the patches, fix issues
> *in* the patches, ignore any "new discoveries" then call it a day.

We are in brave new world right!

So, I would not add any new regressions. AI finding old issues can be
fixed at your leisure... I am going by that guidance

-- 
~Vinod

      reply	other threads:[~2026-09-09 12:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 13:14 [PATCH v2 00/13] dmaengine: ste_dma40: Fix probe and allocation bugs Linus Walleij
2026-08-20 13:14 ` [PATCH v2 01/13] dmaengine: ste_dma40: Fix failed start cleanup Linus Walleij
2026-08-20 13:30   ` sashiko-bot
2026-08-20 13:14 ` [PATCH v2 02/13] dmaengine: ste_dma40: Check runtime PM in IRQ Linus Walleij
2026-08-20 13:31   ` sashiko-bot
2026-08-20 13:14 ` [PATCH v2 03/13] dmaengine: ste_dma40: Init hardware before registration Linus Walleij
2026-08-20 13:14 ` [PATCH v2 04/13] dmaengine: ste_dma40: Fix DMA registration unwind Linus Walleij
2026-08-20 13:30   ` sashiko-bot
2026-08-20 13:14 ` [PATCH v2 05/13] dmaengine: ste_dma40: Fix LCLA allocation order Linus Walleij
2026-08-20 13:29   ` sashiko-bot
2026-08-20 13:15 ` [PATCH v2 06/13] dmaengine: ste_dma40: Fix probe LCLA free Linus Walleij
2026-08-20 13:15 ` [PATCH v2 07/13] dmaengine: ste_dma40: Fix probe runtime PM disable Linus Walleij
2026-08-20 13:29   ` sashiko-bot
2026-08-20 13:15 ` [PATCH v2 08/13] dmaengine: ste_dma40: Fix probe IRQ leak Linus Walleij
2026-08-20 13:29   ` sashiko-bot
2026-08-20 13:15 ` [PATCH v2 09/13] dmaengine: ste_dma40: Fix memcpy channel parsing Linus Walleij
2026-08-20 13:29   ` sashiko-bot
2026-08-20 13:15 ` [PATCH v2 10/13] dmaengine: ste_dma40: Fix logical channel bounds check Linus Walleij
2026-08-20 13:32   ` sashiko-bot
2026-08-20 13:15 ` [PATCH v2 11/13] dmaengine: ste_dma40: Fix event group bounds Linus Walleij
2026-08-20 13:34   ` sashiko-bot
2026-08-20 13:15 ` [PATCH v2 12/13] dmaengine: ste_dma40: Validate memcpy configuration Linus Walleij
2026-08-20 13:37   ` sashiko-bot
2026-08-20 13:15 ` [PATCH v2 13/13] dmaengine: Use unique debugfs names Linus Walleij
2026-08-24  9:14 ` [PATCH v2 00/13] dmaengine: ste_dma40: Fix probe and allocation bugs Linus Walleij
2026-09-09 12:28   ` Vinod Koul [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aqFQ7Z-4Vcsu8z8w@parshuram \
    --to=vkoul@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linusw@kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=sashiko-bot@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.