diff options
author | David Tolnay <dtolnay@chromium.org> | 2019-03-08 15:57:49 -0800 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2019-03-13 21:05:03 -0700 |
commit | fe3ef7d99892fad804cbc9de8801033fd483f337 (patch) | |
tree | b07b227d98466d14e61660d144e85109bc632abd /aarch64 | |
parent | fa132759424c5019dc9086e53d8db14500fee64f (diff) | |
download | crosvm-fe3ef7d99892fad804cbc9de8801033fd483f337.tar crosvm-fe3ef7d99892fad804cbc9de8801033fd483f337.tar.gz crosvm-fe3ef7d99892fad804cbc9de8801033fd483f337.tar.bz2 crosvm-fe3ef7d99892fad804cbc9de8801033fd483f337.tar.lz crosvm-fe3ef7d99892fad804cbc9de8801033fd483f337.tar.xz crosvm-fe3ef7d99892fad804cbc9de8801033fd483f337.tar.zst crosvm-fe3ef7d99892fad804cbc9de8801033fd483f337.zip |
edition: Update absolute paths to 2018 style
This is an easy step toward adopting 2018 edition eventually, and will make any future CL that sets `edition = "2018"` this much smaller. The module system changes in Rust 2018 are described here: https://doc.rust-lang.org/edition-guide/rust-2018/module-system/path-clarity.html Generated by running: cargo fix --edition --all in each workspace, followed by bin/fmt. TEST=cargo check TEST=cargo check --all-features TEST=cargo check --target aarch64-unknown-linux-gnu Change-Id: I000ab5e69d69aa222c272fae899464bbaf65f6d8 Reviewed-on: https://chromium-review.googlesource.com/1513054 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: David Tolnay <dtolnay@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: David Tolnay <dtolnay@chromium.org>
Diffstat (limited to 'aarch64')
-rw-r--r-- | aarch64/src/fdt.rs | 34 |
1 files changed, 17 insertions, 17 deletions
diff --git a/aarch64/src/fdt.rs b/aarch64/src/fdt.rs index b03d039..98cadc4 100644 --- a/aarch64/src/fdt.rs +++ b/aarch64/src/fdt.rs @@ -12,32 +12,32 @@ use devices::PciInterruptPin; use sys_util::{GuestAddress, GuestMemory}; // This is the start of DRAM in the physical address space. -use AARCH64_PHYS_MEM_START; +use crate::AARCH64_PHYS_MEM_START; // These are GIC address-space location constants. -use AARCH64_GIC_CPUI_BASE; -use AARCH64_GIC_CPUI_SIZE; -use AARCH64_GIC_DIST_BASE; -use AARCH64_GIC_DIST_SIZE; +use crate::AARCH64_GIC_CPUI_BASE; +use crate::AARCH64_GIC_CPUI_SIZE; +use crate::AARCH64_GIC_DIST_BASE; +use crate::AARCH64_GIC_DIST_SIZE; // These are RTC related constants +use crate::AARCH64_RTC_ADDR; +use crate::AARCH64_RTC_IRQ; +use crate::AARCH64_RTC_SIZE; use devices::pl030::PL030_AMBA_ID; -use AARCH64_RTC_ADDR; -use AARCH64_RTC_IRQ; -use AARCH64_RTC_SIZE; // These are serial device related constants. -use AARCH64_SERIAL_ADDR; -use AARCH64_SERIAL_IRQ; -use AARCH64_SERIAL_SIZE; -use AARCH64_SERIAL_SPEED; +use crate::AARCH64_SERIAL_ADDR; +use crate::AARCH64_SERIAL_IRQ; +use crate::AARCH64_SERIAL_SIZE; +use crate::AARCH64_SERIAL_SPEED; // These are related to guest virtio devices. -use AARCH64_IRQ_BASE; -use AARCH64_MMIO_BASE; -use AARCH64_MMIO_SIZE; -use AARCH64_PCI_CFG_BASE; -use AARCH64_PCI_CFG_SIZE; +use crate::AARCH64_IRQ_BASE; +use crate::AARCH64_MMIO_BASE; +use crate::AARCH64_MMIO_SIZE; +use crate::AARCH64_PCI_CFG_BASE; +use crate::AARCH64_PCI_CFG_SIZE; // This is an arbitrary number to specify the node for the GIC. // If we had a more complex interrupt architecture, then we'd need an enum for |