From: Shuah Khan <skhan@linuxfoundation.org>
To: Joseph Jang <jjang@nvidia.com>,
shuah@kernel.org, mochs@nvidia.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Bjorn Helgaas <bjorn@helgaas.com>
Cc: linux-tegra@vger.kernel.org,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/1] selftest: drivers: Add support its msi hwirq checking
Date: Tue, 30 Jul 2024 14:59:47 -0600 [thread overview]
Message-ID: <ab271d7f-f495-4853-813e-10972cbff45d@linuxfoundation.org> (raw)
In-Reply-To: <20240530012727.324611-1-jjang@nvidia.com>
On 5/29/24 19:27, Joseph Jang wrote:
> In order to validate ITS-MSI hwirq entry in the /proc/interrupts, we
> have created a shell script to check is there any duplicated ITS-MSI
> hwirq entry.
>
> Joseph Jang (1):
> selftest: drivers: Add support its msi hwirq checking
>
> tools/testing/selftests/drivers/irq/Makefile | 5 +++++
> .../selftests/drivers/irq/its-msi-irq-test.sh | 20 +++++++++++++++++++
> 2 files changed, 25 insertions(+)
> create mode 100644 tools/testing/selftests/drivers/irq/Makefile
> create mode 100755 tools/testing/selftests/drivers/irq/its-msi-irq-test.sh
>
Sorry for the delay on this. It has gotten lost in my Inbox.
Since this is related to PCIe and MSI, I would like PCIe
maintainers to review this first.
Adding Bjorn Helgaas and linux-pci@vger.kernel.org list
Bjorn, please review - I can take this through kselftest
tree once I get your okay.
thanks,
-- Shuah
prev parent reply other threads:[~2024-07-30 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 1:27 [PATCH 0/1] selftest: drivers: Add support its msi hwirq checking Joseph Jang
2024-05-30 1:27 ` [PATCH 1/1] " Joseph Jang
2024-07-31 19:24 ` Bjorn Helgaas
2024-07-31 20:42 ` Thomas Gleixner
2024-07-31 23:12 ` Thomas Gleixner
2024-07-30 20:59 ` Shuah Khan [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=ab271d7f-f495-4853-813e-10972cbff45d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=bjorn@helgaas.com \
--cc=jjang@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mochs@nvidia.com \
--cc=shuah@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