From: <ffrederick@prov-liege.be>
To: <linux-kernel@vger.kernel.org>
Cc: <ffrederick@users.sourceforge.net>
Subject: [PATCH] Trivial Typo fixes in ipc
Date: Tue, 8 Jul 2003 09:59:29 CEST [thread overview]
Message-ID: <S265287AbTGHHRG/20030708071706Z+20939@vger.kernel.org> (raw)
Fabian Frederick:
-<ipc> typo fixes
--- util.orig 2003-07-08 08:59:03.000000000 +0200
+++ util.c 2003-07-08 08:59:15.000000000 +0200
@@ -432,12 +432,12 @@ void ipc64_perm_to_ipc_perm (struct ipc6
* So far only shm_get_stat() calls ipc_get() via shm_get(), so ipc_get()
* is called with shm_ids.sem locked. Since grow_ary() is also called with
* shm_ids.sem down(for Shared Memory), there is no need to add read
- * barriers here to gurantee the writes in grow_ary() are seen in order
+ * barriers here to guarantee the writes in grow_ary() are seen in order
* here (for Alpha).
*
- * However ipc_get() itself does not necessary require ipc_ids.sem down. So
+ * However ipc_get() itself does not necessarily require ipc_ids.sem down. So
* if in the future ipc_get() is used by other places without ipc_ids.sem
- * down, then ipc_get() needs read memery barriers as ipc_lock() does.
+ * down, then ipc_get() needs read memory barriers as ipc_lock() does.
*/
struct kern_ipc_perm* ipc_get(struct ipc_ids* ids, int id)
{
___________________________________
reply other threads:[~2003-07-08 7:17 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=S265287AbTGHHRG/20030708071706Z+20939@vger.kernel.org \
--to=ffrederick@prov-liege.be \
--cc=ffrederick@users.sourceforge.net \
--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
all inboxes | Powered by JetHome®