From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] ieee802154: merge cleanup
Date: Mon, 30 Nov 2009 21:55:01 -0800 (PST) [thread overview]
Message-ID: <20091130.215501.267396660.davem@davemloft.net> (raw)
In-Reply-To: <4B149498.4030307@gmail.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 01 Dec 2009 04:59:20 +0100
> A small cleanup after last net-2.6 merge into net-next-2.6
>
> As we are going to free skb, no need to set skb->skb_iif or skb->dev
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
-ECORRUPTEDPATCH
Are you really sure you want to keep using Thunderbird for
your email? :-)
next prev parent reply other threads:[~2009-12-01 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091130.010520.56312368.davem@davemloft.net>
2009-12-01 3:59 ` [PATCH net-next-2.6] ieee802154: merge cleanup Eric Dumazet
2009-12-01 5:55 ` David Miller [this message]
2009-12-01 6:05 ` Eric Dumazet
2009-12-02 9:13 ` 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=20091130.215501.267396660.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.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).