From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Kr���m������" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, linux-arch <linux-arch@vger.kernel.org>,
"Palmer Dabbelt" <palmer@sifive.com>,
"Greentime Hu" <green.hu@gmail.com>,
"Vincent Chen" <deanbo422@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>, "Joerg Roedel" <joro@8bytes.org>,
"Christoffer Dall" <christoffer.dall@arm.com>,
"Marc Zyngier" <marc.zyngier@arm.com>,
"James Hogan" <jhogan@kernel.org>,
"Paul Mackerras" <paulus@ozlabs.org>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
"Christoph Hellwig" <hch@lst.de>,
"Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: [PATCH] KVM: export <linux/kvm_para.h> and <asm/kvm_para.h> for all architectures
Date: Wed, 6 Feb 2019 14:21:10 +0900 [thread overview]
Message-ID: <CAK7LNARk3Ww8ty=BvYo=xeVwHEL8qPRxfeY_=sQxQqL9-KUnWA@mail.gmail.com> (raw)
In-Reply-To: <fb57fc25-0288-741b-8fb6-942124c0f6a6@redhat.com>
On Tue, Feb 5, 2019 at 9:13 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 04/02/19 04:55, Masahiro Yamada wrote:
> > If you prefer [B] (or you have a better idea),
> > please suggest.
>
> I prefer [B] but this is already much better so feel free to do it on top.
>
> Paolo
There is no point to move <asm/kvm_para.h> back and forth
between the kernel/user spaces.
We should choose [A] or [B].
Although [B] is not so clean in the code-diff PoV,
I will send it so that you can choose either one you prefer.
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2019-02-06 5:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 3:55 [PATCH] KVM: export <linux/kvm_para.h> and <asm/kvm_para.h> for all architectures Masahiro Yamada
2019-02-04 8:26 ` Christoph Hellwig
2019-02-05 12:13 ` Paolo Bonzini
2019-02-06 5:21 ` Masahiro Yamada [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='CAK7LNARk3Ww8ty=BvYo=xeVwHEL8qPRxfeY_=sQxQqL9-KUnWA@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=arnd@arndb.de \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@arm.com \
--cc=deanbo422@gmail.com \
--cc=frankja@linux.ibm.com \
--cc=green.hu@gmail.com \
--cc=hch@lst.de \
--cc=jhogan@kernel.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=palmer@sifive.com \
--cc=paulus@ozlabs.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sam@ravnborg.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.