summaryrefslogtreecommitdiff
path: root/util/nvmutil/nvmutil.c
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2023-04-15 21:18:12 +0100
committerLeah Rowe <leah@libreboot.org>2023-04-15 21:18:12 +0100
commit8fb54e801f64eb50ab2702930d412f80e0fd8f6b (patch)
tree3e0686f3ad138472376952a0aa5f5739bee0358c /util/nvmutil/nvmutil.c
parent7e0177139524c62998cc7390712211417dff304b (diff)
util/nvmutil: sort includes alphabetically
small nitpick, but i try to use openbsd style since i like that style. upon further reading of their style guidelines today, it was revealed to me that for includes, they: * sort sys/ includes alphabetically, at the top * after sys/ includes, have an empty line * includes for networking-related headers below that * empty space below networking headers if there * after that, have the rest of the includes, sorted alphabetically at least, that is my understanding. i have to admit, it does look cleaner not really that critical but why not do it?
Diffstat (limited to 'util/nvmutil/nvmutil.c')
-rw-r--r--util/nvmutil/nvmutil.c15
1 files changed, 8 insertions, 7 deletions
diff --git a/util/nvmutil/nvmutil.c b/util/nvmutil/nvmutil.c
index d7d3fa60..a489dd8d 100644
--- a/util/nvmutil/nvmutil.c
+++ b/util/nvmutil/nvmutil.c
@@ -26,16 +26,17 @@
* https://libreboot.org/docs/install/nvmutil.html
*/
-#include <stdint.h>
-#include <string.h>
-#include <stdlib.h>
-#include <stdio.h>
-#include <fcntl.h>
#include <sys/stat.h>
-#include <unistd.h>
-#include <errno.h>
+
#include <dirent.h>
#include <err.h>
+#include <errno.h>
+#include <fcntl.h>
+#include <stdint.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <unistd.h>
void readGbeFile(int *fd, const char *path, int flags,
size_t nr);