All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: sashiko-bot@kernel.org
Cc: sashiko-reviews@lists.linux.dev,  linux-clk@vger.kernel.org,
	robh@kernel.org,  conor+dt@kernel.org,
	 devicetree@vger.kernel.org
Subject: Re: [PATCH v3 4/6] clk: nuvoton: ma35d1: Add missing WDT/WWDT parent clocks
Date: Fri, 25 Sep 2026 17:06:49 +0200	[thread overview]
Message-ID: <87cxu14bg6.fsf@bootlin.com> (raw)
In-Reply-To: <20260925145701.6ACF51F00893@smtp.kernel.org> (sashiko-bot@kernel.org's message of "Fri, 25 Sep 2026 14:57:01 +0000")

On 25/09/2026 at 14:57:01 GMT, sashiko-bot@kernel.org wrote:

> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] clk: nuvoton: ma35d1: heap buffer overflow when assigning
> WDT/WWDT parent clocks

Of course I got it wrong and forgot to bump the counter in the
driver. Let's iterate.

Miquèl

  reply	other threads:[~2026-09-25 15:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 14:44 [PATCH v3 0/6] clk: nuvoton: ma35d1: Fix mux parenting and peripheral clock rates Miquel Raynal
2026-09-25 14:44 ` [PATCH v3 1/6] clk: nuvoton: ma35d1: Keep the clock count in the driver Miquel Raynal
2026-09-25 14:44 ` [PATCH v3 2/6] dt-bindings: clock: ma35d1: Drop CLK_MAX_IDX define Miquel Raynal
2026-09-25 14:44 ` [PATCH v3 3/6] dt-bindings: clock: ma35d1: Add missing WDT/WWDT parent clocks Miquel Raynal
2026-09-25 14:55   ` sashiko-bot
2026-09-25 14:44 ` [PATCH v3 4/6] clk: nuvoton: " Miquel Raynal
2026-09-25 14:57   ` sashiko-bot
2026-09-25 15:06     ` Miquel Raynal [this message]
2026-09-25 14:44 ` [PATCH v3 5/6] clk: nuvoton: ma35d1: Use clk_hw pointers as mux parents Miquel Raynal
2026-09-25 14:44 ` [PATCH v3 6/6] clk: nuvoton: ma35d1: Avoid possible error pointer dereferencing Miquel Raynal

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=87cxu14bg6.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.