Having moved metadata usage to mbuf tags, remove code that supports

the old way of doing it.

Submitted by:	Gleb Smirnoff <glebius@cell.sick.ru>

1 files changed, 10 insertions, 10 deletions

diff --git a/sys/netgraph/ng_sample.c b/sys/netgraph/ng_sample.c
index 20a3056..48b58c7 100644
--- a/sys/netgraph/ng_sample.c
+++ b/sys/netgraph/ng_sample.c
@@ -310,12 +310,12 @@ ng_xxx_rcvmsg(node_p node, item_p item, hook_p lasthook)
 /*
  * Receive data, and do something with it.
  * Actually we receive a queue item which holds the data.
- * If we free the item it wil also froo the data and metadata unless
- * we have previously disassociated them using the NGI_GET_xxx() macros.
+ * If we free the item it will also free the data unless we have
+ * previously disassociated it using the NGI_GET_M() macro.
  * Possibly send it out on another link after processing.
  * Possibly do something different if it comes from different
- * hooks. the caller will never free m or meta, so
- * if we use up this data or abort we must free BOTH of these.
+ * hooks. The caller will never free m, so if we use up this data or
+ * abort we must free it.
  *
  * If we want, we may decide to force this data to be queued and reprocessed
  * at the netgraph NETISR time.
@@ -358,15 +358,15 @@ ng_xxx_rcvdata(hook_p hook, item_p item )
 				return (ENETUNREACH);
 			}
 			/* If we were called at splnet, use the following:
-			 * NG_SEND_DATA(error, otherhook, m, meta); if this
+			 * NG_SEND_DATA_ONLY(error, otherhook, m); if this
 			 * node is running at some SPL other than SPLNET
 			 * then you should use instead: error =
-			 * ng_queueit(otherhook, m, meta); m = NULL: meta =
-			 * NULL; this queues the data using the standard
-			 * NETISR system and schedules the data to be picked
+			 * ng_queueit(otherhook, m, NULL); m = NULL;
+			 * This queues the data using the standard NETISR
+			 * system and schedules the data to be picked
 			 * up again once the system has moved to SPLNET and
-			 * the processing of the data can continue. after
-			 * these are run 'm' and 'meta' should be considered
+			 * the processing of the data can continue. After
+			 * these are run 'm' should be considered
 			 * as invalid and NG_SEND_DATA actually zaps them. */
 			NG_FWD_NEW_DATA(error, item,
 				xxxp->channel[chan].hook, m);