From: Mathias Krause <mathias.krause@secunet.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] net: move pskb_put() to core code
Date: Wed, 06 Nov 2013 10:01:11 +0100 [thread overview]
Message-ID: <527A0557.2060707@secunet.com> (raw)
In-Reply-To: <1383676424.2868.11.camel@bwh-desktop.uk.level5networks.com>
On 05.11.2013 19:33, Ben Hutchings wrote:
> On Tue, 2013-11-05 at 14:54 +0100, Mathias Krause wrote:
>> This function has usage beside IPsec so move it to the core skbuff code.
>> While doing so, give it some documentation and change its return type to
>> 'unsigned char *' to be in line with skb_put().
> [...]
>> --- a/net/core/skbuff.c
>> +++ b/net/core/skbuff.c
>> @@ -1257,6 +1257,29 @@ free_skb:
>> EXPORT_SYMBOL(skb_pad);
>>
>> /**
>> + * pskb_put - add data to the tail of a potentially fragmented buffer
>> + * @skb: start of the buffer to use
>> + * @tail: tail fragment of the buffer to use
>> + * @len: amount of data to add
>> + *
>> + * This function extends the used data area of the potentially
>> + * fragmented buffer. &tail must be the last fragment of &skb -- or
>> + * &skb itself. If this would exceed the total buffer size the kernel
>
> Keep using @ to refer to the parameters in this description.
>
> Ben.
Thanks Ben. Looks like I looked at the wrong examples on how to do it.
Will fix those as well.
>
>> + * will panic. A pointer to the first byte of the extra data is
>> + * returned.
>> + */
> [...]
>
next prev parent reply other threads:[~2013-11-06 9:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 13:54 [PATCH net-next 0/3] IPsec improvements Mathias Krause
2013-11-05 13:54 ` [PATCH net-next 1/3] net: move pskb_put() to core code Mathias Krause
2013-11-05 18:33 ` Ben Hutchings
2013-11-06 9:01 ` Mathias Krause [this message]
2013-11-05 13:54 ` [PATCH net-next 2/3] caif: use pskb_put() instead of reimplementing its functionality Mathias Krause
2013-11-05 13:54 ` [PATCH net-next 3/3] net: allow to leave the buffer fragmented in skb_cow_data() Mathias Krause
2013-11-05 14:33 ` Eric Dumazet
2013-11-05 14:43 ` Mathias Krause
2013-11-06 9:30 ` Herbert Xu
2013-11-06 9:49 ` Mathias Krause
2013-11-06 9:52 ` Herbert Xu
2013-11-06 12:42 ` Mathias Krause
2013-11-06 12:48 ` Herbert Xu
2013-11-06 16:39 ` Eric Dumazet
2013-11-07 8:56 ` Mathias Krause
2013-11-07 8:55 ` Mathias Krause
2013-11-07 9:01 ` Herbert Xu
2013-11-07 10:01 ` Mathias Krause
2013-11-06 4:48 ` [PATCH net-next 0/3] IPsec improvements David Miller
2013-11-06 9:02 ` Mathias Krause
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=527A0557.2060707@secunet.com \
--to=mathias.krause@secunet.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=dmitry.tarnyagin@lockless.no \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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).