From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752751AbdFLSVB (ORCPT ); Mon, 12 Jun 2017 14:21:01 -0400 Received: from lelnx194.ext.ti.com ([198.47.27.80]:46286 "EHLO lelnx194.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752707AbdFLSU7 (ORCPT ); Mon, 12 Jun 2017 14:20:59 -0400 Subject: Re: [PATCH 1/2] hsr: fix coding style issues To: David Miller References: <1496701907-29376-1-git-send-email-m-karicheri2@ti.com> <20170606.160937.2113672006487973562.davem@davemloft.net> CC: , , From: Murali Karicheri Organization: Texas Instruments Message-ID: <593EDBA6.2080302@ti.com> Date: Mon, 12 Jun 2017 14:21:26 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20170606.160937.2113672006487973562.davem@davemloft.net> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/06/2017 04:09 PM, David Miller wrote: > > Please do not mix cleanups with legitimate bug fixes. Also, when posting > a multi-patch series, you must always provide an appropriate "[PATCH 0/N]" > header posting that describes what you series is doing at a high level, > how it is doing it, and why it is doing it that way. > > For this, submit the erroneous warning removal against 'net' as a single > patch. And then once that propagates into the 'net-next' tree you can > submit the coding style cleanups against 'net-next', thanks. > Thanks. Will do -- Murali Karicheri Linux Kernel, Keystone