From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [patch] xen-netback: double free on unload Date: Mon, 24 Jun 2013 01:44:49 -0700 (PDT) Message-ID: <20130624.014449.788391647881401988.davem@davemloft.net> References: <20130621062008.GA10873@elgon.mountain> <20130624.002607.1816906327683052502.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: netdev-owner@vger.kernel.org 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 List-Id: xen-devel@lists.xenproject.org From: Julia Lawall Date: Mon, 24 Jun 2013 08:31:31 +0100 (BST) > On Mon, 24 Jun 2013, David Miller wrote: > >> From: Dan Carpenter >> 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 >> >> 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'.