[OpenAFS-devel] Silly but confusing typo in "fstrace" messages

Rainer Toebbicke rtb@pclella.cern.ch
Mon, 12 Jan 2009 14:04:20 +0100


--------------050502080401030602080401
Content-Type: text/plain; charset="ISO-8859-15"; format=flowed
Content-Transfer-Encoding: 7bit

The attached patch corrects an obvious typo in fstrace messages.

Just got annoyed because for the n-th time some low-level pattern processor in 
my brain silently converted this lower case "l" (ell) in the wrong place to a 
1 (one) and got me confused for a while, so decided to fix it for good.

bcc'ed to openafs-bugs

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rainer Toebbicke
European Laboratory for Particle Physics(CERN) - Geneva, Switzerland
Phone: +41 22 767 8985       Fax: +41 22 767 7155

--------------050502080401030602080401
Content-Type: text/plain; name="p_trace_lx"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="p_trace_lx"

--- openafs/src/afs/afs_trace.et.~	2008-12-16 08:56:31.000000000 +0100
+++ openafs/src/afs/afs_trace.et	2008-12-17 09:51:54.000000000 +0100
@@ -132,8 +132,8 @@
 	ec	CM_TRACE_VMRDWR, "afs_vm_rdwr: vp = 0x%lx, xfrSize 0x%lx,  toffset 0x%x"
 	ec	CM_TRACE_READFAST, "ReadFast vp 0x%lx off (0x%x, 0x%x) resid 0x%x file length (0x%x, 0x%x)"
 	ec	CM_TRACE_FETCH64CODE, "StartRX_FetchData64 for vp 0x%lx returned %d"
-	ec	CM_TRACE_FETCH64LENG, "FetchData64 for vp 0xl%x code = %d, length = (0x%x, 0x%x)"
-	ec	CM_TRACE_FETCH64READ, "FetchData64 for vp 0xl%x code = %d, length = 0x%x"
+	ec	CM_TRACE_FETCH64LENG, "FetchData64 for vp 0x%lx code = %d, length = (0x%x, 0x%x)"
+	ec	CM_TRACE_FETCH64READ, "FetchData64 for vp 0x%lx code = %d, length = 0x%x"
 	ec	CM_TRACE_VMWRITE, "afs_vm_rdwr: vp 0x%lx offset (0x%x, 0x%x) length (0x%x, 0x%x)"
 	ec	CM_TRACE_VMWRITE2, "afs_vm_rdwr: vp 0x%lx first page 0x%x pages %d"
 	ec	CM_TRACE_VMSTOREALL, "osi_VM_StoreAllSegments for vp 0x%lx call %d"

--------------050502080401030602080401--