From: Simon Horman <horms@kernel.org>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, magnus.karlsson@intel.com,
jesse.brandeburg@intel.com
Subject: Re: [PATCH iwl-next] i40e: avoid forward declarations in i40e_nvm.c
Date: Tue, 26 Mar 2024 13:58:39 +0000 [thread overview]
Message-ID: <20240326135839.GT403975@kernel.org> (raw)
In-Reply-To: <20240306163054.90627-1-maciej.fijalkowski@intel.com>
On Wed, Mar 06, 2024 at 05:30:54PM +0100, Maciej Fijalkowski wrote:
> Move code around to get rid of forward declarations. No functional
> changes.
>
> After a plain code juggling, checkpatch reported:
> total: 0 errors, 7 warnings, 12 checks, 1581 lines checked
>
> so while at it let's address old issues as well. Should we ever address
> the remaining unnecessary forward declarations within
> drivers/net/ethernet/intel/, consider this change as a starting
> point/reference.
>
> As reported in [0], there would be a lot more of work to do...if we
> care.
>
> [0]: https://lore.kernel.org/intel-wired-lan/Zeh8qadiTGf413YU@boxer/T/#u
> Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e_nvm.c | 1050 ++++++++++----------
> 1 file changed, 509 insertions(+), 541 deletions(-)
Thanks Maciej,
FWIIW, it might have been easier to review if this had been broken up.
But I appreciate that is a lot more work, and perhaps it wouldn't
have been easier to review anyway.
In any case, I did find time to work through this and I agree that
the patch matches it's description. And is a positive step IMHO.
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2024-03-26 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 16:30 [PATCH iwl-next] i40e: avoid forward declarations in i40e_nvm.c Maciej Fijalkowski
2024-03-12 15:20 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-03-26 13:58 ` Simon Horman [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=20240326135839.GT403975@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).