From: David Miller <davem@davemloft.net>
To: krkumar2@in.ibm.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] Remove unused function - skb_frag_add_head
Date: Fri, 15 Jan 2010 00:40:05 -0800 (PST) [thread overview]
Message-ID: <20100115.004005.128351897.davem@davemloft.net> (raw)
In-Reply-To: <20100115053205.31534.85551.sendpatchset@krkumar2.in.ibm.com>
From: Krishna Kumar <krkumar2@in.ibm.com>
Date: Fri, 15 Jan 2010 11:02:05 +0530
> From: Krishna Kumar <krkumar2@in.ibm.com>
>
> Remove unused function - skb_frag_add_head
>
> Signed-off-by: Krishna Kumar <krkumar2@in.ibm.com>
It rounds out the abstractions for accessing the fragment list.
All uses of the frag list need to be converted to these things
so that we can finally change sk_buff to use struct list_head
instead of a by-hand linked list.
So I'm not applying this.
prev parent reply other threads:[~2010-01-15 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 5:32 [PATCH] Remove unused function - skb_frag_add_head Krishna Kumar
2010-01-15 8:40 ` David Miller [this message]
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=20100115.004005.128351897.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=krkumar2@in.ibm.com \
--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).