aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Maynard <Christopher.Maynard@GTECH.COM>2011-11-27 16:17:22 +0000
committerChris Maynard <Christopher.Maynard@GTECH.COM>2011-11-27 16:17:22 +0000
commitbdbe75190f1d0533d34512e2a61b2857b8d80505 (patch)
tree51410e9e6cab70630918be98d00bfebf97ce5cf3
parentc4ace59928e1a14fb17d3989fd2e718ca9499ffd (diff)
Fix a typo.
svn path=/trunk/; revision=40018
-rw-r--r--epan/dissectors/packet-ntp.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/epan/dissectors/packet-ntp.c b/epan/dissectors/packet-ntp.c
index 51e88fce0a..9129b7fda4 100644
--- a/epan/dissectors/packet-ntp.c
+++ b/epan/dissectors/packet-ntp.c
@@ -132,7 +132,7 @@ static const value_string li_types[] = {
/* Version info, 3bit field informs about NTP version used in particular
* packet. According to rfc2030, version info could be only 3 or 4, but I
* have noticed packets with 1 or even 6 as version numbers. They are
- * produced as a result of ntptrace command. Are those packets mailformed
+ * produced as a result of ntptrace command. Are those packets malformed
* on purpose? I don't know yet, probably some browsing through ntp sources
* would help. My solution is to put them as reserved for now.
*/