From: Thorsten Blum <thorsten.blum@toblux.com>
To: code@tyhicks.com, brian@kubisiak.com, brauner@kernel.org
Cc: ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Thorsten Blum <thorsten.blum@toblux.com>
Subject: [PATCH] ecryptfs: Fix packet format comment in parse_tag_67_packet()
Date: Fri, 13 Sep 2024 17:12:22 +0200 [thread overview]
Message-ID: <20240913151220.2688-3-thorsten.blum@toblux.com> (raw)
s/TAG 65/TAG 67/
Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
---
fs/ecryptfs/keystore.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ecryptfs/keystore.c b/fs/ecryptfs/keystore.c
index 7f9f68c00ef6..7266fc1a5fc4 100644
--- a/fs/ecryptfs/keystore.c
+++ b/fs/ecryptfs/keystore.c
@@ -355,7 +355,7 @@ parse_tag_67_packet(struct ecryptfs_key_record *key_rec,
int rc;
/*
- * ***** TAG 65 Packet Format *****
+ * ***** TAG 67 Packet Format *****
* | Content Type | 1 byte |
* | Status Indicator | 1 byte |
* | Encrypted File Encryption Key Size | 1 or 2 bytes |
--
2.46.0
reply other threads:[~2024-09-13 15:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240913151220.2688-3-thorsten.blum@toblux.com \
--to=thorsten.blum@toblux.com \
--cc=brauner@kernel.org \
--cc=brian@kubisiak.com \
--cc=code@tyhicks.com \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-kernel@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 read-only IMAP folder(s) and NNTP newsgroup(s).