From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Thangaraj Samynathan <thangaraj.s@microchip.com>
Cc: UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v1 for-next] spi: spi-pci1xxxx: Fix Probe failure with Dual SPI instance with INTx interrupts
Date: Tue, 27 May 2025 14:15:39 +0100 [thread overview]
Message-ID: <174835173941.43742.10482177523404609545.b4-ty@kernel.org> (raw)
In-Reply-To: <20250527103244.26861-1-thangaraj.s@microchip.com>
On Tue, 27 May 2025 16:02:44 +0530, Thangaraj Samynathan wrote:
> Fixes a probe failure that occurs when dual SPI controllers are
> enabled and INTx interrupts are used. Reduces the minimum required
> number of interrupt vectors to 1 and registers a shared ISR when
> the allocated vectors are fewer than the number of controllers.
> This change ensures that the probe succeeds even with limited
> vectors, restoring INTx functionality when multiple SPI
> controllers are present.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-pci1xxxx: Fix Probe failure with Dual SPI instance with INTx interrupts
commit: b4608e944177531334a79f3df2cd14275b47808c
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2025-05-27 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 10:32 Thangaraj Samynathan
2025-05-27 13:15 ` Mark Brown [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=174835173941.43742.10482177523404609545.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=thangaraj.s@microchip.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®