From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Wei Liu <wei.liu@kernel.org>,
linux-pci@vger.kernel.org,
Xen Development List <xen-devel@lists.xenproject.org>
Cc: linux-kernel@vger.kernel.org, Juergen Gross <jgross@suse.com>,
konrad.wilk@oracle.com, x86@kernel.org, sstabellini@kernel.org,
Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH] x86/xen: drop an unused parameter gsi_override
Date: Tue, 28 Apr 2020 22:17:35 -0400 [thread overview]
Message-ID: <3d3c2073-90c8-d3b1-0dd4-4045c3f01a5e@oracle.com> (raw)
In-Reply-To: <20200428153640.76476-1-wei.liu@kernel.org>
On 4/28/20 11:36 AM, Wei Liu wrote:
> All callers within the same file pass in -1 (no override).
>
> Signed-off-by: Wei Liu <wei.liu@kernel.org>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
WARNING: multiple messages have this Message-ID (diff)
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Wei Liu <wei.liu@kernel.org>,
linux-pci@vger.kernel.org,
Xen Development List <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
sstabellini@kernel.org, konrad.wilk@oracle.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH] x86/xen: drop an unused parameter gsi_override
Date: Tue, 28 Apr 2020 22:17:35 -0400 [thread overview]
Message-ID: <3d3c2073-90c8-d3b1-0dd4-4045c3f01a5e@oracle.com> (raw)
In-Reply-To: <20200428153640.76476-1-wei.liu@kernel.org>
On 4/28/20 11:36 AM, Wei Liu wrote:
> All callers within the same file pass in -1 (no override).
>
> Signed-off-by: Wei Liu <wei.liu@kernel.org>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
next prev parent reply other threads:[~2020-04-29 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 15:36 [PATCH] x86/xen: drop an unused parameter gsi_override Wei Liu
2020-04-28 15:36 ` Wei Liu
2020-04-29 2:17 ` Boris Ostrovsky [this message]
2020-04-29 2:17 ` Boris Ostrovsky
2020-05-21 17:26 ` Boris Ostrovsky
2020-05-21 17:26 ` Boris Ostrovsky
2020-05-21 19:41 ` Bjorn Helgaas
2020-05-21 19:41 ` Bjorn Helgaas
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=3d3c2073-90c8-d3b1-0dd4-4045c3f01a5e@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.