From: Mark Brown <broonie@kernel.org>
To: shao.mingyin@zte.com.cn
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, pjw@kernel.org,
samuel.holland@sifive.com, william.zhang@broadcom.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 0/5] spi: fix division by zero with a zero transfer speed
Date: Tue, 10 Nov 2026 16:14:21 +0000 [thread overview]
Message-ID: <b8b3dd8e-7d66-4d8f-87f8-c88148334ebf@sirena.org.uk> (raw)
In-Reply-To: <20261110233450305Smji446Uhvoxa7r8SHEgl@zte.com.cn>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
On Tue, Nov 10, 2026 at 11:34:50PM +0800, shao.mingyin@zte.com.cn wrote:
> 1/5 spi: sifive: clamp the clock divider to the register range
> 2/5 spi: bcm63xx-hsspi: fix division by zero for devices without a max speed
> 3/5 spi: bcmbca-hsspi: fix division by zero for devices without a max speed
> 4/5 spi: apple: fix division by zero in clock divisor calculation
> 5/5 spi: atmel: use the maximum divider for an unspecified speed
Oh, I see you also sent those v2 patches as part of the series as
normal.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-11-10 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 15:34 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
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 ` Mark Brown [this message]
2026-11-11 9:36 ` [PATCH v2 0/5] spi: fix division by zero with a zero transfer speed 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=b8b3dd8e-7d66-4d8f-87f8-c88148334ebf@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®