All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next V5 2/2] intel: ixgbevf: Support Windows hosts (Hyper-V)
Date: Tue, 19 Apr 2016 23:24:42 -0700	[thread overview]
Message-ID: <1461133482.2923.28.camel@intel.com> (raw)
In-Reply-To: <1461118677-28142-2-git-send-email-kys@microsoft.com>

On Tue, 2016-04-19 at 19:17 -0700, K. Y. Srinivasan wrote:
> On Hyper-V, the VF/PF communication is a via software mediated path
> as opposed to the hardware mailbox. Make the necessary
> adjustments to support Hyper-V.
> 
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> ????????V2: Addressed most of the comments from
> ??????????? Alexander Duyck <alexander.duyck@gmail.com>
> ??????????? and Rustad, Mark D <mark.d.rustad@intel.com>.
> 
> ????????V3: Addressed additional comments from
> ??????????? Alexander Duyck <alexander.duyck@gmail.com>
> 
> ????????V4: Addressed kbuild errors reported by:
> ??????????? kbuild test robot <lkp@intel.com>
> 
> ????????V5: Addressed additional comments from
> ??????????? Alexander Duyck <alexander.duyck@gmail.com>

First I commend you on actually making a proper changelog for a patch.
?The only issue I have is that the changelog provides not actual
changes. ?Saying you reacted to comments does not summarize what the
actual changes were. ?I purposely did not review the earlier versions
because by the time I went to do a review, there was another version
already submitted. ?So your changelog requires that users look at all
the previous emails to actually see what Alex and Mark requested in
changes.

I am telling you this for future patches, it will not impact these
patches, just really disappointing. ?I will take the extra time to
track down all the previous emails and the changes requested to ensure
you made all the changes that were requested of you. :-( ?This will
just delay when I apply the patches for testing.

> 
> ?drivers/net/ethernet/intel/ixgbevf/ixgbevf.h????? |?? 12 ++
> ?drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c |?? 31 +++-
> ?drivers/net/ethernet/intel/ixgbevf/mbx.c????????? |?? 12 ++
> ?drivers/net/ethernet/intel/ixgbevf/vf.c?????????? |? 216
> +++++++++++++++++++++
> ?drivers/net/ethernet/intel/ixgbevf/vf.h?????????? |??? 2 +
> ?5 files changed, 266 insertions(+), 7 deletions(-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160419/f4665147/attachment.asc>

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>,
	davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com,
	eli@mellanox.com, jackm@mellanox.com, yevgenyp@mellanox.com,
	john.ronciak@intel.com, intel-wired-lan@lists.osuosl.org,
	alexander.duyck@gmail.com
Subject: Re: [Intel-wired-lan] [PATCH net-next V5 2/2] intel: ixgbevf: Support Windows hosts (Hyper-V)
Date: Tue, 19 Apr 2016 23:24:42 -0700	[thread overview]
Message-ID: <1461133482.2923.28.camel@intel.com> (raw)
In-Reply-To: <1461118677-28142-2-git-send-email-kys@microsoft.com>

[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]

On Tue, 2016-04-19 at 19:17 -0700, K. Y. Srinivasan wrote:
> On Hyper-V, the VF/PF communication is a via software mediated path
> as opposed to the hardware mailbox. Make the necessary
> adjustments to support Hyper-V.
> 
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
>         V2: Addressed most of the comments from
>             Alexander Duyck <alexander.duyck@gmail.com>
>             and Rustad, Mark D <mark.d.rustad@intel.com>.
> 
>         V3: Addressed additional comments from
>             Alexander Duyck <alexander.duyck@gmail.com>
> 
>         V4: Addressed kbuild errors reported by:
>             kbuild test robot <lkp@intel.com>
> 
>         V5: Addressed additional comments from
>             Alexander Duyck <alexander.duyck@gmail.com>

First I commend you on actually making a proper changelog for a patch.
 The only issue I have is that the changelog provides not actual
changes.  Saying you reacted to comments does not summarize what the
actual changes were.  I purposely did not review the earlier versions
because by the time I went to do a review, there was another version
already submitted.  So your changelog requires that users look at all
the previous emails to actually see what Alex and Mark requested in
changes.

I am telling you this for future patches, it will not impact these
patches, just really disappointing.  I will take the extra time to
track down all the previous emails and the changes requested to ensure
you made all the changes that were requested of you. :-(  This will
just delay when I apply the patches for testing.

> 
>  drivers/net/ethernet/intel/ixgbevf/ixgbevf.h      |   12 ++
>  drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c |   31 +++-
>  drivers/net/ethernet/intel/ixgbevf/mbx.c          |   12 ++
>  drivers/net/ethernet/intel/ixgbevf/vf.c           |  216
> +++++++++++++++++++++
>  drivers/net/ethernet/intel/ixgbevf/vf.h           |    2 +
>  5 files changed, 266 insertions(+), 7 deletions(-)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-04-20  6:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  2:17 [Intel-wired-lan] [PATCH net-next V5 0/2] ethernet: intel: Support Hyper-V hosts K. Y. Srinivasan
2016-04-20  2:17 ` K. Y. Srinivasan
2016-04-20  2:17 ` K. Y. Srinivasan
2016-04-20  2:17 ` [Intel-wired-lan] [PATCH net-next V5 1/2] ethernet: intel: Add the device ID's presented while running on Hyper-V K. Y. Srinivasan
2016-04-20  2:17   ` K. Y. Srinivasan
2016-04-20  2:17   ` K. Y. Srinivasan
2016-04-20  2:17   ` [Intel-wired-lan] [PATCH net-next V5 2/2] intel: ixgbevf: Support Windows hosts (Hyper-V) K. Y. Srinivasan
2016-04-20  2:17     ` K. Y. Srinivasan
2016-04-20  2:17     ` K. Y. Srinivasan
2016-04-20  6:24     ` Jeff Kirsher [this message]
2016-04-20  6:24       ` [Intel-wired-lan] " Jeff Kirsher
2016-04-20 13:44       ` KY Srinivasan
2016-04-20 13:44         ` KY Srinivasan
2016-04-22 19:32     ` Bowers, AndrewX
2016-04-27 18:33       ` KY Srinivasan
2016-04-27 20:50         ` Alexander Duyck
2016-04-27 22:02           ` KY Srinivasan
2016-05-02 21:37   ` [Intel-wired-lan] [PATCH net-next V5 1/2] ethernet: intel: Add the device ID's presented while running on Hyper-V Bowers, AndrewX

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=1461133482.2923.28.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=intel-wired-lan@osuosl.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.