From: seeteena <s1seetee@linux.vnet.ibm.com>
To: clg@kaod.org
Cc: linuxppc-dev@lists.ozlabs.org, stable@vger.kernel.org
Subject: Re: [PATCH] powerpc/xive: Discard disabled interrupts in get_irqchip_state()
Date: Mon, 11 Oct 2021 15:20:10 +0530 [thread overview]
Message-ID: <23f69a53-c331-a61f-9d89-04fe824e62f4@linux.vnet.ibm.com> (raw)
In-Reply-To: <20211011070203.99726-1-clg@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
Tested-by: seeteena<s1seetee@linux.vnet.ibm.com>
I have used a KVM guest with a passthrough ethernet adapter and the
lspci output to identify the adapter.
[-- Attachment #2: Type: text/html, Size: 2399 bytes --]
next prev parent reply other threads:[~2021-10-11 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 7:02 [PATCH] powerpc/xive: Discard disabled interrupts in get_irqchip_state() Cédric Le Goater
2021-10-11 9:47 ` seeteena
2021-10-11 9:50 ` seeteena [this message]
2021-10-17 12:28 ` Michael Ellerman
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=23f69a53-c331-a61f-9d89-04fe824e62f4@linux.vnet.ibm.com \
--to=s1seetee@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).