From: <Thangaraj.S@microchip.com>
To: <ewhk9887@gmail.com>, <miguel.ojeda.sandonis@gmail.com>
Cc: <broonie@kernel.org>, <linux-kernel@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH 1/2] spi: spi-pci1xxxx: Drop MSI-X usage as unsupported by DMA engine
Date: Thu, 19 Jun 2025 03:44:45 +0000 [thread overview]
Message-ID: <965a9fcd6bba9915b4e0cdc442067c7479477b84.camel@microchip.com> (raw)
In-Reply-To: <CANiq72=QUbe-koU-BEhEJ1-7AafC0kGcG6HOhiVaR1TWqPoLFg@mail.gmail.com>
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@gmail.com>
> wrote:
> > From: Thangaraj Samynathan <thangaraj.s@microchip.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@microchip.com>
> > Link:
> > https://patch.msgid.link/20250612023059.71726-1-thangaraj.s@microchip.com
> > Signed-off-by: Mark Brown <broonie@kernel.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
next prev parent reply other threads:[~2025-06-19 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 8:13 [PATCH 1/2] rust: macros: allow optional trailing comma in module! Eunsoo Eun
2025-06-14 8:13 ` [PATCH 1/2] spi: spi-pci1xxxx: Drop MSI-X usage as unsupported by DMA engine Eunsoo Eun
2025-06-17 8:05 ` Miguel Ojeda
2025-06-19 3:44 ` Thangaraj.S [this message]
2025-06-21 16:24 ` Miguel Ojeda
2025-06-14 17:42 ` [PATCH 1/2] rust: macros: allow optional trailing comma in module! Charalampos Mitrodimas
2025-06-14 18:15 ` Benno Lossin
2025-06-17 8:13 ` Miguel Ojeda
2025-06-16 15:51 ` Mark Brown
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=965a9fcd6bba9915b4e0cdc442067c7479477b84.camel@microchip.com \
--to=thangaraj.s@microchip.com \
--cc=broonie@kernel.org \
--cc=ewhk9887@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
/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®