From: Christoph Hellwig <hch@lst.de>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH 2/2] correct dev_alloc_skb kerneldoc
Date: Fri, 7 Jul 2006 11:09:57 +0200 [thread overview]
Message-ID: <20060707090956.GA2543@lst.de> (raw)
dev_alloc_skb is designated for RX descriptors, not TX. (Some drivers
use it for the latter anyway, but that's a different story)
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/include/linux/skbuff.h
===================================================================
--- linux-2.6.orig/include/linux/skbuff.h 2006-07-07 11:05:30.000000000 +0200
+++ linux-2.6/include/linux/skbuff.h 2006-07-07 11:06:31.000000000 +0200
@@ -1067,7 +1067,7 @@
}
/**
- * __dev_alloc_skb - allocate an skbuff for sending
+ * __dev_alloc_skb - allocate an skbuff for receiving
* @length: length to allocate
* @gfp_mask: get_free_pages mask, passed to alloc_skb
*
@@ -1088,7 +1088,7 @@
}
/**
- * dev_alloc_skb - allocate an skbuff for sending
+ * dev_alloc_skb - allocate an skbuff for receiving
* @length: length to allocate
*
* Allocate a new &sk_buff and assign it a usage count of one. The
next reply other threads:[~2006-07-07 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 9:09 Christoph Hellwig [this message]
2006-07-07 22:52 ` [PATCH 2/2] correct dev_alloc_skb kerneldoc Stephen Hemminger
2006-07-07 23:55 ` David Miller
2006-07-08 3:11 ` Herbert Xu
2006-07-08 10:48 ` Christoph Hellwig
2006-07-08 20:37 ` David Miller
2006-07-13 20:36 ` Christoph Hellwig
2006-07-13 20:47 ` Randy.Dunlap
2006-07-13 20:47 ` David Miller
2006-07-14 15:24 ` chas williams - CONTRACTOR
2006-07-13 21:24 ` Stephen Hemminger
2006-07-13 21:29 ` Christoph Hellwig
2006-07-13 22:01 ` David Miller
2006-07-14 7:27 ` Samuel Ortiz
2006-07-14 6:49 ` Christoph Hellwig
2006-07-24 22:31 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060707090956.GA2543@lst.de \
--to=hch@lst.de \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).