Searched hist:211690 (Results 1 - 25 of 35) sorted by relevance
/freebsd-10.1-release/sys/modules/dtrace/ | ||
H A D | Makefile.inc | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/ppc/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/hptmv/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/hptrr/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/io/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/linsysfs/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/vx/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/asr/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/cyclic/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/i2c/controllers/pcf/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/aac/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/bge/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/dtrace/fasttrap/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/le/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/amr/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/cpufreq/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/dtrace/dtrace/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/linprocfs/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/mem/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/mfi/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/procfs/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/smbfs/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/syscons/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/agp/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
/freebsd-10.1-release/sys/modules/cxgb/ | ||
H A D | Makefile | diff 211690 Mon Aug 23 04:17:24 MDT 2010 imp MFtbemd: Use MACHINE_CPUARCH in preference to MACHINE_ARCH. The former is the source code location of the machine, the latter the binary output. In general, we want to use MACHINE_CPUARCH instead of MACHINE_ARCH unless we're tesitng for a specific target. The isn't even moot for i386/amd64 where there's momemntum towards a MACHINE_CPUARCH == x86, although a specific cleanup for that likely would be needed... |
Completed in 156 milliseconds