From: Jacob Keller <jacob.e.keller@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3 0/7] ice: staticization refactor
Date: Wed, 9 Aug 2023 10:29:00 -0700 [thread overview]
Message-ID: <eaca8a6c-2787-ecea-3d72-2c965a9a8b7f@intel.com> (raw)
In-Reply-To: <20230809133913.2652736-1-jan.sokolowski@intel.com>
On 8/9/2023 6:39 AM, Jan Sokolowski wrote:
> ice: refactor methods to make them static
>
> This series of patches refactor some ice driver files
> in order to make as many methods as possible static.
> One additional patch introduced in v3 also refactors
> one method that can be simplified thanks to being
> static.
>
> Also there's a minor cleanup of unused methods.
>
> Jan Sokolowski (7):
> ice: remove unused methods
> ice: refactor ice_ddp to make functions static
> ice: refactor ice_lib to make functions static
> ice: refactor ice_vf_lib to make functions static
> ice: refactor ice_sched to make functions static
> ice: refactor ice_ptp_hw to make functions static
> ice: refactor ice_vsi_is_vlan_pruning_ena
>
I read through this and it all seems reasonable. Some of the code in
ice_vf_lib.c used to be called from other files but later refactors have
since eliminated those calls.
Additionally the read PHY register functions in ice_ptp_hw.c also were
previously called in other files but no longer.
Thanks for the cleanup.
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> drivers/net/ethernet/intel/ice/ice_ddp.c | 120 ++---
> drivers/net/ethernet/intel/ice/ice_ddp.h | 10 -
> drivers/net/ethernet/intel/ice/ice_lib.c | 82 ++-
> drivers/net/ethernet/intel/ice/ice_lib.h | 5 -
> drivers/net/ethernet/intel/ice/ice_ptp_hw.c | 25 +-
> drivers/net/ethernet/intel/ice/ice_ptp_hw.h | 4 -
> drivers/net/ethernet/intel/ice/ice_sched.c | 2 +-
> drivers/net/ethernet/intel/ice/ice_sched.h | 4 -
> drivers/net/ethernet/intel/ice/ice_switch.c | 48 --
> drivers/net/ethernet/intel/ice/ice_switch.h | 1 -
> drivers/net/ethernet/intel/ice/ice_vf_lib.c | 468 +++++++++---------
> .../ethernet/intel/ice/ice_vf_lib_private.h | 2 -
> 12 files changed, 331 insertions(+), 440 deletions(-)
>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-08-09 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:39 [Intel-wired-lan] [PATCH iwl-next v3 0/7] ice: staticization refactor Jan Sokolowski
2023-08-09 13:39 ` [Intel-wired-lan] [PATCH iwl-next v3 1/7] ice: remove unused methods Jan Sokolowski
2023-08-09 13:39 ` [Intel-wired-lan] [PATCH iwl-next v3 2/7] ice: refactor ice_ddp to make functions static Jan Sokolowski
2023-08-09 13:39 ` [Intel-wired-lan] [PATCH iwl-next v3 3/7] ice: refactor ice_lib " Jan Sokolowski
2023-08-09 13:39 ` [Intel-wired-lan] [PATCH iwl-next v3 4/7] ice: refactor ice_vf_lib " Jan Sokolowski
2023-08-09 13:39 ` [Intel-wired-lan] [PATCH iwl-next v3 5/7] ice: refactor ice_sched " Jan Sokolowski
2023-08-09 13:39 ` [Intel-wired-lan] [PATCH iwl-next v3 6/7] ice: refactor ice_ptp_hw " Jan Sokolowski
2023-08-09 13:39 ` [Intel-wired-lan] [PATCH iwl-next v3 7/7] ice: refactor ice_vsi_is_vlan_pruning_ena Jan Sokolowski
2023-08-09 17:29 ` Jacob Keller [this message]
2023-08-10 11:11 ` [Intel-wired-lan] [PATCH iwl-next v3 0/7] ice: staticization refactor 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=eaca8a6c-2787-ecea-3d72-2c965a9a8b7f@intel.com \
--to=jacob.e.keller@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