From: David Miller <davem@davemloft.net>
To: rvatsavayi@caviumnetworks.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 00/18] liquidio support for new device cn23xx
Date: Wed, 03 Aug 2016 15:05:04 -0700 (PDT) [thread overview]
Message-ID: <20160803.150504.2220219685584839824.davem@davemloft.net> (raw)
In-Reply-To: <1470250549-10993-1-git-send-email-rvatsavayi@caviumnetworks.com>
From: Raghu Vatsavayi <rvatsavayi@caviumnetworks.com>
Date: Wed, 3 Aug 2016 11:55:31 -0700
> Please consider following patches for support of new device
> CN23XX in liquidio family of adapters. Patches may have to
> be applied in following order as some of the patches depend
> on earlier patches.
You can't have the same Subject line text for every patch in the
series.
It is required that you use unique subject lines so that someone
scanning the shortlog can see what is unique in each of these patches.
And don't try to thward this by saying something like:
liquidio support for new device cn23xx part 1
Really describe in words what each change is uniquely doing.
prev parent reply other threads:[~2016-08-03 22:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 18:55 [PATCH net-next 00/18] liquidio support for new device cn23xx Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 01/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 02/18] " Raghu Vatsavayi
2016-08-04 18:12 ` Yuval Mintz
2016-08-03 18:55 ` [PATCH net-next 03/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 04/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 05/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 06/18] " Raghu Vatsavayi
2016-08-04 0:13 ` kbuild test robot
2016-08-03 18:55 ` [PATCH net-next 07/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 08/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 09/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 10/18] " Raghu Vatsavayi
2016-08-04 17:07 ` Yuval Mintz
2016-08-03 18:55 ` [PATCH net-next 11/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 12/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 13/18] " Raghu Vatsavayi
2016-08-04 16:04 ` Yuval Mintz
2016-08-03 18:55 ` [PATCH net-next 14/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 15/18] " Raghu Vatsavayi
2016-08-03 22:54 ` kbuild test robot
2016-08-03 23:15 ` kbuild test robot
2016-08-03 18:55 ` [PATCH net-next 16/18] " Raghu Vatsavayi
2016-08-04 5:58 ` kbuild test robot
2016-08-03 18:55 ` [PATCH net-next 17/18] " Raghu Vatsavayi
2016-08-03 18:55 ` [PATCH net-next 18/18] " Raghu Vatsavayi
2016-08-03 20:51 ` [PATCH net-next 00/18] " David Daney
2016-08-03 22:05 ` David Miller [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=20160803.150504.2220219685584839824.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rvatsavayi@caviumnetworks.com \
/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).