Home
last modified time | relevance | path

Searched refs:format (Results 1 – 6 of 6) sorted by relevance

/DragonStub/inc/dragonstub/
H A Dbug.h10 #define WARN(condition, format...) \ argument
15 efi_printk(format); \
32 #define WARN_ONCE(condition, format...) WARN(condition, format) argument
33 #define WARN_TAINT(condition, taint, format...) WARN(condition, format) argument
34 #define WARN_TAINT_ONCE(condition, taint, format...) WARN(condition, format) argument
/DragonStub/
H A DMakefile149 …@git archive --format=tar $(shell git branch | awk '/^*/ { print $$2 }') | ( cd /tmp/gnu-efi-$(VER…
162 @git archive --format=tar $(VERSION) | ( cd /tmp/gnu-efi-$(VERSION)-tmp/ ; tar x )
H A D.clang-format3 # clang-format configuration file. Intended for clang-format >= 11.
7 # Documentation/process/clang-format.rst
H A DChangeLog405 Subject: [PATCH 3/4] document format of LoadedImage::LoadOptions data
651 Changelog format change from here and above to 'git log' style.
1202 ELF image. ELILO autodetects the format
/DragonStub/docs/
H A DREADME.gnuefi163 stands for "Portable Executable" and is the object file format
165 object file format with an MS-DOS2.0 compatible header slapped on in
167 is a 32-bit object file format. The plus in "PE32+" indicates that
168 this format has been hacked to allow loading a 4GB binary anywhere in
170 64-bit object file format because the entire binary cannot span more
360 As mentioned above, the IA-64 PE32+ format assumes that the entry
/DragonStub/inc/
H A Defidebug.h105 CONST CHAR8 *format,