From: Christoph Hellwig <hch@lst.de>
To: David Miller <davem@davemloft.net>
Cc: hch@lst.de, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] add netdev_alloc_skb
Date: Fri, 28 Jul 2006 09:08:51 +0200 [thread overview]
Message-ID: <20060728070851.GB25174@lst.de> (raw)
In-Reply-To: <20060726.152451.35043090.davem@davemloft.net>
On Wed, Jul 26, 2006 at 03:24:51PM -0700, David Miller wrote:
> From: Christoph Hellwig <hch@lst.de>
> Date: Wed, 26 Jul 2006 13:31:36 +0200
>
> > + * %NULL is returned in there is no free memory. Although this function
> > + * allocates memory it can be called from an interrupt.
> ...
> > + * %NULL is returned in there is no free memory.
>
> Looks like a typo in both cases, I think you mean
> "NULL is returned _if_ there" not "in there"
Yes, Joe Perches already pointed that out in private. This typo is copy
and pasted from the dev_alloc_skb kerneldoc, so this patch fixes up all
four occurances:
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-28 09:06:55.000000000 +0200
+++ linux-2.6/include/linux/skbuff.h 2006-07-28 09:07:35.000000000 +0200
@@ -1076,7 +1076,7 @@
* the headroom they think they need without accounting for the
* built in space. The built in space is used for optimisations.
*
- * %NULL is returned in there is no free memory.
+ * %NULL is returned if there is no free memory.
*/
static inline struct sk_buff *__dev_alloc_skb(unsigned int length,
gfp_t gfp_mask)
@@ -1096,7 +1096,7 @@
* the headroom they think they need without accounting for the
* built in space. The built in space is used for optimisations.
*
- * %NULL is returned in there is no free memory. Although this function
+ * %NULL is returned if there is no free memory. Although this function
* allocates memory it can be called from an interrupt.
*/
static inline struct sk_buff *dev_alloc_skb(unsigned int length)
@@ -1117,7 +1117,7 @@
* the headroom they think they need without accounting for the
* built in space. The built in space is used for optimisations.
*
- * %NULL is returned in there is no free memory. Although this function
+ * %NULL is returned if there is no free memory. Although this function
* allocates memory it can be called from an interrupt.
*/
static inline struct sk_buff *netdev_alloc_skb(struct net_device *dev,
Index: linux-2.6/net/core/skbuff.c
===================================================================
--- linux-2.6.orig/net/core/skbuff.c 2006-07-28 09:06:51.000000000 +0200
+++ linux-2.6/net/core/skbuff.c 2006-07-28 09:07:26.000000000 +0200
@@ -267,7 +267,7 @@
* the headroom they think they need without accounting for the
* built in space. The built in space is used for optimisations.
*
- * %NULL is returned in there is no free memory.
+ * %NULL is returned if there is no free memory.
*/
struct sk_buff *__netdev_alloc_skb(struct net_device *dev,
unsigned int length, gfp_t gfp_mask)
next prev parent reply other threads:[~2006-07-28 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 11:31 [PATCH 1/3] add netdev_alloc_skb Christoph Hellwig
2006-07-26 22:24 ` David Miller
2006-07-28 7:08 ` Christoph Hellwig [this message]
2006-07-28 8:24 ` David Miller
2006-07-28 8:27 ` Christoph Hellwig
2006-07-28 8:28 ` David Miller
2006-07-28 8:46 ` Christoph Hellwig
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=20060728070851.GB25174@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).