From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, Ahmed Zaki <ahmed.zaki@intel.com>,
"Maciej Fijalkowski" <maciej.fijalkowski@intel.com>
Subject: Re: [PATCH iwl-next 0/2] iavf: make some functions static
Date: Wed, 14 Jun 2023 10:27:28 -0700 [thread overview]
Message-ID: <cb2b26e2-a716-eddd-c182-744437591d66@intel.com> (raw)
In-Reply-To: <20230613141253.57811-1-przemyslaw.kitszel@intel.com>
On 6/13/2023 7:12 AM, Przemek Kitszel wrote:
> Make static functions that are used in just one translation unit.
> Remove all unused and unexported functions.
This doesn't apply.
> Przemek Kitszel (2):
> iavf: remove some unused functions and pointless wrappers
> iavf: make functions static where possible
>
> drivers/net/ethernet/intel/iavf/iavf.h | 10 -----
> drivers/net/ethernet/intel/iavf/iavf_alloc.h | 3 +-
> drivers/net/ethernet/intel/iavf/iavf_common.c | 45 -------------------
> drivers/net/ethernet/intel/iavf/iavf_main.c | 34 ++++++--------
> drivers/net/ethernet/intel/iavf/iavf_osdep.h | 9 ----
> .../net/ethernet/intel/iavf/iavf_prototype.h | 5 ---
> drivers/net/ethernet/intel/iavf/iavf_txrx.c | 43 +++++++++---------
> drivers/net/ethernet/intel/iavf/iavf_txrx.h | 4 --
> 8 files changed, 35 insertions(+), 118 deletions(-)
>
next prev parent reply other threads:[~2023-06-14 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:12 [PATCH iwl-next 0/2] iavf: make some functions static Przemek Kitszel
2023-06-13 14:12 ` [PATCH iwl-next 1/2] iavf: remove some unused functions and pointless wrappers Przemek Kitszel
2023-06-13 14:12 ` [PATCH iwl-next 2/2] iavf: make functions static where possible Przemek Kitszel
2023-06-13 14:23 ` [Intel-wired-lan] " Paul Menzel
2023-06-14 17:27 ` Tony Nguyen [this message]
2023-06-15 9:53 ` [PATCH iwl-next 0/2] iavf: make some functions static Przemek Kitszel
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=cb2b26e2-a716-eddd-c182-744437591d66@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=ahmed.zaki@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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).