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:	Fri, 8 Jun 2007 10:53:37 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Eric Dumazet <dada1@...mosbay.com>, Andi Kleen <ak@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [TRIVIAL] X86_64: fix wrong comment regarding set_fixmap()

On Fri, 8 Jun 2007, Eric Dumazet wrote:

> Why not taking the opportunity of spelling fix  ( highger -> higher ) ?

I missed that one, thanks. Andi, could you please take the one below 
instead? Thanks.

From: Jiri Kosina <jkosina@...e.cz>

X86_64: fix wrong comment regarding set_fixmap()
    
The function name is set_fixmap(), not fixmap_set() as stated in the comment.
    
Also fix a typo, punctuation and lower/uppercase a bit.
    
Signed-off-by: Jiri Kosina <jkosina@...e.cz>

diff --git a/include/asm-x86_64/fixmap.h b/include/asm-x86_64/fixmap.h
index e90e167..c3574e5 100644
--- a/include/asm-x86_64/fixmap.h
+++ b/include/asm-x86_64/fixmap.h
@@ -22,9 +22,9 @@
  * compile time, but to set the physical address only
  * in the boot process.
  *
- * these 'compile-time allocated' memory buffers are
- * fixed-size 4k pages. (or larger if used with an increment
- * highger than 1) use fixmap_set(idx,phys) to associate
+ * These 'compile-time allocated' memory buffers are
+ * fixed-size 4k pages (or larger if used with an increment
+ * higher than 1). Use set_fixmap(idx,phys) to associate
  * physical memory with fixmap indices.
  *
  * TLB entries of such buffers will not be flushed across
-
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