From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AB9B7C282CA for ; Mon, 28 Jan 2019 02:04:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 73A7620880 for ; Mon, 28 Jan 2019 02:04:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="BD1Z9PZi" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726585AbfA1CDx (ORCPT ); Sun, 27 Jan 2019 21:03:53 -0500 Received: from vps0.lunn.ch ([185.16.172.187]:56828 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726517AbfA1CDx (ORCPT ); Sun, 27 Jan 2019 21:03:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=UxPRcgp3DGqCi8fSQ4dxTy4I4uVhttX3cD42Z85rIW0=; b=BD1Z9PZiRdyJUcV941H4gtgE/I 324hWPW4N9yjYg10t6NnR/GGymM0UrYUM2kyLRo8DXugV4KL/8h96n5Ven8+Zp7T2rMd+tRbJXlEf D33BnokwzBTRgCfSMoX1qGR0F79LvK7/sQsy5YlRNAKSomDP1NwSCj+3FWG9m24tE0fA=; Received: from andrew by vps0.lunn.ch with local (Exim 4.89) (envelope-from ) id 1gnwGy-0002Rc-5C; Mon, 28 Jan 2019 03:03:40 +0100 Date: Mon, 28 Jan 2019 03:03:40 +0100 From: Andrew Lunn To: yang.wei9@zte.com.cn Cc: albin_yang@163.com, netdev@vger.kernel.org, davem@davemloft.net Subject: Re: [PATCH V2] net: i825xx: replace dev_kfree_skb_irq bydev_consume_skb_irq Message-ID: <20190128020340.GC4765@lunn.ch> References: <20190127163419.GA28088@lunn.ch> <201901280950423897221@zte.com.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201901280950423897221@zte.com.cn> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Jan 28, 2019 at 09:50:42AM +0800, yang.wei9@zte.com.cn wrote: > > It is normal to include here, under the ---, what has changed since > > the previous version of the patch. > > > > Please also read > > > > https://www.kernel.org/doc/html/latest/networking/netdev-FAQ.html > > > > Your patches don't have the correct subject. > > Hi Andrew > > The previous patch (as follow) is wrong, so I submit a new and named V2. > Please reject the previous patch. > > net: i825xx: replace dev_kfree_skb_irq by dev_consume_skb_irq > http://patchwork.ozlabs.org/patch/1031590/ > > The original suject in patch is as follow, but it be truncated due to return character. > I have changed it, make the suject in one line. Do I need to resubmit it? https://www.kernel.org/doc/html/latest/networking/netdev-FAQ.html#q-how-do-i-indicate-which-tree-net-vs-net-next-my-patch-should-be-in Andrew