Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755715AbYC1K1X (ORCPT ); Fri, 28 Mar 2008 06:27:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753872AbYC1K1O (ORCPT ); Fri, 28 Mar 2008 06:27:14 -0400 Received: from smtp04.mtu.ru ([62.5.255.51]:51370 "EHLO smtp04.mtu.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752831AbYC1K1O (ORCPT ); Fri, 28 Mar 2008 06:27:14 -0400 X-Greylist: delayed 880 seconds by postgrey-1.27 at vger.kernel.org; Fri, 28 Mar 2008 06:27:13 EDT From: Dmitri Vorobiev To: dsd@gentoo.org, randy.dunlap@oracle.com, trivial@kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 1/1] Fix typos in Documentation/unaligned-memory-access.txt Date: Fri, 28 Mar 2008 13:10:42 +0300 Message-Id: <1206699042-1334-1-git-send-email-dmitri.vorobiev@gmail.com> X-Mailer: git-send-email 1.5.3.6 X-DCC-STREAM-Metrics: smtp04.mtu.ru 10001; Body=0 Fuz1=0 Fuz2=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1787 Lines: 38 This patch deletes a couple of superfluous word occurrences in the document Documentation/unaligned-memory-access.txt. --- Sorry for a duplicate email, I forgot to Cc LKML when sending the patch. Documentation/unaligned-memory-access.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/unaligned-memory-access.txt b/Documentation/unaligned-memory-access.txt index 6223eac..ed57b53 100644 --- a/Documentation/unaligned-memory-access.txt +++ b/Documentation/unaligned-memory-access.txt @@ -57,7 +57,7 @@ here; a summary of the common scenarios is presented below: unaligned access to be corrected. - Some architectures are not capable of unaligned memory access, but will silently perform a different memory access to the one that was requested, - resulting a a subtle code bug that is hard to detect! + resulting a subtle code bug that is hard to detect! It should be obvious from the above that if your code causes unaligned memory accesses to happen, your code will not work correctly on certain @@ -209,7 +209,7 @@ memory and you wish to avoid unaligned access, its usage is as follows: u32 value = get_unaligned((u32 *) data); -These macros work work for memory accesses of any length (not just 32 bits as +These macros work for memory accesses of any length (not just 32 bits as in the examples above). Be aware that when compared to standard access of aligned memory, using these macros to access unaligned memory can be costly in terms of performance. -- 1.5.3.6 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/