From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH S30 1/9] ice: Introduce ice_base.c
Date: Tue, 15 Oct 2019 23:13:20 +0000 [thread overview]
Message-ID: <e308d8b7a26b46e1a8f2c8400623a6d9@intel.com> (raw)
In-Reply-To: <20191009140925.13997-1-anthony.l.nguyen@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Tony Nguyen
> Sent: Wednesday, October 9, 2019 7:09 AM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH S30 1/9] ice: Introduce ice_base.c
>
> From: Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
>
> Remove a few uses of kernel configuration flags from ice_lib.c by
> introducing a new source file ice_base.c. Also move corresponding
> function prototypes from ice_lib.h to ice_base.h and include ice_base.h
> where required.
>
> Signed-off-by: Anirudh Venkataramanan
> <anirudh.venkataramanan@intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
> drivers/net/ethernet/intel/ice/Makefile | 1 +
> drivers/net/ethernet/intel/ice/ice.h | 8 +
> drivers/net/ethernet/intel/ice/ice_base.c | 767 +++++++++++++++++
> drivers/net/ethernet/intel/ice/ice_base.h | 31 +
> drivers/net/ethernet/intel/ice/ice_dcb_lib.h | 1 +
> drivers/net/ethernet/intel/ice/ice_lib.c | 787 +-----------------
> drivers/net/ethernet/intel/ice/ice_lib.h | 39 -
> drivers/net/ethernet/intel/ice/ice_main.c | 1 +
> drivers/net/ethernet/intel/ice/ice_txrx.h | 2 -
> .../net/ethernet/intel/ice/ice_virtchnl_pf.c | 1 +
> 10 files changed, 811 insertions(+), 827 deletions(-)
> create mode 100644 drivers/net/ethernet/intel/ice/ice_base.c
> create mode 100644 drivers/net/ethernet/intel/ice/ice_base.h
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
prev parent reply other threads:[~2019-10-15 23:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 14:09 [Intel-wired-lan] [PATCH S30 1/9] ice: Introduce ice_base.c Tony Nguyen
2019-10-09 14:09 ` [Intel-wired-lan] [PATCH S30 2/9] ice: get rid of per-tc flow in Tx queue configuration routines Tony Nguyen
2019-10-15 18:18 ` Bowers, AndrewX
2019-10-15 23:13 ` Bowers, AndrewX
2019-10-09 14:09 ` [Intel-wired-lan] [PATCH S30 3/9] ice: Add support for XDP Tony Nguyen
2019-10-15 23:14 ` Bowers, AndrewX
2019-10-09 14:09 ` [Intel-wired-lan] [PATCH S30 4/9] ice: Move common functions to ice_txrx_lib.c Tony Nguyen
2019-10-15 23:14 ` Bowers, AndrewX
2019-10-09 14:09 ` [Intel-wired-lan] [PATCH S30 5/9] ice: Add support for AF_XDP Tony Nguyen
2019-10-15 23:15 ` Bowers, AndrewX
2019-10-09 14:09 ` [Intel-wired-lan] [PATCH S30 6/9] ice: introduce legacy rx flag Tony Nguyen
2019-10-15 23:15 ` Bowers, AndrewX
2019-10-09 14:09 ` [Intel-wired-lan] [PATCH S30 7/9] ice: introduce frame padding computation logic Tony Nguyen
2019-10-15 23:16 ` Bowers, AndrewX
2019-10-09 14:09 ` [Intel-wired-lan] [PATCH S30 8/9] ice: add build_skb() support Tony Nguyen
2019-10-15 23:16 ` Bowers, AndrewX
2019-10-09 14:09 ` [Intel-wired-lan] [PATCH S30 9/9] ice: allow 3k MTU for XDP Tony Nguyen
2019-10-15 23:17 ` Bowers, AndrewX
2019-10-15 23:13 ` Bowers, AndrewX [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=e308d8b7a26b46e1a8f2c8400623a6d9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox