From: David Vrabel <dvrabel@cantab.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: [GIT PULL] xen: MFN/GFN/BFN terminology changes for 4.3-rc0
Date: Thu, 10 Sep 2015 11:11:49 +0100 [thread overview]
Message-ID: <55F15765.2080100@cantab.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.3-rc0b-tag
xen: MFN/GFN/BFN terminology changes for 4.3-rc0
- - Use the correct GFN/BFN terms more consistently.
Thanks.
David
arch/arm/include/asm/xen/page.h | 28 +++++++++++++++------
arch/arm/xen/enlighten.c | 18 +++++++-------
arch/arm/xen/mm.c | 4 +--
arch/x86/include/asm/xen/page.h | 39 +++++++++++++++++++++++++++--
arch/x86/xen/mmu.c | 32 ++++++++++++------------
arch/x86/xen/smp.c | 2 +-
drivers/block/xen-blkfront.c | 6 ++---
drivers/input/misc/xen-kbdfront.c | 4 +--
drivers/net/xen-netback/netback.c | 4 +--
drivers/net/xen-netfront.c | 12 +++++----
drivers/scsi/xen-scsifront.c | 10 ++++----
drivers/tty/hvc/hvc_xen.c | 18 ++++++--------
drivers/video/fbdev/xen-fbfront.c | 20 +++++++--------
drivers/xen/balloon.c | 2 +-
drivers/xen/biomerge.c | 6 ++---
drivers/xen/events/events_base.c | 2 +-
drivers/xen/events/events_fifo.c | 4 +--
drivers/xen/gntalloc.c | 3 ++-
drivers/xen/manage.c | 2 +-
drivers/xen/privcmd.c | 44 ++++++++++++++++-----------------
drivers/xen/swiotlb-xen.c | 16 ++++++------
drivers/xen/tmem.c | 24 ++++++------------
drivers/xen/xenbus/xenbus_client.c | 2 +-
drivers/xen/xenbus/xenbus_dev_backend.c | 2 +-
drivers/xen/xenbus/xenbus_probe.c | 16 ++++++------
drivers/xen/xlate_mmu.c | 18 +++++++-------
include/uapi/xen/privcmd.h | 4 +++
include/xen/page.h | 4 +--
include/xen/xen-ops.h | 10 ++++----
29 files changed, 198 insertions(+), 158 deletions(-)
Julien Grall (8):
xen: Make clear that swiotlb and biomerge are dealing with DMA address
arm/xen: implement correctly pfn_to_mfn
xen: Use correctly the Xen memory terminologies
xen/tmem: Use xen_page_to_gfn rather than pfn_to_gfn
video/xen-fbfront: Further s/MFN/GFN clean-up
hvc/xen: Further s/MFN/GFN clean-up
xen/privcmd: Further s/MFN/GFN/ clean-up
xen/xenbus: Rename the variable xen_store_mfn to xen_store_gfn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJV8VdlAAoJEFxbo/MsZsTRVfAH/jP2E4h+NiNwyrEOc0FIFnNb
DTQW2SSpy49tLBP1AZwBgalCr3sdy3Obws8zn4PwaWqxBsjiFG+BUVp7uIxVS9pg
KjxhZzwvPWVGKczT+cKp+bqY8RRukLx8PezDQ3lZmHu3KHjowMMJmp6aboVG2TZF
RROY0yWReA6rKNQi610PEEmAaWlkRFph6SX2dp9KnnI29oPIlJcbEmTBwvc1G0pz
imEIXJGOvVD5Soikzgh/s1mLGnyMq2ZqYrOFjYagvvR7w6v0ZJqQyNKEhdsM3ITK
bVcGZwIAupG130RdqQPx8laPBfiGO/Bw4sXdKwCWB0lV/iIX09vTLpC9fF1kTO4=
=XDTK
-----END PGP SIGNATURE-----
reply other threads:[~2015-09-10 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55F15765.2080100@cantab.net \
--to=dvrabel@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox