From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH S4 iavf 2/9] iavf: change iavf_status_code to iavf_status
Date: Thu, 2 May 2019 21:44:30 +0000 [thread overview]
Message-ID: <26D9FDECA4FBDD4AADA65D8E2FC68A4A1D39C47E@ORSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <20190417221737.11460-2-alice.michael@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Alice Michael
> Sent: Wednesday, April 17, 2019 3:18 PM
> To: Michael, Alice <alice.michael@intel.com>; intel-wired-
> lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [next PATCH S4 iavf 2/9] iavf: change
> iavf_status_code to iavf_status
>
> From: Sergey Nemov <sergey.nemov@intel.com>
>
> Instead of typedefing the enum iavf_status_code with iavf_status, just
> shorten the enum itself and get rid of typedef.
>
> Signed-off-by: Sergey Nemov <sergey.nemov@intel.com>
> ---
> drivers/net/ethernet/intel/iavf/iavf.h | 2 +-
> drivers/net/ethernet/intel/iavf/iavf_adminq.c | 67 ++++++++++---------
> drivers/net/ethernet/intel/iavf/iavf_alloc.h | 17 +++--
> drivers/net/ethernet/intel/iavf/iavf_client.c | 6 +-
> drivers/net/ethernet/intel/iavf/iavf_common.c | 53 ++++++++-------
> drivers/net/ethernet/intel/iavf/iavf_main.c | 20 +++---
> drivers/net/ethernet/intel/iavf/iavf_osdep.h | 1 -
> .../net/ethernet/intel/iavf/iavf_prototype.h | 52 +++++++-------
> drivers/net/ethernet/intel/iavf/iavf_status.h | 2 +-
> .../net/ethernet/intel/iavf/iavf_virtchnl.c | 14 ++--
> 10 files changed, 121 insertions(+), 113 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
next prev parent reply other threads:[~2019-05-02 21:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 22:17 [Intel-wired-lan] [next PATCH S4 iavf 1/9] iavf: Rename i40e_adminq* files to iavf_adminq* Alice Michael
2019-04-17 22:17 ` [Intel-wired-lan] [next PATCH S4 iavf 2/9] iavf: change iavf_status_code to iavf_status Alice Michael
2019-05-02 21:44 ` Bowers, AndrewX [this message]
2019-04-17 22:17 ` [Intel-wired-lan] [next PATCH S4 iavf 3/9] iavf: rename i40e functions to be iavf Alice Michael
2019-05-02 21:44 ` Bowers, AndrewX
2019-04-17 22:17 ` [Intel-wired-lan] [next PATCH S4 iavf 4/9] iavf: replace i40e variables with iavf Alice Michael
2019-05-02 21:45 ` Bowers, AndrewX
2019-04-17 22:17 ` [Intel-wired-lan] [next PATCH S4 iavf 5/9] iavf: rename iavf_status structure flags Alice Michael
2019-05-02 21:45 ` Bowers, AndrewX
2019-04-17 22:17 ` [Intel-wired-lan] [next PATCH S4 iavf 6/9] iavf: rename iavf_client.h defines to match driver name Alice Michael
2019-05-02 21:46 ` Bowers, AndrewX
2019-04-17 22:17 ` [Intel-wired-lan] [next PATCH S4 iavf 7/9] iavf: change remaining i40e defines to be iavf Alice Michael
2019-05-02 21:46 ` Bowers, AndrewX
2019-04-17 22:17 ` [Intel-wired-lan] [next PATCH S4 iavf 8/9] iavf: rename i40e_device to iavf_device Alice Michael
2019-05-02 21:47 ` Bowers, AndrewX
2019-04-17 22:17 ` [Intel-wired-lan] [next PATCH S4 iavf 9/9] iavf: update comments and file checks to match iavf Alice Michael
2019-05-02 21:47 ` Bowers, AndrewX
2019-05-02 21:44 ` [Intel-wired-lan] [next PATCH S4 iavf 1/9] iavf: Rename i40e_adminq* files to iavf_adminq* 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=26D9FDECA4FBDD4AADA65D8E2FC68A4A1D39C47E@ORSMSX106.amr.corp.intel.com \
--to=andrewx.bowers@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.