From: mhkelley58@gmail.com
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
vkuznets@redhat.com, jasowang@redhat.com,
leann.ogasawara@canonical.com, marcelo.cerri@canonical.com,
sthemmin@microsoft.com, kys@microsoft.com
Subject: [PATCH char-misc 0/2] Drivers: hv: vmbus: Remove x86-isms in arch independent code
Date: Mon, 7 May 2018 17:37:29 -0700 [thread overview]
Message-ID: <1525739851-54919-1-git-send-email-mikelley@microsoft.com> (raw)
From: Michael Kelley <mikelley@microsoft.com>
More changes to cleanly separate architecture independent code from
architecture dependent code. The first patch moves x86-specific code
out of the Hyper-V architecture independent drivers and into the arch/x86
directory. The second patch removes the string "X64" from symbol names
that aren't x86/x64-specific.
These changes are preparation for supporting Hyper-V on ARM64.
Michael Kelley (2):
Drivers: hv: vmbus: Remove x86 MSR refs in arch independent code
Drivers: hv: vmbus: Make TLFS #define names architecture neutral
arch/x86/hyperv/hv_init.c | 4 ++--
arch/x86/include/asm/hyperv-tlfs.h | 12 ++++++------
arch/x86/include/asm/mshyperv.h | 12 ++++++++----
arch/x86/kernel/cpu/mshyperv.c | 4 ++--
drivers/hv/hv.c | 30 +++++++++++++-----------------
5 files changed, 31 insertions(+), 31 deletions(-)
--
2.7.4
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2018-05-08 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 0:37 mhkelley58 [this message]
2018-05-08 0:37 ` [PATCH char-misc 1/2] Drivers: hv: vmbus: Remove x86 MSR refs in arch independent code mhkelley58
2018-05-12 8:37 ` KY Srinivasan
2018-05-12 12:55 ` Michael Kelley (EOSG)
2018-05-08 0:37 ` [PATCH char-misc 2/2] Drivers: hv: vmbus: Make TLFS #define names architecture neutral mhkelley58
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=1525739851-54919-1-git-send-email-mikelley@microsoft.com \
--to=mhkelley58@gmail.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=mikelley@microsoft.com \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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).