aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoe Hershberger2015-04-08 01:41:21 -0500
committerSimon Glass2015-04-18 11:11:35 -0600
commitbc0571fc1067ff8a8fd16990ae65c1a2826ea90c (patch)
tree1381f5ebd824a415652755afd5adc65d362071b9 /doc
parenta34f2075633d7928e2988193b0caba5854e6ef20 (diff)
net: cosmetic: Fix checkpatch.pl failures in net.c
Finish eliminating CamelCase from net.c and other failures Signed-off-by: Joe Hershberger <joe.hershberger@ni.com> Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.link-local4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/README.link-local b/doc/README.link-local
index 9586eca269d..148b4987f27 100644
--- a/doc/README.link-local
+++ b/doc/README.link-local
@@ -32,11 +32,11 @@ after successful negotiation to enable network access.
-------------
RFC3927 requires that addresses are continuously checked to
-avoid conflicts, however this can only happen when the NetLoop
+avoid conflicts, however this can only happen when the net_loop
is getting called. It is possible for a conflict to go undetected
until a command that accesses the network is executed.
-Using NetConsole is one way to ensure that NetLoop is always
+Using NetConsole is one way to ensure that net_loop is always
processing packets and monitoring for conflicts.
This is also not a concern if the feature is use to connect