linux-kernel - Re: [PATCH 1/2] spi: spi-pci1xxxx: Drop MSI-X usage as unsupported by DMA engine

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <965a9fcd6bba9915b4e0cdc442067c7479477b84.camel@microchip.com>
Date: Thu, 19 Jun 2025 03:44:45 +0000
From: <Thangaraj.S@...rochip.com>
To: <ewhk9887@...il.com>, <miguel.ojeda.sandonis@...il.com>
CC: <broonie@...nel.org>, <linux-kernel@...r.kernel.org>,
	<rust-for-linux@...r.kernel.org>
Subject: Re: [PATCH 1/2] spi: spi-pci1xxxx: Drop MSI-X usage as unsupported by
 DMA engine

Hi Miguel,
On Tue, 2025-06-17 at 10:05 +0200, Miguel Ojeda wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> On Sat, Jun 14, 2025 at 10:14 AM Eunsoo Eun <ewhk9887@...il.com>
> wrote:
> > From: Thangaraj Samynathan <thangaraj.s@...rochip.com>
> > 
> > Removes MSI-X from the interrupt request path, as the DMA engine
> > used by
> > the SPI controller does not support MSI-X interrupts.
> > 
> > Signed-off-by: Thangaraj Samynathan <thangaraj.s@...rochip.com>
> > Link: 
> > https://patch.msgid.link/20250612023059.71726-1-thangaraj.s@microchip.com
> > Signed-off-by: Mark Brown <broonie@...nel.org>
> 
> For some reason this came as a "1/2" patch in the same email thread
> as
> a Rust one, and that got things confusing. This patch looks
> spurious/bogus, i.e. it is already in mainline, and it is not
> authored
> nor signed by you, and it is not even numbered as "2/2".
> 
> Do you know what happened?
> 

Thanks for pointing it out. There was a mistake on my end during patch
generation - the patch isn't part of a series, but it was mistakenly
created with an incorrect header. Apologies for the confusion, and I'll
make sure to avoid this in the future.

Thanks,
Thanngaraj Samynathan
> Thanks!
> 
> Cheers,
> Miguel