From: Simon Horman <simon.horman@corigine.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Subject: Re: [PATCH net-next 3/3] iavf: make functions static where possible
Date: Fri, 23 Jun 2023 09:42:01 +0200 [thread overview]
Message-ID: <ZJVMyQYRCTMhsnrq@corigine.com> (raw)
In-Reply-To: <20230622165914.2203081-4-anthony.l.nguyen@intel.com>
On Thu, Jun 22, 2023 at 09:59:14AM -0700, Tony Nguyen wrote:
> From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
>
> Make all possible functions static.
>
> Move iavf_force_wb() up to avoid forward declaration.
>
> Suggested-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> Signed-off-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-06-23 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 16:59 [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-06-22 (iavf) Tony Nguyen
2023-06-22 16:59 ` [PATCH net-next 1/3] iavf: fix err handling for MAC replace Tony Nguyen
2023-06-23 7:41 ` Simon Horman
2023-06-22 16:59 ` [PATCH net-next 2/3] iavf: remove some unused functions and pointless wrappers Tony Nguyen
2023-06-23 7:41 ` Simon Horman
2023-06-22 16:59 ` [PATCH net-next 3/3] iavf: make functions static where possible Tony Nguyen
2023-06-23 7:42 ` Simon Horman [this message]
2023-06-24 22:20 ` [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-06-22 (iavf) patchwork-bot+netdevbpf
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=ZJVMyQYRCTMhsnrq@corigine.com \
--to=simon.horman@corigine.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).