From: David Miller <davem@davemloft.net>
To: skhare@vmware.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pv-drivers@vmware.com
Subject: Re: [PATCH net-next v3 0/7] vmxnet3: upgrade to version 3
Date: Wed, 15 Jun 2016 00:23:52 -0700 (PDT) [thread overview]
Message-ID: <20160615.002352.1381014639121724661.davem@davemloft.net> (raw)
In-Reply-To: <1465869007-10822-1-git-send-email-skhare@vmware.com>
From: Shrikrishna Khare <skhare@vmware.com>
Date: Mon, 13 Jun 2016 18:50:00 -0700
> This patchset upgrades vmxnet3 to version 3.
As stated by others, it is completely unacceptable to post so many
patches with little or no commit log message.
You must describe, in full detail, what each and every patch does, why
it is doing so, and how it is doing it.
prev parent reply other threads:[~2016-06-15 7:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 1:50 [PATCH net-next v3 0/7] vmxnet3: upgrade to version 3 Shrikrishna Khare
2016-06-14 1:50 ` [PATCH net-next v3 1/7] vmxnet3: prepare for version 3 changes Shrikrishna Khare
2016-06-14 1:50 ` [PATCH net-next v3 2/7] vmxnet3: introduce generic command interface to configure the device Shrikrishna Khare
2016-06-14 1:50 ` [PATCH net-next v3 3/7] vmxnet3: allow variable length transmit data ring buffer Shrikrishna Khare
2016-06-14 1:50 ` [PATCH net-next v3 4/7] vmxnet3: add receive data ring support Shrikrishna Khare
2016-06-14 1:50 ` [PATCH net-next v3 5/7] vmxnet3: add support for get_coalesce, set_coalesce ethtool operations Shrikrishna Khare
2016-06-14 15:04 ` Ben Hutchings
2016-06-14 1:50 ` [PATCH net-next v3 6/7] vmxnet3: introduce command to register memory region Shrikrishna Khare
2016-06-14 5:54 ` Or Gerlitz
2016-06-14 1:50 ` [PATCH net-next v3 7/7] vmxnet3: update to version 3 Shrikrishna Khare
2016-06-14 5:52 ` [PATCH net-next v3 0/7] vmxnet3: upgrade " Or Gerlitz
2016-06-15 7:23 ` 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=20160615.002352.1381014639121724661.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=skhare@vmware.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).