Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Jan Sokolowski <jan.sokolowski@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 4/6] ice: refactor ice_vf_lib to make functions static
Date: Fri, 4 Aug 2023 14:08:35 -0700	[thread overview]
Message-ID: <ac611110-3a2a-6885-53e6-2c14a4063c1b@intel.com> (raw)
In-Reply-To: <131487ef-a94c-76f2-3bd8-531f77bbd7c3@intel.com>

On 8/1/2023 6:25 AM, Przemek Kitszel wrote:
> On 8/1/23 13:53, Jan Sokolowski wrote:
>> Refactor ice_vf_lib.c/_private.h in order to make as many methods
>> as possible static.
>>
>> Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com>
>> ---
>>   drivers/net/ethernet/intel/ice/ice_vf_lib.c   | 468 +++++++++---------
>>   .../ethernet/intel/ice/ice_vf_lib_private.h   |   2 -
>>   2 files changed, 234 insertions(+), 236 deletions(-)
> 
> I don't like such big code movement to achieve something that two 
> predeclarations would provide.

To me this is not different than the other patches/intent; this just 
happens to involve more lines. Seems arbitrary to allow the others but 
not this one. I'm ok with sending this on to see if netdev will accept. 
Based on comments, I believe v3 will include netdev so we'll get an idea 
if they are open to this change with the next revision.

> We could either just abandon idea of converting those two functions,
> or move predeclarations, augmented by "static" keyword, to ice_vf.lib.c
> 
> That would slightly violate "the style", but you will achieve SAME THING.
> 
> I have tried locally to see the diff size:
>   drivers/net/ethernet/intel/ice/ice_vf_lib.c         | 7 +++++--
>   drivers/net/ethernet/intel/ice/ice_vf_lib_private.h | 2 --
>   2 files changed, 5 insertions(+), 4 deletions(-)
> 
> -Przemek
> 
> [...half thousand lines snipped...]
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-08-04 21:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 11:53 [Intel-wired-lan] [PATCH iwl-next v2 0/6] ice: staticization refactor Jan Sokolowski
2023-08-01 11:53 ` [Intel-wired-lan] [PATCH iwl-next v2 1/6] ice: remove unused methods Jan Sokolowski
2023-08-01 11:53 ` [Intel-wired-lan] [PATCH iwl-next v2 2/6] ice: refactor ice_ddp to make functions static Jan Sokolowski
2023-08-01 14:05   ` kernel test robot
2023-08-01 11:53 ` [Intel-wired-lan] [PATCH iwl-next v2 3/6] ice: refactor ice_lib " Jan Sokolowski
2023-08-04 21:08   ` Tony Nguyen
2023-08-01 11:53 ` [Intel-wired-lan] [PATCH iwl-next v2 4/6] ice: refactor ice_vf_lib " Jan Sokolowski
2023-08-01 13:25   ` Przemek Kitszel
2023-08-04 21:08     ` Tony Nguyen [this message]
2023-08-01 11:53 ` [Intel-wired-lan] [PATCH iwl-next v2 5/6] ice: refactor ice_sched " Jan Sokolowski
2023-08-01 11:53 ` [Intel-wired-lan] [PATCH iwl-next v2 6/6] ice: refactor ice_ptp_hw " Jan Sokolowski
2023-08-01 12:26   ` 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=ac611110-3a2a-6885-53e6-2c14a4063c1b@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jan.sokolowski@intel.com \
    --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