linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: linux-fscrypt@vger.kernel.org
Cc: kernel-team@fb.com, Jes Sorensen <jsorensen@fb.com>
Subject: [PATCH 5/7] Rename commands.h to fsverity.h
Date: Mon, 10 Feb 2020 19:00:35 -0500	[thread overview]
Message-ID: <20200211000037.189180-6-Jes.Sorensen@gmail.com> (raw)
In-Reply-To: <20200211000037.189180-1-Jes.Sorensen@gmail.com>

From: Jes Sorensen <jsorensen@fb.com>

This is a more appropriate name to provide the API for the shared library

Signed-off-by: Jes Sorensen <jsorensen@fb.com>
---
 cmd_enable.c             | 2 +-
 cmd_measure.c            | 2 +-
 cmd_sign.c               | 2 +-
 fsverity.c               | 2 +-
 commands.h => fsverity.h | 0
 5 files changed, 4 insertions(+), 4 deletions(-)
 rename commands.h => fsverity.h (100%)

diff --git a/cmd_enable.c b/cmd_enable.c
index 8c55722..732f3f6 100644
--- a/cmd_enable.c
+++ b/cmd_enable.c
@@ -14,7 +14,7 @@
 #include <string.h>
 #include <sys/ioctl.h>
 
-#include "commands.h"
+#include "fsverity.h"
 #include "fsverity_uapi.h"
 #include "hash_algs.h"
 
diff --git a/cmd_measure.c b/cmd_measure.c
index fc3108d..3cd313e 100644
--- a/cmd_measure.c
+++ b/cmd_measure.c
@@ -11,7 +11,7 @@
 #include <stdlib.h>
 #include <sys/ioctl.h>
 
-#include "commands.h"
+#include "fsverity.h"
 #include "fsverity_uapi.h"
 
 /* Display the measurement of the given verity file(s). */
diff --git a/cmd_sign.c b/cmd_sign.c
index 2d3fa54..42779f2 100644
--- a/cmd_sign.c
+++ b/cmd_sign.c
@@ -16,7 +16,7 @@
 #include <stdlib.h>
 #include <string.h>
 
-#include "commands.h"
+#include "fsverity.h"
 #include "fsverity_uapi.h"
 #include "hash_algs.h"
 
diff --git a/fsverity.c b/fsverity.c
index b4e67a2..f0e94bf 100644
--- a/fsverity.c
+++ b/fsverity.c
@@ -15,7 +15,7 @@
 #include <getopt.h>
 #include <errno.h>
 
-#include "commands.h"
+#include "fsverity.h"
 #include "hash_algs.h"
 
 enum {
diff --git a/commands.h b/fsverity.h
similarity index 100%
rename from commands.h
rename to fsverity.h
-- 
2.24.1


  parent reply	other threads:[~2020-02-11  0:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  0:00 [PATCH 0/7] Split fsverity-utils into a shared library Jes Sorensen
2020-02-11  0:00 ` [PATCH 1/7] Build basic " Jes Sorensen
2020-02-11  0:00 ` [PATCH 2/7] Restructure fsverity_cmd_sign for shared libraries Jes Sorensen
2020-02-11  0:00 ` [PATCH 3/7] Make fsverity_cmd_measure() a library function Jes Sorensen
2020-02-11  0:00 ` [PATCH 4/7] Make fsverity_cmd_enable a library call() Jes Sorensen
2020-02-11  0:00 ` Jes Sorensen [this message]
2020-02-11  0:00 ` [PATCH 6/7] Move cmdline helper functions to fsverity.c Jes Sorensen
2020-02-11  0:00 ` [PATCH 7/7] cmd_sign: fsverity_cmd_sign() into two functions Jes Sorensen
2020-02-11 19:22 ` [PATCH 0/7] Split fsverity-utils into a shared library Eric Biggers
2020-02-11 22:09   ` Jes Sorensen
2020-02-11 23:14     ` Eric Biggers
2020-02-11 23:35       ` Jes Sorensen
2020-02-14 20:35         ` Eric Biggers
2020-02-19 23:49           ` Jes Sorensen
2020-07-30 17:52             ` Eric Biggers
2020-07-31 17:40               ` Jes Sorensen
2020-07-31 17:47                 ` Chris Mason
2020-07-31 19:14                   ` Eric Biggers

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=20200211000037.189180-6-Jes.Sorensen@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=jsorensen@fb.com \
    --cc=kernel-team@fb.com \
    --cc=linux-fscrypt@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).