From: Murali Karicheri <m-karicheri2@ti.com>
To: David Miller <davem@davemloft.net>
Cc: <arvid.brodin@alten.se>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] hsr: fix coding style issues
Date: Mon, 12 Jun 2017 14:21:26 -0400 [thread overview]
Message-ID: <593EDBA6.2080302@ti.com> (raw)
In-Reply-To: <20170606.160937.2113672006487973562.davem@davemloft.net>
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
prev parent reply other threads:[~2017-06-12 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 22:31 [PATCH 1/2] hsr: fix coding style issues Murali Karicheri
2017-06-05 22:31 ` [PATCH 2/2] hsr: fix incorrect warning Murali Karicheri
2017-06-06 20:09 ` [PATCH 1/2] hsr: fix coding style issues David Miller
2017-06-12 18:21 ` Murali Karicheri [this message]
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=593EDBA6.2080302@ti.com \
--to=m-karicheri2@ti.com \
--cc=arvid.brodin@alten.se \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.