From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dan Carpenter <error27@gmail.com>
Cc: "Shirley Ma" <xma@us.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] skbuff: use kfree_skb() instead of kfree()
Date: Wed, 20 Jul 2011 10:21:24 +0200 [thread overview]
Message-ID: <1311150084.2338.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <20110720080109.GH6445@shale.localdomain>
Le mercredi 20 juillet 2011 à 11:01 +0300, Dan Carpenter a écrit :
> On Wed, Jul 20, 2011 at 09:42:03AM +0200, Eric Dumazet wrote:
> > Le mercredi 20 juillet 2011 à 10:25 +0300, Dan Carpenter a écrit :
> > > Crap. Sorry, I shouldn't have sent that. We shouldn't return the
> > > freed "n" here. I'll send a v2 shortly.
> >
> > Also, dont forget to say its a patch for net-next-2.6
>
> If you're using linux-next, is there a way to tell which tree a
> patch came from? Obviously in this case it's core networking, but
> in other cases how does that work?
In this particular case, David will know for sure since patch is very
recent, but I wanted to make a general advice.
Keep in mind David has to review dozens of patches _per_ day, so netdev
related patches need some extra cooperation from submitters to help the
maintainer.
This extra cooperation means to test the patch on either net-next-2.6 or
net-2.6 tree ;)
next prev parent reply other threads:[~2011-07-20 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 7:23 [patch] skbuff: use kfree_skb() instead of kfree() Dan Carpenter
2011-07-20 7:25 ` Dan Carpenter
2011-07-20 7:42 ` Eric Dumazet
2011-07-20 8:01 ` Dan Carpenter
2011-07-20 8:21 ` Eric Dumazet [this message]
2011-07-20 8:37 ` Julia Lawall
2011-07-20 21:03 ` Julie Sullivan
2011-07-20 8:51 ` [patch net-next-2.6 v2] skbuff: fix error handling in pskb_copy() Dan Carpenter
2011-07-20 8:59 ` Eric Dumazet
2011-07-21 21:48 ` 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=1311150084.2338.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=xma@us.ibm.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