From: Christoph Hellwig <hch@infradead.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Alexey Kardashevskiy" <aik@ozlabs.ru>,
linuxppc-dev@lists.ozlabs.org,
"David Gibson" <david@gibson.dropbear.id.au>,
kvm-ppc@vger.kernel.org,
"Alistair Popple" <alistair@popple.id.au>,
"Reza Arbab" <arbab@linux.ibm.com>,
"Sam Bobroff" <sbobroff@linux.ibm.com>,
"Piotr Jaroszynski" <pjaroszynski@nvidia.com>,
"Leonardo Augusto Guimarães Garcia" <lagarcia@br.ibm.com>,
"Jose Ricardo Ziviani" <joserz@linux.ibm.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Paul Mackerras" <paulus@ozlabs.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH kernel v6 18/20] vfio_pci: Allow mapping extra regions
Date: Thu, 20 Dec 2018 00:03:41 -0800 [thread overview]
Message-ID: <20181220080341.GA24210@infradead.org> (raw)
In-Reply-To: <20181219094358.1bcd03a5@x1.home>
On Wed, Dec 19, 2018 at 09:43:58AM -0700, Alex Williamson wrote:
> [cc +kvm, +lkml]
>
> Sorry, just noticed these are only visible on ppc lists or for those
> directly cc'd. vfio's official development list is the kvm list. I'll
> let spapr specific changes get away without copying this list, but
> changes like this really need to be visible to everyone. Thanks,
Please resend the whole series to include everyone.
next prev parent reply other threads:[~2018-12-20 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181219085232.103441-1-aik@ozlabs.ru>
[not found] ` <20181219085232.103441-19-aik@ozlabs.ru>
2018-12-19 16:43 ` [PATCH kernel v6 18/20] vfio_pci: Allow mapping extra regions Alex Williamson
2018-12-20 8:03 ` Christoph Hellwig [this message]
[not found] ` <20181219085232.103441-20-aik@ozlabs.ru>
2018-12-19 16:44 ` [PATCH kernel v6 19/20] vfio_pci: Allow regions to add own capabilities Alex Williamson
[not found] ` <20181219085232.103441-21-aik@ozlabs.ru>
2018-12-19 16:44 ` [PATCH kernel v6 20/20] vfio_pci: Add NVIDIA GV100GL [Tesla V100 SXM2] subdriver Alex Williamson
2018-12-20 1:10 ` [PATCH kernel v6.1 20/20 REPOST] " Alexey Kardashevskiy
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=20181220080341.GA24210@infradead.org \
--to=hch@infradead.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=alistair@popple.id.au \
--cc=arbab@linux.ibm.com \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=joserz@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lagarcia@br.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@ozlabs.org \
--cc=pjaroszynski@nvidia.com \
--cc=sbobroff@linux.ibm.com \
/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).