linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] Documentation: siphash: Fix typo in the name of offsetofend macro
@ 2022-07-12 10:44 Dov Murik
  2022-07-12 13:05 ` Jonathan Corbet
  0 siblings, 1 reply; 5+ messages in thread
From: Dov Murik @ 2022-07-12 10:44 UTC (permalink / raw)
  To: linux-doc; +Cc: Dov Murik, Jonathan Corbet, Eric Biggers, linux-kernel

The siphash documentation misspelled "offsetendof" instead of
"offsetofend".

Fixes: 2c956a60778cbb ("siphash: add cryptographically secure PRF")
Signed-off-by: Dov Murik <dovmurik@linux.ibm.com>
---
 Documentation/security/siphash.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/security/siphash.rst b/Documentation/security/siphash.rst
index a10380cb78e5..023bd95c74a5 100644
--- a/Documentation/security/siphash.rst
+++ b/Documentation/security/siphash.rst
@@ -85,7 +85,7 @@ Often times the XuY functions will not be large enough, and instead you'll
 want to pass a pre-filled struct to siphash. When doing this, it's important
 to always ensure the struct has no padding holes. The easiest way to do this
 is to simply arrange the members of the struct in descending order of size,
-and to use offsetendof() instead of sizeof() for getting the size. For
+and to use offsetofend() instead of sizeof() for getting the size. For
 performance reasons, if possible, it's probably a good thing to align the
 struct to the right boundary. Here's an example::
 
-- 
2.25.1


^ permalink raw reply related	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2022-07-14  8:29 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-07-12 10:44 [PATCH] Documentation: siphash: Fix typo in the name of offsetofend macro Dov Murik
2022-07-12 13:05 ` Jonathan Corbet
2022-07-12 13:30   ` Jason A. Donenfeld
2022-07-13 20:01     ` Jonathan Corbet
2022-07-14  8:29       ` Dov Murik

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).