mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: shao.mingyin@zte.com.cn
Cc: william.zhang@broadcom.com, linux-spi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	pjw@kernel.org, samuel.holland@sifive.com,
	kursad.oney@broadcom.com, jonas.gorski@gmail.com,
	bcm-kernel-feedback-list@broadcom.com, anand.gore@broadcom.com,
	florian.fainelli@broadcom.com, rafal@milecki.pl,
	linux-arm-kernel@lists.infradead.org, sven@kernel.org,
	j@jannau.net, neal@gompa.dev, asahi@lists.linux.dev,
	ryan.wanner@microchip.com, nicolas.ferre@microchip.com,
	alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev
Subject: Re: [PATCH v2 3/5] spi: bcmbca-hsspi: fix division by zero for devices without a max speed
Date: Sat, 14 Nov 2026 14:14:55 +0000	[thread overview]
Message-ID: <6a977239-f9fa-4eee-b2b4-944e77026b30@sirena.org.uk> (raw)
In-Reply-To: <20261114140757347tqYOa2IkTGVulSwLrw2Mf@zte.com.cn>

[-- Attachment #1: Type: text/plain, Size: 262 bytes --]

On Sat, Nov 14, 2026 at 02:07:57PM +0800, shao.mingyin@zte.com.cn wrote:

> If you would still like an explicit FCW lower bound in both drivers,
> I can prepare an incremental patch on top of the applied commits.

It might make it clearer that everything is OK.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-11-14 14:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 15:34 [PATCH v2 0/5] spi: fix division by zero with a zero transfer speed shao.mingyin
2026-11-10 15:34 ` [PATCH v2 1/5] spi: sifive: clamp the clock divider to the register range shao.mingyin
2026-11-10 15:34 ` [PATCH v2 2/5] spi: bcm63xx-hsspi: fix division by zero for devices without a max speed shao.mingyin
2026-11-10 15:34 ` [PATCH v2 3/5] spi: bcmbca-hsspi: " shao.mingyin
2026-11-10 20:30   ` William Zhang
2026-11-11  9:36     ` shao.mingyin
2026-11-14  0:51       ` Mark Brown
2026-11-14  1:13         ` William Zhang
2026-11-14  6:07           ` shao.mingyin
2026-11-14 14:14             ` Mark Brown [this message]
2026-11-10 15:35 ` [PATCH v2 4/5] spi: apple: fix division by zero in clock divisor calculation shao.mingyin
2026-11-10 15:35 ` [PATCH v2 5/5] spi: atmel: use the maximum divider for an unspecified speed shao.mingyin
2026-11-10 16:14 ` [PATCH v2 0/5] spi: fix division by zero with a zero transfer speed Mark Brown
2026-11-11  9:36   ` shao.mingyin
2026-11-13 22:07 ` Mark Brown
2026-11-14  0:39   ` William Zhang
2026-11-14  0:57     ` Mark Brown
2026-11-14  1:11       ` William Zhang

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=6a977239-f9fa-4eee-b2b4-944e77026b30@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=anand.gore@broadcom.com \
    --cc=asahi@lists.linux.dev \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=florian.fainelli@broadcom.com \
    --cc=j@jannau.net \
    --cc=jonas.gorski@gmail.com \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=neal@gompa.dev \
    --cc=nicolas.ferre@microchip.com \
    --cc=pjw@kernel.org \
    --cc=rafal@milecki.pl \
    --cc=ryan.wanner@microchip.com \
    --cc=samuel.holland@sifive.com \
    --cc=shao.mingyin@zte.com.cn \
    --cc=sven@kernel.org \
    --cc=william.zhang@broadcom.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®