linux-kernel - [PATCH] kdbus: fix minor typo in the walk-through example

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 15 Mar 2015 13:13:08 +0800
From:	Nicolas Iooss <nicolas.iooss_linux@....org>
To:	gregkh@...uxfoundation.org, daniel@...que.org,
	dh.herrmann@...glemail.com, tixxdz@...ndz.org
Cc:	linux-kernel@...r.kernel.org,
	Nicolas Iooss <nicolas.iooss_linux@....org>
Subject: [PATCH] kdbus: fix minor typo in the walk-through example

s/receveiver/receiver/

Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@....org>
---
 samples/kdbus/kdbus-workers.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/samples/kdbus/kdbus-workers.c b/samples/kdbus/kdbus-workers.c
index d1d8f7a7697b..d331e0186899 100644
--- a/samples/kdbus/kdbus-workers.c
+++ b/samples/kdbus/kdbus-workers.c
@@ -787,8 +787,8 @@ static int child_run(struct child *c)
 	 * The 2nd item contains a vector to memory we want to send. It
 	 * can be content of any type. In our case, we're sending a one-byte
 	 * string only. The memory referenced by this item will be copied into
-	 * the pool of the receveiver connection, and does not need to be
-	 * valid after the command is employed.
+	 * the pool of the receiver connection, and does not need to be valid
+	 * after the command is employed.
 	 */
 	item = KDBUS_ITEM_NEXT(item);
 	item->type = KDBUS_ITEM_PAYLOAD_VEC;
-- 
2.3.2

--
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/