Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v3 00/14] i40e/i40evf: AVF series
Date: Thu, 11 May 2017 11:27:49 -0700	[thread overview]
Message-ID: <20170511112749.00000e65@intel.com> (raw)
In-Reply-To: <20170511182321.147850-1-jesse.brandeburg@intel.com>

On Thu, 11 May 2017 11:23:07 -0700
Jesse Brandeburg <jesse.brandeburg@intel.com> wrote:
> v3: updated patch 4 to remove some unnecessary transforms to client
>     interface files, also had to update patch 9 to remove unused
>     I40E_QUEUE_ defines

Sorry for having to send a v3, we found a couple more issues with
changes that were not necessary related to client interface.

      parent reply	other threads:[~2017-05-11 18:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 18:23 [Intel-wired-lan] [PATCH net-next v3 00/14] i40e/i40evf: AVF series Jesse Brandeburg
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 01/14] i40evf: drop i40e_type.h include Jesse Brandeburg
2017-05-12 17:55   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 02/14] i40e/i40evf: create and use new unified header file Jesse Brandeburg
2017-05-12 17:56   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 03/14] i40e: use new unified virtchnl " Jesse Brandeburg
2017-05-12 17:57   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 04/14] virtchnl: rename i40e to generic virtchnl Jesse Brandeburg
2017-05-12 18:05   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 05/14] virtchnl: move some code to core driver Jesse Brandeburg
2017-05-12 17:57   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 06/14] virtchnl: convert to new macros Jesse Brandeburg
2017-05-12 17:58   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 07/14] i40e/virtchnl: refactor code for validate checks Jesse Brandeburg
2017-05-12 18:05   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 08/14] i40evf/virtchnl: whitespace cleanups Jesse Brandeburg
2017-05-12 17:59   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 09/14] virtchnl: finish conversion to virtchnl interface Jesse Brandeburg
2017-05-12 17:59   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 10/14] i40e/virtchnl: move function to virtchnl Jesse Brandeburg
2017-05-12 18:00   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 11/14] virtchnl: Add pad fields to a couple of structures Jesse Brandeburg
2017-05-12 18:00   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 12/14] virtchnl: Add compile time static asserts to validate structure sizes Jesse Brandeburg
2017-05-12 18:01   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 13/14] i40evf: Add support for Adaptive Virtual Function Jesse Brandeburg
2017-05-12 18:01   ` Bowers, AndrewX
2017-05-11 18:23 ` [Intel-wired-lan] [PATCH net-next v3 14/14] i40evf: update i40evf.txt with new content Jesse Brandeburg
2017-05-12 18:02   ` Bowers, AndrewX
2017-05-11 18:27 ` Jesse Brandeburg [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=20170511112749.00000e65@intel.com \
    --to=jesse.brandeburg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox