From: David Miller <davem@davemloft.net>
To: julia.lawall@lip6.fr
Cc: dan.carpenter@oracle.com, ian.campbell@citrix.com,
xen-devel@lists.xensource.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] xen-netback: double free on unload
Date: Mon, 24 Jun 2013 01:44:49 -0700 (PDT) [thread overview]
Message-ID: <20130624.014449.788391647881401988.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1306240830580.2215@hadrien>
From: Julia Lawall <julia.lawall@lip6.fr>
Date: Mon, 24 Jun 2013 08:31:31 +0100 (BST)
> On Mon, 24 Jun 2013, David Miller wrote:
>
>> From: Dan Carpenter <dan.carpenter@oracle.com>
>> Date: Fri, 21 Jun 2013 09:20:08 +0300
>>
>> > There is a typo here, "i" vs "j", so we would crash on module_exit().
>> >
>> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>>
>> Please always explicitly state the tree for which a patch is
>> applicable.
>>
>> Here I figured it out by trial an error, trying to apply it
>> to 'net' (where it failed) and then 'net-next' (where it
>> applied cleanly).
>>
>> I should never have to play patch monkey games like that, you
>> need to tell me where a patch is targetted.
>
> Shouldn't one always, by default, work on linux-next?
Bug fixes, especially serious ones, should be targetted at 'net'.
next prev parent reply other threads:[~2013-06-24 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 6:20 [patch] xen-netback: double free on unload Dan Carpenter
2013-06-21 9:51 ` Wei Liu
2013-06-24 7:26 ` David Miller
2013-06-24 7:31 ` Julia Lawall
2013-06-24 8:44 ` David Miller [this message]
2013-06-24 8:57 ` Dan Carpenter
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=20130624.014449.788391647881401988.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dan.carpenter@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xensource.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).