From: Amit Ghadge <amitg.b14@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] net: Fix coding style warnings and errors.
Date: Tue, 17 May 2016 23:55:35 +0530 [thread overview]
Message-ID: <20160517182439.GA10709@localhost.localdomain> (raw)
In-Reply-To: <20160517.140152.2072218978327713532.davem@davemloft.net>
On Tue, May 17, 2016 at 02:01:52PM -0400, David Miller wrote:
>
> Whenever you have to make changes to a patch within a series, you must always
> resubmit the entire series, not just the one that need changes.
You want say submit patch with version series v1, v2 or patches series?
If that is patches series, the first patch maintainer is different.
Should I resend this patch without patch series.
Thanks,
Amit G
prev parent reply other threads:[~2016-05-17 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 17:53 [PATCH v2 2/2] net: Fix coding style warnings and errors Amit Ghadge
2016-05-17 18:01 ` David Miller
2016-05-17 18:25 ` Amit Ghadge [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=20160517182439.GA10709@localhost.localdomain \
--to=amitg.b14@gmail.com \
--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 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).