lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Wed, 15 Sep 2010 09:21:21 +0200
From:	Alexander Holupirek <alex@...upirek.de>
To:	john@...nmccutchan.com
Cc:	rlove@...ve.org, linux-kernel@...r.kernel.org,
	Alexander Holupirek <alex@...upirek.de>
Subject: [PATCH] include: linux: [fan|fs|i]notify: Fixed typos and a coding style issue

s/Writtable/Writeable
s/Unwrittable/Unwriteable

While there fixed an coding style issue reported by
./scripts/checkpatch.pl --file include/linux/fanotify.h

Signed-off-by: Alexander Holupirek <alex@...upirek.de>
---
 include/linux/fanotify.h         |    6 +++---
 include/linux/fsnotify_backend.h |    4 ++--
 include/linux/inotify.h          |    4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/include/linux/fanotify.h b/include/linux/fanotify.h
index 63531a6..e36baba 100644
--- a/include/linux/fanotify.h
+++ b/include/linux/fanotify.h
@@ -6,8 +6,8 @@
 /* the following events that user-space can register for */
 #define FAN_ACCESS		0x00000001	/* File was accessed */
 #define FAN_MODIFY		0x00000002	/* File was modified */
-#define FAN_CLOSE_WRITE		0x00000008	/* Unwrittable file closed */
-#define FAN_CLOSE_NOWRITE	0x00000010	/* Writtable file closed */
+#define FAN_CLOSE_WRITE		0x00000008	/* Unwriteable file closed */
+#define FAN_CLOSE_NOWRITE	0x00000010	/* Writeable file closed */
 #define FAN_OPEN		0x00000020	/* File was opened */
 
 #define FAN_EVENT_ON_CHILD	0x08000000	/* interested in child events */
@@ -88,7 +88,7 @@ struct fanotify_response {
 #define FAN_EVENT_METADATA_LEN (sizeof(struct fanotify_event_metadata))
 
 #define FAN_EVENT_NEXT(meta, len) ((len) -= (meta)->event_len, \
-				   (struct fanotify_event_metadata*)(((char *)(meta)) + \
+				   (struct fanotify_event_metadata *)(((char *)(meta)) + \
 				   (meta)->event_len))
 
 #define FAN_EVENT_OK(meta, len)	((long)(len) >= (long)FAN_EVENT_METADATA_LEN && \
diff --git a/include/linux/fsnotify_backend.h b/include/linux/fsnotify_backend.h
index e40190d..0403fc4 100644
--- a/include/linux/fsnotify_backend.h
+++ b/include/linux/fsnotify_backend.h
@@ -27,8 +27,8 @@
 #define FS_ACCESS		0x00000001	/* File was accessed */
 #define FS_MODIFY		0x00000002	/* File was modified */
 #define FS_ATTRIB		0x00000004	/* Metadata changed */
-#define FS_CLOSE_WRITE		0x00000008	/* Writtable file was closed */
-#define FS_CLOSE_NOWRITE	0x00000010	/* Unwrittable file closed */
+#define FS_CLOSE_WRITE		0x00000008	/* Writeable file was closed */
+#define FS_CLOSE_NOWRITE	0x00000010	/* Unwriteable file closed */
 #define FS_OPEN			0x00000020	/* File was opened */
 #define FS_MOVED_FROM		0x00000040	/* File was moved from X */
 #define FS_MOVED_TO		0x00000080	/* File was moved to Y */
diff --git a/include/linux/inotify.h b/include/linux/inotify.h
index d33041e..134082b 100644
--- a/include/linux/inotify.h
+++ b/include/linux/inotify.h
@@ -29,8 +29,8 @@ struct inotify_event {
 #define IN_ACCESS		0x00000001	/* File was accessed */
 #define IN_MODIFY		0x00000002	/* File was modified */
 #define IN_ATTRIB		0x00000004	/* Metadata changed */
-#define IN_CLOSE_WRITE		0x00000008	/* Writtable file was closed */
-#define IN_CLOSE_NOWRITE	0x00000010	/* Unwrittable file closed */
+#define IN_CLOSE_WRITE		0x00000008	/* Writeable file was closed */
+#define IN_CLOSE_NOWRITE	0x00000010	/* Unwriteable file closed */
 #define IN_OPEN			0x00000020	/* File was opened */
 #define IN_MOVED_FROM		0x00000040	/* File was moved from X */
 #define IN_MOVED_TO		0x00000080	/* File was moved to Y */
-- 
1.7.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ